loader/wine.man: update man page

Sun Apr 19 19:27:16 CDT 2009

Wow, lots of old stuff in there.

-- 
-Austin
-------------- next part --------------

diff --git a/loader/wine.man.in b/loader/wine.man.in
index 0f71f95..d9fe908 100644
--- a/loader/wine.man.in
+++ b/loader/wine.man.in
@@ -1,5 +1,5 @@
 .\" -*- nroff -*-
-.TH WINE 1 "October 2005" "@PACKAGE_STRING@" "Windows On Unix"
+.TH WINE 1 "April 2009" "@PACKAGE_STRING@" "Windows On Unix"
 .SH NAME
 wine \- run Windows programs on Unix
 .SH SYNOPSIS
@@ -22,14 +22,14 @@ For debugging wine, use
 .B winedbg
 instead.
 .PP
-For running CUI executables (Windows console programs), use
+For running CLI executables (Windows console programs), use
 .B wineconsole
 instead of
 .B wine.
 This will display all the output in a separate windows (this requires X11 to
 run). Not using
 .B wineconsole
-for CUI programs will only provide very limited console support, and your
+for CLI programs will only provide very limited console support, and your
 program might not function properly.
 .PP
 When invoked with
@@ -40,12 +40,10 @@ as the only argument,
 .B wine
 will simply print a small help message or its version respectively and exit.
 .SH PROGRAM/ARGUMENTS
-The program name may be specified in DOS format (
-.I
-C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE)
-or in Unix format (
-.I /msdos/windows/sol.exe
-).  You may pass arguments to the program being executed by adding them 
+The program name should be specified in DOS format (
+.I C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE)
+). You may pass arguments to the program 
+being executed by adding them 
 to the end of the command line invoking
 .B wine
 (such as: wine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT).
