From owner-svn-doc-all@FreeBSD.ORG Fri Aug 23 03:59:23 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9E3BB2AC; Fri, 23 Aug 2013 03:59:23 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 872552A5B; Fri, 23 Aug 2013 03:59:23 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r7N3xMu0057209; Fri, 23 Aug 2013 03:59:22 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r7N3xM5O057208; Fri, 23 Aug 2013 03:59:22 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201308230359.r7N3xM5O057208@svn.freebsd.org> From: Warren Block Date: Fri, 23 Aug 2013 03:59:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r42576 - head/en_US.ISO8859-1/books/handbook/x11 X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 03:59:23 -0000 Author: wblock Date: Fri Aug 23 03:59:22 2013 New Revision: 42576 URL: http://svnweb.freebsd.org/changeset/doc/42576 Log: Whitespace-only fixes. Translators, please ignore. Modified: head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/x11/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Fri Aug 23 02:14:23 2013 (r42575) +++ head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Fri Aug 23 03:59:22 2013 (r42576) @@ -36,8 +36,8 @@ used by &os;. For more information on the video hardware that X11 - supports, check the &xorg; web site. + supports, check the + &xorg; web site. After reading this chapter, you will know: @@ -97,11 +97,12 @@ Window). X was just the next letter in the Roman alphabet. - X can be called X, X Window - System, X11, and a number of other - terms. You may find that using the term X - Windows to describe X11 can be offensive to some - people; for a bit more insight on this, see &man.X.7;. + X can be called X, + X Window System, X11, and a + number of other terms. You may find that using the term + X Windows to describe X11 can be offensive to + some people; for a bit more insight on this, see + &man.X.7;. @@ -110,21 +111,20 @@ X was designed from the beginning to be network-centric, and adopts a client-server model. - In the X model, the - X server runs on the computer that has the - keyboard, monitor, and mouse attached. The server's - responsibility includes tasks such as managing the - display, handling input from the keyboard and mouse, and + In the X model, the X server runs on the + computer that has the keyboard, monitor, and mouse attached. + The server's responsibility includes tasks such as managing + the display, handling input from the keyboard and mouse, and other input or output devices (i.e., a tablet - can be used as an input device, and a video projector - may be an alternative output device). Each X application - (such as XTerm or + can be used as an input device, and a video projector may be + an alternative output device). Each X application (such as + XTerm or Firefox) is a - client. A client sends messages to the server - such as Please draw a window at these - coordinates, and the server sends back messages such - as The user just clicked on the OK - button. + client. A client sends messages to the server + such as + Please draw a window at these coordinates, and + the server sends back messages such as + The user just clicked on the OK button. In a home or small office environment, the X server and the X clients commonly run on the same computer. However, it @@ -177,16 +177,15 @@ application called a Window Manager. There are dozens of window managers - available for X. Each of - these window managers provides a different look and feel; - some of them support virtual desktops; some - of them allow customized keystrokes to manage the desktop; - some have a Start button or similar device; - some are themeable, allowing a complete change - of look-and-feel by applying a new theme. Window managers - are available in the - x11-wm category of the Ports - Collection. + available for X. Each of these window managers provides a + different look and feel; some of them support + virtual desktops; some of them allow customized + keystrokes to manage the desktop; some have a + Start button or similar device; some are + themeable, allowing a complete change of + look-and-feel by applying a new theme. Window managers are + available in the x11-wm category of the + Ports Collection. In addition, the KDE and GNOME desktop environments both @@ -203,14 +202,14 @@ Focus Policy - Another feature the window manager is responsible for - is the mouse focus policy. Every windowing + Another feature the window manager is responsible for is + the mouse focus policy. Every windowing system needs some means of choosing a window to be actively receiving keystrokes, and should visibly indicate which window is active as well. A familiar focus policy is called - click-to-focus. This is the model utilized + click-to-focus. This is the model utilized by µsoft.windows;, in which a window becomes active upon receiving a mouse click. @@ -326,28 +325,26 @@ available. - Alternatively, X11 - can be installed directly from packages. + Alternatively, X11 can be installed directly from packages. Binary packages to use with &man.pkg.add.1; tool are also available for X11. When the remote fetching feature of - &man.pkg.add.1; is used, the version number of the package - must be removed. &man.pkg.add.1; will automatically fetch - the latest version of the application. + &man.pkg.add.1; is used, the version number of the package must + be removed. &man.pkg.add.1; will automatically fetch the latest + version of the application. So to fetch and install the package of &xorg;, simply type: &prompt.root; pkg_add -r xorg - The examples above will install the complete - X11 distribution including the - servers, clients, fonts etc. Separate packages and ports of X11 - are also - available. - - To install a minimal X11 distribution you can - alternatively install - x11/xorg-minimal. + + The examples above will install the complete X11 + distribution including the servers, clients, fonts etc. + Separate packages and ports of X11 are also available. + + To install a minimal X11 distribution you can + alternatively install + x11/xorg-minimal. The rest of this chapter will explain how to configure @@ -368,7 +365,6 @@ X11 Configuration - &xorg; X11 @@ -380,9 +376,17 @@ hardware information before beginning configuration. - Monitor sync frequencies - Video card chipset - Video card memory + + Monitor sync frequencies + + + + Video card chipset + + + + Video card memory + @@ -421,13 +425,13 @@ Configuring X11 - &xorg; - uses HAL to autodetect keyboards and mice. - The sysutils/hal and + &xorg; uses + HAL to autodetect keyboards and mice. The + sysutils/hal and devel/dbus ports are - installed as dependencies of x11/xorg, but must be enabled by - the following entries in the + installed as dependencies of + x11/xorg, but must be + enabled by the following entries in the /etc/rc.conf file: hald_enable="YES" @@ -437,9 +441,9 @@ dbus_enable="YES" rebooting) before further &xorg; configuration or use is attempted. - &xorg; can - often work without any further configuration steps by - simply typing at prompt: + &xorg; can often work without + any further configuration steps by simply typing at + prompt: &prompt.user; startx @@ -465,16 +469,14 @@ dbus_enable="YES" &prompt.root; Xorg -configure - This will generate an - X11 configuration skeleton file in the - /root directory called + This will generate an X11 configuration skeleton file in + the /root directory called xorg.conf.new (whether you &man.su.1; or do a direct login affects the inherited supervisor - $HOME directory variable). The - X11 program will attempt to probe - the graphics hardware on the system and write a - configuration file to load the proper drivers for the detected - hardware on the target system. + $HOME directory variable). The X11 program + will attempt to probe the graphics hardware on the system and + write a configuration file to load the proper drivers for the + detected hardware on the target system. The next step is to test the existing configuration to verify that &xorg; @@ -504,9 +506,9 @@ dbus_enable="YES" Alt Backspace key combination may also be used to break out of - &xorg;. To enable it, - you can either type the following - command from any X terminal emulator: + &xorg;. To enable it, you can + either type the following command from any X terminal + emulator: &prompt.user; setxkbmap -option terminate:ctrl_alt_bksp @@ -514,7 +516,7 @@ dbus_enable="YES" hald called x11-input.fdi and saved in the /usr/local/etc/hal/fdi/policy + class="directory">/usr/local/etc/hal/fdi/policy directory. This file should contain the following lines: @@ -538,25 +540,25 @@ dbus_enable="YES" Option "DontZap" "off" - If the mouse does not work, you will need to first - configure it before proceeding. See - in the &os; install chapter. In recent - Xorg versions, - the InputDevice sections in - xorg.conf are ignored in favor of the - autodetected devices. To restore the old behavior, add the - following line to the ServerLayout or - ServerFlags 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). + If the mouse does not work, you will need to first + configure it before proceeding. See + in the &os; install chapter. In recent + Xorg versions, + the InputDevice sections in + xorg.conf are ignored in favor of the + autodetected devices. To restore the old behavior, add the + following line to the ServerLayout or + ServerFlags 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 hald daemon will, by default, + As previously explained the + hald daemon will, by default, automatically detect your keyboard. There are chances that your keyboard layout or model will not be correct, desktop environments like GNOME, @@ -572,7 +574,7 @@ dbus_enable="YES" configuration file for hald called x11-input.fdi and saved in the /usr/local/etc/hal/fdi/policy + class="directory">/usr/local/etc/hal/fdi/policy directory. This file should contain the following lines: @@ -605,13 +607,13 @@ dbus_enable="YES" X11 tuning - The xorg.conf.new - configuration file may now be tuned to taste. Open the - file in a text editor such as &man.emacs.1; or &man.ee.1;. - If the monitor is an older or unusual model that does not - support autodetection of sync frequencies, those settings - can be added to xorg.conf.new - under the "Monitor" section: + The xorg.conf.new configuration file + may now be tuned to taste. Open the file in a text editor + such as &man.emacs.1; or &man.ee.1;. If the monitor is an + older or unusual model that does not support autodetection of + sync frequencies, those settings can be added to + xorg.conf.new under the + "Monitor" section: Section "Monitor" Identifier "Monitor0" @@ -622,9 +624,9 @@ dbus_enable="YES" 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 + 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 @@ -640,9 +642,9 @@ EndSection While the xorg.conf.new - configuration file is still open in an editor, select - the default resolution and color depth desired. This is - defined in the "Screen" section: + configuration file is still open in an editor, select the + default resolution and color depth desired. This is defined + in the "Screen" section: Section "Screen" Identifier "Screen0" @@ -656,45 +658,42 @@ EndSection EndSubSection EndSection - The DefaultDepth keyword describes - the color depth to run at by default. This can be overridden - with the command line switch to - &man.Xorg.1;. - The Modes 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. + The DefaultDepth keyword describes the + color depth to run at by default. This can be overridden with + the command line switch to + &man.Xorg.1;. The Modes 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 X11 log files, which - contain information on each device that the X11 server - attaches to. &xorg; log file - names are in the format of - /var/log/Xorg.0.log. The exact name - of the log can vary from Xorg.0.log - to Xorg.8.log and so forth. + troubleshooting process are the X11 log files, which contain + information on each device that the X11 server attaches to. + &xorg; log file names are in the + format of /var/log/Xorg.0.log. The + exact name of the log can vary from + Xorg.0.log to + Xorg.8.log and so forth. - If all is well, the configuration - file needs to be installed in a common location where - &man.Xorg.1; can find it. + If all is well, the configuration file needs to be + installed in a common location where &man.Xorg.1; can find it. This is typically /etc/X11/xorg.conf or /usr/local/etc/X11/xorg.conf. &prompt.root; cp xorg.conf.new /etc/X11/xorg.conf - The X11 configuration process is now - complete. &xorg; may be now - started with the &man.startx.1; utility. - The X11 server may also be started with the use of - &man.xdm.1;. + The X11 configuration process is now complete. + &xorg; may be now started with the + &man.startx.1; utility. The X11 server may also be started + with the use of &man.xdm.1;. @@ -704,47 +703,62 @@ EndSection Configuration with &intel; <literal>i810</literal> Graphics Chipsets - Intel i810 graphic chipset + + Intel i810 graphic chipset + Configuration with &intel; i810 integrated chipsets - requires the agpgart - AGP programming interface for X11 - to drive the card. See the &man.agp.4; driver manual page - for more information. + requires the agpgart AGP + programming interface for X11 to drive the card. See the + &man.agp.4; driver manual page for more information. This will allow configuration of the hardware as any other graphics board. Note on systems without the &man.agp.4; driver compiled in the kernel, trying to load - the module with &man.kldload.8; will not work. This - driver has to be in the kernel at boot time through being - compiled in or using - /boot/loader.conf. + the module with &man.kldload.8; will not work. This driver + has to be in the kernel at boot time through being compiled + in or using /boot/loader.conf. Adding a Widescreen Flatpanel to the Mix - widescreen flatpanel configuration + + widescreen flatpanel configuration + This section assumes a bit of advanced configuration knowledge. If attempts to use the standard configuration tools above have not resulted in a working configuration, - there is information enough in the log files to be of use - in getting the setup working. Use of a text editor will - be necessary. - - Current widescreen (WSXGA, WSXGA+, WUXGA, WXGA, - WXGA+, et.al.) formats support 16:10 and 10:9 formats or - aspect ratios that can be problematic. Examples of some - common screen resolutions for 16:10 aspect ratios - are: + there is information enough in the log files to be of use in + getting the setup working. Use of a text editor will be + necessary. + + Current widescreen (WSXGA, WSXGA+, WUXGA, WXGA, WXGA+, + et.al.) formats support 16:10 and 10:9 formats or aspect + ratios that can be problematic. Examples of some common + screen resolutions for 16:10 aspect ratios are: - 2560x1600 - 1920x1200 - 1680x1050 - 1440x900 - 1280x800 + + 2560x1600 + + + + 1920x1200 + + + + 1680x1050 + + + + 1440x900 + + + + 1280x800 + At some point, it will be as easy as adding one of these @@ -764,17 +778,17 @@ EndSubSection EndSection &xorg; is smart enough to - pull the resolution information from the widescreen via - I2C/DDC information so it knows what the monitor can - handle as far as frequencies and resolutions. + pull the resolution information from the widescreen via + I2C/DDC information so it knows what the monitor can handle + as far as frequencies and resolutions. If those ModeLines do not exist in the drivers, one might need to give &xorg; a little hint. Using /var/log/Xorg.0.log one can extract enough information to manually create a - ModeLine that will work. Simply look - for information resembling this: + ModeLine that will work. Simply look for + information resembling this: (II) MGA(0): Supported additional Video Mode: (II) MGA(0): clock: 146.2 MHz Image Size: 433 x 271 mm @@ -789,8 +803,8 @@ EndSection ModeLine <name> <clock> <4 horiz. timings> <4 vert. timings> So that the ModeLine in - Section "Monitor" - for this example would look like this: + Section "Monitor" for this example would + look like this: Section "Monitor" Identifier "Monitor1" @@ -819,41 +833,41 @@ EndSection Using Fonts in X11 - Type1 Fonts + Type1 Fonts - The default fonts that ship with X11 are less than ideal - for typical desktop publishing applications. Large - presentation fonts show up jagged and unprofessional looking, - and small fonts are - almost completely unintelligible. However, there are several - free, high quality Type1 (&postscript;) fonts available which - can be readily used with X11. For instance, the URW font - collection (x11-fonts/urwfonts) includes high - quality versions of standard type1 fonts (Times Roman, - Helvetica, Palatino and others). The - Freefonts collection (x11-fonts/freefonts) includes - many more fonts, but most of them are intended for use in - graphics software such as the Gimp, - and are not complete enough to serve as screen fonts. In - addition, X11 can be configured to use &truetype; fonts with - a minimum of effort. For more details on this, see the - &man.X.7; manual page or the section - on &truetype; fonts. + The default fonts that ship with X11 are less than ideal + for typical desktop publishing applications. Large + presentation fonts show up jagged and unprofessional looking, + and small fonts are almost completely unintelligible. + However, there are several free, high quality Type1 + (&postscript;) fonts available which can be readily used with + X11. For instance, the URW font collection + (x11-fonts/urwfonts) + includes high quality versions of standard type1 fonts + (Times Roman, + Helvetica, + Palatino and + others). The Freefonts collection + (x11-fonts/freefonts) + includes many more fonts, but most of them are intended for + use in graphics software such as the + Gimp, and are not complete enough + to serve as screen fonts. In addition, X11 can be configured + to use &truetype; fonts with a minimum of effort. For more + details on this, see the &man.X.7; manual page or the + section on &truetype; + fonts. - To install the above Type1 font collections from the - Ports Collection, run the following commands: + To install the above Type1 font collections from the + Ports Collection, run the following commands: - &prompt.root; cd /usr/ports/x11-fonts/urwfonts + &prompt.root; cd /usr/ports/x11-fonts/urwfonts &prompt.root; make install clean - And likewise with the freefont or other collections. To - have the X server detect these fonts, add an appropriate line - to the X server configuration file - (/etc/X11/xorg.conf), which reads: + And likewise with the freefont or other collections. To + have the X server detect these fonts, add an appropriate line + to the X server configuration file + (/etc/X11/xorg.conf), which reads: FontPath "/usr/local/lib/X11/fonts/URW/" @@ -871,55 +885,58 @@ EndSection graphical login manager like XDM). A third way is to use the new /usr/local/etc/fonts/local.conf file: see - the section on anti-aliasing. + the section on + anti-aliasing. - &truetype; Fonts + &truetype; Fonts - TrueType Fonts - fonts - TrueType - - - &xorg; has built in support - for rendering &truetype; fonts. There are two different - modules that can enable this functionality. The freetype - module is used in this example because it is more consistent - with the other font rendering back-ends. To enable the - freetype module just add the following line to the - "Module" section of the - /etc/X11/xorg.conf file. - - Load "freetype" - - Now make a directory for the &truetype; fonts (for - example, - /usr/local/lib/X11/fonts/TrueType) - and copy all of the &truetype; fonts into this directory. - Keep in mind that &truetype; fonts cannot be directly taken - from a &macintosh;; they must be in &unix;/&ms-dos;/&windows; - format for use by X11. Once the files have been copied into - this directory, use ttmkfdir to - create a fonts.dir file, so that the X - font renderer knows that these new files have been installed. - ttmkfdir is available from the FreeBSD - Ports Collection as - x11-fonts/ttmkfdir. + + TrueType Fonts + + + fonts + TrueType + + + &xorg; has built in support for + rendering &truetype; fonts. There are two different modules + that can enable this functionality. The freetype module is + used in this example because it is more consistent with the + other font rendering back-ends. To enable the freetype module + just add the following line to the "Module" + section of the /etc/X11/xorg.conf + file. + + Load "freetype" + + Now make a directory for the &truetype; fonts (for + example, + /usr/local/lib/X11/fonts/TrueType) and + copy all of the &truetype; fonts into this directory. Keep in + mind that &truetype; fonts cannot be directly taken from a + &macintosh;; they must be in &unix;/&ms-dos;/&windows; format + for use by X11. Once the files have been copied into this + directory, use ttmkfdir to create a + fonts.dir file, so that the X font + renderer knows that these new files have been installed. + ttmkfdir is available from the FreeBSD + Ports Collection as + x11-fonts/ttmkfdir. - &prompt.root; cd /usr/local/lib/X11/fonts/TrueType + &prompt.root; cd /usr/local/lib/X11/fonts/TrueType &prompt.root; ttmkfdir -o fonts.dir - Now add the &truetype; directory to the font - path. This is just the same as described above for Type1 fonts, that is, use + Now add the &truetype; directory to the font path. This + is just the same as described above for + Type1 fonts, that is, use - &prompt.user; xset fp+ /usr/local/lib/X11/fonts/TrueType + &prompt.user; xset fp+ /usr/local/lib/X11/fonts/TrueType &prompt.user; xset fp rehash - or add a FontPath line to the - xorg.conf file. + or add a FontPath line to the + xorg.conf file. That's it. Now Gimp, Apache OpenOffice, and all of the @@ -931,75 +948,79 @@ EndSection - - - - Joe Marcus - Clarke - Updated by - - - - - Anti-Aliased Fonts + + + + Joe Marcus + Clarke + Updated by + + + + + Anti-Aliased Fonts + + + anti-aliased fonts + + + fonts + anti-aliased + - anti-aliased fonts - fonts - anti-aliased - - All fonts in X11 that are found - in /usr/local/lib/X11/fonts/ and - ~/.fonts/ are automatically - made available for anti-aliasing to Xft-aware applications. - Most recent applications are Xft-aware, including - KDE, - GNOME, and - Firefox. - - In order to control which fonts are anti-aliased, or to - configure anti-aliasing properties, create (or edit, if it - already exists) the file - /usr/local/etc/fonts/local.conf. Several - advanced features of the Xft font system can be tuned using - this file; this section describes only some simple - possibilities. For more details, please see - &man.fonts-conf.5;. - - XML - - This file must be in XML format. Pay careful attention - to case, and make sure all tags are properly closed. The - file begins with the usual XML header followed by a DOCTYPE - definition, and then the <fontconfig> - tag: + All fonts in X11 that are found in + /usr/local/lib/X11/fonts/ and + ~/.fonts/ are automatically made + available for anti-aliasing to Xft-aware applications. Most + recent applications are Xft-aware, including + KDE, + GNOME, and + Firefox. + + In order to control which fonts are anti-aliased, or to + configure anti-aliasing properties, create (or edit, if it + already exists) the file + /usr/local/etc/fonts/local.conf. Several + advanced features of the Xft font system can be tuned using + this file; this section describes only some simple + possibilities. For more details, please see + &man.fonts-conf.5;. + + XML + + This file must be in XML format. Pay careful attention to + case, and make sure all tags are properly closed. The file + begins with the usual XML header followed by a DOCTYPE + definition, and then the <fontconfig> + tag: - + <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> - As previously stated, all fonts in - /usr/local/lib/X11/fonts/ as well as - ~/.fonts/ are already made available to - Xft-aware applications. If you wish to add another directory - outside of these two directory trees, add a line similar to the - following to - /usr/local/etc/fonts/local.conf: - - <dir>/path/to/my/fonts</dir> - - After adding new fonts, and especially new font directories, - you should run the following command to rebuild the font - caches: - - &prompt.root; fc-cache -f - - Anti-aliasing makes borders slightly fuzzy, which makes - very small text more readable and removes - staircases from large text, but can cause - eyestrain if applied to normal text. To exclude font sizes - smaller than 14 point from anti-aliasing, include these - lines: + As previously stated, all fonts in + /usr/local/lib/X11/fonts/ as well as + ~/.fonts/ are already made available to + Xft-aware applications. If you wish to add another directory + outside of these two directory trees, add a line similar to + the following to + /usr/local/etc/fonts/local.conf: + + <dir>/path/to/my/fonts</dir> + + After adding new fonts, and especially new font + directories, you should run the following command to rebuild + the font caches: + + &prompt.root; fc-cache -f + + Anti-aliasing makes borders slightly fuzzy, which makes + very small text more readable and removes + staircases from large text, but can cause + eyestrain if applied to normal text. To exclude font sizes + smaller than 14 point from anti-aliasing, include these + lines: <match target="font"> <test name="size" compare="less"> @@ -1018,16 +1039,18 @@ EndSection </edit> </match> - fonts - spacing + + fonts + spacing + - Spacing for some monospaced fonts may also be inappropriate - with anti-aliasing. This seems to be an issue with - KDE, in particular. One possible - fix for this is to force the spacing for such fonts to be 100. - Add the following lines: + Spacing for some monospaced fonts may also be + inappropriate with anti-aliasing. This seems to be an issue + with KDE, in particular. One + possible fix for this is to force the spacing for such fonts + to be 100. Add the following lines: - <match target="pattern" name="family"> + <match target="pattern" name="family"> <test qual="any" name="family"> <string>fixed</string> </test> @@ -1059,9 +1082,8 @@ EndSection Certain fonts, such as Helvetica, may have a problem when anti-aliased. Usually this manifests itself as a font that seems cut in half vertically. At worst, it may cause - applications to - crash. To avoid this, consider adding the following to - local.conf: + applications to crash. To avoid this, consider adding the + following to local.conf: <match target="pattern" name="family"> <test qual="any" name="family"> @@ -1077,24 +1099,24 @@ EndSection with the </fontconfig> tag. Not doing this will cause your changes to be ignored. - Finally, users can add their own settings via their - personal .fonts.conf files. To do - this, each user should simply create a - ~/.fonts.conf. This file must also be - in XML format. - - LCD screen - Fonts - LCD screen - - One last point: with an LCD screen, sub-pixel sampling - may be desired. This basically treats the (horizontally - separated) red, green and blue components separately to - improve the horizontal resolution; the results can be - dramatic. To enable this, add the line somewhere in the - local.conf file: + Finally, users can add their own settings via their + personal .fonts.conf files. To do this, + each user should simply create a + ~/.fonts.conf. This file must also be in + XML format. + + LCD screen + Fonts + LCD screen + + One last point: with an LCD screen, sub-pixel sampling may + be desired. This basically treats the (horizontally + separated) red, green and blue components separately to + improve the horizontal resolution; the results can be + dramatic. To enable this, add the line somewhere in the + local.conf file: - + <match target="font"> <test qual="all" name="rgba"> <const>unknown</const> @@ -1104,13 +1126,13 @@ EndSection </edit> </match> - + Depending on the sort of display, rgb may need to be changed to bgr, vrgb or vbgr: experiment and see which works best. - + @@ -1125,8 +1147,8 @@ EndSection The X Display Manager - + Overview X Display Manager @@ -1143,17 +1165,16 @@ EndSection and entering authorization information such as a login and password combination. - Think of XDM as - providing the same functionality to the user as the - &man.getty.8; utility (see for - details). That is, it performs system logins to the display - being connected to and then runs a session manager on - behalf of the user (usually an X window manager). - XDM then waits for this program to - exit, signaling that the user is done and should be logged out - of the display. At this point, XDM - can display the login and display chooser screens for the next - user to login. + Think of XDM as providing the + same functionality to the user as the &man.getty.8; utility + (see for details). That is, it + performs system logins to the display being connected to and + then runs a session manager on behalf of the user (usually an + X window manager). XDM then waits + for this program to exit, signaling that the user is done and + should be logged out of the display. At this point, + XDM can display the login and + display chooser screens for the next user to login. @@ -1167,12 +1188,12 @@ EndSection found in /usr/local/bin/xdm. This program can be run at any time as root and it will start managing the X display on the local machine. - If XDM is to be run every - time the machine boots up, a convenient way to do this is by *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***