From b45607ea081c4b8402660338df5955ea7b9884c0 Mon Sep 17 00:00:00 2001 From: Daniel Harris Date: Thu, 28 Mar 2002 17:50:23 +0000 Subject: [PATCH] Typos, grammar, add some markup. Make some parts sound better. --- .../books/handbook/x11/chapter.sgml | 68 +++++++++---------- 1 file changed, 34 insertions(+), 34 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/x11/chapter.sgml b/en_US.ISO8859-1/books/handbook/x11/chapter.sgml index 8454745d9f..982d649632 100644 --- a/en_US.ISO8859-1/books/handbook/x11/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/x11/chapter.sgml @@ -11,7 +11,7 @@ Synopsis 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. 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. @@ -338,7 +338,7 @@ detection does not work correctly. 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. @@ -367,12 +367,12 @@ The next step is to test the existing configuration to verify that XFree86 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: &prompt.root; XFree86 -xf86config XF86Config.new - If a black and grey grid and an X mouse cursor appears, then + If a black and grey grid and an X mouse cursor appear, the configuration was successful. To exit the test, just press Ctrl @@ -383,8 +383,8 @@ XFree86 4 Tuning Next, tune the XF86Config.new - 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 XF86Config.new file @@ -394,17 +394,17 @@ Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" - Horizsync 30-107 + HorizSync 30-107 VertRefresh 48-120 EndSection - The Horizsync and + The HorizSync and VertRefresh 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 Horizsync keyword and the vertical synchronization rate after the VertRefresh - keyword. In the example above the target monitor's rates where + keyword. In the example above the target monitor's rates were entered. X allows DPMS (Energy Star) features to be used with capable @@ -421,8 +421,8 @@ EndSection While the XF86Config.new - 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 Screen section: Section "Screen" @@ -440,24 +440,24 @@ EndSection the color depth to run at by default. This can be overridden with the -bpp command line switch to &man.XFree86.1; - The Modes keyword + The Modes 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. - 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 DefaultDepth keyword with the - value of twenty four, and add to the "Display" - subsection with the desired Depth the Modes keyword with the + 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 DefaultDepth keyword with the + value of twenty-four, and add to the "Display" + subsection with the desired Depth the Modes 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. - Finally, write out the configuration file and test it using - the test mode given above. If all is well, then the configuration + 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 Configuration with Intel i810 integrated chipsets requires the agpgart AGP programming interface for XFree86 - to drive the card. To agpgart, + to drive the card. To use agpgart, the agp.ko 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 &prompt.root; cd /dev &prompt.root; sh MAKEDEV agpgart - This will allow configuration the hardware as any other + This will allow configuration of the hardware as any other graphics board. If you are using XFree86 4.1.0 (or later) and messages @@ -801,9 +801,9 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono";ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure - 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 off to - on and then restart &man.init.8; using the + on and restart &man.init.8; using the directions in . The first field, the name of the terminal this program will manage, is ttyv8. This means that @@ -972,7 +972,7 @@ DisplayManager.requestPort: 0 comments in app-defaults files begin with a ! character, not the usual #. More strict access controls may be desired. Look at the example - entries in Xaccess file, and refer to the + entries in Xaccess, and refer to the &man.xdm.1; manual page. @@ -1006,8 +1006,8 @@ DisplayManager.requestPort: 0 This section describes the different desktop environments available for X on FreeBSD. A desktop environment - 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 KDE or GNOME. @@ -1036,7 +1036,7 @@ DisplayManager.requestPort: 0 The easiest way to install GNOME is through the Desktop Configuration 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: @@ -1100,7 +1100,7 @@ DisplayManager.requestPort: 0 /usr/X11R6/share/doc/gdkxft/README file carefully. - Then, all that is needed is to do is tell gtk + Then, all that is needed is to tell gtk applications to look for their font-rendering functions in libgdkxft.so before looking in the standard place, libgdk.so. This is @@ -1179,7 +1179,7 @@ export LD_PRELOAD Installing KDE2 - Just like with GNOME or any + Just as with GNOME or any other desktop environment, the easiest way to install KDE is through the Desktop Configuration menu during the FreeBSD installation @@ -1205,11 +1205,11 @@ export LD_PRELOAD &prompt.user; echo "/usr/local/bin/startkde" > ~/.xinitrc - Now, whenever invoke X Window System with startx, + Now, whenever the X Window System is invoked with startx, KDE2 will be the desktop. If a display manager such as - xdm is being used, then + xdm is being used, the configuration is slightly different. Edit the .xsession file instead. Instructions for kdm are described later in