svn commit: r42895 - head/en_US.ISO8859-1/books/handbook/x11
Dru Lavigne
dru at FreeBSD.org
Tue Oct 8 15:11:07 UTC 2013
Author: dru
Date: Tue Oct 8 15:11:06 2013
New Revision: 42895
URL: http://svnweb.freebsd.org/changeset/doc/42895
Log:
White space fix only. Translators can 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 Tue Oct 8 14:56:51 2013 (r42894)
+++ head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Tue Oct 8 15:11:06 2013 (r42895)
@@ -79,25 +79,28 @@
<title>Terminology</title>
<para>While it is not necessary to understand all of the details
- of the various components in the X Window System and how they interact, some basic
- knowledge of these components can be useful:</para>
+ of the various components in the X Window System and how they
+ interact, some basic knowledge of these components can be
+ useful:</para>
<variablelist>
<varlistentry>
<term>X server</term>
-
+
<listitem>
- <para>X was designed from the beginning to be network-centric,
- and adopts a <quote>client-server</quote> model. In this 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
- handling input or output from other devices such as a tablet
- or a video projector. 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>X was designed from the beginning to be
+ network-centric, and adopts a <quote>client-server</quote>
+ model. In this 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 handling input or output from
+ other devices such as a tablet or a video projector.
+ 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>
</listitem>
</varlistentry>
@@ -105,22 +108,22 @@
<term>X client</term>
<listitem>
- <para>Each X application, such as
- <application>XTerm</application> or
- <application>Firefox</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. It
- is also possible to run the X server on a less powerful
- computer and to run the X applications on a more
- powerful system.
- In this scenario, the communication between the X
- client and server takes place over the network.</para>
+ <para>Each X application, such as
+ <application>XTerm</application> or
+ <application>Firefox</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. It
+ is also possible to run the X server on a less powerful
+ computer and to run the X applications on a more
+ powerful system. In this scenario, the communication
+ between the X client and server takes place over the
+ network.</para>
</listitem>
</varlistentry>
@@ -128,27 +131,27 @@
<term>window manager</term>
<listitem>
- <para>X does not dictate what windows
- should look like on screen, how to move them around with the
- mouse, which keystrokes should be used to move between 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 a
- separate window manager application. There
- are <ulink
- url="http://xwinman.org/">dozens of window managers</ulink>
- available. Each window manager provides a
- different look and feel: some support
- virtual desktops, some allow customized
- keystrokes to manage the desktop, some have a
- <quote>Start</quote> button, and some are
- themeable, allowing a complete change of the desktop's
- look-and-feel. Window managers are
- available in the <filename>x11-wm</filename> category of the
- Ports Collection.</para>
-
- <para>Each window manager uses a different configuration
- mechanism. Some expect configuration file written by hand while
- others provide graphical tools for most configuration tasks.</para>
+ <para>X does not dictate what windows should look like on
+ screen, how to move them around with the mouse, which
+ keystrokes should be used to move between 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 a separate
+ window manager application. There are <ulink
+ url="http://xwinman.org/">dozens of window
+ managers</ulink> available. Each window manager
+ provides a different look and feel: some support virtual
+ desktops, some allow customized keystrokes to manage the
+ desktop, some have a <quote>Start</quote> button, and
+ some are themeable, allowing a complete change of the
+ desktop's look-and-feel. Window managers are available
+ in the <filename>x11-wm</filename> category of the
+ Ports Collection.</para>
+
+ <para>Each window manager uses a different configuration
+ mechanism. Some expect configuration file written by
+ hand while others provide graphical tools for most
+ configuration tasks.</para>
</listitem>
</varlistentry>
@@ -156,66 +159,68 @@
<term>desktop environment</term>
<listitem>
- <para><application>KDE</application> and
- <application>GNOME</application> are considered to be desktop environments
- as they include an entire suite of applications for performing
- common desktop tasks. These may include office suites, web
- browsers, and games.</para>
+ <para><application>KDE</application> and
+ <application>GNOME</application> are considered to be
+ desktop environments as they include an entire suite of
+ applications for performing common desktop tasks. These
+ may include office suites, web browsers, and games.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>focus policy</term>
- <listitem>
- <para>The window manager is responsible for the
- mouse focus policy. This policy provides
- some means for choosing which window is actively
- receiving keystrokes and it should also visibly indicate which
- window is currently active.</para>
-
- <para>One focus policy is called
- <quote>click-to-focus</quote>. In this model, a window becomes active
- upon receiving a mouse click. In the
- <quote>focus-follows-mouse</quote> policy, the window that is under the mouse pointer
- has focus and the focus is changed by pointing at
- another window. If the mouse is over the root window, then this
- window is focused. In the <quote>sloppy-focus</quote> model, if
- the mouse is moved over the root window, the most recently used window still
- has the focus. With sloppy-focus, focus
- is only changed when the cursor enters a new
- window, and not when exiting the current
- window. In the <quote>click-to-focus</quote> policy, 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.</para>
-
- <para>Different window managers
- support different focus models. All of them support
- click-to-focus, and the majority of them also support other policies.
- Consult the
- documentation for the window manager to determine which
- focus models are available.</para>
- </listitem>
- </varlistentry>
+ <listitem>
+ <para>The window manager is responsible for the mouse focus
+ policy. This policy provides some means for choosing
+ which window is actively receiving keystrokes and it
+ should also visibly indicate which window is currently
+ active.</para>
+
+ <para>One focus policy is called
+ <quote>click-to-focus</quote>. In this model, a window
+ becomes active upon receiving a mouse click. In the
+ <quote>focus-follows-mouse</quote> policy, the window
+ that is under the mouse pointer has focus and the focus
+ is changed by pointing at another window. If the mouse
+ is over the root window, then this window is focused.
+ In the <quote>sloppy-focus</quote> model, if the mouse
+ is moved over the root window, the most recently used
+ window still has the focus. With sloppy-focus, focus
+ is only changed when the cursor enters a new window, and
+ not when exiting the current window. In the
+ <quote>click-to-focus</quote> policy, 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.</para>
+
+ <para>Different window managers support different focus
+ models. All of them support click-to-focus, and the
+ majority of them also support other policies. Consult
+ the documentation for the window manager to determine
+ which focus models are available.</para>
+ </listitem>
+ </varlistentry>
<varlistentry>
<term>widgets</term>
<listitem>
- <para>Widget is a term for all of the items in
- the user interface that can be clicked or manipulated in
- some way. This includes buttons, check boxes, radio buttons, icons, and lists.
- A widget toolkit is a set of widgets used to create
- graphical applications. There are several popular widget toolkits, including Qt, used by
- <application>KDE</application>, and GTK+, used by
- <application>GNOME</application>. As a result, applications will have a
- different look and feel, depending upon which widget toolkit
- was used to create the application.</para>
+ <para>Widget is a term for all of the items in the user
+ interface that can be clicked or manipulated in some way.
+ This includes buttons, check boxes, radio buttons, icons,
+ and lists. A widget toolkit is a set of widgets used to
+ create graphical applications. There are several popular
+ widget toolkits, including Qt, used by
+ <application>KDE</application>, and GTK+, used by
+ <application>GNOME</application>. As a result,
+ applications will have a different look and feel,
+ depending upon which widget toolkit was used to create
+ the application.</para>
</listitem>
- </varlistentry>
- </variablelist>
+ </varlistentry>
+ </variablelist>
</sect1>
<sect1 id="x-install">
More information about the svn-doc-all
mailing list