Date: Fri, 11 Jan 2013 17:10:04 +0000 (UTC) From: Benedict Reuschling <bcr@FreeBSD.org> 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 Message-ID: <201301111710.r0BHA4U5071639@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
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 <application>&xorg;</application> - (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 <application>&xorg;</application>, 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.</para> + the X.Org Foundation under a license very similar to the one + used by &os;. Commercial X servers for &os; are also + available.</para> <para>For more information on the video hardware that X11 supports, check the <ulink @@ -45,8 +44,8 @@ <itemizedlist> <listitem> - <para>The various components of the X Window System, and how they - interoperate.</para> + <para>The various components of the X Window System, and how + they interoperate.</para> </listitem> <listitem> @@ -80,138 +79,154 @@ <sect1 id="x-understanding"> <title>Understanding X</title> - <para>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;.</para> - - <para>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.</para> + <para>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;.</para> + + <para>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.</para> <sect2> <title>Why X?</title> - <para>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 - <quote>W</quote> (for <quote>Window</quote>). X was just the next - letter in the Roman alphabet.</para> - - <para>X can be called <quote>X</quote>, <quote>X Window System</quote>, - <quote>X11</quote>, and a number of other terms. You may find - that using the term <quote>X Windows</quote> to describe X11 - can be offensive to some people; for a bit more insight on - this, see &man.X.7;.</para> + <para>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 <quote>W</quote> (for + <quote>Window</quote>). X was just the next letter in the + Roman alphabet.</para> + + <para>X can be called <quote>X</quote>, <quote>X Window + System</quote>, <quote>X11</quote>, and a number of other + terms. You may find that using the term <quote>X + Windows</quote> to describe X11 can be offensive to some + people; for a bit more insight on this, see &man.X.7;.</para> </sect2> <sect2> <title>The X Client/Server Model</title> - <para>X was designed from the beginning to be network-centric, and - adopts a <quote>client-server</quote> model.</para> + <para>X was designed from the beginning to be network-centric, + and adopts a <quote>client-server</quote> model.</para> <para>In the X model, the - <quote>X server</quote> 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 <quote>tablet</quote> can be used as - an input device, and a video projector may be an alternative output - device). - Each X application (such as <application>XTerm</application>, or - <application>&netscape;</application>) is a <quote>client</quote>. A - client sends messages to the server such as <quote>Please draw a - window at these coordinates</quote>, and the server sends back - messages such as <quote>The user just clicked on the OK + <quote>X server</quote> 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 <quote>tablet</quote> + can be used as an input device, and a video projector + may be an alternative output device). Each X application + (such as <application>XTerm</application>, or + <application>&netscape;</application>) is a + <quote>client</quote>. A client sends messages to the server + such as <quote>Please draw a window at these + coordinates</quote>, and the server sends back messages such + as <quote>The user just clicked on the OK button</quote>.</para> - <para>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.</para> + <para>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.</para> <para>This confuses some people, because the X terminology is - exactly backward to what they expect. They expect the <quote>X - server</quote> to be the big powerful machine down the hall, and - the <quote>X client</quote> to be the machine on their desk.</para> - - <para>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.</para> - - <para>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.</para> + exactly backward to what they expect. They expect the + <quote>X server</quote> to be the big powerful machine down + the hall, and the <quote>X client</quote> to be the machine + on their desk.</para> + + <para>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.</para> + + <para>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.</para> </sect2> <sect2> <title>The Window Manager</title> - <para>The X design philosophy is much like the &unix; design philosophy, - <quote>tools, not policy</quote>. 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.</para> - - <para>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., + <para>The X design philosophy is much like the &unix; design + philosophy, <quote>tools, not policy</quote>. 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.</para> + + <para>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., <keycombo action="simul"> <keycap>Alt</keycap> <keycap>Tab</keycap> - </keycombo>, 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.</para> - - <para>Instead, X delegates this responsibility to an application called - a <quote>Window Manager</quote>. There are dozens of window - managers available for X: <application>AfterStep</application>, - <application>Blackbox</application>, <application>ctwm</application>, + </keycombo>, 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.</para> + + <para>Instead, X delegates this responsibility to an + application called a <quote>Window Manager</quote>. There + are dozens of window managers available for X: + <application>AfterStep</application>, + <application>Blackbox</application>, + <application>ctwm</application>, <application>Enlightenment</application>, - <application>fvwm</application>, <application>Sawfish</application>, + <application>fvwm</application>, + <application>Sawfish</application>, <application>twm</application>, - <application>Window Maker</application>, and more. Each of these - window managers provides a different look and feel; some of them - support <quote>virtual desktops</quote>; some of them allow customized - keystrokes to manage the desktop; some have a <quote>Start</quote> - button or similar device; some are <quote>themeable</quote>, allowing - a complete change of look-and-feel by applying a new theme. These - window managers, and many more, are available in the - <filename>x11-wm</filename> category of the Ports Collection.</para> + <application>Window Maker</application>, and more. Each of + these window managers provides a different look and feel; + some of them support <quote>virtual desktops</quote>; some + of them allow customized keystrokes to manage the desktop; + some have a <quote>Start</quote> button or similar device; + some are <quote>themeable</quote>, allowing a complete change + of look-and-feel by applying a new theme. These window + managers, and many more, are available in the + <filename>x11-wm</filename> category of the Ports + Collection.</para> <para>In addition, the <application>KDE</application> and - <application>GNOME</application> desktop environments both have their - own window managers which integrate with the desktop.</para> - - <para>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 - (<application>Sawfish</application>) has a configuration file written - in a dialect of the Lisp language.</para> + <application>GNOME</application> desktop environments both + have their own window managers which integrate with the + desktop.</para> + + <para>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 (<application>Sawfish</application>) has a + configuration file written in a dialect of the Lisp + language.</para> <note> <title>Focus Policy</title> - <para>Another feature the window manager is responsible for is the - mouse <quote>focus policy</quote>. 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.</para> - - <para>A familiar focus policy is called <quote>click-to-focus</quote>. - This is the model utilized by µsoft.windows;, in which a window - becomes active upon receiving a mouse click.</para> - - <para>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.</para> + <para>Another feature the window manager is responsible for + is the mouse <quote>focus policy</quote>. 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.</para> + + <para>A familiar focus policy is called + <quote>click-to-focus</quote>. This is the model utilized + by µsoft.windows;, in which a window becomes active + upon receiving a mouse click.</para> + + <para>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.</para> <para>The most popular focus policies are:</para> @@ -220,11 +235,12 @@ <term>focus-follows-mouse</term> <listitem> - <para>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.</para> + <para>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.</para> </listitem> </varlistentry> @@ -232,12 +248,14 @@ <term>sloppy-focus</term> <listitem> - <para>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.</para> + <para>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.</para> </listitem> </varlistentry> @@ -245,52 +263,56 @@ <term>click-to-focus</term> <listitem> - <para>The active window is selected by mouse click. The - window may then be <quote>raised</quote>, 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.</para> + <para>The active window is selected by mouse click. + The window may then be <quote>raised</quote>, 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.</para> </listitem> </varlistentry> </variablelist> - <para>Many window managers support other policies, as well as - variations on these. Be sure to consult the documentation for - the window manager itself.</para> + <para>Many window managers support other policies, as well + as variations on these. Be sure to consult the + documentation for the window manager itself.</para> </note> </sect2> <sect2> <title>Widgets</title> - <para>The X approach of providing tools and not policy extends to the - widgets seen on screen in each application.</para> - - <para><quote>Widget</quote> 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 <quote>controls</quote>.</para> - - <para>µ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.</para> - - <para>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, - <application>&motif;</application> (on which the widget set in - µsoft.windows; was modeled, all bevelled edges and three shades of - grey), <application>OpenLook</application>, and others.</para> - - <para>Most newer X applications today will use a modern-looking widget - set, either Qt, used by <application>KDE</application>, or - GTK+, used by the - <application>GNOME</application> - 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.</para> + <para>The X approach of providing tools and not policy + extends to the widgets seen on screen in each + application.</para> + + <para><quote>Widget</quote> 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 + <quote>controls</quote>.</para> + + <para>µ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.</para> + + <para>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, <application>&motif;</application> (on which the widget + set in µsoft.windows; was modeled, all bevelled edges and + three shades of grey), <application>OpenLook</application>, + and others.</para> + + <para>Most newer X applications today will use a + modern-looking widget set, either Qt, used by + <application>KDE</application>, or GTK+, used by the + <application>GNOME</application> 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.</para> </sect2> </sect1> @@ -298,15 +320,16 @@ <title>Installing X11</title> <para><application>&xorg;</application> is the default X11 - implementation for &os;. <application>&xorg;</application> is - the X server of the open source X Window System implementation released by the X.Org - Foundation. <application>&xorg;</application> is based on the code of + implementation for &os;. <application>&xorg;</application> + is the X server of the open source X Window System + implementation released by the X.Org Foundation. + <application>&xorg;</application> is based on the code of <application>&xfree86; 4.4RC2</application> and X11R6.6. The version of <application>&xorg;</application> currently available in the &os; Ports Collection is &xorg.version;.</para> - <para>To build and install <application>&xorg;</application> from the - Ports Collection:</para> + <para>To build and install <application>&xorg;</application> + from the Ports Collection:</para> <screen>&prompt.root; <userinput>cd /usr/ports/x11/xorg</userinput> &prompt.root; <userinput>make install clean</userinput></screen> @@ -319,10 +342,10 @@ <para>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.</para> <para>So to fetch and install the package of @@ -336,7 +359,8 @@ are also available.</para> - <para>To install a minimal X11 distribution you can alternatively install + <para>To install a minimal X11 distribution you can + alternatively install <filename role="package">x11/xorg-minimal</filename>.</para> </note> @@ -414,9 +438,10 @@ <para><application>&xorg;</application> uses <acronym>HAL</acronym> to autodetect keyboards and mice. The <filename role="package">sysutils/hal</filename> and - <filename role="package">devel/dbus</filename> ports are installed - as dependencies of <filename role="package">x11/xorg</filename>, but - must be enabled by the following entries in the + <filename role="package">devel/dbus</filename> ports are + installed as dependencies of <filename + role="package">x11/xorg</filename>, but must be enabled by + the following entries in the <filename>/etc/rc.conf</filename> file:</para> <programlisting>hald_enable="YES" @@ -427,14 +452,14 @@ dbus_enable="YES"</programlisting> configuration or use is attempted.</para> <para><application>&xorg;</application> can - often work without any further configuration steps by simply typing at - prompt:</para> + often work without any further configuration steps by + simply typing at prompt:</para> <screen>&prompt.user; <userinput>startx</userinput></screen> - <para>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.</para> + <para>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.</para> <note> <para>Desktop environments like @@ -448,11 +473,9 @@ dbus_enable="YES"</programlisting> appropriate screen settings tool.</para> </note> - <para>Configuration of X11 is - a multi-step process. The first step is to build an initial - configuration file. - As the super user, simply - run:</para> + <para>Configuration of X11 is a multi-step process. The first + step is to build an initial configuration file. As the super + user, simply run:</para> <screen>&prompt.root; <userinput>Xorg -configure</userinput></screen> @@ -475,14 +498,14 @@ dbus_enable="YES"</programlisting> <screen>&prompt.root; <userinput>Xorg -config xorg.conf.new -retro</userinput></screen> <para>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 <keycombo action="simul"> <keycap>Ctrl</keycap> <keycap>Alt</keycap> <keycap>F<replaceable>n</replaceable></keycap> - </keycombo> (<keycap>F1</keycap> for the first virtual console) - and press + </keycombo> (<keycap>F1</keycap> for the first virtual + console) and press <keycombo action="simul"> <keycap>Ctrl</keycap> <keycap>C</keycap> @@ -523,8 +546,8 @@ dbus_enable="YES"</programlisting> <para>The following line will also have to be added to <filename>xorg.conf.new</filename>, in the - <literal>ServerLayout</literal> or <literal>ServerFlags</literal> - section:</para> + <literal>ServerLayout</literal> or + <literal>ServerFlags</literal> section:</para> <programlisting>Option "DontZap" "off"</programlisting> </note> @@ -541,9 +564,9 @@ dbus_enable="YES"</programlisting> <programlisting>Option "AutoAddDevices" "false"</programlisting> - <para>Input devices may then be configured as in previous versions, - along with any other options needed (e.g., keyboard layout - switching).</para> + <para>Input devices may then be configured as in previous + versions, along with any other options needed (e.g., + keyboard layout switching).</para> <note> <para>As previously explained @@ -597,11 +620,11 @@ dbus_enable="YES"</programlisting> <indexterm><primary>X11 tuning</primary></indexterm> <para>The <filename>xorg.conf.new</filename> - 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 <filename>xorg.conf.new</filename> + 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 <filename>xorg.conf.new</filename> under the <literal>"Monitor"</literal> section:</para> <programlisting>Section "Monitor" @@ -612,20 +635,19 @@ dbus_enable="YES"</programlisting> VertRefresh 48-120 EndSection</programlisting> - <para>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 + <para>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.</para> - <para>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:</para> + <para>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:</para> - <programlisting> - Option "DPMS"</programlisting> + <programlisting>Option "DPMS"</programlisting> <indexterm> <primary><filename>xorg.conf</filename></primary> @@ -657,21 +679,21 @@ EndSection</programlisting> 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.</para> + bits per pixel. At this color depth, the accepted + resolution is 1024 by 768 pixels.</para> <para>Finally, write the configuration file and test it using the test mode given above.</para> <note> <para>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. - <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.</para> + troubleshooting process are the X11 log files, which + contain information on each device that the X11 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.</para> </note> <para>If all is well, the configuration @@ -693,7 +715,8 @@ EndSection</programlisting> <title>Advanced Configuration Topics</title> <sect3> - <title>Configuration with &intel; <literal>i810</literal> Graphics Chipsets</title> + <title>Configuration with &intel; <literal>i810</literal> + Graphics Chipsets</title> <indexterm><primary>Intel i810 graphic chipset</primary></indexterm> @@ -703,12 +726,13 @@ EndSection</programlisting> to drive the card. See the &man.agp.4; driver manual page for more information.</para> - <para>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 <filename>/boot/loader.conf</filename>.</para> + <para>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 + <filename>/boot/loader.conf</filename>.</para> </sect3> <sect3> @@ -716,16 +740,18 @@ EndSection</programlisting> <indexterm><primary>widescreen flatpanel configuration</primary></indexterm> - <para>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.</para> - - <para>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:</para> + <para>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.</para> + + <para>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:</para> <itemizedlist> <listitem><para>2560x1600</para></listitem> @@ -736,8 +762,8 @@ EndSection</programlisting> </itemizedlist> <para>At some point, it will be as easy as adding one of these - resolutions as a possible <literal>Mode</literal> in the <literal>Section - "Screen"</literal> as such:</para> + resolutions as a possible <literal>Mode</literal> in the + <literal>Section "Screen"</literal> as such:</para> <programlisting>Section "Screen" Identifier "Screen0" @@ -751,16 +777,18 @@ SubSection "Display" EndSubSection EndSection</programlisting> - <para><application>&xorg;</application> 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.</para> - - <para>If those <literal>ModeLines</literal> do not exist in the drivers, - one might need to give <application>&xorg;</application> a little hint. - Using <filename>/var/log/Xorg.0.log</filename> one can extract - enough information to manually create a <literal>ModeLine</literal> that - will work. Simply look for information resembling this:</para> + <para><application>&xorg;</application> 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.</para> + + <para>If those <literal>ModeLines</literal> do not exist in + the drivers, one might need to give + <application>&xorg;</application> a little hint. Using + <filename>/var/log/Xorg.0.log</filename> one can extract + enough information to manually create a + <literal>ModeLine</literal> that will work. Simply look + for information resembling this:</para> <programlisting>(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</programlisting> (II) MGA(0): Ranges: V min: 48 V max: 85 Hz, H min: 30 H max: 94 kHz, PixClock max 170 MHz</programlisting> <para>This information is called EDID information. Creating a - <literal>ModeLine</literal> from this is just a matter of putting the - numbers in the correct order:</para> + <literal>ModeLine</literal> from this is just a matter of + putting the numbers in the correct order:</para> <programlisting>ModeLine <name> <clock> <4 horiz. timings> <4 vert. timings></programlisting> - <para>So that the <literal>ModeLine</literal> in <literal>Section "Monitor"</literal> + <para>So that the <literal>ModeLine</literal> in + <literal>Section "Monitor"</literal> for this example would look like this:</para> <programlisting>Section "Monitor" @@ -785,8 +814,8 @@ ModeLine "1680x1050" 146.2 1680 1 Option "DPMS" EndSection</programlisting> - <para>Now having completed these simple editing steps, X should start - on your new widescreen monitor.</para> + <para>Now having completed these simple editing steps, X + should start on your new widescreen monitor.</para> </sect3> </sect2> </sect1> @@ -805,25 +834,29 @@ EndSection</programlisting> <sect2 id="type1"> <title>Type1 Fonts</title> - <para>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 - <application>&netscape;</application> 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 - (<filename role="package">x11-fonts/urwfonts</filename>) includes - high quality versions of standard type1 fonts (<trademark class="registered">Times Roman</trademark>, - <trademark class="registered">Helvetica</trademark>, <trademark class="registered">Palatino</trademark> and others). The Freefonts collection - (<filename role="package">x11-fonts/freefonts</filename>) includes - many more fonts, but most of them are intended for use in - graphics software such as the <application>Gimp</application>, 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 - <link linkend="truetype">section on &truetype; fonts</link>.</para> + + <para>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 <application>&netscape;</application> 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 (<filename + role="package">x11-fonts/urwfonts</filename>) includes high + quality versions of standard type1 fonts (<trademark + class="registered">Times Roman</trademark>, + <trademark class="registered">Helvetica</trademark>, <trademark + class="registered">Palatino</trademark> and others). The + Freefonts collection (<filename + role="package">x11-fonts/freefonts</filename>) includes + many more fonts, but most of them are intended for use in + graphics software such as the <application>Gimp</application>, + 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 <link linkend="truetype">section + on &truetype; fonts</link>.</para> <para>To install the above Type1 font collections from the Ports Collection, run the following commands:</para> @@ -831,10 +864,10 @@ EndSection</programlisting> <screen>&prompt.root; <userinput>cd /usr/ports/x11-fonts/urwfonts</userinput> &prompt.root; <userinput>make install clean</userinput></screen> - <para>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 (<filename>/etc/X11/xorg.conf</filename>), - which reads:</para> + <para>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 + (<filename>/etc/X11/xorg.conf</filename>), which reads:</para> <programlisting>FontPath "/usr/local/lib/X11/fonts/URW/"</programlisting> @@ -844,14 +877,16 @@ EndSection</programlisting> <screen>&prompt.user; <userinput>xset fp+ /usr/local/lib/X11/fonts/URW</userinput> &prompt.user; <userinput>xset fp rehash</userinput></screen> - <para>This will work but will be lost when the X session is closed, - unless it is added to the startup file (<filename>~/.xinitrc</filename> - for a normal <command>startx</command> session, - or <filename>~/.xsession</filename> when logging in through a - graphical login manager like <application>XDM</application>). - A third way is to use the new - <filename>/usr/local/etc/fonts/local.conf</filename> file: see the - section on <link linkend="antialias">anti-aliasing</link>.</para> + <para>This will work but will be lost when the X session is + closed, unless it is added to the startup file + (<filename>~/.xinitrc</filename> for a normal + <command>startx</command> session, or + <filename>~/.xsession</filename> when logging in through a + graphical login manager like <application>XDM</application>). + A third way is to use the new + <filename>/usr/local/etc/fonts/local.conf</filename> file: see + the section on <link + linkend="antialias">anti-aliasing</link>.</para> </sect2> <sect2 id="truetype"> @@ -863,25 +898,26 @@ EndSection</programlisting> </indexterm> <para><application>&xorg;</application> 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 <literal>"Module"</literal> section of the - <filename>/etc/X11/xorg.conf</filename> file.</para> + 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 + <literal>"Module"</literal> section of the + <filename>/etc/X11/xorg.conf</filename> file.</para> <programlisting>Load "freetype"</programlisting> - <para>Now make a directory for the &truetype; fonts (for example, + <para>Now make a directory for the &truetype; fonts (for + example, <filename>/usr/local/lib/X11/fonts/TrueType</filename>) - 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 - <application>ttmkfdir</application> to create a - <filename>fonts.dir</filename> 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 <application>ttmkfdir</application> to + create a <filename>fonts.dir</filename> file, so that the X + font renderer knows that these new files have been installed. <command>ttmkfdir</command> is available from the FreeBSD Ports Collection as <filename role="package">x11-fonts/ttmkfdir</filename>.</para> @@ -901,12 +937,12 @@ EndSection</programlisting> <para>That's it. Now <application>&netscape;</application>, <application>Gimp</application>, - <application>&staroffice;</application>, 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 - <application>&staroffice;</application>) will look much better - now.</para> + <application>&staroffice;</application>, 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 <application>&staroffice;</application>) will + look much better now.</para> </sect2> <sect2 id="antialias"> @@ -931,7 +967,8 @@ EndSection</programlisting> <filename>~/.fonts/</filename> are automatically made available for anti-aliasing to Xft-aware applications. Most recent applications are Xft-aware, including - <application>KDE</application>, <application>GNOME</application>, and + <application>KDE</application>, + <application>GNOME</application>, and <application>Firefox</application>.</para> <para>In order to control which fonts are anti-aliased, or to @@ -945,16 +982,16 @@ EndSection</programlisting> <indexterm><primary>XML</primary></indexterm> - <para>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 <literal><fontconfig></literal> tag:</para> + <para>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 <literal><fontconfig></literal> + tag:</para> <programlisting> <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> - <fontconfig> - </programlisting> + <fontconfig></programlisting> <para>As previously stated, all fonts in <filename>/usr/local/lib/X11/fonts/</filename> as well as @@ -972,11 +1009,12 @@ EndSection</programlisting> <screen>&prompt.root; <userinput>fc-cache -f</userinput></screen> - <para>Anti-aliasing makes borders slightly fuzzy, which makes very - small text more readable and removes <quote>staircases</quote> 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:</para> + <para>Anti-aliasing makes borders slightly fuzzy, which makes + very small text more readable and removes + <quote>staircases</quote> 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:</para> <programlisting> <match target="font"> <test name="size" compare="less"> @@ -1000,9 +1038,9 @@ EndSection</programlisting> <para>Spacing for some monospaced fonts may also be inappropriate with anti-aliasing. This seems to be an issue with - <application>KDE</application>, in particular. One possible fix for - this is to force the spacing for such fonts to be 100. Add the - following lines:</para> + <application>KDE</application>, in particular. One possible + fix for this is to force the spacing for such fonts to be 100. + Add the following lines:</para> <programlisting> <match target="pattern" name="family"> <test qual="any" name="family"> @@ -1051,23 +1089,25 @@ EndSection</programlisting> <para>Once you have finished editing <filename>local.conf</filename> make sure you end the file - with the <literal></fontconfig></literal> tag. Not doing this will cause - your changes to be ignored.</para> + with the <literal></fontconfig></literal> tag. Not + doing this will cause your changes to be ignored.</para> - <para>Finally, users can add their own settings via their personal - <filename>.fonts.conf</filename> files. To do this, each user should - simply create a <filename>~/.fonts.conf</filename>. This file must - also be in XML format.</para> + <para>Finally, users can add their own settings via their + personal <filename>.fonts.conf</filename> files. To do + this, each user should simply create a + <filename>~/.fonts.conf</filename>. This file must also be + in XML format.</para> <indexterm><primary>LCD screen</primary></indexterm> <indexterm><primary>Fonts</primary> <secondary>LCD screen</secondary></indexterm> *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201301111710.r0BHA4U5071639>