os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Typos, grammar, add some markup. Make some parts sound better.

Browse source
This commit is contained in:
Daniel Harris 2002-03-28 17:50:23 +00:00
parent bfddfc7aec
commit b45607ea08
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=12606
1 changed files with 34 additions and 34 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

68
en_US.ISO8859-1/books/handbook/x11/chapter.sgml
View file

@ -11,7 +11,7 @@
<title>Synopsis</title>
<para>FreeBSD uses XFree86 to provide users with a powerful
graphical user interface. XFree86 is a open-source
graphical user interface. XFree86 is an open-source
implementation of the X Window System. This chapter
will cover installation and configuration of XFree86 on a
FreeBSD system. For more information on XFree86 and
@ -46,7 +46,7 @@
MacOS.</para>
<para>It is not necessary to understand all of the details of various
X components and how they interact, however, some basic knowledge makes
X components and how they interact; however, some basic knowledge makes
it possible to take advantage of X's strengths.</para>
<sect2>
@ -338,7 +338,7 @@
detection does not work correctly.</para>
<para>Video memory on the graphic adapter determines the
resolution and color depth the system can run at. This is
resolution and color depth which the system can run at. This is
important to know so the user knows the limitations of the
system.</para>
@ -367,12 +367,12 @@
<para>The next step is to test the existing
configuration to verify that <application>XFree86</application>
can work with the graphics
hardware on the target system. To preform this task, the user
hardware on the target system. To perform this task, the user
needs to run:</para>
<screen>&prompt.root; XFree86 -xf86config XF86Config.new</screen>
<para>If a black and grey grid and an X mouse cursor appears, then
<para>If a black and grey grid and an X mouse cursor appear,
the configuration was successful. To exit the test, just press
<keycombo action="simul">
<keycap>Ctrl</keycap>
@ -383,8 +383,8 @@
<indexterm><primary>XFree86 4 Tuning</primary></indexterm>
<para>Next, tune the <filename>XF86Config.new</filename>
configuration file to taste. Open up the file in a text editor such
as &man.emacs.1; or &man.ee.1;. The first thing to do is add the
configuration file to taste. Open the file in a text editor such
as &man.emacs.1; or &man.ee.1;. First, add the
frequencies for the target system's monitor. These are usually
expressed as a horizontal and vertical synchronization rate. These
values are added to the <filename>XF86Config.new</filename> file
@ -394,17 +394,17 @@
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
Horizsync 30-107
HorizSync 30-107
VertRefresh 48-120
EndSection</programlisting>
<para>The <varname>Horizsync</varname> and
<para>The <varname>HorizSync</varname> and
<varname>VertRefresh</varname> keywords may not exist in the
configuration file. If they do not, they need to be added, with
the correct horizontal synchronization rate placed after the
<varname>Horizsync</varname> keyword and the vertical
synchronization rate after the <varname>VertRefresh</varname>
keyword. In the example above the target monitor's rates where
keyword. In the example above the target monitor's rates were
entered.</para>
<para>X allows DPMS (Energy Star) features to be used with capable
@ -421,8 +421,8 @@ EndSection</programlisting>
</indexterm>
<para>While the <filename>XF86Config.new</filename>
configuration file is still open in an editor, next select what
the default resolution and color depth is desired. This is
configuration file is still open in an editor, select
the default resolution and color depth desired. This is
defined in the <literal>Screen</literal> section:</para>
<programlisting>Section "Screen"
@ -440,24 +440,24 @@ EndSection</programlisting>
the color depth to run at by default. This can be overridden
with the <command>-bpp</command> command line switch to
&man.XFree86.1;
The Modes keyword
The <varname>Modes</varname> keyword
describes the resolution to run at for the given color depth.
In the example above, the default color depth is twenty four
In the example above, the default color depth is twenty-four
bits per pixel. At this color depth, the accepted resolution is
one thousand twenty four pixels by seven hundred and sixty eight
one thousand twenty-four pixels by seven hundred and sixty-eight
pixels.</para>
<para>To run at a resolution of one thousand twenty four pixels by
seven hundred sixty eight pixels at twenty four bits per pixel,
then add the <varname>DefaultDepth</varname> keyword with the
value of twenty four, and add to the <varname>"Display"</varname>
subsection with the desired Depth the Modes keyword with the
<para>To run at a resolution of one thousand twenty-four pixels by
seven hundred sixty-eight pixels at twenty-four bits per pixel,
add the <varname>DefaultDepth</varname> keyword with the
value of twenty-four, and add to the <varname>"Display"</varname>
subsection with the desired Depth the <varname>Modes</varname> keyword with the
resolution the user wishes to run at. Note that only VESA
standard modes are supported as defined by the target system's
graphics hardware.</para>
<para>Finally, write out the configuration file and test it using
the test mode given above. If all is well, then the configuration
<para>Finally, write the configuration file and test it using
the test mode given above. If all is well, the configuration
file needs to be installed in a common location where
&man.XFree86.1;
can find it.
@ -486,7 +486,7 @@ EndSection</programlisting>
<para>Configuration with Intel i810 integrated chipsets
requires the <devicename>agpgart</devicename>
AGP programming interface for <application>XFree86</application>
to drive the card. To <devicename>agpgart</devicename>,
to drive the card. To use <devicename>agpgart</devicename>,
the <filename>agp.ko</filename> kernel loadable module needs to
be loaded into the kernel with &man.kldload.8;. This can be
done automatically with the &man.loader.8; at boot time.
@ -503,7 +503,7 @@ EndSection</programlisting>
<screen>&prompt.root; cd /dev
&prompt.root; sh MAKEDEV agpgart</screen>
<para>This will allow configuration the hardware as any other
<para>This will allow configuration of the hardware as any other
graphics board.</para>
<para>If you are using XFree86 4.1.0 (or later) and messages
@ -801,9 +801,9 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono";</programl
<screen>ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure</screen>
By default this entry is disabled, and in order to enable it
By default this entry is disabled; in order to enable it
change field 5 from <literal>off</literal> to
<literal>on</literal> and then restart &man.init.8; using the
<literal>on</literal> and restart &man.init.8; using the
directions in <xref linkend="term-hup">. The first field, the
name of the terminal this program will manage, is
<literal>ttyv8</literal>. This means that
@ -972,7 +972,7 @@ DisplayManager.requestPort: 0</screen>
comments in app-defaults files begin with a <quote>!</quote>
character, not the usual <quote>#</quote>. More strict
access controls may be desired. Look at the example
entries in <filename>Xaccess</filename> file, and refer to the
entries in <filename>Xaccess</filename>, and refer to the
&man.xdm.1; manual page.</para>
</sect2>
@ -1006,8 +1006,8 @@ DisplayManager.requestPort: 0</screen>
<para>This section describes the different desktop environments
available for X on FreeBSD. A <quote>desktop environment</quote>
will mean anything ranging from a simple window manager, to a
complete suite of desktop applications such as
can mean anything ranging from a simple window manager to a
complete suite of desktop applications, such as
<application>KDE</application> or <application>GNOME</application>.
</para>
@ -1036,7 +1036,7 @@ DisplayManager.requestPort: 0</screen>
<para>The easiest way to install
<application>GNOME</application> is through the
<quote>Desktop Configuration</quote> menu during the FreeBSD
installation process as described in Chapter 2. They can also
installation process as described in Chapter 2. It can also
be easily installed from a package or the ports
collection:</para>
@ -1100,7 +1100,7 @@ DisplayManager.requestPort: 0</screen>
<filename>/usr/X11R6/share/doc/gdkxft/README</filename> file
carefully.</para>
<para>Then, all that is needed is to do is tell gtk
<para>Then, all that is needed is to tell gtk
applications to look for their font-rendering functions in
<filename>libgdkxft.so</filename> before looking in the
standard place, <filename>libgdk.so</filename>. This is
@ -1179,7 +1179,7 @@ export LD_PRELOAD
<sect3 id="x11-wm-kde2-install">
<title>Installing KDE2</title>
<para>Just like with <application>GNOME</application> or any
<para>Just as with <application>GNOME</application> or any
other desktop environment, the easiest way to install
<application>KDE</application> is through the <quote>Desktop
Configuration</quote> menu during the FreeBSD installation
@ -1205,11 +1205,11 @@ export LD_PRELOAD
<screen>&prompt.user; <userinput>echo "/usr/local/bin/startkde" &gt; ~/.xinitrc</userinput></screen>
<para>Now, whenever invoke X Window System with <command>startx</command>,
<para>Now, whenever the X Window System is invoked with <command>startx</command>,
<application>KDE2</application> will be the desktop.</para>
<para>If a display manager such as
<application>xdm</application> is being used, then
<application>xdm</application> is being used, the
configuration is slightly different. Edit the
<filename>.xsession</filename> file instead. Instructions
for <application>kdm</application> are described later in