[docs] wineusr: Use appropriate values for 'filename' tag attributes.
Frédéric Delanoy
frederic.delanoy at gmail.com
Tue Sep 3 14:28:47 CDT 2013
---
en/wineusr-bugs.sgml | 4 ++--
en/wineusr-configuring.sgml | 50 ++++++++++++++++++++++++---------------------
en/wineusr-getting.sgml | 2 +-
en/wineusr-running.sgml | 31 +++++++++++++++-------------
4 files changed, 47 insertions(+), 40 deletions(-)
diff --git a/en/wineusr-bugs.sgml b/en/wineusr-bugs.sgml
index c47cce5..fb67872 100644
--- a/en/wineusr-bugs.sgml
+++ b/en/wineusr-bugs.sgml
@@ -20,7 +20,7 @@
a recent version of Wine. Launch <command>winecfg</command> and look over the
settings to make sure you have settings that look normal. Look
in <filename class="directory">~/.wine/dosdevices</filename> to make sure your
- c: points to where you think it should.
+ <filename class="devicefile">c:</filename> points to where you think it should.
</para>
</sect2>
@@ -161,7 +161,7 @@
<listitem>
<para>
If you have a program that requires a redistributable runtime
- to be installed, e.g. for <filename>mfc42.dll</filename>, Visual
+ to be installed, e.g. for <filename class="libraryfile">mfc42.dll</filename>, Visual
Basic and so on, <command>winetricks</command>
can be used to supply this. Note, these components are subject to
their own license and are not part of the Wine project.
diff --git a/en/wineusr-configuring.sgml b/en/wineusr-configuring.sgml
index 78031c0..3d27fb5 100644
--- a/en/wineusr-configuring.sgml
+++ b/en/wineusr-configuring.sgml
@@ -143,10 +143,10 @@
the drives section) while others may require an installer, see
the next section on <command>winetricks</command>.
Native versions of these DLLs do not work:
- <filename>kernel32.dll</filename>,
- <filename>gdi32.dll</filename>,
- <filename>user32.dll</filename>,
- and <filename>ntdll.dll</filename>. These libraries require
+ <filename class="libraryfile">kernel32.dll</filename>,
+ <filename class="libraryfile">gdi32.dll</filename>,
+ <filename class="libraryfile">user32.dll</filename>,
+ and <filename class="libraryfile">ntdll.dll</filename>. These libraries require
low-level Windows kernel access that simply doesn't exist
within Wine.
</para>
@@ -161,7 +161,7 @@
selecting an application in the <guilabel>Applications</guilabel> tab.
</para>
<para>
- To add an override for <filename>FOO.DLL</filename>, enter
+ To add an override for <filename class="libraryfile">FOO.DLL</filename>, enter
<userinput>FOO</userinput> into the box
labeled <guilabel>New override for library:</guilabel> and
click on the <guibutton>Add</guibutton> button. To change how
@@ -262,7 +262,8 @@
<para>
Windows requires a fairly rigid drive configuration that Wine
imitates. Most people are familiar with the standard notation
- of the <quote>A:</quote> drive representing the floppy disk, the <quote>C:</quote>
+ of the <filename class="devicefile">A:</filename> drive representing the floppy disk,
+ the <filename class="devicefile">C:</filename>
drive representing the primary system disk, etc. Wine uses
the same concept and maps those drives to the underlying native
filesystem.
@@ -305,8 +306,9 @@
</screen>
<para>
Take note of the DOS-style naming convention used for links -
- the format is a letter followed by a colon, such as <quote>a:</quote>. So,
- if the link to your c: drive points to
+ the format is a letter followed by a colon, such as <filename
+ class="devicefile">a:</filename>. So,
+ if the link to your <filename class="devicefile">c:</filename> drive points to
<filename class="directory">~/.wine/drive_c</filename>, you
can interpret references to <filename class="directory">c:\windows\system32</filename>
to mean <filename class="directory">~/.wine/drive_c/windows/system32</filename>.
@@ -333,7 +335,7 @@
it does allow you to customize the look and feel of a program. Wine
supports the newer MSStyles type of themes. Unlike the older <productname>Microsoft
Plus!</productname> style themes, the <literal>uxtheme</literal> engine supports special
- <filename>.msstyles</filename> files
+ <filename class="extension">.msstyles</filename> files
that can retheme all of the Windows controls. This is more or less the
same kind of theming that modern Linux desktops have supported for
years. If you'd like to try this out:
@@ -341,7 +343,7 @@
<listitem>
<para>
Download a Windows XP theme. Be sure it contains a
- <filename>.msstyles</filename> file.
+ <filename class="extension">.msstyles</filename> file.
</para>
</listitem>
<listitem>
@@ -554,7 +556,7 @@
of each individual user. As a general rule of thumb, the closer
you keep your drive mappings to the default configuration, the easier
this will be to manage. You may or may not be able to share
- some or all of the actual <filename>c:</filename> drive you
+ some or all of the actual <filename class="devicefile">c:</filename> drive you
originally installed the application to. Some applications
require the ability to write specific settings to the drive,
especially those designed for Windows 95/98/ME.
@@ -598,12 +600,13 @@
<filename class="directory">~/.wine/dosdevices</filename> with the name of the
device. Windows serial ports follow a naming convention of the
word <literal>com</literal> followed by a number, such as
- <filename>com1</filename>, <filename>com2</filename>, etc.
- Similarly, parallel ports use <literal>lpt</literal> followed by a
- number, such as <filename>lpt1</filename>.
+ <filename class="devicefile">com1</filename>, <filename
+ class="devicefile">com2</filename>, etc. Similarly, parallel ports use
+ <literal>lpt</literal> followed by a
+ number, such as <filename class="devicefile">lpt1</filename>.
You should link these directly to the corresponding Unix
- devices, such as <filename>/dev/ttyS0</filename> and
- <filename>/dev/lp0</filename>. For example, to configure
+ devices, such as <filename class="devicefile">/dev/ttyS0</filename> and
+ <filename class="devicefile">/dev/lp0</filename>. For example, to configure
one serial port and one parallel port, run the following commands:
</para>
<screen>
@@ -638,7 +641,7 @@
<para>
Font configuration, once a nasty problem, is now much simpler.
If you have a collection of TrueType fonts in Windows it's
- simply a matter of copying the <filename>.ttf</filename> files
+ simply a matter of copying the <filename class="extension">.ttf</filename> files
into <filename class="directory">c:\windows\fonts</filename>.
</para>
</sect2>
@@ -697,10 +700,10 @@
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
- use the built-in <filename>odbc32.dll</filename>,
+ 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
- Wine to use the native <filename>odbc32.dll</filename>
+ Wine to use the native <filename class="libraryfile">odbc32.dll</filename>
it will try to use the native ODBC32 drivers etc.
</para>
<sect3>
@@ -717,8 +720,9 @@
</para>
<para>
The next step is to hook the Unix ODBC library to the Wine built-in
- <filename>odbc32</filename> DLL. The built-in <filename>odbc32</filename> (currently)
- looks in the environment variable
+ <filename class="libraryfile">odbc32</filename> DLL. The built-in <filename
+ class="libraryfile">odbc32</filename> (currently)
+ looks to the environment variable
<envar>LIB_ODBC_DRIVER_MANAGER</envar> for the name of the ODBC
library. For example:
</para>
@@ -727,7 +731,7 @@
</screen>
<para>
If that environment variable is not set then it looks for a
- library called <filename>libodbc.so</filename> and so
+ library called <filename class="libraryfile">libodbc.so</filename> and so
you can add a symbolic link to
equate that to your own library. For example as root you could
run the commands:
@@ -738,7 +742,7 @@
</screen>
<para>
The last step in configuring this is to ensure that Wine is set up
- to run the built-in version of <filename>odbc32.dll</filename>,
+ to run the built-in version of <filename class="libraryfile">odbc32.dll</filename>,
by modifying the DLL
configuration. This built-in DLL merely acts as a stub between the
calling code and the Unix ODBC library.
diff --git a/en/wineusr-getting.sgml b/en/wineusr-getting.sgml
index 37c97b3..c8dc00e 100644
--- a/en/wineusr-getting.sgml
+++ b/en/wineusr-getting.sgml
@@ -49,7 +49,7 @@
</para>
<para>
Getting Wine source archives is simple. Every release, we put a
- source package in compressed <filename>tar.bz2</filename> format
+ source package in compressed <filename class="extension">tar.bz2</filename> format
at the <ulink url="http://www.winehq.org/site/download">WineHQ downloads
page</ulink>. Compiling and installing Wine from source is slightly
more difficult than using a package, however we will cover it in
diff --git a/en/wineusr-running.sgml b/en/wineusr-running.sgml
index 402e34f..34674cf 100644
--- a/en/wineusr-running.sgml
+++ b/en/wineusr-running.sgml
@@ -252,26 +252,29 @@ Path="c:\windows;c:\windows\system;e:\;e:\test;f:\"
<prompt>$</prompt> <userinput>WINEDLLOVERRIDES="comdlg32,shell32=n,b" wine <replaceable>program_name</replaceable></userinput>
</screen>
<para>
- Try to load <filename>comdlg32</filename> and <filename>shell32</filename> as native
- Windows DLLs first and try the builtin version if the native load fails.
+ Try to load <filename class="libraryfile">comdlg32</filename> and <filename
+ class="libraryfile">shell32</filename> as native Windows DLLs first and try the builtin
+ version if the native load fails.
</para>
<screen>
<prompt>$</prompt> <userinput>WINEDLLOVERRIDES="comdlg32,shell32=n;c:\\foo\\bar\\baz=b" wine <replaceable>program_name</replaceable></userinput>
</screen>
<para>
- Try to load the <filename>comdlg32</filename> and <filename>shell32</filename> libraries
- as native Windows DLLs. Furthermore, if an application requests to load
- <filename>c:\foo\bar\baz.dll</filename> load
- the builtin library <filename>baz</filename>.
+ Try to load the <filename class="libraryfile">comdlg32</filename> and <filename
+ class="libraryfile">shell32</filename> libraries
+ as native windows DLLs. Furthermore, if an application requests to load
+ <filename class="libraryfile">c:\foo\bar\baz.dll</filename> load
+ the builtin library <filename class="libraryfile">baz</filename>.
</para>
<screen>
<prompt>$</prompt> <userinput>WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n;oleaut32=" wine <replaceable>program_name</replaceable></userinput>
</screen>
<para>
- Try to load <filename>comdlg32</filename> as builtin first and try the native version if
- the builtin load fails; load <filename>shell32</filename> always as builtin and
- <filename>comctl32</filename> always as native. <filename>oleaut32</filename> will be
- disabled.
+ Try to load <filename class="libraryfile">comdlg32</filename> as builtin first and try the
+ native version if the builtin load fails; load <filename
+ class="libraryfile">shell32</filename> always as builtin and <filename
+ class="libraryfile">comctl32</filename> always as native. <filename
+ class="libraryfile">oleaut32</filename> will be disabled.
</para>
<para>
For more information about DLL overrides, please refer to the <link
@@ -295,8 +298,8 @@ Path="c:\windows;c:\windows\system;e:\;e:\test;f:\"
<title>OSS Audio Driver Settings</title>
<para>
If you are using the OSS audio driver and you have multiple devices,
- (i.e. <filename>/dev/dsp*</filename>, <filename>/dev/mixer*</filename>)
- you can specify which one you want to
+ (i.e. <filename class="devicefile">/dev/dsp*</filename>, <filename
+ class="devicefile">/dev/mixer*</filename>) you can specify which one you want to
use with the following environment variables:
<itemizedlist>
<listitem>
@@ -543,8 +546,8 @@ Path="c:\windows;c:\windows\system;e:\;e:\test;f:\"
</entry>
<entry>
<command>wineconsole</command> will create a new window (hence
- requiring the <filename>user32</filename> DLL is available) where all
- information will be displayed
+ requiring the <filename class="libraryfile">user32</filename> DLL is available)
+ where all information will be displayed
</entry>
<entry>
<command>wineconsole</command> will use existing Unix console
--
1.8.4
More information about the wine-patches
mailing list