The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation

(itstool) path: sect1/programlisting
English
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30-107
VertRefresh 48-120
EndSection
Context English Persian State
In <application>GNOME</application>, this can also be found in the <guimenuitem>System</guimenuitem>, <guimenuitem>Preferences</guimenuitem> menu.
If you have selected <quote>gconf support</quote> during the build, you will also be able to view these settings using <command>gconf-editor</command> under <literal>apps/compiz</literal>.
If the mouse does not work, you will need to first configure it before proceeding. In recent <application>Xorg</application> versions, the <literal>InputDevice</literal> sections in <filename>xorg.conf</filename> are ignored in favor of the autodetected devices. To restore the old behavior, add the following line to the <literal>ServerLayout</literal> or <literal>ServerFlags</literal> section of this file:
Option "AutoAddDevices" "false"
Input devices may then be configured as in previous versions, along with any other options needed (e.g., keyboard layout switching).
As previously explained the <application>hald</application> daemon will, by default, automatically detect your keyboard. There are chances that your keyboard layout or model will not be correct, desktop environments like <application>GNOME</application>, <application>KDE</application> or <application>Xfce</application> provide tools to configure the keyboard. However, it is possible to set the keyboard properties directly either with the help of the <citerefentry vendor="xorg"><refentrytitle>setxkbmap</refentrytitle><manvolnum>1</manvolnum></citerefentry> utility or with a <application>hald</application>'s configuration rule.
For example if, one wants to use a PC 102 keys keyboard coming with a french layout, we have to create a keyboard configuration file for <application>hald</application> called <filename>x11-input.fdi</filename> and saved in the <filename>/usr/local/etc/hal/fdi/policy</filename> directory. This file should contain the following lines:
&lt;?xml version="1.0" encoding="iso-8859-1"?&gt;
&lt;deviceinfo version="0.2"&gt;
&lt;device&gt;
&lt;match key="info.capabilities" contains="input.keyboard"&gt;
&lt;merge key="input.x11_options.XkbModel" type="string"&gt;pc102&lt;/merge&gt;
&lt;merge key="input.x11_options.XkbLayout" type="string"&gt;fr&lt;/merge&gt;
&lt;/match&gt;
&lt;/device&gt;
&lt;/deviceinfo&gt;
If this file already exists, just copy and add to your file the lines regarding the keyboard configuration.
You will have to reboot your machine to force <application>hald</application> to read this file.
It is possible to do the same configuration from an X terminal or a script with this command line:
<prompt>%</prompt> <userinput>setxkbmap -model pc102 -layout fr</userinput>
<filename>/usr/local/share/X11/xkb/rules/base.lst</filename> lists the various keyboard, layouts and options available.
<primary><application>Xorg</application> tuning</primary>
The <filename>xorg.conf.new</filename> configuration file may now be tuned to taste. Open the file in a text editor such as <citerefentry vendor="ports"><refentrytitle>emacs</refentrytitle><manvolnum>1</manvolnum></citerefentry> or <citerefentry><refentrytitle>ee</refentrytitle><manvolnum>1</manvolnum></citerefentry>. If the monitor is an older or unusual model that does not support autodetection of sync frequencies, those settings can be added to <filename>xorg.conf.new</filename> under the <literal>"Monitor"</literal> section:
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30-107
VertRefresh 48-120
EndSection
Most monitors support sync frequency autodetection, making manual entry of these values unnecessary. For the few monitors that do not support autodetection, avoid potential damage by only entering values provided by the manufacturer.
X allows DPMS (Energy Star) features to be used with capable monitors. The <citerefentry vendor="xfree86"><refentrytitle>xset</refentrytitle><manvolnum>1</manvolnum></citerefentry> program controls the time-outs and can force standby, suspend, or off modes. If you wish to enable DPMS features for your monitor, you must add the following line to the monitor section:
Option "DPMS"
<primary><filename>xorg.conf</filename></primary>
While the <filename>xorg.conf.new</filename> configuration file is still open in an editor, select the default resolution and color depth desired. This is defined in the <literal>"Screen"</literal> section:
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768"
EndSubSection
EndSection
The <literal>DefaultDepth</literal> keyword describes the color depth to run at by default. This can be overridden with the <option>-depth</option> command line switch to <citerefentry vendor="xorg"><refentrytitle>Xorg</refentrytitle><manvolnum>1</manvolnum></citerefentry>. The <literal>Modes</literal> keyword describes the resolution to run at for the given color depth. Note that only VESA standard modes are supported as defined by the target system's graphics hardware. In the example above, the default color depth is twenty-four bits per pixel. At this color depth, the accepted resolution is 1024 by 768 pixels.
Finally, write the configuration file and test it using the test mode given above.
One of the tools available to assist you during troubleshooting process are the <application>Xorg</application> log files, which contain information on each device that the <application>Xorg</application> server attaches to. <application>Xorg</application> log file names are in the format of <filename>/var/log/Xorg.0.log</filename>. The exact name of the log can vary from <filename>Xorg.0.log</filename> to <filename>Xorg.8.log</filename> and so forth.
If all is well, the configuration file needs to be installed in a common location where <citerefentry vendor="xorg"><refentrytitle>Xorg</refentrytitle><manvolnum>1</manvolnum></citerefentry> can find it. This is typically <filename>/etc/X11/xorg.conf</filename> or <filename>/usr/local/etc/X11/xorg.conf</filename>.
<prompt>#</prompt> <userinput>cp xorg.conf.new /etc/X11/xorg.conf</userinput>
The <application>Xorg</application> configuration process is now complete. <application>Xorg</application> may be now started with the <citerefentry vendor="xfree86"><refentrytitle>startx</refentrytitle><manvolnum>1</manvolnum></citerefentry> utility. The <application>Xorg</application> server may also be started with the use of <citerefentry vendor="xfree86"><refentrytitle>xdm</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
Configuration with <trademark class="registered">Intel</trademark> <literal>i810</literal> Graphics Chipsets
<primary><trademark class="registered">Intel</trademark> i810 graphic chipset</primary> اصول پایه <trademark class="registered">UNIX</trademark> را آموزش می‌دهند.
Configuration with <trademark class="registered">Intel</trademark> i810 integrated chipsets requires the <filename>agpgart</filename> AGP programming interface for <application>Xorg</application> to drive the card. See the <citerefentry><refentrytitle>agp</refentrytitle><manvolnum>4</manvolnum></citerefentry> driver manual page for more information.

Loading…

No matching activity found.

Browse all component changes

Glossary

English Persian
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect1/programlisting
Flags
no-wrap
Source string location
book.translate.xml:12925
String age
11 months ago
Source string age
a year ago
Translation file
books/fa/handbook.po, string 2216