From owner-svn-doc-all@FreeBSD.ORG Fri Jan 11 17:10:04 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4D85CB29; Fri, 11 Jan 2013 17:10:04 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 3F6EF77E; Fri, 11 Jan 2013 17:10:04 +0000 (UTC) Received: from svn.freebsd.org (svn.FreeBSD.org [8.8.178.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0BHA46U071640; Fri, 11 Jan 2013 17:10:04 GMT (envelope-from bcr@svn.freebsd.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0BHA4U5071639; Fri, 11 Jan 2013 17:10:04 GMT (envelope-from bcr@svn.freebsd.org) Message-Id: <201301111710.r0BHA4U5071639@svn.freebsd.org> From: Benedict Reuschling Date: Fri, 11 Jan 2013 17:10:04 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40566 - 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, 11 Jan 2013 17:10:04 -0000 Author: bcr Date: Fri Jan 11 17:10:03 2013 New Revision: 40566 URL: http://svnweb.freebsd.org/changeset/doc/40566 Log: Whitespace fixes to the entire X11 chapter, improving non-visible indentation of this file. Only minor fixes by me, the original patch was Submitted by: Dru Lavigne 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 Jan 11 15:06:04 2013 (r40565) +++ head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Fri Jan 11 17:10:03 2013 (r40566) @@ -29,13 +29,12 @@ a powerful graphical user interface. X11 is a freely available version of the X Window System that is implemented in &xorg; - (and other software - packages not discussed here). - The + (and other software packages not discussed here). The default and official flavor of X11 in &os; is &xorg;, the X11 server developed by - the X.Org Foundation under a license very similar to the one used - by &os;. Commercial X servers for &os; are also available. + the X.Org Foundation under a license very similar to the one + used by &os;. Commercial X servers for &os; are also + available. For more information on the video hardware that X11 supports, check the - The various components of the X Window System, and how they - interoperate. + The various components of the X Window System, and how + they interoperate. @@ -80,138 +79,154 @@ Understanding X - Using X for the first time can be somewhat of a shock to someone - familiar with other graphical environments, such as µsoft.windows; or - &macos;. - - While it is not necessary to understand all of the details of various - X components and how they interact, some basic knowledge makes - it possible to take advantage of X's strengths. + Using X for the first time can be somewhat of a shock to + someone familiar with other graphical environments, such as + µsoft.windows; or &macos;. + + While it is not necessary to understand all of the details + of various X components and how they interact, some basic + knowledge makes it possible to take advantage of X's + strengths. Why X? - X is not the first window system written for &unix;, but it is the - most popular of them. X's original development team had worked on another - window system prior to writing X. That system's name was - W (for 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 is not the first window system written for &unix;, but + it is the most popular of them. X's original development team + had worked on another window system prior to writing X. That + system's name was W (for + 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;. The X Client/Server Model - X was designed from the beginning to be network-centric, and - adopts a client-server model. + 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 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 - &netscape;) 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 + 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 + &netscape;) 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. - In a home or small - office environment, the X server and the X clients commonly run on - the same computer. However, it is perfectly possible to run the X - server on a less powerful desktop computer, and run X applications - (the clients) on, say, the powerful and expensive machine that serves - the office. In this scenario the communication between the X client - and server takes place over the network. + In a home or small office environment, the X server and + the X clients commonly run on the same computer. However, it + is perfectly possible to run the X server on a less powerful + desktop computer, and run X applications (the clients) on, + say, the powerful and expensive machine that serves the + office. In this scenario the communication between the X + client and server takes place over the network. This confuses some people, because the X terminology is - exactly backward to what they expect. They expect the X - server to be the big powerful machine down the hall, and - the X client to be the machine on their desk. - - It is important to remember that the X server is the machine with the monitor and - keyboard, and the X clients are the programs that display the - windows. - - There is nothing in the protocol that forces the client and - server machines to be running the same operating system, or even to - be running on the same type of computer. It is certainly possible to - run an X server on µsoft.windows; or Apple's &macos;, and there are - various free and commercial applications available that do exactly - that. + exactly backward to what they expect. They expect the + X server to be the big powerful machine down + the hall, and the X client to be the machine + on their desk. + + It is important to remember that the X server is the + machine with the monitor and keyboard, and the X clients are + the programs that display the windows. + + There is nothing in the protocol that forces the client + and server machines to be running the same operating system, + or even to be running on the same type of computer. It is + certainly possible to run an X server on µsoft.windows; + or Apple's &macos;, and there are various free and commercial + applications available that do exactly that. The Window Manager - The X design philosophy is much like the &unix; design philosophy, - tools, not policy. This means that X does not try to - dictate how a task is to be accomplished. Instead, tools are provided - to the user, and it is the user's responsibility to decide how to use - those tools. - - This philosophy extends to X not dictating what windows should - look like on screen, how to move them around with the mouse, what - keystrokes should be used to move between windows (i.e., + The X design philosophy is much like the &unix; design + philosophy, tools, not policy. This means + that X does not try to dictate how a task is to be + accomplished. Instead, tools are provided to the user, and + it is the user's responsibility to decide how to use those + tools. + + This philosophy extends to X not dictating what windows + should look like on screen, how to move them around with the + mouse, what keystrokes should be used to move between windows + (i.e., Alt Tab - , in the case of µsoft.windows;), what the title bars - on each window should look like, whether or not they have close - buttons on them, and so on. - - Instead, X delegates this responsibility to an application called - a Window Manager. There are dozens of window - managers available for X: AfterStep, - Blackbox, ctwm, + , in the case of µsoft.windows;), what the + title bars on each window should look like, whether or not + they have close buttons on them, and so on. + + Instead, X delegates this responsibility to an + application called a Window Manager. There + are dozens of window managers available for X: + AfterStep, + Blackbox, + ctwm, Enlightenment, - fvwm, Sawfish, + fvwm, + Sawfish, twm, - Window Maker, and more. 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. These - window managers, and many more, are available in the - x11-wm category of the Ports Collection. + Window Maker, and more. 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. These window + managers, and many more, are available in the + x11-wm category of the Ports + Collection. In addition, the KDE and - GNOME desktop environments both have their - own window managers which integrate with the desktop. - - Each window manager also has a different configuration mechanism; - some expect configuration file written by hand, others feature - GUI tools for most of the configuration tasks; at least one - (Sawfish) has a configuration file written - in a dialect of the Lisp language. + GNOME desktop environments both + have their own window managers which integrate with the + desktop. + + Each window manager also has a different configuration + mechanism; some expect configuration file written by hand, + others feature GUI tools for most of the configuration tasks; + at least one (Sawfish) has a + configuration file written in a dialect of the Lisp + language. Focus Policy - 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 by µsoft.windows;, in which a window - becomes active upon receiving a mouse click. - - X does not support any particular focus policy. Instead, the - window manager controls which window has the focus at any one time. - Different window managers will support different focus methods. All - of them support click to focus, and the majority of them support - several others. + 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 + by µsoft.windows;, in which a window becomes active + upon receiving a mouse click. + + X does not support any particular focus policy. + Instead, the window manager controls which window has the + focus at any one time. Different window managers will + support different focus methods. All of them support + click to focus, and the majority of them support several + others. The most popular focus policies are: @@ -220,11 +235,12 @@ focus-follows-mouse - The window that is under the mouse pointer is the - window that has the focus. This may not necessarily be - the window that is on top of all the other windows. - The focus is changed by pointing at another window, there - is no need to click in it as well. + The window that is under the mouse pointer is + the window that has the focus. This may not + necessarily be the window that is on top of all the + other windows. The focus is changed by pointing at + another window, there is no need to click in it as + well. @@ -232,12 +248,14 @@ sloppy-focus - This policy is a small extension to focus-follows-mouse. - With focus-follows-mouse, if the mouse is moved over the - root window (or background) then no window has the focus, - and keystrokes are simply lost. With sloppy-focus, focus is - only changed when the cursor enters a new window, and not - when exiting the current window. + This policy is a small extension to + focus-follows-mouse. With focus-follows-mouse, if + the mouse is moved over the root window (or + background) then no window has the focus, and + keystrokes are simply lost. With sloppy-focus, focus + is only changed when the cursor enters a new + window, and not when exiting the current + window. @@ -245,52 +263,56 @@ click-to-focus - The active window is selected by mouse click. The - window may then be raised, and appear in - front of all other windows. All keystrokes will now be - directed to this window, even if the cursor is moved to - another window. + The active window is selected by mouse click. + The window may then be raised, and + appear in front of all other windows. All keystrokes + will now be directed to this window, even if the + cursor is moved to another window. - Many window managers support other policies, as well as - variations on these. Be sure to consult the documentation for - the window manager itself. + Many window managers support other policies, as well + as variations on these. Be sure to consult the + documentation for the window manager itself. Widgets - The X approach of providing tools and not policy extends to the - widgets seen on screen in each application. - - Widget is a term for all the items in the user - interface that can be clicked or manipulated in some way; buttons, - check boxes, radio buttons, icons, lists, and so on. µsoft.windows; - calls these controls. - - µsoft.windows; and Apple's &macos; both have a very rigid widget - policy. Application developers are supposed to ensure that their - applications share a common look and feel. With X, it was not - considered sensible to mandate a particular graphical style, or set - of widgets to adhere to. - - As a result, do not expect X applications to have a common - look and feel. There are several popular widget sets and - variations, including the original Athena widget set from MIT, - &motif; (on which the widget set in - µsoft.windows; was modeled, all bevelled edges and three shades of - grey), OpenLook, and others. - - Most newer X applications today will use a modern-looking widget - set, either Qt, used by KDE, or - GTK+, used by the - GNOME - project. In this respect, there is some convergence in - look-and-feel of the &unix; desktop, which certainly makes things - easier for the novice user. + The X approach of providing tools and not policy + extends to the widgets seen on screen in each + application. + + Widget is a term for all the items in + the user interface that can be clicked or manipulated in + some way; buttons, check boxes, radio buttons, icons, lists, + and so on. µsoft.windows; calls these + controls. + + µsoft.windows; and Apple's &macos; both have a + very rigid widget policy. Application developers are + supposed to ensure that their applications share a common + look and feel. With X, it was not considered sensible to + mandate a particular graphical style, or set of widgets to + adhere to. + + As a result, do not expect X applications to have a + common look and feel. There are several popular widget sets + and variations, including the original Athena widget set from + MIT, &motif; (on which the widget + set in µsoft.windows; was modeled, all bevelled edges and + three shades of grey), OpenLook, + and others. + + Most newer X applications today will use a + modern-looking widget set, either Qt, used by + KDE, or GTK+, used by the + GNOME project. In this respect, + there is some convergence in look-and-feel of the &unix; + desktop, which certainly makes things easier for the novice + user. @@ -298,15 +320,16 @@ Installing X11 &xorg; is the default X11 - implementation for &os;. &xorg; is - the X server of the open source X Window System implementation released by the X.Org - Foundation. &xorg; is based on the code of + implementation for &os;. &xorg; + is the X server of the open source X Window System + implementation released by the X.Org Foundation. + &xorg; is based on the code of &xfree86; 4.4RC2 and X11R6.6. The version of &xorg; currently available in the &os; Ports Collection is &xorg.version;. - To build and install &xorg; from the - Ports Collection: + To build and install &xorg; + from the Ports Collection: &prompt.root; cd /usr/ports/x11/xorg &prompt.root; make install clean @@ -319,10 +342,10 @@ 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 + 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. So to fetch and install the package of @@ -336,7 +359,8 @@ are also available. - To install a minimal X11 distribution you can alternatively install + To install a minimal X11 distribution you can + alternatively install x11/xorg-minimal. @@ -414,9 +438,10 @@ &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 + devel/dbus ports are + installed as dependencies of x11/xorg, but must be enabled by + the following entries in the /etc/rc.conf file: hald_enable="YES" @@ -427,14 +452,14 @@ dbus_enable="YES" configuration or use is attempted. &xorg; can - often work without any further configuration steps by simply typing at - prompt: + often work without any further configuration steps by + simply typing at prompt: &prompt.user; startx - The automatic configuration may fail to work with some hardware, - or may not set things up quite as desired. In these cases, manual - configuration will be necessary. + The automatic configuration may fail to work with some + hardware, or may not set things up quite as desired. In + these cases, manual configuration will be necessary. Desktop environments like @@ -448,11 +473,9 @@ dbus_enable="YES" appropriate screen settings tool. - Configuration of X11 is - a multi-step process. The first step is to build an initial - configuration file. - As the super user, simply - run: + Configuration of X11 is a multi-step process. The first + step is to build an initial configuration file. As the super + user, simply run: &prompt.root; Xorg -configure @@ -475,14 +498,14 @@ dbus_enable="YES" &prompt.root; Xorg -config xorg.conf.new -retro If a black and grey grid and an X mouse cursor appear, - the configuration was successful. To exit the test, switch to the - virtual console used to start it by pressing + the configuration was successful. To exit the test, switch + to the virtual console used to start it by pressing Ctrl Alt Fn - (F1 for the first virtual console) - and press + (F1 for the first virtual + console) and press Ctrl C @@ -523,8 +546,8 @@ dbus_enable="YES" The following line will also have to be added to xorg.conf.new, in the - ServerLayout or ServerFlags - section: + ServerLayout or + ServerFlags section: Option "DontZap" "off" @@ -541,9 +564,9 @@ dbus_enable="YES" Option "AutoAddDevices" "false" - Input devices may then be configured as in previous versions, - along with any other options needed (e.g., keyboard layout - switching). + Input devices may then be configured as in previous + versions, along with any other options needed (e.g., + keyboard layout switching). As previously explained @@ -597,11 +620,11 @@ 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 + 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" @@ -612,20 +635,19 @@ dbus_enable="YES" 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 + 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 &man.xset.1; 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: + X allows DPMS (Energy Star) features to be used with + capable monitors. The &man.xset.1; 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" + Option "DPMS" xorg.conf @@ -657,21 +679,21 @@ EndSection 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. + 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 @@ -693,7 +715,8 @@ EndSection Advanced Configuration Topics - Configuration with &intel; <literal>i810</literal> Graphics Chipsets + Configuration with &intel; <literal>i810</literal> + Graphics Chipsets Intel i810 graphic chipset @@ -703,12 +726,13 @@ EndSection 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. + 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. @@ -716,16 +740,18 @@ EndSection 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: + 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: 2560x1600 @@ -736,8 +762,8 @@ EndSection At some point, it will be as easy as adding one of these - resolutions as a possible Mode in the Section - "Screen" as such: + resolutions as a possible Mode in the + Section "Screen" as such: Section "Screen" Identifier "Screen0" @@ -751,16 +777,18 @@ SubSection "Display" 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. - - 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: + &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. + + 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: (II) MGA(0): Supported additional Video Mode: (II) MGA(0): clock: 146.2 MHz Image Size: 433 x 271 mm @@ -769,12 +797,13 @@ EndSection (II) MGA(0): Ranges: V min: 48 V max: 85 Hz, H min: 30 H max: 94 kHz, PixClock max 170 MHz This information is called EDID information. Creating a - ModeLine from this is just a matter of putting the - numbers in the correct order: + ModeLine from this is just a matter of + putting the numbers in the correct order: ModeLine <name> <clock> <4 horiz. timings> <4 vert. timings> - So that the ModeLine in Section "Monitor" + So that the ModeLine in + Section "Monitor" for this example would look like this: Section "Monitor" @@ -785,8 +814,8 @@ ModeLine "1680x1050" 146.2 1680 1 Option "DPMS" EndSection - Now having completed these simple editing steps, X should start - on your new widescreen monitor. + Now having completed these simple editing steps, X + should start on your new widescreen monitor. @@ -805,25 +834,29 @@ EndSection 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 in - &netscape; 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 in &netscape; 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: @@ -831,10 +864,10 @@ EndSection &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/" @@ -844,14 +877,16 @@ EndSection &prompt.user; xset fp+ /usr/local/lib/X11/fonts/URW &prompt.user; xset fp rehash - This will work but will be lost when the X session is closed, - unless it is added to the startup file (~/.xinitrc - for a normal startx session, - or ~/.xsession when logging in through a - 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. + This will work but will be lost when the X session is + closed, unless it is added to the startup file + (~/.xinitrc for a normal + startx session, or + ~/.xsession when logging in through a + 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. @@ -863,25 +898,26 @@ EndSection &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. + 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, + 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. + 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. @@ -901,12 +937,12 @@ EndSection That's it. Now &netscape;, Gimp, - &staroffice;, and all of the other X - applications should now recognize the installed &truetype; - fonts. Extremely small fonts (as with text in a high resolution - display on a web page) and extremely large fonts (within - &staroffice;) will look much better - now. + &staroffice;, and all of the + other X applications should now recognize the installed + &truetype; fonts. Extremely small fonts (as with text in a + high resolution display on a web page) and extremely large + fonts (within &staroffice;) will + look much better now. @@ -931,7 +967,8 @@ EndSection ~/.fonts/ are automatically made available for anti-aliasing to Xft-aware applications. Most recent applications are Xft-aware, including - KDE, GNOME, and + KDE, + GNOME, and Firefox. In order to control which fonts are anti-aliased, or to @@ -945,16 +982,16 @@ EndSection 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: + 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> - + <fontconfig> As previously stated, all fonts in /usr/local/lib/X11/fonts/ as well as @@ -972,11 +1009,12 @@ EndSection &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: + 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"> @@ -1000,9 +1038,9 @@ EndSection 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: + 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"> <test qual="any" name="family"> @@ -1051,23 +1089,25 @@ EndSection Once you have finished editing local.conf make sure you end the file - with the </fontconfig> tag. Not doing this will cause - your changes to be ignored. + 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. + 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 *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***