ReceiveTempSMS
/
Sweden-Number
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge from lostwages faq.

This commit is contained in:
Tom Wickline 2003-09-02 18:19:09 +00:00 committed by Alexandre Julliard
parent b286233fa7
commit 6163fa21af
1 changed files with 88 additions and 73 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

117
documentation/faq.sgml
View File

@ -11,7 +11,7 @@
<para>Dave Gardner maintained it from 1995-1998.</para>
<para>Douglas Ridgway (ridgway@winehq.com) took it over in 1999.</para>
<para>Andreas Mohr (amohr@codeweavers.com) converted it to FAQ-O-Matic in 2000.</para>
<para>Dimitrie O. Paun, Keith Matthews and Thomas Wickline reorganised it in 2002.</para>
<para>Dimitrie O. Paun, Keith Matthews and Tom Wickline (in alphabetical order) reorganized it in 2002.</para>
<para>For suggestions/additions/complaints regarding this FAQ, please send an email to
<ulink url="mailto:wine-faq@winehq.org">wine-faq@winehq.org</ulink></para>
</answer>
@ -232,7 +232,7 @@
copy/paste from one to the other, and run it all at full speed.
</para>
<para>
It is also a pretty vital part of migrating a large organisation,
It is also a pretty vital part of migrating a large organization,
you can't change a 5000 desktop setup overnight without a lot of risk.
</para>
</answer>
@ -341,7 +341,7 @@
<para>
Special Wine installation to be used for running Windows
Netscape browser plugins such as e.g. QuickTime in Linux
browsers. Costs $24.95.
browsers. Costs $34.95.
Well worth it (very stable and useful packaging).
</para>
</listitem>
@ -360,6 +360,20 @@
</listitem>
</varlistentry>
<varlistentry>
<term><ulink url="http://www.codeweavers.com/products/cxofficeserver/">Codeweavers' CrossOver Office Server Edition</ulink></term>
<listitem>
<para>
Allows you to run your favorite Windows productivity applications in
a distributed thin-client environment under Linux. Server Edition is
also a great addition to Solaris environments, since there built-in
support for Solaris desktops makes running Windows applications a
possibility on Sun workstations as well. For pricing just follow this link:
<ulink url="http://www.codeweavers.com/products/pricing.php">CrossOver Office Server Edition Pricing</ulink>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><ulink url="http://www.winehq.org/download/">Other packaged versions of Wine</ulink></term>
<listitem>
@ -389,8 +403,8 @@
applications became popular.
</para>
<para>
For more information, see <ulink url="http://www.winehq.com/about.shtml">
http://www.winehq.com/about.shtml</ulink>
For more information, see <ulink url="http://www.winehq.com/site/about">
http://www.winehq.com/site/about</ulink>
</para>
</answer>
</qandaentry>
@ -410,12 +424,12 @@
<ulink url="http://www.winehq.com/download.shtml">the Download page</ulink>
for some of these choices), you can make sure that you are getting
the latest version by watching the version numbers in the distribution
filename. For instance, the distribution released on October 31, 2002
was called Wine-20021031.tar.gz. Patch files are also available. If
file name. For instance, the distribution released on August 13, 2003
was called Wine-20030813.tar.gz. Patch files are also available. If
you are current to the previous version, you can download and apply
just the current patch file rather than the entire new distribution.
The patch file names follow the same conventions as the monthly
distribution. <ulink url="http://www.winehq.com/dev.shtml">
distribution. <ulink url="http://www.winehq.org/site/cvs">
Read-only CVS</ulink> access is also available.
</para>
</answer>
@ -435,7 +449,7 @@
</para>
<para>
You may also want to look at the
<ulink url="http://www.winehq.com/about/index.php?status">
<ulink url="http://www.winehq.org/site/status">
Status page</ulink> for a global view on Wine's implementation progress.
</para>
</answer>
@ -468,7 +482,7 @@
<answer>
<para>
Wine is available thanks to the work of many people. Please see the
<ulink url="http://www.winehq.com/source/AUTHORS">AUTHORS</ulink>
<ulink url="http://source.winehq.org/source/AUTHORS">AUTHORS</ulink>
file in the distribution for the complete list. Some companies that
are or have been involved with Wine development are CodeWeavers,
TransGaming, Corel, and Macadamian.
@ -519,7 +533,7 @@
<listitem>
<para>
CodeWeavers
(<ulink url="http://www.codeweavers.com/">http://www.codeweavers.com</>)
(<ulink url="http://www.codeweavers.com/">http://www.codeweavers.com</ulink>)
</para>
</listitem>
</itemizedlist>
@ -584,19 +598,19 @@
<listitem>
<para>
Cygwin
(<ulink url="http:/www.cygwin.com/">http://www.cygwin.com</>)
(<ulink url="http:/www.cygwin.com/">http://www.cygwin.com</ulink>)
</para>
</listitem>
<listitem>
<para>
MinGW
(<ulink url="http:/www.mingw.org/">http://www.mingw.org</>)
(<ulink url="http:/www.mingw.org/">http://www.mingw.org</ulink>)
</para>
</listitem>
<listitem>
<para>
ReactOS
(<ulink url="http://www.reactos.com/">http://www.reactos.com</>)
(<ulink url="http://www.reactos.com/">http://www.reactos.com</ulink>)
</para>
</listitem>
</itemizedlist>
@ -734,8 +748,8 @@
<para>
Many development tools are needed in order to compile Wine.
A list of required packages for several distributions is included in
the README (<ulink url="http://www.winehq.com/source/README">
http://www.winehq.com/source/README</ulink>).
the README (<ulink url="http://source.winehq.org/source/README">
http://source.winehq.org/source/README</ulink>).
</para>
<para>
To run Wine, you will need the following:
@ -931,9 +945,9 @@
<para>
Also Wine is not an operating system, so that writing device
drivers is not part of Wine's goals. However if you are interested
in device drivers, the <ulink url="http://www.kernel.org/">Linux</>,
<ulink url="http://www.freebsd.org/">FreeBSD</> and
<ulink url="http://www.reactos.com/">ReactOS</> kernel developpers
in device drivers, the <ulink url="http://www.kernel.org/">Linux</ulink>,
<ulink url="http://www.freebsd.org/">FreeBSD</ulink> and
<ulink url="http://www.reactos.com/">ReactOS</ulink> kernel developers
would certainly appreciate your contribution.
</para>
<para>
@ -944,8 +958,8 @@
to a large extant be redundant with other open-source projects.
Again, there are projects that would certainly appreciate your
contributions in this areas, such as the
<ulink url="http://www.gnome.org/">Gnome</> or
<ulink url="http://www.kde.org/">KDE</> desktop environments. You
<ulink url="http://www.gnome.org/">Gnome</ulink> or
<ulink url="http://www.kde.org/">KDE</ulink> desktop environments. You
will get the added benefit that your contribution will then be
usable by everyone, not just by Wine users.
</para>
@ -1066,7 +1080,7 @@
<para>
It should also be available from any other site that mirrors
ibiblio.org. For more download locations, see
<ulink url="http://ftp search.lycos.com.">lycos</ulink> Some of
<ulink url="http://www.compucan.com/Lycos.htm">lycos</ulink> Some of
these ftp sites may archive previous versions of Wine as well as the
current one. To determine which is the latest one, look at the
distribution file name, which will take the form
@ -1077,7 +1091,7 @@
<para>
Wine binary packages are available for several OS'es and
distributions. See
<ulink url="http://www.winehq.com/download.shtml">
<ulink url="http://www.winehq.org/site/download">
the download page</ulink> for the most recent list.
</para>
</answer>
@ -1121,8 +1135,8 @@ cvs -z 3 checkout wine/ANNOUNCE
Be aware, though, that getting the entire Wine source tree via CVS
is pretty slow, especially compared to getting Wine from an FTP
mirror near you. For a CVS mirror list, see
<ulink url="http://www.winehq.com/dev.shtml">
http://www.winehq.com/dev.shtml</ulink>
<ulink url="http://www.winehq.com/site/cvs#cvsservers">
http://www.winehq.com/site/cvs#cvsservers</ulink>
</para>
<para>
Patch files are also available, so that you don't have to download,
@ -1191,7 +1205,7 @@ wine
</question>
<answer>
<para>
See the README (<ulink url="http://www.winehq.com/source/README">http://www.winehq.com/source/README</ulink>) for instructions.
See the README (<ulink url="http://source.winehq.org/source/README">http://source.winehq.org/source/README</ulink>) for instructions.
Additionally, you may want to set the <parameter>TMPDIR</parameter>
environment variable <command>TMPDIR=~/tmp</command> or
<command>TMPDIR=/tmp</command> (if you are root).
@ -1229,12 +1243,12 @@ wine
<filename>~/.wine/config</filename>. The format of this file is
explained in the <filename>wine.conf</filename> man page. The file
<filename>documentation/samples/config</filename>
(<ulink url="http://www.winehq.com/source/documentation/samples/config">
http://www.winehq.com/source/documentation/samples/config</ulink>)
(<ulink url="http://source.winehq.org/source/documentation/samples/config">
http://source.winehq.org/source/documentation/samples/config</ulink>)
contains a config file example. More explicit directions can be
found in the <filename>README</filename> file
(<ulink url="http://www.winehq.com/source/README">
http://www.winehq.com/source/README</ulink>) that will be located in
(<ulink url="http://source.winehq.org/source/README">
http://source.winehq.org/source/README</ulink>) that will be located in
the base Wine directory after you gunzip and untar the distribution
file.
</para>
@ -1369,8 +1383,8 @@ export PATH=$PATH:/path/to/wine/binary
package...
</para>
<para>
For complete packages, use <ulink url="http://www.rpmfind.net/">
www.rpmfind.net</ulink> or the <ulink url="http://www.winehq.org/download/">
For complete packages, use <ulink url="http://rpmseek.com/rpm-pl/wine.html?hl=com&amp;cx=0::">
http://rpmseek.com/</ulink> or the <ulink url="http://www.winehq.org/site/download">
Download</ulink> section.
</para>
</answer>
@ -1616,8 +1630,8 @@ rm -fR \[/path/\]Wine*
</question>
<answer>
<para>
Yes, see <ulink url="http://www.winehq.org/support.shtml">
http://www.winehq.com/support.shtml.</ulink>
Yes, see <ulink url="http://www.winehq.org/site/documentation">
http://www.winehq.org/site/documentation.</ulink>
</para>
</answer>
</qandaentry>
@ -1633,10 +1647,9 @@ rm -fR \[/path/\]Wine*
<para>
Updates and additions to the Wine documentation directory should be
sent to the wine-patches mailing list at
<ulink url="http://www.winehq.com/dev.shtml#ml">
http://www.winehq.com/dev.shtml#ml</ulink>. Website and FAQ
additions should be added to the appropriate Wine Knowledgebase
directory.
<ulink url="http://www.winehq.com/site/forums">
http://www.winehq.com/site/forums</ulink>. Website and FAQ
additions should be added to the appropriate Wine Knowledge base directory.
</para>
</answer>
</qandaentry>
@ -1716,7 +1729,7 @@ rm -fR \[/path/\]Wine*
<answer>
<para>
Bug reports should be submitted to our online Bugzilla system
(<ulink url="http://bugs.winehq.com">http://bugs.winehq.com/</ulink>).
(<ulink url="http://bugs.winehq.com/">http://bugs.winehq.com/</ulink>).
You should include at least the following:
</para>
<itemizedlist>
@ -1765,11 +1778,14 @@ rm -fR \[/path/\]Wine*
<answer>
<para>
If you can program C, that's a good start. Download the sources via
CVS, subscribe to the mailing lists, look around the source, and pay
attention to the comp.emulators.ms-windows.wine newsgroup and the
mailing lists (<ulink url="http://www.winehq.com/dev.shtml#ml">http://www.winehq.com/dev.shtml#ml</ulink>). See if there's anything
that you think you can fix or work on. You won't have much trouble
finding areas that need work in Wine (grep for FIXMEs in the source).
(<ulink url="http://www.winehq.com/site/cvs">CVS,</ulink>)
subscribe to the mailing lists, look around the source, and
pay attention to the comp.emulators.ms-windows.wine newsgroup
and the mailing lists (<ulink
url="http://www.winehq.com/site/forums">http://www.winehq.com/site/forums</ulink>).
See if there's anything that you think you can fix or work
on. You won't have much trouble finding areas that need work
in Wine (grep for FIXMEs in the source).
</para>
</answer>
</qandaentry>
@ -1786,7 +1802,7 @@ rm -fR \[/path/\]Wine*
</para>
<para>
For a list of ideas of how you can help, please consult the
<ulink url="http://www.winehq.com/about/index.php?contrib">
<ulink url="http://www.winehq.com/site/contributing">
Wine contrib page</ulink>.
</para>
</answer>
@ -1817,7 +1833,7 @@ rm -fR \[/path/\]Wine*
Submitting a patch for inclusion in Wine is pretty simple.
Basically all you have to do is send the patch to the
wine-patches mailing list
(<ulink url="http://www.winehq.com/dev.shtml#ml">http://www.winehq.com/dev.shtml#ml</>).
(<ulink url="http://www.winehq.org/mailman/listinfo/wine-patches">http://www.winehq.org/mailman/listinfo/wine-patches</>).
Still there are a couple of recommendations about the patch format
and all so it's best to read our page describing <ulink
url="http://www.winehq.com/site/sending_patches">how to submit
@ -1890,7 +1906,7 @@ rm -fR \[/path/\]Wine*
</listitem>
<listitem>
<para>
MusicMatch JukeBox 5 has also been
MusicMatch Jukebox 5 has also been
<ulink url="http://www.itworld.com/nl/lnx_desktop/01042001/">ported</>
to Linux using Winelib. However more recent versions have not, and
version 5 is no longer available.
@ -1923,9 +1939,7 @@ rm -fR \[/path/\]Wine*
<answer>
<para>
You really shouldn't want to do this. If there's a quirk in Wine
you need to work around, it's much better to fix it in Wine (after
all you're a developer, so you should be able to gather enough help
and knowledge to fix it for real).
you need to work around, it's much better to fix it in Wine.
</para>
</answer>
</qandaentry>
@ -1954,7 +1968,8 @@ rm -fR \[/path/\]Wine*
</question>
<answer>
<para>
Please see: <ulink url="http://www.winehq.org/development/#ml">http://www.winehq.org/development/#ml</ulink>
Please see: <ulink url="http://www.winehq.org/site/forums">http://www.winehq.org/site/forums</ulink>
And select [(Un-)Subscribe]
</para>
</answer>
</qandaentry>