=?UTF-8?Q?Fr=C3=A9d=C3=A9ric=20Delanoy=20?=: wineusr: Assorted formatting & tagging fixes.
Alexandre Julliard
julliard at winehq.org
Fri Sep 20 13:44:02 CDT 2013
Module: docs
Branch: master
Commit: c206e3d0be7ea2a35c64be37fc8c212b8fe69591
URL: http://source.winehq.org/git/docs.git/?a=commit;h=c206e3d0be7ea2a35c64be37fc8c212b8fe69591
Author: Frédéric Delanoy <frederic.delanoy at gmail.com>
Date: Fri Sep 20 11:08:18 2013 +0200
wineusr: Assorted formatting & tagging fixes.
A couple typos as well.
---
en/wineusr-bugs.sgml | 2 +-
en/wineusr-configuring.sgml | 15 ++++++++-------
en/wineusr-running.sgml | 29 +++++++++++++++--------------
3 files changed, 24 insertions(+), 22 deletions(-)
diff --git a/en/wineusr-bugs.sgml b/en/wineusr-bugs.sgml
index e251bdd..c13cb17 100644
--- a/en/wineusr-bugs.sgml
+++ b/en/wineusr-bugs.sgml
@@ -270,7 +270,7 @@
</listitem>
<listitem>
<para>
- The exact command line you used to start Wine.
+ The exact command line you used to start Wine
(e.g. <userinput>wine "C:\Program Files\<replaceable>Test</replaceable>\<replaceable>program.exe</replaceable>"</userinput>).
</para>
</listitem>
diff --git a/en/wineusr-configuring.sgml b/en/wineusr-configuring.sgml
index ff54fa5..84a6de0 100644
--- a/en/wineusr-configuring.sgml
+++ b/en/wineusr-configuring.sgml
@@ -288,7 +288,7 @@ err:module:import_dll Library MFC42.DLL (which is needed by L"C:\\Program Files\
You may be interested in configuring your drive settings
outside of <command>winecfg</command>, in which case you're in luck because it's
quite easy. All of the drive settings reside in a special
- directory, <filename class="directory">~/.wine/dosdevices</filename>. Each
+ directory: <filename class="directory">~/.wine/dosdevices</filename>. Each
<quote>drive</quote> is simply a link to where it actually resides. Wine automatically
sets up two drives the first time you run Wine:
</para>
@@ -700,7 +700,7 @@ ln -s /mnt/smb/<replaceable>myserver</replaceable>/<replaceable>some</replaceabl
The ODBC system within Wine, as with the printing system, is designed
to hook across to the Unix system at a high level. Rather than
ensuring that all the Windows code works under Wine it uses a suitable
- Unix ODBC provider, such as UnixODBC. Thus if you configure Wine to
+ Unix ODBC provider, such as <literal>unixODBC</literal>. Thus if you configure Wine to
use the built-in <filename class="libraryfile">odbc32.dll</filename>,
that Wine DLL will interface to your
Unix ODBC package and let that do the work, whereas if you configure
@@ -713,7 +713,7 @@ ln -s /mnt/smb/<replaceable>myserver</replaceable>/<replaceable>some</replaceabl
The first step in using a Unix ODBC system with Wine is, of course,
to get the Unix ODBC system working itself. This may involve
downloading code or binary packages etc. There are several Unix ODBC systems
- available such as unixODBC or an ODBC-ODBC bridge that can be used
+ available such as <literal>unixODBC</literal> or an ODBC-ODBC bridge that can be used
to access a Microsoft Access database. Typically such systems will
include a tool, such as <command>isql</command>, which will allow
you to access the data from the command line so that you can check
@@ -752,10 +752,10 @@ LIB_ODBC_DRIVER_MANAGER=/usr/lib/libodbc.so.1.0.0
If you have any problems then you can use
<userinput><envar>WINEDEBUG</envar>=+odbc32</userinput> command
before running Wine to trace what is happening. One word of
- warning. Some programs actually cheat a little and bypass the ODBC
+ warning: some programs actually cheat a little and bypass the ODBC
library. For example the Crystal Reports engine goes to the registry
- to check on the DSN. The fix for this is documented at unixODBC
- site where there is a section on using unixODBC with Wine.
+ to check on the DSN. The fix for this is documented at <literal>unixODBC</literal>
+ site where there is a section on using <literal>unixODBC</literal> with Wine.
</para>
</sect3>
<sect3>
@@ -769,7 +769,8 @@ LIB_ODBC_DRIVER_MANAGER=/usr/lib/libodbc.so.1.0.0
</para>
<para>
In order to set up MSSQL support you will first need to download
- and run the <command>mdac_typ.exe</command> installer from microsoft.com. In order to
+ and run the <command>mdac_typ.exe</command> installer from <uri
+ type="homepage">www.microsoft.com</uri>. In order to
configure your ODBC connections you must then run <command>CLICONFG.EXE</command>
and <command>ODBCAD32.EXE</command> under Wine. You can find them in the
<filename class="directory">windows\system</filename>
diff --git a/en/wineusr-running.sgml b/en/wineusr-running.sgml
index 090eb58..ce4abae 100644
--- a/en/wineusr-running.sgml
+++ b/en/wineusr-running.sgml
@@ -383,7 +383,7 @@ Path="c:\windows;c:\windows\system;e:\;e:\test;f:\"
<title>-w</title>
<para>
This parameter makes a newly started <command>wineserver</command> wait until the
- currently active <command>wineserver</command> instance terminates.
+ currently active instance terminates.
</para>
</sect2>
</sect1>
@@ -470,12 +470,12 @@ export <envar>MYENVIRONMENTVAR</envar>=<replaceable>myenvironmentvarsetting</rep
</listitem>
<listitem>
<para>
- <command>wineconsole</command> with <parameter>user</parameter> backend
+ <command>wineconsole</command> with <literal>user</literal> backend
</para>
</listitem>
<listitem>
<para>
- <command>wineconsole</command> with <parameter>curses</parameter> backend
+ <command>wineconsole</command> with <literal>curses</literal> backend
</para>
</listitem>
</itemizedlist>
@@ -496,8 +496,8 @@ export <envar>MYENVIRONMENTVAR</envar>=<replaceable>myenvironmentvarsetting</rep
<row>
<entry>Function</entry>
<entry>Bare streams</entry>
- <entry>Wineconsole & user backend</entry>
- <entry>Wineconsole & curses backend</entry>
+ <entry>Wineconsole with <literal>user</literal> backend</entry>
+ <entry>Wineconsole with <literal>curses</literal> backend</entry>
</row>
</thead>
<tbody>
@@ -538,8 +538,9 @@ export <envar>MYENVIRONMENTVAR</envar>=<replaceable>myenvironmentvarsetting</rep
</row>
<row>
<entry>Implementation</entry>
- <entry>Maps the standard Windows streams to the
- standard Unix streams (stdin/stdout/stderr)
+ <entry>
+ Maps the standard Windows streams to the standard Unix streams
+ (<literal>stdin<literal>/<literal>stdout</literal>/<literal>stderr</literal>)
</entry>
<entry>
<command>wineconsole</command> will create a new window (hence
@@ -549,8 +550,9 @@ export <envar>MYENVIRONMENTVAR</envar>=<replaceable>myenvironmentvarsetting</rep
<entry>
<command>wineconsole</command> will use existing Unix console
(from which the program is run) and with the help of
- the (n)curses library take control of all the terminal
- surface for interacting with the user
+ the <filename class="libraryfile">curses</filename>/<filename
+ class="libraryfile">ncurses</filename> library take control of all
+ the terminal surface for interacting with the user
</entry>
</row>
<row>
@@ -576,9 +578,9 @@ export <envar>MYENVIRONMENTVAR</envar>=<replaceable>myenvironmentvarsetting</rep
to have for a given application.
</para>
<para>
- As of today, only the USER backend allows you to edit those
+ As of today, only the <literal>user</literal> backend allows you to edit those
options (we don't recommend editing by hand the registry
- contents). This edition is fired when a user right click in
+ contents). This edition is fired when a user right clicks in
the console (this popups a menu), where you can either
choose from:
<itemizedlist>
@@ -588,9 +590,8 @@ export <envar>MYENVIRONMENTVAR</envar>=<replaceable>myenvironmentvarsetting</rep
applications which haven't been configured yet. So,
when an application is first run (on your machine,
under your account) in <command>wineconsole</command>,
- <command>wineconsole</command> will
- inherit this default settings for the
- application. Afterwards, the application will have its
+ it will inherit these default settings.
+ Afterwards, the application will have its
own settings, that you'll be able to modify at your will.
</para>
<para>
More information about the wine-cvs
mailing list