Hi all!

While working on the translation of the (main) manpage, I noticed a few
issues in the English version and started working on a patch. That was
quite some time ago, I had little spare time lately and didn't get
around to finish and send it in. So I figured I just take what I have
now and ask you guys for comments. I appreciate any remarks or
suggestions.

Thanks,
Julian

Notes:

I had a change similar to Frédéric's, mentioning wine can run 64-bit
programs now. He was quicker and I like his wording better. I had
something like "[...]or Win64 executable (if your version of wine was
compiled with 64-bit support)."
I guess that would be more confusing to people using their distro's wine
packages and people compiling their own wine know that anyway.
Do you agree or do you think it's better to be more specific?

CUI -> CLI:
According to Google and Wikipedia, CLI is more common.

-.BR @bindir@/wineserver ,
+.IR @bindir@/wineserver ,
and following, similar changes:

This is the way it is formatted in the wineserver manpage. I noticed
there is no uniform style across our manpages, so we should have a
guideline.
Should paths be bold or italic/underlined?


>From 66391fbb22bdb150333b99e05250df4a3fa6f3f5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Julian=20R=C3=BCger?= <j...@gmx.net>
Date: Tue, 16 Jul 2013 19:29:34 +0200
Subject: loader: Various small manpage improvements.

---
 loader/wine.man.in |   56 ++++++++++++++++++++++++----------------------------
 1 file changed, 26 insertions(+), 30 deletions(-)

diff --git a/loader/wine.man.in b/loader/wine.man.in
index aac5e75..84db685 100644
--- a/loader/wine.man.in
+++ b/loader/wine.man.in
@@ -1,4 +1,5 @@
-.TH WINE 1 "July 2013" "@PACKAGE_STRING@" "Windows On Unix"
+.\" -*- nroff -*-
+.TH WINE 1 "October 2005" "@PACKAGE_STRING@" "Windows On Unix"
 .SH NAME
 wine \- run Windows programs on Unix
 .SH SYNOPSIS
@@ -10,8 +11,7 @@ wine \- run Windows programs on Unix
 .B wine --version
 .PP
 For instructions on passing arguments to Windows programs, please see the
-.B
-PROGRAM/ARGUMENTS
+.B PROGRAM/ARGUMENTS
 section of the man page.
 .SH DESCRIPTION
 .B wine
@@ -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
 .BR wine .
-This will display all the output in a separate windows (this requires X11 to
-run). Not using
+This will display the program's output in a separate window (requires a
+graphical environment using the X11 or Mac driver to run). Not using
 .B wineconsole
-for CUI programs will only provide very limited console support, and your
+for CLI programs will provide very limited console support, and your
 program might not function properly.
 .PP
 When invoked with
@@ -44,8 +44,8 @@ The program name may be specified in DOS format
 .RI ( C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE )
 or in Unix format
 .RI ( /msdos/windows/sol.exe ).
-You may pass arguments to the program being executed by adding them to the
-end of the command line invoking
+You may pass arguments to the program being executed by appending them to the
+command line invoking
 .B wine
 (such as: wine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT).
 Note that you need to '\(rs' escape special characters (and spaces) when invoking Wine via
@@ -55,48 +55,44 @@ 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
-.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.
-.TP 
+makes the environment variables of the shell from which it is run accessible
+to the windows/dos processes started. 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
 .B wine
-stores its data (the default is 
+stores it's data (the default is
 .IR $HOME/.wine ).
-This directory is also used to identify the socket which is used to
-communicate with the
+This directory is also used to determine the socket used for communication with the
 .IR wineserver .
 All 
 .B wine
 processes using the same 
 .B wineserver
 (i.e.: same user) share certain things like registry, shared memory,
-and config file.
+and kernel objects.
 By setting 
 .I WINEPREFIX
 to different values for different 
 .B wine
-processes, it is possible to run a number of truly independent 
-.B wine
-processes. 
+processes, it is possible to run a number of truly independent sessions.
 .TP
 .I WINESERVER
 Specifies the path and name of the
 .B wineserver
 binary. If not set, Wine will try to load
-.BR @bindir@/wineserver ,
+.IR @bindir@/wineserver ,
 and if this doesn't exist it will then look for a file named
-"wineserver" in the path and in a few other likely locations.
+\fIwineserver\fR in the path and in a few other likely locations.
 .TP
 .I WINELOADER
 Specifies the path and name of the
 .B wine
-binary to use to launch new Windows processes. If not set, Wine will
+binary used to launch new Windows processes. If not set, Wine will
 try to load
-.BR @bindir@/wine ,
-and if this doesn't exist it will then look for a file named "wine" in
+.IR @bindir@/wine ,
+and if this doesn't exist it will then look for a file named \fIwine\fR in
 the path and in a few other likely locations.
 .TP
 .I WINEDEBUG
@@ -175,8 +171,8 @@ 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
-different libraries by separating the entries by ";".
+commas. It is also possible to specify different load orders for
+different libraries by separating the entries with ";".
 .PP
 The load order for a 16-bit dll is always defined by the load order of
 the 32-bit dll that contains it (which can be identified by looking at
@@ -195,7 +191,7 @@ the builtin version if the native load fails.
 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
@@ -308,7 +304,7 @@ can be downloaded from
 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://www.winehq.org/git
 .PP
 WineHQ, the
 .B wine
-- 
1.7.10.4



Reply via email to