@@ -56,10 +54,11 @@ wine C:\(rs\(rsProgram\(rs Files\(rs\(rsMyPrg\(rs\(rstest.exe
 .PP
 .SH ENVIRONMENT VARIABLES
 .B wine
-makes the environment variables of the shell from which
+takes the environment variables of the shell from which
 .B wine
-is started accessible to the windows/dos processes started. So use the
-appropriate syntax for your shell to enter environment variables you need.
+is started. These environmental variables are also made accessible to the
+windows/dos processes started. So use the appropriate syntax for your shell to 
+enter environment variables you need.
 .TP 
 .I WINEPREFIX
 If set, the content of this variable is taken as the name of the directory where
@@ -74,7 +73,7 @@ All
 processes using the same 
 .B wineserver
 (i.e.: same user) share certain things like registry, shared memory,
-and config file.
+and device mappings.
 By setting 
 .I WINEPREFIX
 to different values for different 
@@ -114,11 +113,11 @@ or
 If
 .I class
 is not specified, all debugging messages for the specified
-channel are turned on.  Each channel will print messages about a particular
+channel are turned on. Each channel will print messages about a particular
 component of 
-.B wine.  
+.B wine. 
 The following character can be either + or - to switch the specified
-channel on or off respectively.  If there is no
+channel on or off respectively. If there is no
 .I class
 part before it, a leading + can be omitted. Note that spaces are not
 allowed anywhere in the string.
@@ -126,11 +125,12 @@ allowed anywhere in the string.
 Examples:
 .TP
 WINEDEBUG=warn+all
-will turn on all warning messages (recommended for debugging).
+will turn on all warning messages (recommended for debugging). Please don't attach
+this to bug reports, unless asked for it specifically.
 .br
 .TP
 WINEDEBUG=warn+dll,+heap
-will turn on DLL warning messages and all heap messages.  
+will turn on DLL warning messages and all heap messages.
 .br
 .TP
 WINEDEBUG=fixme-all,warn+cursor,+relay
@@ -158,8 +158,8 @@ Wine will also look in
 .TP
 .I WINEDLLOVERRIDES
 Defines the override type and load order of dlls used in the loading
-process for any dll. The default is set in the configuration
-file. There are currently two types of libraries that can be loaded
+process for any dll. The default is set in the registry using .B winecfg.
+There are currently two types of libraries that can be loaded
 into a process' address space: Native windows dlls (
 .I native
 ), 
@@ -175,7 +175,7 @@ Each dll may have its own specific load order. The load order
 determines which version of the dll is attempted to be loaded into the
 address space. If the first fails, then the next is tried and so
 on. Multiple libraries with the same load order can be separated with
-commas. It is also possible to use specify different loadorders for
+commas. It is also possible to use different load orders for
 different libraries by separating the entries by ";".
 .PP
 The load order for a 16-bit dll is always defined by the load order of
@@ -189,19 +189,18 @@ Examples:
 .TP
 WINEDLLOVERRIDES="comdlg32,shell32=n,b"
 .br
-Try to load comdlg32 and shell32 as native windows dll first and try
+Try to load comdlg32 and shell32 as native windows dlls first and try
 the builtin version if the native load fails.
 .TP
 WINEDLLOVERRIDES="comdlg32,shell32=n;c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b"
 .br
 Try to load the libraries comdlg32 and shell32 as native windows dlls. Furthermore, if 
-an application request to load c:\(rsfoo\(rsbar\(rsbaz.dll load the builtin library baz. 
+an application requests to load c:\(rsfoo\(rsbar\(rsbaz.dll load the builtin library baz. 
 .TP
 WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n;oleaut32="
 .br
-Try to load comdlg32 as builtin first and try the native version if
-the builtin load fails; load shell32 always as builtin and comctl32
-always as native. Oleaut32 will be disabled.
+Try to load comdlg32 as builtin first and try the native version if the builtin 
+load fails. Use builtin shell32 and native comctl32. Oleaut32 will be disabled.
 .RE
 .TP
 .I DISPLAY
@@ -227,10 +226,15 @@ The
 .B wine 
 program loader.
 .TP
+.I @bindir@/winecfg
+The 
+.B wine 
+configuration tool.
+.TP
 .I @bindir@/wineconsole
 The 
 .B wine 
-program loader for CUI (console) applications.
+program loader for CLI (console) applications.
 .TP
 .I @bindir@/wineserver
 The 
@@ -274,31 +278,29 @@ license is in the file
 in the top-level directory of the source distribution.
 .SH BUGS
 .PP
-A status report on many applications is available from
-.I http://appdb.winehq.org.
+Many applications have test results available at
+.I http://appdb.winehq.org,
+showing what works, does not work, current bugs and workarounds, etc.
 Please add entries to this list for applications you currently run, if
-there is no entry for this application.
+there is no entry for your application.
 .PP
 Bug reports may be posted to Wine Bugzilla
-.I http://bugs.winehq.org
-If you want to post a bug report, please read the file
-.I documentation/bugs.sgml
-in the 
-.B wine 
-source to see what information is necessary
+.I http://bugs.winehq.org.
+If you want to post a bug report, please read
+.I http://wiki.winehq.org/Bugs.
 .PP
 Problems and suggestions with this manpage please also report to
-.I http://bugs.winehq.org
+.I http://bugs.winehq.org.
 .SH AVAILABILITY
 The most recent public version of 
 .B wine
 can be downloaded from
 .I http://www.winehq.org/download
 .PP
-The latest snapshot of the code may be obtained via GIT.  For information
+The latest snapshot of the code may be obtained via GIT. For information
 on how to do this, please see
 .I
-http://www.winehq.org/site/git
+http://wiki.winehq.org/GitWine
 .PP
 WineHQ, the
 .B wine
@@ -315,4 +317,5 @@ mailing lists at
 .I http://www.winehq.org/forums
 
 .SH "SEE ALSO"
-.BR wineserver (1),\  winedbg (1)
+.BR wineserver (1),\ 
+.BR winedbg (1)
