Begin to uniformize sample commands in documentation.
This commit is contained in:
Vincent Béron
Alexandre Julliard
parent
7006ab1450
commit
473d7ac0dd
|
|
@ -519,8 +519,6 @@
|
|||
</para>
|
||||
<para>
|
||||
<programlisting>"DefaultLoadOrder" =" native, builtin"</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
This setting is a comma-delimited list of the order in
|
||||
which to attempt loading DLLs. If the first option fails,
|
||||
it will try the second, and so on. The order specified
|
||||
|
|
@ -546,31 +544,15 @@
|
|||
<title>The [DllOverrides] Section</title>
|
||||
<para>
|
||||
The format for this section is the same for each line:
|
||||
<programlisting>
|
||||
<DLL>{,<DLL>,<DLL>...} = <FORM>{,<FORM>,<FORM>...}
|
||||
</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
<programlisting><DLL>{,<DLL>,<DLL>...} = <FORM>{,<FORM>,<FORM>...}</programlisting>
|
||||
For example, to load built-in KERNEL pair (case doesn't
|
||||
matter here):
|
||||
<programlisting>
|
||||
"kernel,kernel32" = "builtin"
|
||||
</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
<programlisting>"kernel,kernel32" = "builtin"</programlisting>
|
||||
To load the native COMMDLG pair, but if that doesn't work
|
||||
try built-in:
|
||||
<programlisting>
|
||||
"commdlg,comdlg32" = "native, builtin"
|
||||
</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
<programlisting>"commdlg,comdlg32" = "native, builtin"</programlisting>
|
||||
To load the native COMCTL32:
|
||||
<programlisting>
|
||||
"comctl32" = "native"
|
||||
</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
<programlisting>"comctl32" = "native"</programlisting>
|
||||
Here is a good generic setup (As it is defined in config
|
||||
that was included with your wine package):
|
||||
<programlisting>
|
||||
|
|
@ -632,8 +614,6 @@
|
|||
</para>
|
||||
<para>
|
||||
<programlisting>"Resolution" = "96"</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
Since the way X handles fonts is different from the way
|
||||
Windows does, wine uses a special mechanism to deal with
|
||||
them. It must scale them using the number defined in the
|
||||
|
|
@ -656,11 +636,7 @@
|
|||
The <literal>Alias</literal> setting allows you to map an X font to a font
|
||||
used in wine. This is good for apps that need a special font you don't have,
|
||||
but a good replacement exists. The syntax is like so:
|
||||
<programlisting>
|
||||
"AliasX" = "[Fake windows name],[Real X name]"<,optional "masking" section>
|
||||
</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
<programlisting>"AliasX" = "[Fake windows name],[Real X name]"<,optional "masking" section></programlisting>
|
||||
Pretty straightforward. Replace "AliasX" with "Alias0",
|
||||
then "Alias1" and so on. The fake windows name is the name
|
||||
that the font will be under a windows app in wine. The
|
||||
|
|
@ -673,19 +649,10 @@
|
|||
<para>
|
||||
Here is an example of an alias without masking. The font will show up in windows
|
||||
apps as "Google".
|
||||
|
||||
<programlisting>
|
||||
"Alias0" = "Foo,--google-"
|
||||
</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
<programlisting>"Alias0" = "Foo,--google-"</programlisting>
|
||||
Here is an example with masking enabled. The font will show up as "Foo" in
|
||||
windows apps.
|
||||
<programlisting>
|
||||
"Alias1" = "Foo,--google-,subst"
|
||||
</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
<programlisting>"Alias1" = "Foo,--google-,subst"</programlisting>
|
||||
For more information check out the <link linkend="config-fonts-main">Fonts</link>
|
||||
chapter.
|
||||
</para>
|
||||
|
|
@ -702,8 +669,6 @@
|
|||
The [serialports] section tells wine what serial ports it
|
||||
is allowed to use.
|
||||
<programlisting>"ComX" = "/dev/ttySY"</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
Replace <literal>X</literal> with the number of the COM
|
||||
port in Windows (1-8) and <literal>Y</literal> with the
|
||||
number of it in <literal>X</literal> (Usually the number
|
||||
|
|
@ -713,8 +678,6 @@
|
|||
not always necessary to define any COM ports (An optional
|
||||
setting). Here is an example:
|
||||
<programlisting>"Com1" = "/dev/ttyS0"</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
Use as many of these as you like in the section to define
|
||||
all of the COM ports you need.
|
||||
</para>
|
||||
|
|
@ -722,8 +685,6 @@
|
|||
The [parallelports] section sets up any parallel ports
|
||||
that will be allowed access under wine.
|
||||
<programlisting>"LptX" = "/dev/lpY"</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
Sounds familiar? Syntax is just like the COM port setting.
|
||||
Replace <literal>X</literal> with a value from 1-4 as it
|
||||
is in Windows and <literal>Y</literal> with a value from
|
||||
|
|
@ -733,8 +694,6 @@
|
|||
the other section, LptX can equal any device (Maybe
|
||||
<medialabel>/dev/printer</medialabel>). Here is an
|
||||
example: <programlisting>"Lpt1" = "/dev/lp0"</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
The [spooler] section will inform wine where to spool
|
||||
print jobs. Use this if you want to try printing. Wine
|
||||
docs claim that spooling is "rather primitive" at this
|
||||
|
|
@ -743,13 +702,9 @@
|
|||
for example) to a file or a command. Here is an example,
|
||||
mapping LPT1 to the file <filename>out.ps</filename>:
|
||||
<programlisting>"LPT1:" = "out.ps"</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
The following command maps printing jobs to LPT1 to the
|
||||
command <command>lpr</command>. Notice the |:
|
||||
<programlisting>"LPT1:" = "|lpr"</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
The [ports] section is usually useful only for people who
|
||||
need direct port access for programs requiring dongles or
|
||||
scanners. <emphasis>If you don't need it, don't use
|
||||
|
|
@ -1004,9 +959,7 @@
|
|||
configuration on Linux, then <emphasis>make sure</emphasis> to add
|
||||
the <quote>unhide</quote> mount option to the CD-ROM file system
|
||||
entry in <filename>/etc/fstab</filename>, e.g.:
|
||||
<programlisting>
|
||||
/dev/cdrom /cdrom iso9660 ro,noauto,users,unhide 0 0
|
||||
</programlisting>
|
||||
<programlisting>/dev/cdrom /cdrom iso9660 ro,noauto,users,unhide 0 0</programlisting>
|
||||
Several Windows program setup CD-ROMs or other CD-ROMs chose
|
||||
to do such braindamaged things as marking very important setup
|
||||
helper files on the CD-ROM as <quote>hidden</quote>.
|
||||
|
|
@ -1296,11 +1249,7 @@ And here is a setup for Drive A, a generic floppy drive:
|
|||
access</emphasis>!!
|
||||
</para>
|
||||
<para>
|
||||
<programlisting>
|
||||
"Path" = "c:\\windows;c:\\windows\\system;c:\\blanco"
|
||||
</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
<programlisting>"Path" = "c:\\windows;c:\\windows\\system;c:\\blanco"</programlisting>
|
||||
Behaves like the <envar>PATH</envar> setting on UNIX
|
||||
boxes. When wine is run like <userinput>wine
|
||||
sol.exe</userinput>, if <filename>sol.exe</filename>
|
||||
|
|
@ -1313,9 +1262,7 @@ And here is a setup for Drive A, a generic floppy drive:
|
|||
<filename>"c:\\windows;c:\\windows\\system"</filename>).
|
||||
</para>
|
||||
<para id="dirsymlinks">
|
||||
<programlisting>
|
||||
"ShowDirSymlinks" = "1"
|
||||
</programlisting>
|
||||
<programlisting>"ShowDirSymlinks" = "1"</programlisting>
|
||||
Wine doesn't pass directory symlinks to Windows programs by
|
||||
default, as doing so may crash some programs that do
|
||||
recursive lookups of whole subdirectory trees
|
||||
|
|
@ -1922,7 +1869,7 @@ And here is a setup for Drive A, a generic floppy drive:
|
|||
read from the device on both CD-ROM and floppy; serial
|
||||
numbers on floppy only:
|
||||
</para>
|
||||
<screen>
|
||||
<programlisting>
|
||||
[Drive A]
|
||||
"Path" = "/mnt/floppy"
|
||||
"Type" = "floppy"
|
||||
|
|
@ -1934,11 +1881,11 @@ And here is a setup for Drive A, a generic floppy drive:
|
|||
"Type" = "cdrom"
|
||||
"Device" = "/dev/hda1"
|
||||
"Filesystem" = "win95"
|
||||
</screen>
|
||||
</programlisting>
|
||||
<para>
|
||||
Here's an example of overriding the CD-ROM label:
|
||||
</para>
|
||||
<screen>
|
||||
<programlisting>
|
||||
[Drive J]
|
||||
"Path" = "/mnt/cdrom"
|
||||
"Type" = "cdrom"
|
||||
|
|
@ -1946,7 +1893,7 @@ And here is a setup for Drive A, a generic floppy drive:
|
|||
; note that the device isn't really needed here as we have a fixed label
|
||||
"Device" = "/dev/cdrom"
|
||||
"Filesystem" = "msdos"
|
||||
</screen>
|
||||
</programlisting>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
|
|
|
|||
|
|
@ -265,11 +265,10 @@
|
|||
<title>Red Hat Linux</title>
|
||||
|
||||
<para>
|
||||
Red Hat users can use <ulink url="http://rpmfind.net/linux/RPM/">
|
||||
rpmfind.net</ulink> to track down available Wine RPM binaries.
|
||||
<ulink url="http://rpmfind.net/linux/RPM/WByName.html">This
|
||||
page</ulink> contains a list of all rpmfind packages that start with
|
||||
the letter "W", including a few Wine packages.
|
||||
Red Hat users can use the
|
||||
<ulink url="http://sourceforge.net/project/showfiles.php?group_id=6241">
|
||||
sourceforge.net Wine page</ulink> to get the RPM most suitable for
|
||||
their system.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -407,22 +406,8 @@
|
|||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<ulink url="ftp://ftp.infomagic.com/pub/mirrors/linux/sunsite/ALPHA/wine/development/">
|
||||
ftp://ftp.infomagic.com/pub/mirrors/linux/sunsite/ALPHA/wine/development/
|
||||
</ulink>
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<ulink url="ftp://ftp.fu-berlin.de/unix/linux/mirrors/sunsite.unc.edu/ALPHA/wine/development/">
|
||||
ftp://ftp.fu-berlin.de/unix/linux/mirrors/sunsite.unc.edu/ALPHA/wine/development/
|
||||
</ulink>
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<ulink url="ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/">
|
||||
ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/
|
||||
<ulink url="http://prdownloads.sourceforge.net/wine/">
|
||||
http://prdownloads.sourceforge.net/wine/
|
||||
</ulink>
|
||||
</para>
|
||||
</listitem>
|
||||
|
|
@ -663,8 +648,7 @@ checkout -P
|
|||
<parameter>--dry-run</> parameter to run the patch
|
||||
without writing to any files:
|
||||
<screen>
|
||||
<prompt>$ </><userinput>patch -p0 --dry-run <<replaceable>../patch_to_apply.d
|
||||
iff</></>
|
||||
<prompt>$ </><userinput>patch -p0 --dry-run <<replaceable>../patch_to_apply.diff</></>
|
||||
</screen>
|
||||
</para>
|
||||
<para>
|
||||
|
|
|
|||
|
|
@ -520,7 +520,7 @@
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
<literallayout>A computer ;-)</literallayout>
|
||||
A computer ;-)
|
||||
<literallayout> Wine: only PCs >= i386 are supported at the moment.</literallayout>
|
||||
<literallayout> Winelib: selected other platforms are supported, but can be tricky.</literallayout>
|
||||
</para>
|
||||
|
|
|
|||
Loading…
Reference in New Issue