Documentation improvements.

README

@@ -52,7 +52,7 @@ FreeBSD info:
 Solaris info:
   You will most likely need to build Wine with the GNU toolchain
   (gcc, gas, etc.). Warning : installing gas does *not* ensure that it
-  will be used by gcc. Recompiling gcc after installing gas or 
+  will be used by gcc. Recompiling gcc after installing gas or
   symlinking cc, as and ld to the gnu tools is said to be necessary.
 
 NetBSD info:
@@ -86,10 +86,15 @@ are compiled with optimization, often due to problems with header file
 management. pgcc currently doesn't work with Wine. The cause of this problem
 is unknown.
 
+Of course you also need "make" (most likely GNU make).
+
 You also need flex version 2.5 or later and yacc.
 Bison will work as a replacement for yacc. If you are
 using RedHat or Debian, install the flex and bison packages.
 
+For the automatic processing of the test suite scripts, you also need
+libperl development header support (libperl-dev package on Debian).
+
 For requirements in case you intend to build the documentation yourself,
 see "DOCUMENTATION" section.
 
@@ -102,7 +107,7 @@ to build Wine:
 make depend
 make
 
-This will build the program "wine" and numerous support libraries/binaries.  
+This will build the program "wine" and numerous support libraries/binaries.
 The program "wine" will load and run Windows executables.
 The library "libwine" ("Winelib") can be used to compile and link
 Windows source code under Unix.
@@ -217,16 +222,13 @@ Bugs:	Report bugs to Wine Bugzilla at http://bugs.winehq.com/.
 	Please read the file documentation/bugs.sgml to see what
 	information is required.
 
-HOWTO:	The Wine HOWTO (outdated !) is available at
-	http://www.westfalen.de/witch/wine-HOWTO.txt .
-
 IRC:	Online help is available at channel #WineHQ on irc.openprojects.net.
 
 CVS:	The current Wine development tree is available through CVS.
 	Go to http://www.winehq.com/development/ for more information.
 
 Mailing lists:
-	There are several mailing lists for Wine developers; see 
+	There are several mailing lists for Wine developers; see
 	http://www.winehq.com/development/#ml for more information.
 
 If you add something, or fix a bug, please send a patch (in 'diff -u'

documentation/fonts.sgml

@@ -106,7 +106,8 @@ STUB: AddFontResource( SOMEFILE.FON )
           if you're on FreeBSD you can use the port in
           <filename>/usr/ports/x11-servers/Xfstt</filename>.  And
           there is <command>xfsft</command> which uses the freetype
-          library, see <filename>documentation/ttfserver</filename>).
+          library, see <link linkend="ttfont-server">freetype</link>
+	  description).
         </para>
         <para>
           However, there is a possibility of the native TrueType

documentation/implementation.sgml

@@ -397,7 +397,7 @@ XXXX > YY @ ZZZZ:ZZZZ
 0x37a > 04 @ 0297:0211
       </programlisting>
       <para>
-        As you can see their is a repeating structure starting at
+        As you can see there is a repeating structure starting at
         address <literal>0297:01ec</literal> that consists of four io
         accesses on the parallel port. Looking at it the first io
         access writes a changing byte to the data port the second

documentation/installing.sgml

@@ -153,8 +153,10 @@ C:\                Root directory of primary disk drive
           And there are of course DLLs that wine does not currently
           implement very well (or at all). If you do not have a real
           Windows you can steal necessary DLLs from, you can always
-          get some from a DLL archive such as
-          <ulink url="http://solo.abac.com/dllarchive/">http://solo.abac.com/dllarchive/</ulink>.
+          get some from one of the Windows DLL archive sites
+	  that can be found via internet search engine.
+	  Please make sure to obey any licenses on the DLLs you fetch...
+	  (some are redistributable, some aren't).
         </para>
       </sect2>
     </sect1>

documentation/samples/config

@@ -26,6 +26,7 @@ WINE REGISTRY Version 2
 "Path" = "/mnt/fd0"
 "Type" = "floppy"
 "Label" = "Floppy"
+"Filesystem" = "win95"
 "Serial" = "87654321"
 "Device" = "/dev/fd0"
 
@@ -174,6 +175,13 @@ WINE REGISTRY Version 2
 ;"DefaultSerif" = "-cronyx-times-"
 ;"DefaultSansSerif" = "-cronyx-helvetica-"
 
+; the TrueType font dirs you want to make accessible to wine
+[FontDirs]
+;"dir1" = "/usr/X11R6/lib/X11/fonts/TrueType"
+;"dir2" = "/usr/share/fonts/truetype"
+;"dir3" = "/usr/X11R6/lib/X11/fonts/TT"
+;"dir4" = "/usr/share/fonts/TT"
+
 [serialports]
 "Com1" = "/dev/ttyS0"
 "Com2" = "/dev/ttyS1"

documentation/wine.conf.man

@@ -153,6 +153,26 @@ Tells Wine which graphics driver to use. Normally you'd want to use
 x11drv (for X11). In case you want to run programs as text console/TTY only
 without having Wine rely on X11 support, then use ttydrv.
 .PP
+.B [Version]
+.br
+.I format: """Windows""=""<version string>"""
+.br
+default: none; chosen by semi-intelligent detection mechanism based on DLL environment
+.br
+Used to specify which Windows version to return to programs (forced value,
+overrides standard detection mechanism !).
+Valid settings are e.g. "win31", "win95", "win98", "win2k", "winxp".
+Also valid as an AppDefaults setting (recommended/preferred use).
+.PP
+.I format: """DOS""=""<version string>"""
+.br
+default: "<Windows version specific>"
+.br
+Used to specify the DOS version that should be returned to programs.
+Only takes effect in case Wine acts as "win31" Windows version !
+Common DOS version settings include 6.22, 6.20, 6.00, 5.00, 4.00, 3.30, 3.10.
+Also valid as an AppDefaults setting (recommended/preferred use).
+.PP
 .B [DllOverrides]
 .br
 .I format: """modulename""=""native,so,builtin"""