docs/ fr/Makefile.in fr/.cvsignore en/Makefile ...

Alexandre Julliard ajulliard at users.sourceforge.net
Tue Jun 26 15:42:55 CDT 2007


ChangeSet ID:	1182890575827467004143731
CVSROOT:	/cvsroot/wine
Module name:	docs
Changes by:	ajulliard at sc8-pr-cvs9.sourceforge.net	2007/06/26 13:42:55

Modified files:
	fr             : Makefile.in .cvsignore 
	en             : Makefile.in .cvsignore 
	.              : Make.rules.in 
Removed files:
	fr             : wine-faq.po 
	en             : wine-faq.sgml 

Log message:
	The FAQ is maintained on the wiki now.


Old revision  New revision  Changes     Path
 1.7           1.8           +1 -4       docs/fr/Makefile.in
 1.4           1.5           +0 -5       docs/fr/.cvsignore
 1.2           Removed       +0 -0       docs/fr/wine-faq.po
 1.5           1.6           +1 -4       docs/en/Makefile.in
 1.1           1.2           +0 -4       docs/en/.cvsignore
 1.19          Removed       +0 -0       docs/en/wine-faq.sgml
 1.7           1.8           +0 -1       docs/Make.rules.in

Index: docs/fr/Makefile.in
diff -u -p docs/fr/Makefile.in:1.7 docs/fr/Makefile.in:1.8
--- docs/fr/Makefile.in	26 Jun 2007 20:42:55 -0000
+++ /dev/null	26 Jun 2007 20:42:55 -0000
@@ -22,12 +22,9 @@ WINELIB_SRCS = \
 	$(SGMLDIR)/winelib-porting.sgml \
 	$(SGMLDIR)/winelib-toolkit.sgml
 
-WINEFAQ_SRCS = \
-
 ALLBOOKS = \
 	wineusr-guide \
-	winelib-guide \
-	wine-faq
+	winelib-guide
 
 all: doc
 
Index: docs/fr/.cvsignore
diff -u -p docs/fr/.cvsignore:1.4 docs/fr/.cvsignore:1.5
--- docs/fr/.cvsignore	26 Jun 2007 20:42:55 -0000
+++ /dev/null	26 Jun 2007 20:42:55 -0000
@@ -1,9 +1,4 @@
 Makefile
-wine-faq.html
-wine-faq.pdf
-wine-faq.sgml
-wine-faq.ps
-wine-faq.txt
 winelib-guide.html
 winelib-guide.pdf
 winelib-guide.sgml
Index: docs/fr/wine-faq.po
diff -u -p docs/fr/wine-faq.po:1.2 /dev/null
--- docs/fr/wine-faq.po	26 Jun 2007 20:42:55 -0000
+++ /dev/null	26 Jun 2007 20:42:55 -0000
@@ -1,2472 +0,0 @@
-# French translation for the Wine FAQ
-#
-# The initial translation was performed by:
-# Copyright (C) 2005 Romuald VIEUX
-# And reviewed by:
-# Copyright (C) 2005 Yvon BENOIST
-# 
-msgid ""
-msgstr ""
-"Project-Id-Version: Wine CVS\n"
-"POT-Creation-Date: 2005-03-14 19:50+0100\n"
-"PO-Revision-Date: 2005-02-18 00:00+1\n"
-"Last-Translator: Yvon BENOIST <benoist at insa-rouen.fr>\n"
-"Language-Team: Wine-Devel <wine-devel at winehq.org>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=iso-8859-1\n"
-"Content-Transfer-Encoding: iso-8859-1\n"
-
-# type: <title></title>
-#: ../wine-faq.sgml:7 ../faq.sgml:3
-#, no-wrap
-msgid "Wine FAQ"
-msgstr "Wine FAQ"
-
-# type: <title></title>
-#: ../wine-faq.sgml:7 ../faq.sgml:6
-#, no-wrap
-msgid "About this FAQ"
-msgstr "A propos de cette FAQ"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:9
-msgid "Who maintains this FAQ ?"
-msgstr "Qui assure le suivi de cette FAQ ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:12
-msgid "Dave Gardner maintained it from 1995-1998."
-msgstr "Dave Gardner l'a maintenu de 1995 à 1998."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:13
-msgid "Douglas Ridgway took it over in 1999."
-msgstr "Douglas Ridgway a pris le relais en 1999."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:14
-msgid "Andreas Mohr converted it to FAQ-O-Matic in 2000."
-msgstr "Andreas Mohr l'a converti en FAQ-O-Matic en 2000."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:15
-msgid ""
-"Dimitrie O. Paun, Keith Matthews and Tom Wickline (in alphabetical order) "
-"reorganized it in 2002."
-msgstr ""
-"Dimitrie O. Paun, Keith Matthews et Tom Wickline (par ordre alphabétique) "
-"l'ont réorganisée en 2002."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:16
-msgid ""
-"For suggestions/additions/complaints regarding this FAQ, please send an "
-"email to <ulink url=\"mailto:wine-devel at winehq.org\">wine-devel at winehq.org</"
-"ulink>"
-msgstr ""
-"Pour toute suggestion, ajout ou remarque concernant cette FAQ, n'hésitez pas "
-"à nous écrire à <ulink url=\"mailto:wine-devel at winehq.org\">wine-devel at winehq."
-"org</ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:22
-msgid "What is the copyright of this FAQ? And how may I use it?"
-msgstr "Quel est le copyright de cette FAQ? Comment puis-je l'utiliser?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:25
-msgid ""
-"The original Wine FAQ, which this FAQ was based on, was copyright &copy; "
-"1995-1998 David Gardner."
-msgstr ""
-"La FAQ originale de Wine, sur laquelle est basée la présente FAQ, a pour "
-"copyright &copy; 1995-1998 David Gardner."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:26
-msgid "It may be reproduced and modified under the same terms as Wine itself."
-msgstr ""
-"Elle peut être reproduite et modifiée selon les même termes que Wine lui-"
-"même."
-
-# type: <title></title>
-#: ../wine-faq.sgml:7 ../faq.sgml:31
-#, no-wrap
-msgid "General Questions about Wine"
-msgstr "Questions générales sur Wine"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:35
-msgid "What is Wine and what is it supposed to do?"
-msgstr "Qu'est-ce que Wine et qu'est-il supposé faire ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:39
-msgid ""
-"Wine is a program which allows the operation of DOS and MS Windows programs "
-"(Windows 3.x and Win32 executables) on UNIX operating systems such as Linux. "
-"It consists of a program loader, which loads and executes a Windows binary, "
-"and a set of libraries that implements Windows API calls using their UNIX or "
-"X11 equivalents. The libraries may also be used for porting Win32 code into "
-"native UNIX executables, often without many changes in the source. Wine is "
-"free software, and its license (contained in the file LICENSE in each "
-"distribution) is the LGPL."
-msgstr ""
-"Wine est un programme qui permet d'exécuter les opérations DOS et les "
-"programmes MS Windows (Windows 3.x et exécutables Win32 ) sur les systèmes "
-"d'exploitation UNIX comme Linux. il comprend un programme de chargement, qui "
-"charge et exécute un binaire Windows, et un ensemble de bibliothèques qui "
-"implémentent les appels aux API Windows en utilisant leurs équivalents UNIX "
-"ou X11. Les bibliothèques peuvent être également utilisées pour porter du "
-"code Win32 en exécutables UNIX, souvent sans beaucoup de changement au "
-"niveau du code source. Wine est un logiciel libre, et sa license (qui se "
-"trouve dans le fichier LICENSE de chaque distribution) est la LGPL (GNU "
-"Lesser General Public License)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:54
-msgid "Does Wine emulate a full computer?"
-msgstr "Est-ce que Wine émule complétement un ordinateur ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:58
-msgid ""
-"No, as the name says, Wine Is Not a (CPU) Emulator. Wine just provides the "
-"Windows API. This means that you will need an x86-compatible processor to "
-"run an x86 Windows application, for instance from Intel or AMD. The "
-"advantage is that, unlike solutions that rely on CPU emulation, Wine runs "
-"applications at full speed. Sometimes a program run under Wine will be "
-"slower than when run on a copy of Microsoft Windows, but this is more due to "
-"the fact that Microsoft has heavily optimized parts of their code, whereas "
-"mostly Wine is not well optimized (yet). Occasionally, an app may run faster "
-"under Wine than on Windows. Most apps run at roughly the same speed."
-msgstr ""
-"Non, comme son nom l'indique, Wine n'est pas un émulateur [Wine Is Not a "
-"(CPU) Emulator]. Wine fournit simplement les API Windows. Cela signifie que "
-"vous aurez besoin d'un processeur compatible x86 pour exécuter une "
-"application Windows x86, par exemple un Intel ou un AMD. L'avantage est que, "
-"à la différence des solutions qui s'appuient sur une émulation CPU, Wine "
-"exécute des applications à pleine vitesse. Parfois un programme exécuté sous "
-"Wine sera plus lent que s'il était exécuté sur une copie de Microsoft "
-"Windows, mais cela est principalement dû au fait que Microsoft a énormément "
-"optimisé des parties de son code, alors qu'essentiellement Wine n'est pas "
-"(pour le moment) bien optimisé. Occasionellement, il arrive qu'une "
-"application tourne plus vite sous Wine que sous Windows. La plupart des "
-"applications tourne approximativement à la même vitesse."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:73
-msgid "Are there any alternatives to Wine?"
-msgstr "Y-a-t-il d'autres solutions que Wine ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:77
-msgid ""
-"Yes, there are. You can use <ulink url=\"http://www.vmware.com\">VMWare</"
-"ulink> to run a Windows installation inside a virtual machine, or use <ulink "
-"url=\"http://www.win4lin.com\">Win4Lin</ulink> to run a specially adapted "
-"Windows version on Linux. Both solutions cost money for both the software "
-"itself and a Windows license."
-msgstr ""
-"Oui. Vous pouvez utiliser VMWare (http://www.vmware.com) pour exécuter une "
-"installation Windows au sein d'une machine virtuelle, ou utiliser Win4Lin "
-"(http://www.win4lin.com) pour exécuter une version spécialement adaptée de "
-"Windows sous Linux. Les deux solutions coûtent de l'argent pour à la fois le "
-"logiciel lui-même et la license Windows."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:84
-msgid ""
-"Note that, like Wine, they can only use the hardware platform that the "
-"target programs were originally compiled for (see below)."
-msgstr ""
-"Notez que, comme Wine, ils peuvent seulement utiliser la plate-forme "
-"matérielle pour laquelle le programme cible a été compilé (voir ci-dessus)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:93
-msgid "What is the difference between Wine and x86 hardware emulators?"
-msgstr "Quelle est la différence entre Wine et les émulateurs matériels x86 ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:97
-msgid ""
-"There are two free x86 hardware emulators: <ulink url=\"http://bochs."
-"sourceforge.net\">Bochs</ulink>, and <ulink url=\"http://savannah.nongnu.org/"
-"projects/plex86\">Plex86</ulink>."
-msgstr ""
-"Il existe deux émulateurs x86 libres: <ulink url=\"http://bochs.sourceforge."
-"net\">Bochs</ulink>, and <ulink url=\"http://savannah.nongnu.org/projects/"
-"plex86\">Plex86</ulink>."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:103
-msgid ""
-"Plex86 is the open-source free-software alternative for VMWare, VirtualPC, "
-"and other IA-32 on IA-32 \"Virtual PC products.\" It can only run on the IA-"
-"32 architecture."
-msgstr ""
-"Plex86 est un logiciel libre open-source offrant une solution de rechange "
-"pour VMWare, VirtualPC, et autre IA-32 sur IA-32 \"Virtual PC products.\" Il "
-"peut uniquement fonctionner sur l'architecture IA-32."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:109
-msgid ""
-"Bochs is a highly portable open source IA-32 (x86) PC emulator written in C+"
-"+, that runs on most popular platforms. It includes emulation of the Intel "
-"x86 CPU, common I/O devices, and a custom BIOS. Currently, Bochs can be "
-"compiled to emulate a 386, 486 or Pentium CPU. Bochs is capable of running "
-"most Operating Systems inside the emulation including Linux, Windows® 95, "
-"DOS, and recently Windows® NT 4."
-msgstr ""
-"Bochs est un émulateur de PC (x86) IA-32 open-source parfaitement portable "
-"écrit en C++, qui tourne sous les plate-formes les plus utilisées. Il permet "
-"l'émulation du CPU x86 d'Intel, des périphériques d'entrée/sortie courants, "
-"et d'un BIOS personnalisé. Actuellement, Bochs peut être compilé pour émuler "
-"un CPU 386, 486 ou Pentium. Bochs est capable de faire fonctionner la "
-"plupart des systèmes d'opérations par son émulation y compris Linux, "
-"Windows® 95, DOS, et récemment Windows® NT 4."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:118
-msgid ""
-"Both are licensed under the GPL. Bochs is older than Plex86, seems to be "
-"easier to install, but Plex86 will run faster because Plex86 uses a just in "
-"time binary compiler."
-msgstr ""
-"Les deux logiciels sont sous license GPL. Bochs est plus ancien que Plex86, "
-"semble être plus facile à installer, mais Plex86 se révélera plus rapide car "
-"il utilise un compilateur binaire en juste à temps."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:123
-msgid ""
-"The drawback of all emulators is that you need a version of Windows in order "
-"to run Windows, and that they all have an impact on performance. Wine also "
-"gives much better desktop integration - for instance, programs use your "
-"standard window manager, system tray icons will appear in your tray area (if "
-"you have one), and you can run programs direct from the command line as well "
-"as menus. The clipboard also works seamlessly at this time."
-msgstr ""
-"L'inconvénient de tous les émulateurs est que vous avez besoin d'une version "
-"de Windows pour exécuter Windows, et qu'ils ont tous un impact sur la "
-"performance. Wine offre également une meilleure intégration du bureau- par "
-"exemple, les programmes utilisent votre gestionnaire de fenêtre standard, "
-"les icônes de la barre de lancement rapide [system tray] apparaîtront dans "
-"votre barre des tâches (si vous en avez une), et vous pouvez exécuter les "
-"programmes directement depuis la ligne de commande comme depuis les menus. "
-"La tablette électronique fonctionne aussi d'une façon homogène actuellement."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:136
-msgid ""
-"When will Wine integrate an x86 CPU emulator so we can run Windows "
-"applications on non-x86 machines?"
-msgstr ""
-"Quand Wine intégrera-t-il un émulateur CPU x86 de façon à faire tourner des "
-"applications Windows sur des mahines non-x86 ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:141
-msgid ""
-"The short answer is 'probably never'. Remember, Wine Is Not a (CPU) "
-"Emulator. The long answer is that we probably don't want or need to "
-"integrate one in the traditional sense."
-msgstr ""
-"Pour être bref, probablement jamais. Souvenez-vous, Wine n'est pas un "
-"émulateur (de CPU). Pour être plus précis disons que nous ne voulons "
-"probablement pas ou ne ressentons pas le besoin d'en intégrer un au sens "
-"traditionnel du terme."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:146
-msgid ""
-"Integrating a CPU emulator in Wine would be extremely hard, due to the large "
-"number of Windows APIs and the complex data types they exchange. It is not "
-"uncommon for a Windows API to take three or more pointers to structures "
-"composed of many fields, including pointers to other complex structures. For "
-"each of these we would need a conversion routine to deal with the byte order "
-"and alignment issues. Furthermore, Windows also contains many callback "
-"mechanisms that constitute as many extra places where we would have to "
-"handle these conversion issues. Wine already has to deal with 16 vs. 32 bit "
-"APIs and Ansi vs. Unicode APIs which both introduce significant complexity. "
-"Adding support for a CPU emulator inside Wine would introduce at least "
-"double that complexity and only serve to slow down the development of Wine."
-msgstr ""
-"Intégrer un émulateur CPU à Wine serait extrémement difficile, à cause du "
-"grand nombre d'API Windows et de la compléxité des types de données qu'elles "
-"échangent. Il n'est pas rare de voir dans une API Windows trois pointeurs ou "
-"plus vers des structures composées de nombreux champs, y compris des "
-"pointeurs vers d'autres structures complexes. Pour chacun d'entre eux, nous "
-"aurions besoin d'un mécanisme automatique de conversion qui puisse traiter "
-"les problèmes d'ordre des octets et d'alignement. De plus, Windows contient "
-"aussi de nombreux méchanisme de rappel automatique [callback] qui "
-"constituent autant d'occasions où nous aurions à essuyer ces problèmes de "
-"conversion. Wine doit déjà faire avec les API 16 bits face aux API 32 bits "
-"et les API Ansi face aux API Unicode, des différences qui apportent leur lot "
-"de compléxité. Ajouter un support pour les émulateurs CPU à l'intérieur de "
-"Wine compliquerait deux fois plus les choses et ne servirait qu'à ralentir "
-"le développement de Wine."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:161
-msgid ""
-"Fortunately another solution exists to run Windows applications on non-x86 "
-"platforms: run both Wine and the application inside the CPU emulator. As "
-"long as the emulator provides a standard Unix environment, Wine should only "
-"need minimal modifications. What performance you lose due to Wine running "
-"inside the emulator rather than natively, you gain in complexity inside of "
-"Wine. Furthermore, if the emulator is fast enough to run Windows "
-"applications, Photoshop for instance, then it should be fast enough to run "
-"that same Windows application plus Wine."
-msgstr ""
-"Heureusement, une autre solution existe pour faire fonctionner des "
-"applications Windows sous des plateformes non x86 : exécuter à la fois Wine "
-"et l'application au sein de l'émulateur CPU. Tant que l'émulateur offre un "
-"environnement UNIX standard, Wine devrait seulement avoir besoin de "
-"modifications minimes. La performance que vous perdez en faisant tourner "
-"Wine dans l'émulateur plutôt que nativement, vous la gagnez en compléxité "
-"dans Wine. De plus, si l'émulateur est assez rapide pour faire tourner des "
-"applications Windows, Photoshop par exemple, alors il devrait être "
-"suffisament rapide pour exécuter cette même application et Wine."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:175
-msgid ""
-"Two projects have started along those lines: <ulink url=\"http://fabrice."
-"bellard.free.fr/qemu/\">QEMU</ulink>, an open-source project, and <ulink url="
-"\"http://www.transitives.com/tech_overview.htm\">Dynamite</ulink>, a "
-"commercial CPU emulator environment from <ulink url=\"http://www.transitives."
-"com/\">Transitives Technologies</ulink>."
-msgstr ""
-"Deux nouveaux projets s'inscrivent dans cette optique :  <ulink url=\"http://"
-"fabrice.bellard.free.fr/qemu/\">QEMU</ulink>, projet open-source, et "
-"Dynamite <ulink url=\"http://www.transitives.com/tech_overview.htm"
-"\">Dynamite</ulink>, environment commercial émulant un CPU de chez <ulink "
-"url=\"http://www.transitives.com/\">Transitives Technologies</ulink>."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:185
-msgid "Why would anyone want Wine? Doesn't Windows suck?"
-msgstr ""
-"Pourquoi quelqu'un voudrait-il utiliser Wine? Est-ce que Windows ne craint "
-"pas?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:189
-msgid ""
-"First Wine is not about running Windows but about running Windows "
-"applications."
-msgstr ""
-"Tout d'abord Wine n'est pas là pour faire tourner Windows mais pour faire "
-"tourner des applications Windows."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:193
-msgid ""
-"So if all your computing needs are fulfilled by native Unix applications, "
-"then you do not need Wine and should not be using it. However, if you depend "
-"on one or more of the tens of thousands of Windows applications, then Wine "
-"is the best way to use it without giving up on Unix. Let's look at the "
-"alternatives to see why:"
-msgstr ""
-"Par conséquent si tous vos besoins informatiques sont satisfaits par des "
-"applications natives UNIX, alors vous n'avez pas besoin de Wine et vous ne "
-"devriez pas l'utiliser. Cependant, si vous avez vraiment besoin d'une ou "
-"plusieurs des dizaines de milliers d'applications Windows , alors Wine et le "
-"meilleur moyen de les utiliser sans abandonner Unix. Jetons un oeil sur "
-"toutes les autres solutions possibles pour voir pourquoi:"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:201
-msgid ""
-"The most obvious alternative is to dual-boot. This is the solution that "
-"provides the best compatibility. However it requires that you acquire a "
-"Windows license and then dedicate a good chunk of your hard-drive to "
-"Windows. But the worst is yet to come. Each time you will want to use that "
-"application you will have to reboot to Windows. This is especially "
-"significant if external factors dictate when you must use this application "
-"(e.g. credit card to process, email to retrieve from a Lotus Notes server). "
-"Then you will find yourself forced to close all your Linux applications just "
-"to run that one Windows application. You may quickly get tired of this, or "
-"will find that such a situation is impossible to justify in a business "
-"environment."
-msgstr ""
-"Parmi celles-ci, la plus évidente, est d'utiliser le double démarrage. C'est "
-"la solution qui offre la meilleure compatibilité. Cependant cela implique "
-"d'acquérir une license Windows et de dédier une bon morceau de votre disque "
-"dur à Windows. Mais le pire est encore à venir. Chaque fois que vous voudrez "
-"utiliser cette application vous devrez redémarrer sur Windows. C'est "
-"particulièrement désagréable si cette obligation vient de l'extérieur et "
-"vous obligent à utiliser cette application (e.g le traitement du carte de "
-"crédit, email a récupérer depuis un serveur Lotus Notes). Vous serez alors "
-"obligé de fermer toutes vos applications Linux juste pour ouvrir cette "
-"application Windows. Vous serez sans doute vite exaspéré de cette situation, "
-"ou vous trouverez qu'une telle situation n'est pas acceptable dans le cadre "
-"du travail."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:215
-msgid ""
-"The next solution is to install virtual machine emulation software such as "
-"VMWare, Win4Lin or Plex86. Then you can use windows applications without "
-"suffering such a big disruption. But it still requires that you acquire a "
-"Windows license and dedicate as much disk space to Windows. Furthermore you "
-"will pay for the added convenience: if using VMWare or Win4Lin you have to "
-"buy another license, and more importantly you now have to dedicate a good "
-"chunk of your computer's memory to the virtual machine. Performance will "
-"take a significant hit too."
-msgstr ""
-"L'autre solution est d'installer un logiciel d'émulation de machine "
-"virtuelle tel que VMWare, Win4Lin ou Plex86. Vous pouvez alors utiliser des "
-"applications Windows sans déplorer une telle interruption. Mais cela "
-"implique également d'acquérir une license Windows et autant d'espace disque "
-"pour Windows. De plus vous devrez payer pour cet inconvénient "
-"supplémentaire : si puisque vous utilisez VMWare ou Win4Lin vous devez "
-"acheter une nouvelle license, et plus important vous devez dédiez maintenant "
-"une bonne partie de votre mémoire vive à la machine virtuelle. Les "
-"performances vont en prendre un sérieux coup également."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:226
-msgid ""
-"Using Wine lets you avoid all of that overhead: Windows license, hard-drive "
-"space required by Windows, memory and performance hit taken by emulated "
-"virtual machines. Now you can start your Windows application straight from "
-"your regular desktop environment, place that application's window side by "
-"side with native applications, copy/paste from one to the other, and run it "
-"all at full speed."
-msgstr ""
-"L'utilisation de Wine vous permet d'éviter toutes ces charges : la license "
-"Windows, l'espace disque-dur pris par Windows, les conséquences sur la "
-"mémoire et les performances dûes à l'émulation de la machine virtuelle. Vous "
-"pouvez maintenant démarrer votre application Windows depuis votre "
-"environnement bureau habituel, placer la fenêtre de cette application côte à "
-"côte avec d'autres applications natives, faire des copier/coller de l'une "
-"vers l'autre, et l'exécuter à pleine vitesse."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:234
-msgid ""
-"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."
-msgstr ""
-"C'est aussi un élément assez important pour la migration d'un organisme de "
-"grande taille, on ne change pas en une nuit changez la configuration de 5000 "
-"bureaux sans risque."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:243
-msgid ""
-"Can I use Wine to make the Windows driver for my network card / graphics "
-"card / scanner / etc. work on Unix?"
-msgstr ""
-"Puis-je utiliser Wine pour que les pilotes Windows de ma carte réseau / "
-"carte graphique / scanner / etc. marchent sous Unix ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:248
-msgid ""
-"The goal of Wine is to make it possible to run Windows applications on Unix, "
-"not Windows drivers or VxDs."
-msgstr ""
-"Le but de Wine est de rendre possible l'exécution d'applications Windows "
-"sous Unix, mais pas les pilotes Windows ou les VxD."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:252
-msgid ""
-"Drivers and Windows applications belong to different worlds. Applications "
-"run in user mode and use the APIs provided by the kernel and the other user "
-"mode dlls. In contrast, drivers are loaded in the Windows kernel, i.e. in "
-"ring 0 instead of ring 3, drivers have to deal with specific memory "
-"management issues, and use instructions not available to regular "
-"applications. This means they would not be able to run in Wine since Wine "
-"runs entirely in user mode. Rather you would have to modify the Linux "
-"kernel. But in addition, drivers use a completely different API from regular "
-"Windows applications. So the work performed on Wine would not even be of any "
-"use for such a project. In other words, making it possible to use Windows "
-"drivers or VxDs on Unix would be a completely separate project."
-msgstr ""
-"Les pilotes et les applications Windows appartiennent à des mondes "
-"différents. Les applications tournent en mode utilisateur et utilisent les "
-"API fournies par le noyau et les autres dll mode utilisateur. A l'inverse, "
-"les pilotes sont chargés dans le noyau Windows, c.à.d. au niveau 0 au lieu "
-"du niveau 3, ils doivent faire face à des problèmes spécifiques de gestion "
-"de mémoire, et utilisent des instructions qui ne sont pas disponibles pour "
-"les applications classiques. Cela signifie qu'ils ne pourraient tourner dans "
-"Wine puisque ce dernier s'exécute en mode utilisateur. Il vous faudrait "
-"alors modifier le noyau Linux. Mais par ailleurs, les pilotes utilisent une "
-"API complétement différente des applications Windows classiques. Le travail "
-"réalisé sur Wine ne serait donc d'aucune utilité pour un tel projet. En "
-"d'autres termes, rendre possible l'utilisation de pilotes Windows ou VxDs "
-"sous Unix serait un tout autre projet."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:267
-msgid ""
-"However, if you want to reuse Windows drivers on a non-Microsoft operating "
-"system we recommend that you have a look at <ulink url=\"http://www.reactos."
-"com/\">ReactOS</ulink>."
-msgstr ""
-"Cependant, si vous voulez réutiliser des pilotes Windows sous un système "
-"d'exploitation non-Microsoft nous vous recommandons la lecture de <ulink url="
-"\"http://www.reactos.com/\">ReactOS</ulink>."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:277
-msgid "Which one of the different Wine packages out there is good for me?"
-msgstr "Lequel des packages Wine existant me convient ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:281
-msgid ""
-"Currently there is a broad selection of different Wine packages/versions:"
-msgstr ""
-"Actuellement il existe un large choix de différentes versions/packages de "
-"Wine:"
-
-# type: <term></term>
-#: ../wine-faq.sgml:7 ../faq.sgml:286
-msgid "<ulink url=\"http://www.winehq.org\">Wine</ulink>"
-msgstr "<ulink url=\"http://www.winehq.org\">Wine</ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:289
-msgid ""
-"This is the \"standard\" distribution of Wine. Its license is the LGPL, it "
-"can be downloaded for free. Both source code and binaries are available in "
-"the download section of the site."
-msgstr ""
-"C'est la distribution \"standard\" de Wine. Sa license est la LGPL, il peut "
-"être téléchargé gratuitement. Le code source et les binaires sont "
-"disponibles dans la section \"download\" du site."
-
-# type: <term></term>
-#: ../wine-faq.sgml:7 ../faq.sgml:297
-msgid "<ulink url=\"http://www.transgaming.com\">TransGaming's Cedega</ulink>"
-msgstr "<ulink url=\"http://www.transgaming.com\">Cedega</ulink> de TransGaming"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:300
-msgid ""
-"This is TransGaming's Wine version specially suited for games. It includes "
-"more mature Direct3D support than WineHQ, although these days WineHQ has "
-"quite advanced D3D support as well. Most of the code is under the AFPL and "
-"can be downloaded for free."
-msgstr "Il s'agit de la version TransGaming de Wine spécialement faite pour les jeux. Elle comprend un support plus mature du Direct3D que WineHQ, bien qu'actuellement WineHQ soit également très avancé pour le support D3D. La plupart du code est sous l'AFPL et peut être téléchargé gratuitement."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:307
-msgid ""
-"However TransGaming also distributes binaries that contain improved copy "
-"protection support (needed for many games), support, and other enhancements. "
-"These packages are only available in binary form to subscribed customers ($5/"
-"month, minimum three months)."
-msgstr "Cependant TransGaming distribue également des binaires pour le support de protection améliorée des copies (requis pour de nombreux jeux), une assistance, et d'aures avantages. Ces packages sont seulement disponibles sous forme de binaires pour les clients inscrits (5$/mois, minimum de trois mois)."
-
-# type: <term></term>
-#: ../wine-faq.sgml:7 ../faq.sgml:317
-msgid ""
-"<ulink url=\"http://www.codeweavers.com/site/products/cxoffice/"
-"\">CodeWeavers' CrossOver Office</ulink>"
-msgstr ""
-"<ulink url=\"http://www.codeweavers.com/site/products/cxoffice/\">CrossOver "
-"Office</ulink> de CodeWeavers"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:320
-msgid ""
-"Wine version with special packaging to make sure almost all important Office "
-"type programs work pretty well. Costs $74.95 for the Pro version and $39.95 "
-"for the Standard version. Seems to be well worth it so far according to some "
-"comments. (note: you're supporting a company actively contributing to Wine "
-"if you decide to buy CrossOver.)"
-msgstr "C'est la version Wine avec un assortiment spécial pour s'assurer que la plupart des programmes de la suite Office fonctionne correctement. Elle coûte 74.95$ pour la version Pro et 39.95$ pour la version Standard. Elle semble véritablement valoir le coup, jusqu'à maintenant, si l'on s'en référe à certains commentaires. (note: vous apporterez votre soutien à une entreprise contribuant activement à Wine si vous décidez d'acheter CrossOver.)"
-
-# type: <term></term>
-#: ../wine-faq.sgml:7 ../faq.sgml:331
-msgid ""
-"<ulink url=\"http://www.codeweavers.com/site/products/cxserver/"
-"\">CodeWeavers' CrossOver Office Server Edition</ulink>"
-msgstr "<ulink url=\"http://www.codeweavers.com/site/products/cxserver/"
-"\">CrossOver Office Server Edition</ulink> de CodeWeavers"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:334
-msgid ""
-"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/site/products/pricing/\">CrossOver Office Server Edition "
-"Pricing</ulink>"
-msgstr "Elle vous permet d'exécuter vos applications de productivité Windows favorites dans un environnement client léger distribué sous Linux. La Server Edition est aussi un bon ajout aux environnements Solaris, puisque le support intégré pour les bureaux Solaris permet de faire tourner les applications sur les stations de travail Sun. Pour les tarifs veuillez vous référez au lien suivant: <ulink url=\"http://"
-"www.codeweavers.com/site/products/pricing/\">CrossOver Office Server Edition "
-"Pricing</ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:350
-msgid "What's the history of Wine?"
-msgstr "Quelle est l'histoire de Wine ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:354
-msgid ""
-"The Wine project started in 1993 as a way to support running Windows 3.1 "
-"programs on Linux. Bob Amstadt was the original coordinator, but turned it "
-"over fairly early on to Alexandre Julliard, who has run it ever since. A "
-"<ulink url=\"news:comp.emulators.ms-windows.wine\">newsgroup</ulink> was "
-"created in July 1994. Over the years, ports for other Unixes have been "
-"added, along with support for Win32 as Win32 applications became popular."
-msgstr "Le projet Wine a commencé en 1993 dans le but de supporter des programmes tournant sous Windows 3.1 pour Linux. Bob Amstadt a été le coordinateur original, mais a cédé assez rapidement la place à Alexandre Julliard, qui est toujours en place. Un groupe d'actualités (news:comp.emulators.ms-windows.wine) a été créé en Juillet 1994. Au fil des ans, des ports pour d'autres Unix ont été ajoutés, avec le support pour Win32 quand les applications Win32 sont devenues très répandues."
-
-# type: <term></term>
-#: ../wine-faq.sgml:7 ../faq.sgml:364
-msgid ""
-"For more information, see <ulink url=\"http://www.winehq.com/site/history\"> "
-"http://www.winehq.com/site/history</ulink>"
-msgstr "Pour plus d'informations, voyez <ulink url=\"http://www.winehq.com/site/history\"> "
-"http://www.winehq.com/site/history</ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:371
-msgid "What is the current version of Wine?"
-msgstr "Quelle est la version actuelle de Wine ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:390
-msgid ""
-"A new version of Wine is distributed about every month. You will be able to "
-"keep up on all the latest releases by reading the newsgroup <ulink url="
-"\"news:comp.emulators.ms-windows.wine\"> comp.emulators.ms-windows.wine</"
-"ulink>, or by visiting the <ulink url=\"http://www.winehq.org\">Wine HQ "
-"homepage</ulink>. When downloading Wine from your FTP site of choice (see "
-"<ulink url=\"http://www.winehq.org/site/download\">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 file "
-"name. For instance, the distribution released on August 13, 2004 was called "
-"Wine-20040813.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."
-"org/site/cvs\"> Read-only CVS</ulink> access is also available."
-msgstr "Une nouvelle version de Wine sort a peu près chaque mois. Vous pourrez vous tenir au courant de toutes les dernières versions en lisant la newsgroup <ulink url="
-"\"news:comp.emulators.ms-windows.wine\"> comp.emulators.ms-windows.wine</"
-"ulink>, ou en visitant la page d'accueil de <ulink url=\"http://www.winehq.org\">WineHQ"
-"</ulink>. Quand vous téléchargez Wine depuis le site FTP de votre choix (voir la <ulink url=\"http://www.winehq.org/site/download\">page de téléchargement</ulink> pour certains de ces choix), vous pouvez vérifier que vous récupérez bien la dernière version en regardant le numéro de version dans le nom du fichier. Par exemple, la distribution réalisée le 13 août 2004 s'appelle Wine-20040813.tar.gz. Les fichiers correctifs [patch] sont aussi disponibles. Si vous avez la précédente version, vous pouvez télécharger et appliquer le correctif actuel plutôt que de réinstaller entièrement la dernière distribution. Le nom du correctif suit les mêmes conventions que la distribution mensuelle. Un accès en lecture du <ulink url=\"http://www.winehq."
-"org/site/cvs\"> Read-only CVS</ulink> est également disponible."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:397
-msgid "What is the current Status of Wine?"
-msgstr "Quel est le statut actuel de Wine ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:401
-msgid ""
-"As of mid 2004, Wine consists of about 1.6 million lines of code, written by "
-"more than 600 developers from dozens of countries around the world. Wine is "
-"in active use by an estimated 100K people. Wine implements more than 90% of "
-"the calls in popular Windows specifications such as ECMA-234 and Open32."
-msgstr "A mi 2004, Wine c'est 1,6 million de lignes de code, écrites par plus de 600 développeurs de douzaines de pays à travers le monde. On estime que Wine est utilisé par 100 000 personnes. Wine implémente plus de 90% des appels dans les spécifications Windows répandues telles que ECMA-234 et Open32."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:410
-msgid ""
-"You may also want to look at the <ulink url=\"http://www.winehq.org/site/"
-"status\"> Status page</ulink> for a global view on Wine's implementation "
-"progress."
-msgstr "Vous pouvez également vous référer à la <ulink url=\"http://www.winehq.org/site/"
-"status\">page du statut</ulink> pour avoir une vision globale de l'avancement des implémentations de Wine."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:417
-msgid "When will Wine be finished?"
-msgstr "Quand Wine sera-t-il fini ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:421
-msgid ""
-"Large software projects are never finished, only released. In any case Wine "
-"is chasing a moving target since every new release of Windows contains new "
-"API calls or variations on the existing ones."
-msgstr "Les grands projets informatiques ne sont jamais finis, ils n'existent que sous forme de versions. En tout cas, Wine court après une cible mouvante car chaque nouvelle révision de Windows contient de nouveaux appels aux API ou des variations sur celles existantes."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:426
-msgid ""
-"Because Wine is being developed by volunteers, it is difficult to predict "
-"when it will be ready for general release. But due to the much increased "
-"interest by companies in porting apps via Wine, Wine development is "
-"constantly getting more and more active. Right now we are working on "
-"releasing Wine 0.9 Real Soon Now(tm)."
-msgstr "Puisque Wine est développé par des bénévoles, il est difficile de prédire quand il sera prêt pour une une version générale. Mais l'intérêt croissant des entreprises pour porter des applications via Wine fait que, le développement de ce dernier est de plus en plus actif. A l'heure actuelle, nous sommes en train de travailler sur le lancement de Wine 0.9 Real Soon Now(tm)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:437
-msgid "Who is responsible for Wine?"
-msgstr "Qui est responsable de Wine ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:441
-msgid ""
-"Wine is available thanks to the work of many people. Please see the <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."
-msgstr "Wine existe grâce au travail de nombreuses personnes. Voyez le fichier <ulink "
-"url=\"http://source.winehq.org/source/AUTHORS\">AUTHORS</ulink> dans la distribution pour la liste compléte. Parmi les entreprises qui sont ou qui ont été impliquées dans le développement de Wine on trouve CodeWeavers, TransGaming, Corel, et Macadamian."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:452
-msgid ""
-"What undocumented APIs / interfaces are not understood? Would seeing "
-"Microsoft source help?"
-msgstr "Parmi les API/interfaces non documentées, lesquelles ne le sont pas parce qu'elles sont difficiles à comprendre? Est-ce que regarder les sources de Microsoft pourrait aider ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:458
-msgid ""
-"The best would be if the Windows API was fully documented, so Wine could be "
-"a perfect \"clean-room\" implementation. Seeing the source code might make "
-"it harder to prove that no copyright violations have taken place. That said, "
-"the documentation is often bad, nonexistent, and even misleading where it "
-"exists, so a fair amount of reverse engineering has been necessary, "
-"particularly in the shell (Explorer) interface. The biggest problem facing "
-"Wine though is simply lack of manpower. At one point, over 5000 people were "
-"working on Windows 2000. While Wine doesn't need to replicate all of Windows "
-"(we only cover the parts needed to make Windows programs work), that's still "
-"nearly 10 times more people working simply on one release than have "
-"<emphasis>ever</emphasis> worked on Wine, in the history of the project."
-msgstr "L'déal serait que les API Windows soient complétement documentées; Wine serait alors une implémentation parfaite et nickel chrome. Avec un accès au code source, il pourrait être plus difficile de prouver qu'aucun copyright n'a été violé. Ceci dit, la documentation est souvent mal faite, inexistante, et même erronée quand elle existe, ce qui fait qu'un taux important de retro-engineering a été nécessaire, particulièrement dans l'interface shell. Le problème majeur concernant Wine est cependant le manque de ressources humaines. A un moment donné, plus de 5000 personnes travaillaient sur Windows 2000. Alors que Wine n'a pas besoin de répliquer Windows entiérement (nous reprenons simplement les parties nécessaires pour faire tourner les programmes Windows), ce chiffre, qui représente le nombre de personnes mobilisé pour une seule version, est 10 fois supérieur au nombre de personnes ayant travaillé sur Wine jusqu'alors, depuis le début du projet."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:476
-msgid "Is TransGaming's latest patch included in the standard Wine release?"
-msgstr "Est-ce que le dernier correctif de TransGaming est inclu dans la version Wine standard ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:480
-msgid "No, it's not."
-msgstr "Non."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:483
-msgid ""
-"TransGaming makes money via a subscription service and the license of their "
-"Cedega tree is incompatible with the Wine license. Thus Cedega patches "
-"cannot be integrated into the Wine tree without express permission by "
-"TransGaming. They have submitted some of their work for integration into "
-"Wine, most notably DirectDraw and some DirectSound work, and such work has "
-"been integrated into the Wine tree. However it seems highly unlikely they "
-"will ever submit their Direct3D work."
-msgstr "TransGaming gagne de l'argent via un service d'abonnement et la license de son arbre Cedega est incompatible avec la license Wine. Les correctifs Cedega ne peuvent pas ainsi être intégré dans l'arbre de Wine sans la permission expresse de TransGaming. Ils ont proposé une partie de leur travail pour une intégration dans Wine, notamment DirectDraw et une partie de DirectSound, et celui-ci a été intégré dans l'arbre de Wine. Cependant, il semble très improbable qu'ils ne proposeront un jour leur travail sur Direct3D."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:497
-msgid "Will there be a Windows version of Wine?"
-msgstr "Y aura-t-il une version Windows de Wine ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:501
-msgid ""
-"Some people are working on getting Wine code to compile on Windows using one "
-"of the following projects as a basis:"
-msgstr "Certaines personnes sont en train de travailler sur la portabilité de Wine pour qu'il puisse être compilé sous Windows en utilisant l'un des projets suivants comme base :"
-
-# type: <term></term>
-#: ../wine-faq.sgml:7 ../faq.sgml:507
-msgid ""
-"Cygwin (<ulink url=\"http:/www.cygwin.com/\">http://www.cygwin.com</ulink>)"
-msgstr "Cygwin (<ulink url=\"http:/www.cygwin.com/\">http://www.cygwin.com</ulink>)"
-
-# type: <term></term>
-#: ../wine-faq.sgml:7 ../faq.sgml:513
-msgid ""
-"MinGW (<ulink url=\"http:/www.mingw.org/\">http://www.mingw.org</ulink>)"
-msgstr "MinGW (<ulink url=\"http:/www.mingw.org/\">http://www.mingw.org</ulink>)"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:519
-msgid ""
-"ReactOS (<ulink url=\"http://www.reactos.com/\">http://www.reactos.com</"
-"ulink>)"
-msgstr ""
-"ReactOS (<ulink url=\"http://www.reactos.com/\">http://www.reactos.com</"
-"ulink>)"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:525
-msgid ""
-"There's some progress, so a Wine version that's usable on Windows might be "
-"available at some time in the future."
-msgstr "Il y a des progrès, une version de Wine utilisable sous Wine devrait donc être disponible dans un futur proche."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:529
-msgid ""
-"Part of the rationale for these projects is to find out areas where Wine "
-"portability is lacking. This is especially true of the ReactOS project which "
-"is a reimplementation of the Windows kernel and should thus be able to reuse "
-"most of Wine dlls."
-msgstr "La logique pour ces projets est en partie de trouver des zones où la portabilité de Wine est absente. C'est particulièrement vrai pour le porjet ReactOS qui est une réimplémentation du noyau Windows et qui devrait ainsi être capable de réutiliser la plupart des dll de Wine."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:535
-msgid ""
-"Another reason for pursuing these projects is to be able to replace a single "
-"Windows dll with its Wine counterpart. Besides being a good test for the "
-"Wine dll, this lets us detect cases where we made incorrect assumptions "
-"about how the dlls interact."
-msgstr "Une autre raison de mener ces projets est la possibilité de remplacer une simple dll Windows par son alter ego Wine. Outre que c'est un bon test pour la dll Wine, cela nous laisse la possibilité de détecter les cas où nous nous trompons au sujet de l'interaction des dll entre elles."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:545
-msgid "Can I use Windows printer drivers in Wine?"
-msgstr "Puis-je utiliser les pilotes d'impression Windows dans Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:549
-msgid ""
-"Native printer drivers are not supported. At one time Wine supported 16bit "
-"native drivers but that was long ago. Wine uses the printers (and other "
-"devices) installed in your operating system. For the most part if you don't "
-"have the device installed on your OS then wine can't use it."
-msgstr "Les pilotes d'impressions natifs ne sont pas supportés. Il fût un temps où Wine supportait les pilotes natifs 16bit mais cela remonte à longtemps. Wine utilise les imprimantes (et autres matériels) installées sur votre système d'exploitation. La plupart du temps, si vous n'avez le matériel installé sur votre SE alors Wine ne peut pas l'utiliser."
-
-# type: <title></title>
-#: ../wine-faq.sgml:7 ../faq.sgml:559
-#, no-wrap
-msgid "What do I need in order to use Wine?"
-msgstr "De quoi ai-je besoin pour utiliser Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:563
-msgid ""
-"Under what hardware platform(s) and operating system(s) will Wine(Lib) run?"
-msgstr "Sous quelle(s) plateforme(s) et système(s) d'opération tournera Wine(Lib) ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:569
-msgid ""
-"Wine is being developed specifically to run on the <emphasis>Intel x86</"
-"emphasis> class of CPUs under certain UNIXes that run on this platform. "
-"Winelib however is capable of porting the Windows applications "
-"<emphasis>source code</emphasis> to other platforms also, not only x86."
-msgstr "Wine est développé pour tourner spécifiquement sur une classe de CPU Intel x86 sous certains UNIX qui tournent sous cette plate-forme. Winelib est cependant capable de porter le code source des applications Windows également vers d'autres plate-formes, et pas seulement vers les x86."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:576
-msgid ""
-"Thus running Windows binaries on other platforms (e.g. Mac OS X on PowerPC) "
-"using just Wine is <emphasis>not</emphasis> possible. You would have to "
-"either run Wine in an emulated x86 environment or take the Windows "
-"application source code and recompile it using Winelib."
-msgstr "Ainsi faire tourner des binaires Windows sous d'autres plate-formes (par exemple: Mac OS X sous PowerPC) en utilisant seulement Wine est impossible. Il vous faudrait soit faire tourner Wine dans un environnement émulé x86 ou récupérer le code source de l'application Windows et le recompiler en utilisant Winelib."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:583
-msgid ""
-"These are the platforms supported by Wine. Winelib support for other "
-"platforms keeps evolving, so it's not specifically listed here."
-msgstr "Voici les plate-formes supportées par Wine. La compatibilité Winelib avec d'autres plate-formes est sans cesse en évolution, donc il n'en est pas fait spécialement mention dans cette liste."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:588
-msgid ""
-"NetBSD, OpenBSD, UnixWare, and SCO OpenServer 5 worked at one time, but Wine "
-"now requires kernel-level threads which are not currently available (or "
-"understood by the Wine team) on those platforms."
-msgstr "NetBSD, OpenBSD, UnixWare, et SCO OpenServer 5 marchaient à une époque, mais Wine nécessite maintenant des unités d'éxécution au niveau du programme résident [kernel-level threads] qui ne sont pas actuellement disponibles (ou pas bien maîtrisés par l'équipe Wine) sur ces plate-formes."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:593
-msgid ""
-"The Wine development team hopes to attract the interest of other commercial "
-"UNIX and UNIX clone vendors as well."
-msgstr "L'équipe développement Wine espère également attirer l'intérêt d'autres vendeurs d'UNIX commercial et clone d'UNIX."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:597
-msgid ""
-"BeOS: porting efforts (BeWine) used to be pretty strong, but BeOS has severe "
-"limitations in Unix call support. The demise of Be further hampered the "
-"project though it might come back one day on one of the open BeOS projects. "
-"In any case a functional port seems unlikely to ever happen at this stage."
-msgstr "BeOS: efforts de portage asssez sérieux autrefois (BeWine), mais BeOS connaît de sévères limitations dans le support d'appel Unix. La disparition de Be a géné le projet bien qu'il puisse revenir un jour parmi un des projets ouverts BeOS. En tout cas, il apparaît peu probable qu'un port fonctionnel voit le jour en l'état actuel."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:605
-msgid ""
-"Mac OS X / Darwin: The <ulink url=\"http://darwine.sourceforge.net/project."
-"html\">Darwine</ulink> is currently working on porting Wine to the Darwin/"
-"x86 platform. Their goal is to eventually make it possible to run x86 "
-"Windows applications on Darwin/PPC and then Mac OS X by using Bochs."
-msgstr "Mac OS X / Darwin: Le projet Darwine <ulink url=\"http://darwine.sourceforge.net/project."
-"html\">Darwine</ulink> s'occupe actuellement du portage de Wine sur la plate-forme Darwin/x86. Leur but est de rendre finalement possible l'exécution d'applications x86 Windows sur Darwin/PPC puis ensuite sur Mac OS X en utilisant Bochs."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:611
-msgid ""
-"FreeBSD: This port is well maintained and should work with limitations in "
-"specific areas (mainly missing device/hardware support)."
-msgstr "FreeBSD: Le suivi de ce portage est bien assuré malgré quelques limites dans certaines situations précises(principalement en l'absence de support périphérique/matériel)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:616
-msgid ""
-"Linux/x86: Works, and as the most popular platform for both developers and "
-"users, it is the best supported platform of all."
-msgstr "Linux/x86: Pas de problème, et en tant que plate-forme préférée des développeurs et utilisateurs, c'est la plate-forme la mieux supportée de toutes."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:625
-msgid ""
-"What minimum CPU must I have in my computer to be able to run Wine and MS "
-"Windows applications smoothly?"
-msgstr "Quelle puissance CPU minimale doit avoir mon ordinateur pour que Wine et les applications MS Windows tournent bien?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:631
-msgid "We need to differentiate between Wine and Winelib here."
-msgstr "Nous devons différencier ici Wine et Winelib."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:634
-msgid ""
-"Wine won't run on any x86 CPU less than an 80386 due to address management "
-"limitations."
-msgstr "Wine ne tournera sur aucun CPU x86 inférieur au 80386 à cause des limitations de gestion d'adresse."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:638
-msgid ""
-"It is known to also work in the 80486 and upwards compatible CPUs. The basic "
-"test is, if you can run X11 now, you should be able to run Wine and MS "
-"Windows applications under it."
-msgstr "Il fonctionnerait également sur les 80486 et supérieur. Le test simple est, si vous pouvez faire tourner X11 actuellement, vous devriez alors pouvoir faire tourner Wine et des applications MS Windows."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:643
-msgid ""
-"As always, the faster your CPU, the better. Having a math coprocessor is "
-"unimportant. However, having a graphics accelerated video card supported by "
-"X will help greatly."
-msgstr "Comme toujours, plus votre CPU est puissant, mieux c'est. Avoir un coprocesseur math n'est pas important. Cependant, avoir une carte graphique avec accélération 3D supportée par le X sera un plus."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:648
-msgid ""
-"Depending on your application you may find that faster speeds are required "
-"for sensible use. We can't give specific advice on that due to the vast "
-"range of applications out there. However the rule of thumb is that if your "
-"application runs fine on Windows, it should run fine on the same platform in "
-"Wine."
-msgstr "En fonction de votre application vous trouverez probablement que des vitesses plus grandes sont requises pour une utilisation avancée. On ne peut pas donner de conseils spécifiques sur ce sujet à cause du vaste choix des applications disponibles. Cependant la règle de base est que si votre application tourne correctement sous Windows, elle devrait tourner correctement sous la même pate-forme avec Wine."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:660
-msgid ""
-"How much disk space will the Wine source code and binaries take on my hard "
-"drive?"
-msgstr "Quel espace le code source de Wine et les binaires prendront-ils sur mon disque dur?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:666
-msgid ""
-"You need approximately 250 megabytes of free hard drive space to store and "
-"compile the source code. Wine also needs about 18 megs in your /tmp "
-"directory. And about 50 MB are needed to do a make install."
-msgstr "Il vous faut a peu près 250 megaoctets d'espace libre sur le disque dur pour stocker et compiler le code source. Wine requiert également 18 Mo dans votre dossier /tmp. Et environ 50 Mo sont requis pour faire un \"make install\"."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:671
-msgid ""
-"Binary packages, especially those not containing debug information, have "
-"much lower disk space requirements, usually in the 20MB range."
-msgstr "Les paquets binaires, en particulier ceux ne contenant pas d'information de deboggage, ont un besoin moindre d'espace disque disponible, habituellement aux alentours de 20Mo."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:680
-msgid "What other software do I need to install, compile and run Wine?"
-msgstr "De quel autre logiciel ai-je besoin pour installer, compiler et faire tourner Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:689
-msgid ""
-"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://source.winehq.org/source/README\"> http://source.winehq."
-"org/source/README</ulink>)."
-msgstr "De nombreux outils de développement sont nécessaires pour compiler Wine. Une liste des paquets requis pour de nombreuses distributions se trouve dans le fichier README "
-"(<ulink url=\"http://source.winehq.org/source/README\"> http://source.winehq."
-"org/source/README</ulink>)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:692
-msgid "To run Wine, you will need the following:"
-msgstr "Pour lancer Wine, vous aurez besoin des éléments suivants:"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:697
-msgid "The compiled Wine binary"
-msgstr "Le binaire Wine compilé"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:700
-msgid "A properly configured wine.conf file (or ~/.winerc file)"
-msgstr "Un fichier wine.conf parfaitement configuré (ou le fichier ~/.winerc)"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:703
-msgid "An installed and working X Window system"
-msgstr "Un system X Window en état de marche"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:706
-msgid "Some Windows programs to test"
-msgstr "Des programmes Windows à tester"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:714
-msgid ""
-"How much RAM do I need to have on my UNIX system to be able to run Wine and "
-"MS Windows applications smoothly?"
-msgstr "De combien de RAM ai-je besoin sur mon système UNIX pour que Wine et les applications MS Windows tournent bien?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:720
-msgid ""
-"If you can run X smoothly on your UNIX system now, you should be able to run "
-"Wine and MS Windows applications just fine too, depending on how memory "
-"hungry the application is."
-msgstr "Si vous arrivez à faire tourner le X de manière fluide sur votre système UNIX actuellement, vous devriez pouvoir faire tourner Wine et des applications MS Windows tout aussi bien, en fonction de la gourmandise en RAM de l'application."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:725
-msgid ""
-"Wine's memory requirements will depend on the application or game that you "
-"choose to run. You will need to meet the minimum requirements for the "
-"application as well as the overhead of your underlying OS. You may want to "
-"check with the vendor of the application for its suggested memory "
-"requirements."
-msgstr "Les besoins mémoire de Wine dépendront de l'application ou du jeu que vous avez choisi d'exécuter. Il vous faudra répondre au besoin minimal de l'application ainsi que la surcharge de votre système d'exploitation sous-jacent. Vous pourrez voir avec le revendeur pour les besoins en mémoire indiqués pour cette application."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:736
-msgid "How long does Wine take to build"
-msgstr "Combien de temps faut-il pour compiler Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:740
-msgid ""
-"Wine is getting to be quite large, and building from scratch takes a lot of "
-"processing. As of May 2004, compile times were around 10 minutes on a Athlon "
-"2000 with 512 MB of RAM and 20 minutes on a Athlon 1200 with 640 MB of RAM. "
-"If you have a CVS copy of wine, you may not need to rebuild every thing each "
-"update."
-msgstr "Wine tend à devenir assez important, et pour le compiler intégralement il faut un grand nombre de processus. Depuis mai 2004, les temps de compilation étaient d'environ 10 minutes sur un Athlon 2000 avec 512 Mo de RAM et 20 minutes sur un Athlon 1200 avec 640 Mo de RAM. Si vous avez une copie CVS de Wine, vous n'aurez sans doute pas besoin de tout reconstruire à chaque mise à jour."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:751
-msgid ""
-"I have a Drivespaced, Doublespaced or Stackered DOS partition. Can Wine run "
-"MS Windows binaries located in such a partition?"
-msgstr "J'ai une partition Drivespaced, Doublespaced ou Stackered. Est-ce que Wine peut exécuter des binaires MS Windows situés dans une de ces partitions?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:765
-msgid ""
-"Yes, but only if the operating system supports mounting those types of "
-"drives. There is a Linux file system driver called dmsdos that will allow "
-"read/write access to Doublespaced and Drivespace 1.0. More "
-"specifically, it supports mounting DOS 6.0 and 6.2 Doublespaced, DOS 6.22 "
-"Drivespaced, and Windows 95 Doublespaced compressed partitions (read and "
-"write access works fine, but write access is slow). It can be found at "
-"<ulink url=\"ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/\"> "
-"ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/</ulink>"
-msgstr "Oui, mais seulement si le système d'opération supporte le montage de ces types de disques. Il y a un pilote de système de fichier Linux nommé dmsdos qui permettra les accès lecture/écriture vers des lecteurs Doublespaced et Drivespace 1.0 drives. Plus spécifiquement, il supporte le montage de partitions compressées DOS 6.0 et 6.2 Doublespaced, DOS 6.22 Drivespaced, et Windows 95 Doublespaced (l'accès en lecture et en écriture marche correctement, mais l'accès en écriture est lent). On peut le trouver à "
-"<ulink url=\"ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/\"> "
-"ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/</ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:772
-msgid "Do I need to have a DOS partition on my system to use Wine?"
-msgstr "Ai-je besoin d'une partition DOS sur mon système pour utiliser Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:776
-msgid ""
-"You do not need a licensed and installed copy of DOS or MS Windows to "
-"install, configure and run Wine. However, Wine has to be able to 'see' an MS "
-"Windows binary (i.e. application) if it is to run it."
-msgstr "Vous n'avez pas besoin d'une copie installée et sous license de DOS ou de MS Windows pour installer, configurer et utiliser Wine. Cependant, Wine doit pouvoir 'voir' un binaire MS Windows (c.à.d. l'application) si elle doit être exécutée."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:786
-msgid ""
-"Does MS Windows need to be loaded into that partition in order to run MS "
-"Windows programs under Wine?"
-msgstr "MS Windows doit-il être chargé dans cette partition pour exécuter des programmes MS Windows sous Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:792
-msgid ""
-"Many folks have successfully installed and run programs in their UNIX file "
-"system without having a DOS partition or MS Windows. However, in many cases "
-"you need a directory and file infrastructure that is similar to an existing "
-"Windows installation. Some applications' installation programs want to "
-"distribute some of the package's files into the /windows and /windows/system "
-"directories in order to run, and unless these exist on your UNIX file "
-"system, those programs will not install correctly and probably will not run "
-"well, if at all. Most packages will set that up for you as part of the "
-"install process."
-msgstr "Beaucoup de monde a installé et exécuté, avec succès, des programmes dans leur système de fichiers UNIX sans avoir une partition DOS ou MS Windows. Cependant, dans beaucoup de cas, il faut une infrastructure de répertoires et fichiers similaire à une installation existante Windows. Certains programmes d'installation d'applications veulent envoyer les fichiers de package dans les dossier /windows et /windows/system pour s'exécuter, et à moins que ceux-ci n'existent sur système de fichiers UNIX, ces programmes ne s'installeront pas correctement et ne tourneront probablement pas bien, s'ils arrivent à tourner. La plupart des packages régleront cela pour vous en tant que partie du programme d'installation."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:804
-msgid ""
-"If you have a DOS partition with MS Windows installed in it, make sure that "
-"your UNIX system can 'see' this partition (check your /etc/fstab file or "
-"mount the partition manually) so that Wine can run the MS Windows binaries "
-"located in the DOS partition. To run without a DOS partition, you need to "
-"set a UNIX path to be your drive C, and make sure that the /windows and /"
-"windows/system directories point to some place that actually exist."
-msgstr "Si vous avez une partition DOS avec MS Windows installée dessus, assurez vous que votre système UNIX peut 'voir' cette partition (vérifiez votre fichier /etc/fstab ou montez la partition à la main) pour que Wine puisse exécuter les binaires MS Windows situés sur la partition DOS. Pour l'exécution sans une partition DOS, il faut fixer un chemin UNIX correspondant au lecteur C, et s'assurer que les dossiers /windows et /windows/system pointent sur un endroit qui existe bel et bien."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:813
-msgid ""
-"Here's an example, copied from a machine which has no DOS partition but "
-"successfully runs Wine:"
-msgstr "Voici un exemple, copié depuis une machine qui n'a pas de partition DOS mais qui exécute avec succès Wine:"
-
-# type: <screen></screen>
-#: ../wine-faq.sgml:7 ../faq.sgml:817
-#, no-wrap
-msgid ""
-"<screen>    [Drive C]      \n"
-"          Path=/var/lib/wine\n"
-"          Type=hd\n"
-"    [wine]\n"
-"          Windows=c:\\windows\n"
-"          System=c:\\windows\\system\n"
-"          Temp=e:\\\n"
-"          Path=c:\\windows;c:\\windows\\system;c:\n"
-"        "
-msgstr ""
-"<screen>    [Drive C]      \n"
-"          Path=/var/lib/wine\n"
-"          Type=hd\n"
-"    [wine]\n"
-"          Windows=c:\\windows\n"
-"          System=c:\\windows\\system\n"
-"          Temp=e:\\\n"
-"          Path=c:\\windows;c:\\windows\\system;c:\n"
-"        "
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:827
-msgid ""
-"In <filename>/var/lib/wine/windows</filename>, you will need to install a "
-"<filename>win.ini</filename> config file that you might find on a typical MS "
-"Windows 3.1 machine. The directory <filename>/var/lib/wine/windows/system</"
-"filename> should exist, but doesn't need to contain anything. However, to "
-"use MS DLLs, you can copy them into that directory. Note that this is a "
-"contravention of the Windows licence unless Windows is properly installed on "
-"the machine. If you have DOS/MS Windows installed on your system, you can "
-"mount that partition at bootup by modifying the file <filename>/etc/fstab</"
-"filename> in your UNIX partition (assuming that the UNIX kernel supports the "
-"DOS/MS Windows file system type)."
-msgstr "Dans <filename>/var/lib/wine/windows</filename>, il vous faudra installer un fichier de configuration win.ini que vous pourrez trouver sur une machine MS Windows 3.1 classique. Le dossier <filename>/var/lib/wine/windows/system</filename> devrait exister, mais il ne sera pas nécessaire qu'il contienne quoique ce soit. Cependant, pour utiliser des MS DLL, vous pouvez les copier dans ce dossier. Notez que ceci est une entorse à la license Windows à moins que Windows soit installé sur la machine. Si vous avez un DOS/MS Windows installé sur votre système, vous pouvez montez cette partition au démarrage en modifiant le fichier /etc/fstab dans votre partition UNIX (en supposant que le noyau UNIX supporte le type de système de fichiers DOS/MS Windows)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:840
-msgid ""
-"If you edit this file by hand, it should contain something similar to the "
-"following:"
-msgstr "Si vous éditez ce fichier à la main, il devrait afficher quelque chose du genre :"
-
-# type: <screen></screen>
-#: ../wine-faq.sgml:7 ../faq.sgml:844
-#, no-wrap
-msgid ""
-"<screen>/dev/hda1 /dosc msdos uid=0,gid=100,umask=007 0 0\n"
-"        "
-msgstr ""
-"<screen>/dev/hda1 /dosc msdos uid=0,gid=100,umask=007 0 0\n"
-"        "
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:847
-msgid ""
-"This will allow you to read and write to the DOS partition without being "
-"root."
-msgstr "Cela vous permettra de lire et d'écrire sur la partition DOS sans être le root."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:856
-msgid ""
-"If Wine completely replaces MS Windows, will it duplicate all of the "
-"functions of MS Windows?"
-msgstr "Si Wine remplace complétement MS Windows, est-ce qu'il dupliquera toutes les fonctions de MS Windows?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:862
-msgid ""
-"Wine's goal is to make it possible to run Windows applications on Unix. To "
-"this end it will provide replacements for just those DLLs and APIs that are "
-"needed by these Windows applications. This means that Wine will not provide "
-"replacements for DLLs that are not shipped with Windows or are always "
-"shipped with Windows application (e.g. the Visual Basic run time). This also "
-"means that implementing an API that no application ever uses is not a "
-"priority. Similarly, until there are applications out there that use the "
-"Win64 API, it will not be a priority. That being said, we will certainly try "
-"to keep our options open and to improve our API coverage as we can."
-msgstr "L'objectif de Wine est de rendre possible l'exécution d'applications Windows sous Unix. Dans cette perspective, il fournira des remplacements juste pour les DLL et API qui sont requises pour ces applications Windows. Cela signifie que Wine ne fournira aucun remplacement pour les DLL qui ne sont pas fournies avec Windows ou qui sont toujours fournies avec une application Windows (par exemple l'exécutable de Visual Basic). Cela signifie également que l'implémentation d'une API qu'aucune application n'utilise jamais n'est pas une priorité. De la même manière, tant que des applications utilisant l'API Win64 ne sont pas disponibles, cela ne sera pas une priorité. Ceci dit, on essayera certainement de garder des portes ouvertes et d'améliorer notre couverture d'API autant que possible."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:875
-msgid ""
-"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>, <ulink url=\"http://www."
-"freebsd.org/\">FreeBSD</ulink> and <ulink url=\"http://www.reactos.com/"
-"\">ReactOS</ulink> kernel developers would certainly appreciate your "
-"contribution."
-msgstr "Comme Wine n'est pas non plus une SE, écrire des pilotes de matériel ne fait pas partie des objectifs de Wine. Cependant, si vous êtes intéressé par les pilotes de matériel, les développeurs de noyau sur <ulink url=\"http://www.kernel.org/\">Linux</ulink>, FreeBSD (http://www.freebsd.org/) et <ulink url=\"http://www.reactos.com/"
-"\">ReactOS</ulink> apprécieront certainement votre contribution."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:883
-msgid ""
-"Similarly Wine does not try to be a desktop environment so providing applets "
-"such as a calculator, a file manager or even window manager that look like "
-"Windows, are low priority or would even best be done as a separate project. "
-"Such projects would also 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</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."
-msgstr "De la même manière, Wine n'essaie pas d'être un environnement de bureau donc fournir des applets telle qu'une calculatrice, un gestionnaire de fichier ou même un gestionnaire de fenêtre qui ressemble à Windows n'est pas prioritaire ou serait même mieux fait dans un projet à part. De tels projets feraient également pour une grande double emploi avec d'autres projets open-source. Là encore, ils existent des projets où votre aide dans ce domaine seraient certainement appréciée, tels que les environnements de bureau <ulink url=\"http://www.gnome."
-"org/\">Gnome</ulink> ou <ulink url=\"http://www.kde.org/\">KDE</ulink>. Vous aurez en plus la satisfaction de voir que votre contribution est utile à tous et pas seulement aux utilisateurs de Wine."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:900
-msgid ""
-"Will I be able to install MS Windows applications in any flavor of a UNIX "
-"file system?"
-msgstr "Pourrai-je installer des applications MS Windows sur tout système UNIX quel qu'il soit?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:907
-msgid ""
-"Wine is written to be file system independent, so MS Windows applications "
-"will install and run under virtually any file system supported by your brand "
-"of UNIX."
-msgstr "Wine est écrit pour être indépendant du système de fichiers, donc les applications MS Windows s'installeront et s'exécuteront virtuellement sous n'importe quel système de fichiers supporté par votre marque d'UNIX."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:916
-msgid "Will Wine run only under X, or can it run in character mode?"
-msgstr "Est-ce wue Wine ne s'exécutera que sous le X, ou peut-il s'exécuter en mode texte?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:920
-msgid ""
-"Most of Wine's development effort is geared towards MS Windows' GUI, but "
-"some limited support for character mode has appeared, by setting "
-"<parameter>GraphicsDriver=ttydrv</parameter> in wine.conf's <parameter>[wine]"
-"</parameter> section."
-msgstr "La plupart des efforts de développement de Wine est tournée vers l'interface graphique utilisateur de MS Windows, mais un support limité pour le mode de texte est apparu, en réglant <parameter>GraphicsDriver=ttydrv</parameter> dans la section wine.conf <parameter>[wine]</parameter>."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:926
-msgid ""
-"Wine's infrastructure is already somewhat prepared for supporting other "
-"graphics drivers than x11drv, but no real \"alternative\" graphics driver "
-"has been developed yet."
-msgstr "L'infrastructure de Wine est déjà quelquechose préparé pour supporter d'autres pilotes graphiques que x11drv, mais aucun pilote graphique \"alternatif\" n'a encore été développé."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:935
-msgid ""
-"Will Wine run under any X window manager? Does it require a window manager "
-"at all?"
-msgstr "Est-ce que Wine tournera sur n'importe quel gestionnaire de fenêtres X? Est-ce qu'il nécessite un gestionnaire de fenêtre particulier?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:939
-msgid ""
-"Wine is window manager independent, so the X window manager you choose to "
-"run has (almost) no bearing on your ability to run MS Windows programs under "
-"Wine. Wine uses standard X libraries, so no additional ones are needed. Wine "
-"has its own window management, which acts like MS Windows. It can be turned "
-"off to use the native window manager by modifying Managed or Desktop "
-"settings as described in <command>man wine.conf</command>."
-msgstr "Wine est indépendant du gestionnaire de fenêtre, donc le gestionnaire de fenêtres X que vous choisissez de lancer n'a presque aucune incidence sur votre capacité à exécuter des programmes MS Windows sous Wine. Wine utilise des bibliothèques X standard, aucun ajout n'est donc requis. Wine a son propre gestionnaire de fenêtres, qui agit comme MS Windows. Il peut être arrêté pour utiliser le gestionnaire de fenêtres natif en modifiant la configuration de Managed ou Desktop comme décrit dans <command>man wine.conf</command>."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:952
-msgid "Will 32-bit Windows 95/98/ME/NT/2000/XP applications run under Wine?"
-msgstr "Est-ce que les applications 32-bit de Windows 95/98/ME/NT/2000/XP tourneront sous Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:956
-msgid "Yes, 32-bit programs are now well supported."
-msgstr "Oui, les programmes 32-bit sont bien supportés."
-
-# type: <title></title>
-#: ../wine-faq.sgml:7 ../faq.sgml:963
-#, no-wrap
-msgid "Getting Wine"
-msgstr "Récupérer Wine"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:966
-msgid "Where can I get Wine?"
-msgstr "Où puis-je récupérer Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:970
-msgid ""
-"Because of lags created by using a mirror, word of the latest release may "
-"reach you before the release is actually available at the ftp sites listed "
-"here. The sources are available from the following locations:"
-msgstr "A cause de décalages dus à l'utilisation d'un site mirroir, vosu pourriez avoir vent de la dernière révision avant même que la révision ne soit disponible sur les sites ftp dans la liste ci-dessous. Les sources sont disponibles depuis les sites suivants:"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:979
-msgid ""
-"<ulink url=\"http://sourceforge.net/project/showfiles.php?group_id=6241&amp;"
-"package_id=77449\"> http://sourceforge.net/project/showfiles.php?"
-"group_id=6241&amp;package_id=77449 </ulink>"
-msgstr ""
-"<ulink url=\"http://sourceforge.net/project/showfiles.php?group_id=6241&amp;"
-"package_id=77449\"> http://sourceforge.net/project/showfiles.php?"
-"group_id=6241&amp;package_id=77449 </ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:986
-msgid ""
-"<ulink url=\"http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/\"> "
-"http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/ </ulink>"
-msgstr ""
-"<ulink url=\"http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/\"> "
-"http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/ </ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:993
-msgid ""
-"<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>"
-msgstr ""
-"<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>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1001
-msgid ""
-"<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>"
-msgstr ""
-"<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>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1009
-msgid ""
-"<ulink url=\"ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/\"> ftp://"
-"orcus.progsoc.uts.edu.au/pub/Wine/development/ </ulink>"
-msgstr ""
-"<ulink url=\"ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/\"> ftp://"
-"orcus.progsoc.uts.edu.au/pub/Wine/development/ </ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1016
-msgid ""
-"It should also be available from any other site that mirrors ibiblio.org, "
-"see <ulink url=\"http://www.ibiblio.org/pub/Linux/MIRRORS.html\">http://www."
-"ibiblio.org/pub/Linux/MIRRORS.html</ulink>. Some of these 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 "
-"Wine-YYYYMMDD.tar.gz. Simply replace YYYYMMDD in the distribution file name "
-"with the numbers for year, month and date, respectively. The latest one is "
-"the one to get."
-msgstr "Il devrait être également disponible sur tout autre site mirroir de ibiblio.org, voyez <ulink url=\"http://www.ibiblio.org/pub/Linux/MIRRORS.html\">http://www."
-"ibiblio.org/pub/Linux/MIRRORS.html</ulink>. Certains de ces sites archivent parfois des versions antérieures de Wine ainsi que la version courante. Pour savoir quelle est la dernière version, jetez un oeil sur le nom du fichier, qui aura la forme Wine-AAAAMMJJ.tar.gz. Remplacez simplement AAAAMMJJ dans le nom de la distribution par le numéro respectivement de l'année, du mois et du jour. Le plus récent est celui à récupérer."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1029
-msgid ""
-"Wine binary packages are available for several OS'es and distributions. See "
-"<ulink url=\"http://www.winehq.org/site/download\"> the download page</"
-"ulink> for the most recent list."
-msgstr "Les packages binaires de Wine sont disponibles pour différents SE et distributions. Voyez la <ulink url=\"http://www.winehq.org/site/download\">page de téléchargement</ulink> pour une liste récente."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1036
-msgid "Is there a CVS tree?"
-msgstr "Y-a-t-il un arbre CVS?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1040
-msgid ""
-"Current Wine sources are also available via anonymous client/server CVS. You "
-"will need CVS 1.9 or above. If you are coming from behind a firewall, you "
-"will either need a hole in the firewall for the CVS port (2401) or use SOCKS."
-msgstr "Les sources actuelles de Wine sont aussi disponibles via un accès anonyme client/serveur sur le CVS. Il vous faudra la version 1.9 du CVS ou tout autre version supérieure. Si vous êtes derrière un firewall, vous aurez également besoin d'ouvrir le port 2401 de votre firewall ou d'utiliser le protocole SOCKS."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1046
-msgid "To login to the CVS tree, do"
-msgstr "Pour vous connecter au serveur CVS, faites"
-
-# type: <screen></screen>
-#: ../wine-faq.sgml:7 ../faq.sgml:1049
-#, no-wrap
-msgid ""
-"<screen>export CVSROOT=:pserver:cvs at cvs.winehq.org/home/wine\n"
-"cvs login\n"
-"        "
-msgstr ""
-"<screen>export CVSROOT=:pserver:cvs at cvs.winehq.org/home/wine\n"
-"cvs login\n"
-"        "
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1053
-msgid ""
-"Use \"cvs\" as the password (without the quotes). Note that <filename>/home/"
-"wine</filename> is a path on the server, not on your machine. To check out "
-"the entire Wine source tree (which may be slow), use"
-msgstr "Utilisez \"cvs\" comme mot de passe (sans les guillemets). Notez que /home/wine est un chemin sur le serveur, pas sur votre machine. Pour vérifier entièrement l'arbre source de Wine (ce qui peut être très lent), utilisez"
-
-# type: <screen></screen>
-#: ../wine-faq.sgml:7 ../faq.sgml:1059
-#, no-wrap
-msgid ""
-"<screen>cvs -z 3 checkout wine \n"
-"        "
-msgstr ""
-"<screen>cvs -z 3 checkout wine \n"
-"        "
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1062
-msgid ""
-"or if you just want a subtree, or individual file, you can do that too with"
-msgstr "ou si vous voulez juste un sous-arbre, ou un fichier particulier, vous pouvez faire"
-
-# type: <screen></screen>
-#: ../wine-faq.sgml:7 ../faq.sgml:1066
-#, no-wrap
-msgid ""
-"<screen>cvs -z 3 checkout wine/ANNOUNCE \n"
-"        "
-msgstr ""
-"<screen>cvs -z 3 checkout wine/ANNOUNCE \n"
-"        "
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1073
-msgid ""
-"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.org/site/cvs#cvsservers"
-"\"> http://www.winehq.org/site/cvs#cvsservers</ulink>"
-msgstr "Il faut savoir, cependant, que récupérer entièrement l'arbre source de Wine via CVS est assez lent, spécialement si l'on compare par rapport à la récupération depuis un mirroir FTP situé près de chez vous. Pour une liste de site mirroir CVS, voyez <ulink url=\"http://www.winehq.org/site/cvs#cvsservers"
-"\"> http://www.winehq.org/site/cvs#cvsservers</ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1076
-msgid ""
-"Patch files are also available, so that you don't have to download, install, "
-"and configure the entire distribution each month if you are current to the "
-"previous release. Patch file release names follow the same numbering "
-"convention as do the general releases, and take the form"
-msgstr "Des fichiers correctifs sont aussi disponibles, pour que vous n'ayez pas à télécharger, installer et configurer la distribution entière chaque mois si vous voulez la dernière version. Le nom des versions des fichiers patch suit la même règle que les révisions générales, et prend donc la forme"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1083
-msgid "Wine-YYYYMMDD.diff.gz"
-msgstr "Wine-YYYYMMDD.diff.gz"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1086
-msgid ""
-"Patch files are available from the same sites that distribute the full "
-"release. To upgrade to a new release by using a patch file, first cd to the "
-"top-level directory of the release (the one containing the README file), "
-"then do a \"make clean\", and patch the release with"
-msgstr "Les correctifs sont disponibles sur les mêmes sites qui distribuent la version compléte. Pour se mettre à jour avec une nouvelle révision avec un correctif, changez d'abord de dossier jusqu'au répertoire racine de la révision (celui contenant le fichier README), faites ensuite un \"make clean\", et mettez à jour la révision avec"
-
-# type: <screen></screen>
-#: ../wine-faq.sgml:7 ../faq.sgml:1093
-#, no-wrap
-msgid ""
-"<screen>gunzip -c patch-file | patch -p1 \n"
-"        "
-msgstr ""
-"<screen>gunzip -c patch-file | patch -p1 \n"
-"        "
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1096
-msgid ""
-"where patch-file is the name of the patch file something like Wine-YYYYMMDD."
-"diff.gz. You can then re-run ./configure, and then run make depend && make"
-msgstr "où patch-file est le nom du fichier correctif sous la forme Wine-AAAAMMJJ.diff.gz. Vous pouvez ensuite relancer ./configure, et ensuite exécuter make depend && make"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1101
-msgid ""
-"If you are mirroring the Wine distribution from the tsx-11 site and wish to "
-"be listed here in this FAQ, please add it to the \"things to go into the "
-"documentation\" area."
-msgstr "Si vous voulez créer un site mirroir de la distribution Wine depuis le site tsx-11 et que vous voulez faire partie de la liste de cette FAQ, ajoutez vous s'il vous plaît dans la partie \"things to go into the documentation\"."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1110
-msgid "Can I get Wine using cvsup?"
-msgstr "Puis-je récupérer Wine en utilisant cvsup?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1114
-msgid ""
-"The CVS mirrors don't offer cvsup support yet, but the main server does. Use "
-"a <filename>wine.sup</filename> file of:"
-msgstr "Les mirroirs CVS n'offrent pas encore le support cvsup, mais le serveur principal oui. Utilisez le fichier <filename>wine.sup</filename> avec:"
-
-# type: <screen></screen>
-#: ../wine-faq.sgml:7 ../faq.sgml:1118
-#, no-wrap
-msgid ""
-"<screen>*default host=cvs.winehq.org\n"
-"*default base=/cvs\n"
-"*default prefix=/cvs/wine\n"
-"*default release=wine\n"
-"*default delete \n"
-"\n"
-"# If your network link is a T1 or faster, comment out the following line.\n"
-"#*default compress \n"
-"\n"
-"*default use-rel-suffix \n"
-"wine \n"
-"        "
-msgstr ""
-"<screen>*default host=cvs.winehq.org\n"
-"*default base=/cvs\n"
-"*default prefix=/cvs/wine\n"
-"*default release=wine\n"
-"*default delete \n"
-"\n"
-"# If your network link is a T1 or faster, comment out the following line.\n"
-"#*default compress \n"
-"\n"
-"*default use-rel-suffix \n"
-"wine \n"
-"        "
-
-# type: <title></title>
-#: ../wine-faq.sgml:7 ../faq.sgml:1135
-#, no-wrap
-msgid "Installing and Configuring Wine"
-msgstr "Installation et configuration de Wine"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1138
-msgid "How do I compile the Wine distribution source code?"
-msgstr "Comment dois-je compiler le code source de Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1142
-msgid ""
-"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)."
-msgstr "La marche à suivre se trouve dans le fichier README (<ulink url=\"http://source.winehq.org/source/README\">http://"
-"source.winehq.org/source/README</ulink>) pour toutes les instructions. Par ailleurs, vous pouvez positionner la variable d'environnement <parameter>TMPDIR</parameter> a <command>TMPDIR=~/tmp</command> ou <command>TMPDIR=/tmp</command> (si vous êtes root)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1152
-msgid "How do I install Windows in Wine under Linux?"
-msgstr "Comment installer Windows dans Wine sous Linux?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1156
-msgid ""
-"Simple answer: you CAN'T. Windows demands direct access to the hardware and "
-"cannot get it with Wine and UNIX in the way"
-msgstr "Réponse simple: C'EST IMPOSSIBLE. Windows a besoin d'un accès direct au matériel, ce qui n'est pas possible si Wine et UNIX se trouvent en travers de la route."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1160
-msgid ""
-"Wine is supposed to be primarily used WITHOUT Windows. If you want to use a "
-"Windows installation, then use an existing installation alongside the UNIX "
-"installation (see the dual-boot HOWTO for your OS for more details). Or "
-"alternatively use the cabextract utility to extract Windows install archives "
-"to a directory that you want to use as Wine's Windows tree."
-msgstr "Wine est supposé être utilisé à la base SANS Windows. Si vous voulez utiliser une installation Windows, utilisez alors une installation existante en parallèle de l'installation UNIX (voyez le comment faire le double démarrage [dual-boot HOWTO] pour votre SE pour plus de détails). Or alternatively use the cabextract utility to extract Windows install archives to a directory that you want to use as Wine's Windows tree."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1172
-msgid "How do I configure Wine to run on my system?"
-msgstr "Comment dois-je configurer Wine pour qu'il tourne sur mon système?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1185
-msgid ""
-"Wine requires that you have a config file as <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://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://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."
-msgstr "Wine vous oblige à avoir un fichier de configuration comme ~/.wine/config. Le format de ce fichier est expliqué dans la page d'aide [man page] wine.conf. Le fichier <filename>~/.wine/config</"
-"filename>. Le format de ce fichier est expliqué dans la page d'aide [man page] wine.conf. Le fichier <filename>documentation/samples/config</"
-"filename> (<ulink url=\"http://source.winehq.org/source/documentation/"
-"samples/config\"> http://source.winehq.org/source/documentation/samples/"
-"config</ulink>) contient un exemple de fichier de configuration. Des conseils plus explicites se trouvent dans le fichier <filename>README</filename> (<ulink url=\"http://source."
-"winehq.org/source/README\"> http://source.winehq.org/source/README</ulink>) qui se trouvera dans le dossier de base de Wine une fois que vous aurez décompréssé le fichier de distribution avec l'une des deux commandes suivantes gunzip ou untar."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1194
-msgid "How do I upgrade Wine without losing my working configuration?"
-msgstr "Comment puis-je mettre à jour Wine sans perdre la configuration en place?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1198
-msgid ""
-"Upgrading the wine installation does not affect the existing wine "
-"configuration. So after upgrading wine you still have the old (working ) "
-"wine configuration."
-msgstr "La mise à jour de Wine n'affecte pas pas la configuration de Wine existante. Par conséquent après l'amélioration de Wine vous avez encore votre ancienne configuration (de travail)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1207
-msgid "If I want to use a Windows install, which versions are OK?"
-msgstr "Si je veux utiliser une installation de Windows, quelles versions marchent bien?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1211
-msgid ""
-"Either use a classic no-windows install (Wine is getting better all the "
-"time) or use a Win9x install (Win95, 98, 98SE, ME). DON'T configure Wine to "
-"use an NT-based Windows install (NT, Win2K, WinXP, Win2K3)."
-msgstr "Utilisez soit une installation classique non-Windows (Wine s'améliore de jour en jour) soit une installation Win9x (Win95, 98, 98SE, ME). NE configurez PAS Wine pour utiliser une installation Windows basée sur la technologie NT (NT, Win2K, WinXP, Win2K3). En général, la plupart des installations Windows contiennent une quantité monstrueuse de saloperies qui peut perturber Wine et le rendre moins fiable."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1216
-msgid ""
-"In general, most Windows installations contain vast quantities of garbage "
-"that can confuse Wine and make it less reliable. If you can, it's best to "
-"install the programs you want into Wine's fake windows drive."
-msgstr "En général, la plupart des installations Windows contiennent une grande quantité de garbage that can confuse Wine and make it less reliable. Si vous le pouvez, il est préférable d'installer les programmes que vous voulez dans le lecteur Windows factice."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1225
-msgid "If I use a Windows install with Wine, which one works best?"
-msgstr "Si j'utilise une installation Windows avec Wine, laquelle marche le mieux?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1229
-msgid "As of 02/2002:"
-msgstr "Au 02/2002:"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1232
-msgid ""
-"I'd say Win98SE is the best version to use with Wine, as it's fairly "
-"widespread amongst developers and relatively old. Using Win2K files is "
-"<emphasis>definitely</emphasis> worse than a plain no-windows Wine install, "
-"and Win ME is said to be problematic, too (as probably no developer uses "
-"it). In short: all Win9x &lt;= W98SE are good."
-msgstr "Je dirais que Win98SE est la meilleure version à utiliser avec Wine, puisqu'elle est pas mal répandue chez les développeurs et qu'elle est relativement mature. L'utilisation de fichiers Win2K est assurément pire qu'une installation de Wine sans fenêtre, et Win ME est connu pour être problématique, également (vu qu'aucun développeur ne l'utilise). Pour faire bref: tout Win9x <= W98SE est bon."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1244
-msgid ""
-"Installing applications generated by Visual Basic won't run. What should I "
-"do?"
-msgstr "Impossible de faire tourner/d'éxécuter l'installation d'applcations générées par Visual Basic. Que faire?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1250
-msgid ""
-"Make sure you have all the VB run time libraries installed. You can get the "
-"latest version from the Microsoft web site."
-msgstr "Assurez vous que vous avez bien toutes les bibliothéques d'exécution VB d'installées. Vous pouvez obtenir la dernière version depuis le site de Microsoft."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1258
-msgid "When I click on *.exe file in my file Manager, nothing happens."
-msgstr "Quand je clique sur un fichier *.exe dans mon gestionnaire de fichier, rien ne se passe."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1262
-msgid ""
-"The normal Wine releases don't have .exe extensions registered for Wine in "
-"KDE/Gnome yet. You have to open a terminal window instead (often an icon "
-"showing a \"black screen\") and type something like:"
-msgstr "Les versions normales de Wine n'ont pas encore d'extensions .exe enregistrées pour Wine dans KDE/Gnome. Vous devez à la place ouvrir une fenêtre de terminal (souvent une icône représentant un \"écran noir\") et taper quelque chose ressemblant à ça:"
-
-# type: <screen></screen>
-#: ../wine-faq.sgml:7 ../faq.sgml:1267
-#, no-wrap
-msgid ""
-"<screen>cd /my/windows/program/directory\n"
-"wine myprogram.exe\n"
-"        "
-msgstr ""
-"<screen>cd /my/windows/program/directory\n"
-"wine myprogram.exe\n"
-"        "
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1275
-msgid "bash says \"wine: Command not found\" What can I do?"
-msgstr "bash me répond \"wine: Command not found\" Que dois-je faire?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1279
-msgid "Try to logout and login again into bash. That might fix it."
-msgstr "Essayez de vous délogguer puis de vous relogguer sous bash. Cela peut résoudre le problème."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1282
-msgid ""
-"If it doesn't, then make sure the wine binary is in your <parameter>PATH</"
-"parameter>."
-msgstr "Si ce n'est pas le cas, alors assurez-vous que le binaire wine est dans votre <parameter>PATH</parameter>."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1286
-msgid "Run as root:"
-msgstr "Lancez en tant que root:"
-
-# type: <screen></screen>
-#: ../wine-faq.sgml:7 ../faq.sgml:1289
-#, no-wrap
-msgid ""
-"<screen>find / -name \"wine\" -type f -perm +111\n"
-"        "
-msgstr ""
-"<screen>find / -name \"wine\" -type f -perm +111\n"
-"        "
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1292
-msgid ""
-"to find the path where the wine binary is in. Then check whether "
-"<parameter>PATH</parameter> includes it:"
-msgstr "pour trouver le chemin où le binaire Wine se trouve. Vérifiez ensuite que <parameter>PATH</parameter> l'inclut:"
-
-# type: <screen></screen>
-#: ../wine-faq.sgml:7 ../faq.sgml:1296
-#, no-wrap
-msgid ""
-"<screen>echo $PATH \n"
-"        "
-msgstr ""
-"<screen>echo $PATH \n"
-"        "
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1299
-msgid "If not, add that e.g. to <filename>/etc/profile</filename> by doing:"
-msgstr "Sinon, ajoutez le par exemple dans <filename>/etc/profile</filename> en faisant:"
-
-# type: <screen></screen>
-#: ../wine-faq.sgml:7 ../faq.sgml:1302
-#, no-wrap
-msgid ""
-"<screen>export PATH=$PATH:/path/to/wine/binary \n"
-"        "
-msgstr ""
-"<screen>export PATH=$PATH:/path/to/wine/binary \n"
-"        "
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1305
-msgid "That should help."
-msgstr "Cela devrait vous dépanner."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1308
-msgid ""
-"If you used a package manager (<command>rpm</command> or <command>apt</"
-"command>) - Verify your packages. The package <filename>winesetuptk.rpm</"
-"filename> is only a front-end for making a meaningful config file, it DOES "
-"NOT install the wine package..."
-msgstr "Si vous avez utilisé un gestionnaire de paquets (<command>rpm</command> ou <command>apt</"
-"command>) - Vérifiez vos paquets. Le paquet winesetuptk.rpm est seulement une interface [front-end] pour créer un fichier de configuration qui tienne la route, il N'INSTALLE PAS le paquetage Wine..."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1317
-msgid ""
-"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."
-msgstr "Pour les paquets complets, utilisez <ulink url=\"http://rpmseek.com/rpm-pl/wine.html?"
-"hl=com&amp;cx=0::\"> http://rpmseek.com/</ulink> ou la section <ulink url=\"http://"
-"www.winehq.org/site/download\"> Download</ulink>."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1324
-msgid "How do I remove Wine from my Computer?"
-msgstr "Comment désinstaller Wine de mon ordinateur?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1328
-msgid ""
-"It depends on how you installed. If you used an RPM, the right command is "
-"this: <command>rpm -e wine (as root)</command>"
-msgstr "Cela dépend de la façon dont vous l'avez installé. Si vous avez utilisé un RPM, la commande à faire est celle-ci: <command>rpm -e wine (en tant que root)</command>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1332
-msgid ""
-"If you installed from source (the .tar.gz file), the right way to do it is "
-"to change to the root of the source tree (the directory with the configure "
-"script, readme etc) then run as root: <command>make uninstall</command>"
-msgstr "Si vous l'avez installé depuis la source (le fichier .tar.gz), la bonne façon de faire est d'aller à la racine de l'arbre source (le répertoire avec le script de configuration, le fichier readme etc) et de lancer ensuite (en root): <command>make uninstall</command>"
-
-# type: <title></title>
-#: ../wine-faq.sgml:7 ../faq.sgml:1342
-#, no-wrap
-msgid "About running Wine"
-msgstr "A propos de l'exécution de Wine"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1345
-msgid "How do I run an MS Windows program under Wine?"
-msgstr "Comment lancer un programme MS Windows sous Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1349
-msgid ""
-"When invoking Wine, you must specify the entire path to the executable, or "
-"by file name only. For example to run Windows' solitaire, type any of the "
-"following:"
-msgstr "En invoquant Wine, vous devez spécifier le chemin entier de l'exécutable, ou le nom de fichier seulement. Pour exemple pour lancer le solitaire de Windows tapez l'une des commandes suivantes:"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1356
-msgid ""
-"<command>wine sol</command> or <command>wine sol.exe</command> (using the "
-"search path to locate the file)."
-msgstr "<command>wine sol</command> ou <command>wine sol.exe</command> (en utilisant le chemin de recherche pour localiser le fichier)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1362
-msgid ""
-"<command>wine c:\\\\windows\\\\sol.exe</command> (using a DOS file name)."
-msgstr "<command>wine c:\\\\windows\\\\sol.exe</command> (en utilisant le nom de fichier DOS)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1368
-msgid "<command>wine /usr/windows/sol.exe</command> (using a UNIX file name)."
-msgstr "<command>wine /usr/windows/sol.exe</command> (en utilisant le nom de fichier UNIX)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1374
-msgid ""
-"<command>wine \"c:\\windows\\sol.exe\"</command> (using quoted DOS file "
-"name)."
-msgstr "<command>wine \"c:\\windows\\sol.exe\"</command> (en utilisant le nom de fichier DOS entre guillemets)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1380
-msgid ""
-"The path of the file will also be added to the path when a full name is "
-"supplied on the command line."
-msgstr "Le chemin du fichier sera aussi ajouté au chemin [path] quand un nom complet est utilisé en ligne de commande."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1390
-msgid ""
-"I have installed and configured Wine, but Wine cannot find MS Windows on my "
-"drive. Where did I go wrong?"
-msgstr "J'ai installé et configuré Wine, mais Wine ne trouve pas MS Windows sur mon disque. Où est l'erreur?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1396
-msgid ""
-"If you have a DOS partition, first make sure that you have mounted it, "
-"either by putting the entry into <filename>/etc/fstab</filename>, or by "
-"manually mounting it."
-msgstr "Si vous avez une partition DOS, assurez vous d'abord que vous l'avez montée, soit en rajoutant l'entrée dans le fichier <filename>/etc/fstab</filename>, ou en la montant à la main."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1401
-msgid ""
-"Remember too that unless your version of UNIX can see through it, or you are "
-"running a utility that can see through it, your DOS partition must not be "
-"located on a Drivespaced, Doublespaced or Stackered partition, as neither "
-"Linux, FreeBSD, NetBSD or Wine can natively 'see' files located in these "
-"compressed DOS partitions."
-msgstr "Rappelez vous également qu'à moins que votre version d'UNIX puisse voir à travers, ou que vous utilisiez un utilitaire qui puisse voir à travers, votre partition DOS ne doit pas se situer sur une partition Drivespaced, Doublespaced ou Stackered, car par nature ni Linux, ni FreeBSD, ni NetBSD ou Wine ne peuvent 'voir' les fichiers situés sur ces partitions DOS compressées."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1408
-msgid ""
-"Check your path statements in the <filename>wine.conf</filename> file. No "
-"capital letters may be used in paths, as they are automatically converted to "
-"lowercase."
-msgstr "Vérifiez la syntaxe de votre chemin dans le fichier <filename>wine.conf</filename>. Les lettres capitales ne doivent pas être utilisées dans les chemins, car elles sont automatiquement converties en minuscules."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1418
-msgid ""
-"I was able to get various MS Windows programs to run, but parts of them do "
-"not work. What is wrong?"
-msgstr "J'ai réussi à éxécuter différents programmes MS Windows, mais tout ne marche pas dans ces programmes. Qu'est ce qui cloche?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1424
-msgid ""
-"Wine is not complete at this time, so some of each programs' features may "
-"not work. They will in time as more of the MS Windows API calls are included "
-"in Wine."
-msgstr "Wine n'est pour le moment pas complet, par conséquent dans chaque programme certaines caractéristiques peuvent ne pas fonctionner. Cela finira par se régler car de plus en plus d'appels API MS Windows inclus dans Wine."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1434
-msgid ""
-"I have run various MS Windows programs, but since the program menus do not "
-"work, how can I exit these programs?"
-msgstr "J'ai lancé différents programmes MS Windows, mais comme les menus de ces programmes ne fonctionnent pas, comment quitter ces programmes?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1440
-msgid ""
-"Kill the xterm shell window that you called up to run your MS Windows "
-"program, and the X window that appeared with the program will be killed too."
-msgstr "Arrêtez la fenêtre xterm shell que vous avez utilisé pour lancer le programme MS Windows, et la fenêtre X qui est apparue avec le programme s'arrêtera également."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1450
-msgid "My program doesn't work, what can I do?"
-msgstr "Mon programme ne marche pas, que faire?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1455
-msgid ""
-"If you are a programmer and know C, then start debugging Wine and help us "
-"make it better! If you can't, then you will have to either convince a Wine "
-"developer to try and make your program work (there must be a downloadable "
-"version or demo for that)."
-msgstr "Si vous êtes un développeur et que vous avez des connaissances en C, alors vous pouvez commencer à débogguer Wine et nous aider à l'améliorer! Si ce n'est pas le cas, vous devrez alors soit convaincre un développeur Wine d'essayer de faire marcher votre programme (il doit y avoir une version ou une démonstration téléchargeable pour cela)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1462
-msgid ""
-"You can submit your application to the <ulink url=\"http://appdb.winehq.org/"
-"\"> Wine Application DB </ulink> and gather tips on ways to get your app to "
-"work its best."
-msgstr "Vous pouvez soumettre votre application à la base de données <ulink url=\"http://appdb.winehq.org/"
-"\">Wine Application DB </ulink> et récupérer des tuyaux sur la façon d'améliorer le fonctionnement de votre application."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1464
-msgid ""
-"You can also submit your application to the CodeWeavers CrossOver <ulink url="
-"\"http://www.codeweavers.com/site/compatibility/\"> Compatibility </ulink> "
-"Center. Where you can pledge/vote toward future support of your favorite "
-"application."
-msgstr "Vous pouvez également soumettre votre application au CodeWeavers CrossOver <ulink url="
-"\"http://www.codeweavers.com/site/compatibility/\"> Compatibility </ulink> Center. Où vous pouvez votez pour soutenir votre application favorite."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1470
-msgid ""
-"Alternatively, you may be able to get the app working by taking native DLLs "
-"from a Microsoft Windows install, and using them (set the dlls to native in "
-"the config file). Not all DLLs can be replaced that way - in particular "
-"DirectX cannot be, nor can some core system DLLs like gdi32, user, ntdll, "
-"kernel32 etc."
-msgstr "Egalement, il se peut que vous puissiez faire marcher l'application en prenant les DLL natives depuis une installation Microsoft Windows, et en les utilisant (régler les DLL à natif dans le fichier de configuration). Toutes les DLL ne peuvent pas être remplacées de la sorte - en particulier DirectX pas plus que certaines DLL du système central [core system] comme gdi32, user, ntdll, kernel32 etc."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1481
-msgid "Can I use Wine with SUSE, RedHat or other Linux Distro's?"
-msgstr "Puis-je utiliser Wine avec SUSE, RedHat ou d'autres distrib Linux?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1485
-msgid ""
-"You can use Wine on any sufficiently recent Linux installation. The amount "
-"of work getting Wine up and running depends on whether you install a binary "
-"packages or do a source install."
-msgstr "Vous pouvez utiliser Wine sur n'importe quelle installation Linux suffisamment récente. La quantité de travail pour mettre Wine en service et l'utiliser varie selon que vous l'installez avec les paquets binaires ou que vous faites une installation depuis la source."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1494
-msgid "Does Wine work with AMD Processors?"
-msgstr "Est-ce que Wine marche avec des processeurs AMD?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1498
-msgid ""
-"Yes, it does. Wine should work on any processor compatible with the Pentium "
-"or greater."
-msgstr "Oui. Wine devrait marcher avec n'importe quel processeur compatible Pentium ou plus."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1506
-msgid "Can I launch a Unix program from a Windows program?"
-msgstr "Puis-je lancer un programme Unix depuis un programme Windows?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1510
-msgid ""
-"Sure, Wine supports that. Just enter the unix program name wherever a "
-"program has something that it's supposed to execute, and it should just work."
-msgstr "Bien sûr, Wine supporte cela. Entrez juste le nom du programme Unix là où le programme propose l'exécution de quelque chose, et cela devrait marcher."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1519
-msgid ""
-"I get <quote>Error installing iKernel.exe: (0x1400)</quote> when running an "
-"InstallShield 6 installer."
-msgstr "J'obtiens \"Error installing iKernel.exe: (0x1400)\" quand je lance un installeur InstallShield 6."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1525
-msgid ""
-"If you get the error \"Error installing iKernel.exe: (0x1400)\" at any "
-"point, it's probably because there are leftover processes from a previous "
-"try. You can verify this with the command"
-msgstr "Si vous obtenez l'erreur \"Error installing iKernel.exe: (0x1400)\" à chaque fois, c'est probablement parcequ'ils restent certaines processus d'une précédente tentative. Vous pouvez le vérifier avec la commande"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1529
-msgid "<prompt>$ </prompt><command>ps augxw | grep wine</command>"
-msgstr "<prompt>$ </prompt><command>ps augxw | grep wine</command>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1531
-msgid ""
-"If that command shows old copies of wine running your setup, you need to "
-"kill them before you can run the setup program. If there are no other Wine "
-"programs running, you can kill them all with the command"
-msgstr "Si cette commande affiche d'anciennes copies de Wine lançant votre installation, vous devez les arrêter [kill] avant de pouvoir lancer le programme d'installation. S'il n'y a pas d'autres programmes Wine en cours d'éxécution, vous pouvez tous les arrêter [kill] avec la commande"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1536
-msgid "<prompt>$ </prompt><command>killall wine</command>"
-msgstr "<prompt>$ </prompt><command>killall wine</command>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1538
-msgid ""
-"If you're also running Wine programs you care about, you'll have to kill off "
-"the old Setup instances one by one using kill and the individual PIDs (or "
-"perhaps Wine's spiffy Task Manager, which doesn't exist yet)."
-msgstr "Si vous être en train de faire tourner des programmes Wine auquel vous tenez, vous devrez arrêter les anciennes instances d'installation une à une en utilisant la commande kill et les PID de cahque processus PID (ou peut-être le très chic Gestionnaire de tâches de Wine qui n'existe pas encore)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1544
-msgid ""
-"You should repeat the <command>ps</command> to make sure all of the old Wine "
-"processes are gone."
-msgstr "Répétez la commande ps pour vous assurer que tous les anciens processus Wine sont clos."
-
-# type: <title></title>
-#: ../wine-faq.sgml:7 ../faq.sgml:1552
-#, no-wrap
-msgid "Getting help"
-msgstr "Récupérer de l'aide"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1555
-msgid "Is there any documentation for Wine?"
-msgstr "Y-at-il de la documentation sur Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1560
-msgid ""
-"Yes, see <ulink url=\"http://www.winehq.org/site/documentation\"> http://www."
-"winehq.org/site/documentation.</ulink>"
-msgstr "Oui, voir <ulink url=\"http://www.winehq.org/site/documentation\"> http://www."
-"winehq.org/site/documentation.</ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1568
-msgid ""
-"I couldn't find the answer to my question in the documentation, but I've "
-"written a document explaining how to solve it. What should I do?"
-msgstr "Je n'ai pas trouvé la réponse à ma question dans la documentation, mais j'ai écrit une documenation expliquant comment résoudre ce problème. Que dois-je faire?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1577
-msgid ""
-"Updates and additions to the Wine documentation directory should be sent to "
-"the wine-patches mailing list at <ulink url=\"http://www.winehq.org/site/"
-"forums\"> http://www.winehq.org/site/forums</ulink>. Website and FAQ "
-"additions should be added to the appropriate Wine Knowledge base directory."
-msgstr "Des mises à jour et des ajouts concernant la documentation de Wine doivent être envoyés à la liste de diffusion \"wine-patches\" à <ulink url=\"http://www.winehq.org/site/"
-"forums\"> http://www.winehq.org/site/forums</ulink>. Les ajouts sur la FAQ ou le site Web doivent être déposés dans le répertoire de base \"Wine knowledge\" approprié."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1585
-msgid "Is there a Usenet newsgroup for Wine?"
-msgstr "Y-a-t-il une newsgroup Usenet pour Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1591
-msgid ""
-"Yes, and it's called <ulink url=\"news:comp.emulators.ms-windows.wine\"> "
-"comp.emulators.ms-windows.wine</ulink>. The newsgroup serves as a place for "
-"users and developers to discuss Wine, and for minor announcements for the "
-"general public. Major announcements will be cross posted to other "
-"appropriate newsgroups, such as the following:"
-msgstr "Oui, elle s'appelle <ulink url=\"news:comp.emulators.ms-windows.wine\"> "
-"comp.emulators.ms-windows.wine</ulink>. La newsgroup est un espace ouvert aux utilisateurs et aux développeurs qui veulent discuter de Wine, et pour certaines informations non importante grand public. Les annonces importantes seront postées en parallèle sur d'autres newsgroup appropriées, telles que les suivantes:"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1600
-msgid ""
-"<ulink url=\"news:comp.os.linux.announce\"> comp.os.linux.announce</ulink>"
-msgstr ""
-"<ulink url=\"news:comp.os.linux.announce\"> comp.os.linux.announce</ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1606
-msgid ""
-"<ulink url=\"news:ccomp.windows.x.announce\"> comp.windows.x.announce</ulink>"
-msgstr ""
-"<ulink url=\"news:ccomp.windows.x.announce\"> comp.windows.x.announce</ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1612
-msgid ""
-"<ulink url=\"news:ccomp.emulators.announce\"> comp.emulators.announce</ulink>"
-msgstr ""
-"<ulink url=\"news:ccomp.emulators.announce\"> comp.emulators.announce</ulink>"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1617
-msgid ""
-"If your Usenet site does not carry these newsgroups, please urge your ISP's "
-"sysadmin to add and/or uplink them."
-msgstr "Si votre site Usenet ne dispose pas de ces newsgroups, demandez expressément à votre admin FAI de les ajouter et/ou de mettre les liens pour s'y connecter."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1625
-msgid "Is there a World Wide Web site for Wine?"
-msgstr "Y-a-t-il un site Web pour Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1629
-msgid ""
-"Wine HQ (<ulink url=\"http://www.winehq.org\">http://www.winehq.org</ulink>) "
-"is the official site."
-msgstr "Wine HQ (<ulink url=\"http://www.winehq.org\">http://www.winehq.org</ulink>) est le site officiel."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1636
-msgid "Is there an IRC channel for Wine?"
-msgstr "Y-a-t-il un canal IRC pour Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1640
-msgid ""
-"Sure. It's channel <filename>#WineHQ</filename> on <filename>irc.freenode."
-"net</filename> see (<ulink url=\"http://freenode.net\">http://freenode.net</"
-"ulink>). Usually several Wine developers hang out there just to help YOU ;-)"
-msgstr "Bien sûr. C'est le canal <filename>#WineHQ</filename> sur <filename>irc.freenode."
-"net</filename>t voir (<ulink url=\"http://freenode.net\">http://freenode.net</"
-"ulink>). Habituellement plusieurs développeurs Wine sont présents juste pour VOUS aider, vous! ;-)"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1651
-msgid ""
-"I think I've found a bug. How do I report this bug to the Wine programming "
-"team?"
-msgstr "Je crois que j'ai trouvé un bogue. Comment puis-je prévenir l'équipe de programmeurs de Wine de celui-ci?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1657
-msgid ""
-"Bug reports should be submitted to our online Bugzilla system (<ulink url="
-"\"http://bugs.winehq.org/\">http://bugs.winehq.org/</ulink>). You should "
-"include at least the following:"
-msgstr "Les rapports de bogue doivent être soumis à notre système en ligne Bugzilla (<ulink url="
-"\"http://bugs.winehq.org/\">http://bugs.winehq.org/</ulink>). Vous devrez au minimum préciser les choses suivantes:"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1664
-msgid "The Wine version tested"
-msgstr "La version Wine testée"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1669
-msgid ""
-"The Windows application name, including the version, and, if applicable, a "
-"URL the application can be downloaded from"
-msgstr "Le nom de l'application Windows, y compris la version, et, si possible, une URL où l'application peut être téléchargée"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1675
-msgid "A brief description of the bug"
-msgstr "Une brève description du bogue"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1680
-msgid "The relevant part(s) of the output of the Wine debugger"
-msgstr "Les parties importantes de la sortie du déboggueur de Wine"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1685
-msgid "A screenshot of the visual problem, if applicable"
-msgstr "Une capture d'écran du problème, si possible"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1692
-msgid ""
-"For more information about reporting bugs please see the <ulink url=\"http://"
-"www.winehq.org/Docs/wine-user/bug-reporting.shtml\"> How to report a bug</"
-"ulink> section of the Wine Users Guide."
-msgstr "Pour plus d'informations sur la manière de rapporter les bogues voir la section <ulink url=\"http://"
-"www.winehq.org/Docs/wine-user/bug-reporting.shtml\"> How to report a bug</"
-"ulink> du guide de l'utilisateur Wine [the Wine Users Guide]."
-
-# type: <title></title>
-#: ../wine-faq.sgml:7 ../faq.sgml:1699
-#, no-wrap
-msgid "Helping Wine or becoming a Wine developer"
-msgstr "Aider Wine ou devenir un développeur Wine"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1702
-msgid "How do I become a Wine developer? What do I need to know?"
-msgstr "Comment devenir développeur Wine? Qu'ai-je besoin de savoir?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1711
-msgid ""
-"If you can program C, that's a good start. Download the sources via (<ulink "
-"url=\"http://www.winehq.org/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.org/site/forums\">http://www.winehq.org/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)."
-msgstr "Si vous pouvez programmer en C, c'est déjà ça. Téléchargez les sources via (<ulink "
-"url=\"http://www.winehq.org/site/cvs\">CVS,</ulink>) inscrivez-vous aux listes de diffusion, jetez un oeil au code source, et intéressez-vous au groupe de nouvelles comp.emulators.ms-windows.wine et aux listes de diffusion (<ulink url="
-"\"http://www.winehq.org/site/forums\">http://www.winehq.org/site/forums</"
-"ulink>). Regardez si vous voyez quelque chose que vous pensez pouvoir réparer ou dont vous pouvez vous occuper. Vous n'aurez pas de problèmes pour trouver des domaines où il y a du travail à faire dans Wine (filtrer [grep] les FIXME dans le source)."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1721
-msgid "How can I help contribute to the Wine project, and in what way(s)?"
-msgstr "Comment puis-je contribuer au projet Wine, et de quelle(s) manière(s)?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1725
-msgid ""
-"You can contribute programming or documentation skills, or monetary or "
-"equipment donations, to aid the Wine developers in reaching their goals."
-msgstr "Vous pouvez apporter vos (connaissances en programmation et en documentation, ou faire des dons en argent ou matériel, pour aider les développeurs de Wine à atteindre leurs buts."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1732
-msgid ""
-"For a list of ideas of how you can help, please consult the <ulink url="
-"\"http://www.winehq.org/site/contributing\"> Wine contrib page</ulink>."
-msgstr "Pour trouver des idées sur la manière dont vous pouvez aider, consultez la <ulink url="
-"\"http://www.winehq.org/site/contributing\">page de contribution de Wine</ulink>."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1739
-msgid "I want to help beta test Wine. How can I do this?"
-msgstr "Je veux aporter mon aide sur les tests beta de Wine. Comment faire?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1743
-msgid ""
-"Wine still consists of some Alpha code at this time. However, anyone is "
-"welcome to download the latest version, and try it out at any time."
-msgstr "Wine est encore fait de code Alpha en ce moment. Cependant, n'importe qui est le bienvenu pour télécharger la dernière version, et l'essayer à tout moment."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1753
-msgid ""
-"I have written some code that I would like to submit to the Wine project. "
-"How do I go about doing this?"
-msgstr "J'ai écrit du code que je voudrais soumettre au projet Wine. Comment faire?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1765
-msgid ""
-"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.org/mailman/listinfo/wine-patches\">http://www.winehq."
-"org/mailman/listinfo/wine-patches</ulink>). 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.org/site/sending_patches\">how to "
-"submit patches</ulink>. This will also give you more details about the whole "
-"process and in particular to what will happen to your patch once submitted."
-msgstr "Soumettre un correctif pour un ajout dans Wine est très simple. En gros tout ce que vous avez à faire est d'envoyer le correctif à la liste diffusion wine-patches (<ulink url="
-"\"http://www.winehq.org/mailman/listinfo/wine-patches\">http://www.winehq."
-"org/mailman/listinfo/wine-patches</ulink>). Il y a cependant des recommendations sur le format du correctif et par conséquent il est conseillé de lire la page où nous décrivons comment soumettre les correctifs (<ulink url=\"http://www.winehq.org/site/sending_patches\">how to "
-"submit patches</ulink>). Cela vous donnera également plus de détails sur l'ensemble du processus et en particulier sur ce que va devenir votre correctif une fois soumis."
-
-# type: <title></title>
-#: ../wine-faq.sgml:7 ../faq.sgml:1775
-#, no-wrap
-msgid "Developing programs using Wine/WineLib"
-msgstr "Développement de programmes utilisant Wine/WineLib"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1778
-msgid "Can I use Wine to port my Win32 sources to Unix?"
-msgstr "Puis-je utiliser Wine pour porter mes sources Win32 vers Unix?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1782
-msgid ""
-"That is the idea of Winelib. Right now you may still have some difficulties, "
-"but this is changing all the time. Read the <ulink url=\"http://www.winehq."
-"org/Docs/winelib-user/\">Winelib User's Guide</ulink> for info."
-msgstr "C'est justement ça, Winelib. Pour le moment c'est peut-être encore un peu difficile, mais cela évolue tout le temps. Lisez le <ulink url=\"http://www.winehq."
-"org/Docs/winelib-user/\">Guide d'utilisateur de Winelib</ulink> [Winelib User's Guide] pour information."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1791
-msgid "Will MFC work with Wine? What do I need to do?"
-msgstr "Est ce que MFC marchera avec Wine? Que dois-je faire?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1795
-msgid ""
-"Wine is not implementing an MFC replacement nor does it intend to. However "
-"it is possible (with a lot of work) to compile the MFC from source and thus "
-"produce an <filename>mfc42.dll.so</filename> library."
-msgstr "Wine n'implémente pas de remplacements MFC et ne prévoit pas d'en faire. Cependant il est possible (avec beaucoup de travail) de compiler MFC depuis les sources et de créer ainsi une bibliothèque <filename>mfc42.dll.so</filename>."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1800
-msgid ""
-"Please refer to the <ulink url=\"http://www.winehq.org/Docs/winelib-user/"
-"\">Winelib User's Guide</ulink> for how to do this."
-msgstr "Reportez-vous au <ulink url=\"http://www.winehq.org/Docs/winelib-user/"
-"\">Winelib User's Guide</ulink> pour savoir comment faire."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1809
-msgid ""
-"Are there any commercial applications which have been ported using Wine?"
-msgstr "Existe-t-il des applications commerciales qui ont été portées en utilisant Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1815
-msgid "Here are few examples of applications ported using Wine or Winelib:"
-msgstr "Voici quelques exemples d'applications portées en utilisant Wine ou Winelib:"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1820
-msgid "Corel's WordPerfect Office Suite 2000 was ported to Linux using Wine."
-msgstr "Corel's WordPerfect Office Suite 2000 a été porté sous Linux en utilisant Wine."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1826
-msgid ""
-"Kylix, the Linux version of Delphi, was ported to Linux using Winelib. The "
-"IDE actually uses a combination of QT and Winelib which would not have been "
-"possible to achieve using only Wine. The generated applications however do "
-"not depend on Wine in any way."
-msgstr "Kylix, la version Linux de Delphi, a été portée sous Linux en utilisant Winelib. L'IDE utilise en fait une combinaison de QT et Winelib alors qu'il n'aurait pas été possible d'y arriver en utilisant uniquement Wine. Cependant, les applications générées ne dépendent absolument pas de Wine."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1835
-msgid ""
-"MusicMatch Jukebox 5 has also been <ulink url=\"http://www.itworld.com/nl/"
-"lnx_desktop/01042001/\">ported</ulink> to Linux using Winelib. However more "
-"recent versions have not, and version 5 is no longer available."
-msgstr "MusicMatch Jukebox 5 a également été porté (http://www.itworld.com/nl/lnx_desktop/01042001/) sous Linux en utilisant Winelib. Cependant des versions plus récentes ne le sont pas, et la version 5 n'est plus disponible."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1843
-msgid ""
-"Ability Office (<ulink url=\"http://www.ability.com/linux/abilitylinux.php"
-"\">http://www.ability.com/linux/abilitylinux.php</ulink>)"
-msgstr ""
-"Ability Office (<ulink url=\"http://www.ability.com/linux/abilitylinux.php"
-"\">http://www.ability.com/linux/abilitylinux.php</ulink>)"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1849
-msgid ""
-"IBM's Websphere (<ulink url=\"http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p"
-"\">http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p</ulink>)"
-msgstr ""
-"IBM's Websphere (<ulink url=\"http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p"
-"\">http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p</ulink>)"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1855
-msgid ""
-"Many other important applications have already been ported. (we are speaking "
-"of several top 500 applications here)"
-msgstr "Beaucoups d'autres applications ont déjà été portées. (on parle de plusieurs applications dans le top 500 ici)"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1863
-msgid "How can I detect Wine?"
-msgstr "Comment puis-je détecter Wine?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1867
-msgid ""
-"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."
-msgstr "Franchement, vous n'avez pas trop intérêt à faire cela. Si il y a un truc bizarre à corriger dans Wine, il est vraiment préférable de le réparer dans Wine."
-
-# type: <title></title>
-#: ../wine-faq.sgml:7 ../faq.sgml:1877
-#, no-wrap
-msgid "Wine HQ issues"
-msgstr "Points concernant Wine HQ"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1881
-msgid "Why are the mailing lists set to reply to author, not to mailing list?"
-msgstr "Pourquoi la liste de diffusion est-elle réglée pour répondre à l'auteur et pas à la liste?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1886
-msgid "There are some very valid reasons for doing so."
-msgstr "Il y a de bonnes raisons pour procéder de la sorte."
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1893
-msgid "How to unsubscribe from the mailing lists?"
-msgstr "Comment se désinscrire de la mailing liste ?"
-
-# type: <para></para>
-#: ../wine-faq.sgml:7 ../faq.sgml:1897
-msgid ""
-"Please see: <ulink url=\"http://www.winehq.org/site/forums\">http://www."
-"winehq.org/site/forums</ulink> And select [(Un-)Subscribe]"
-msgstr "Voir: <ulink url=\"http://www.winehq.org/site/forums\">http://www."
-"winehq.org/site/forums</ulink> And select [(Un-)Subscribe]"
Index: docs/en/Makefile.in
diff -u -p docs/en/Makefile.in:1.5 docs/en/Makefile.in:1.6
--- docs/en/Makefile.in	26 Jun 2007 20:42:55 -0000
+++ /dev/null	26 Jun 2007 20:42:55 -0000
@@ -36,13 +36,10 @@ WINELIB_SRCS = \
 	winelib-porting.sgml \
 	winelib-toolkit.sgml
 
-WINEFAQ_SRCS = \
-
 ALLBOOKS = \
 	winedev-guide \
 	wineusr-guide \
-	winelib-guide \
-	wine-faq
+	winelib-guide
 
 all: doc
 
Index: docs/en/.cvsignore
diff -u -p docs/en/.cvsignore:1.1 docs/en/.cvsignore:1.2
--- docs/en/.cvsignore	26 Jun 2007 20:42:55 -0000
+++ /dev/null	26 Jun 2007 20:42:55 -0000
@@ -1,8 +1,4 @@
 Makefile
-wine-faq.html
-wine-faq.pdf
-wine-faq.ps
-wine-faq.txt
 winedev-guide.html
 winedev-guide.pdf
 winedev-guide.ps
Index: docs/en/wine-faq.sgml
diff -u -p docs/en/wine-faq.sgml:1.19 /dev/null
--- docs/en/wine-faq.sgml	26 Jun 2007 20:42:55 -0000
+++ /dev/null	26 Jun 2007 20:42:55 -0000
@@ -1,1763 +0,0 @@
-<!doctype Article PUBLIC "-//OASIS//DTD DocBook V3.1//EN">
-<article class="faq" id="index" lang="en">
-  <title>Wine FAQ</title>
-
-  <qandaset>
-    <qandadiv id="About-this-FAQ"><title>About this FAQ</title>
-      <qandaentry>
-      <question id="Who-maintains-this-FAQ">
-        <para>Who maintains this FAQ ?</para>
-      </question>
-      <answer>
-        <para>Dave Gardner maintained it from 1995-1998.</para>
-        <para>Douglas Ridgway took it over in 1999.</para>
-        <para>Andreas Mohr converted it to FAQ-O-Matic in 2000.</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-devel at winehq.org">wine-devel at winehq.org</ulink></para>
-      </answer>
-      </qandaentry>
-      <qandaentry>
-      <question id="What-is-the-copyright-on-the-FAQ-And">
-        <para>What is the copyright of this FAQ? And how may I use it?</para>
-      </question>
-      <answer>
-        <para>The original Wine FAQ, which this FAQ was based on, was copyright &copy; 1995-1998 David Gardner.</para>
-        <para>It may be reproduced and modified under the same terms as Wine itself.</para>
-      </answer>
-      </qandaentry>
-      <qandaentry>
-      <question id="How-can-I-update-the-FAQ">
-        <para>How can I update this FAQ?</para>
-      </question>
-      <answer>
-        <para>This FAQ lives in the CVS repository on SourceForge.  In order
- to update this document you'll need to checkout the the docs from
- CVS, edit it, and then send a patch.  In order to get the docs, run
- the following CVS command:</para>
- <screen>
-cvs -z3 -d:pserver:anonymous at wine.cvs.sourceforge.net:/cvsroot/wine co -P docs
- </screen>
- <para>
- When prompted for a password, just press the enter key.  </para>
- <para> 
- A subdirectory named docs will be created.  If you navigate through there you'll
- find the FAQ in <filename>docs/en/wine-faq.sgml</filename>.  
- The file is written in SGML, which is simply a superset of HTML.
- You can use your favorite text editor to make changes to it but
- be sure to make sure each opening tag has a corresponding closing
- tag.  You may find the <command>tidy</command> or 
- <command>xmllint</command> utilities useful for editing the document.
- </para>
-        <para>After editing the file, 
- <ulink url="http://www.winehq.org/site/sending_patches">
-          generate a patch</ulink> against CVS and
- email it to wine-patches at winehq.org.</para>
-      </answer>
-      </qandaentry>
-    </qandadiv>
-    <qandadiv id="General-Questions-about-Wine">
-      <title>General Questions about Wine</title>
-      <qandaentry>
-
-      <question id="What-is-Wine-and-what-is-it-supposed-to">
-        <para>What is Wine and what is it supposed to do?</para>
-      </question>
-      <answer>
-        <para>
-          Wine is a program which allows the operation of DOS and MS
-          Windows programs (Windows 3.x and Win32 executables) on UNIX operating systems such as Linux. 
-          It consists of a program loader, which loads and executes a Windows
-          binary, and a set of libraries that implements Windows API calls
-          using their UNIX or X11 equivalents. The libraries may also be used
-          for porting Win32 code into native UNIX executables, often
-          without many changes in the source. Wine is free software, 
-          and its license (contained in the file LICENSE
-          in each distribution) is the LGPL.
-        </para>
-      </answer>
-      </qandaentry>
-
-     <qandaentry>
-      <question id="Is-Wine-an-emulator">
-        <para>Does Wine emulate a full computer?</para>
-      </question>
-      <answer>
-        <para>
-          No, as the name says, Wine Is Not a (CPU) Emulator. Wine just
-          provides the Windows API. This means that you will need an
-          x86-compatible processor to run an x86 Windows application, for instance from Intel or AMD. The
-          advantage is that, unlike solutions that rely on CPU emulation, Wine
-          runs applications at full speed. Sometimes a program run under
-	  Wine will be slower than when run on a copy of Microsoft Windows, but
-	  this is more due to the fact that Microsoft has heavily optimized parts of their
-	  code, whereas mostly Wine is not well optimized (yet). Occasionally, an app
-	  may run faster under Wine than on Windows. Most apps run at roughly the same speed.
-       </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Are-here-any-alternatives-to-Wine">
-        <para>Are there any alternatives to Wine?</para>
-      </question>
-      <answer>
-        <para>
-          Yes, there are. You can use <ulink url="http://www.vmware.com">VMWare</ulink> to run a Windows installation inside a virtual machine,
-	  or use <ulink url="http://www.win4lin.com">Win4Lin</ulink>
-	  to run a specially adapted Windows version on Linux.
-	  Both solutions cost money for both the software itself
-	  and a Windows license.
-       </para>
-       <para>
-         Note that, like Wine, they can only use the hardware platform that
-         the target programs were originally compiled for (see below).
-       </para>
-
-      </answer>
-      </qandaentry>
-       
-      <qandaentry>
-      <question id="Difference-between-Wine-and-emulators">
-        <para>What is the difference between Wine and x86 hardware emulators?</para>
-      </question>
-      <answer>
-        <para>
-          There are two free x86 hardware emulators:
-          <ulink url="http://bochs.sourceforge.net">Bochs</ulink>, and
-          <ulink url="http://savannah.nongnu.org/projects/plex86">Plex86</ulink>.
-       </para>
-
-       <para>
-          Plex86 is the open-source free-software alternative for VMWare,
-	  VirtualPC, and other IA-32 on IA-32 "Virtual PC products." It
-          can only run on the IA-32 architecture.
-       </para>
-
-       <para>
-          Bochs is a highly portable open source IA-32 (x86) PC emulator 
-          written in C++, that runs on most popular platforms. It includes emulation
-          of the Intel x86 CPU, common I/O devices, and a custom BIOS. Currently, 
-          Bochs can be compiled to emulate a 386, 486 or Pentium CPU. Bochs is capable
-          of running most Operating Systems inside the emulation including Linux, 
-          <trademark class="registered">Windows</> 95, DOS, and recently <trademark class="registered">Windows</> NT/2000.
-       </para>
-
-       <para>
-          Both are licensed under the GPL. Bochs is older than Plex86, seems to be
-          easier to install, but Plex86 will run faster because Plex86 uses a just in
-          time binary compiler.
-       </para>
-       <para>
-          The drawback of all emulators is that you need a version
-          of Windows in order to run Windows, and that they all have an
-          impact on performance. Wine also gives much better desktop integration - for
-	  instance, programs use your standard window manager, system tray icons will
-	  appear in your tray area (if you have one), and you can run programs direct from the
-	  command line as well as menus. The clipboard also works seamlessly at this time.
-       </para>
-
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Integrate-an-x86-emulator">
-        <para>When will Wine integrate an x86 CPU emulator so we can
-          run Windows applications on non-x86 machines?</para>
-      </question>
-      <answer>
-        <para>
-          The short answer is 'probably never'. Remember, Wine Is Not a
-          (CPU) Emulator. The long answer is that we probably don't want or
-          need to integrate one in the traditional sense.
-        </para>
-        <para>
-          Integrating a CPU emulator in Wine would be extremely hard,
-          due to the large number of Windows APIs and the complex
-          data types they exchange. It is not uncommon for a Windows API to
-          take three or more pointers to structures composed of many fields,
-          including pointers to other complex structures. For each of these
-          we would need a conversion routine to deal with the byte order and
-          alignment issues. Furthermore, Windows also contains many callback
-          mechanisms that constitute as many extra places where we would have
-          to handle these conversion issues. Wine already has to deal with
-          16 vs. 32 bit APIs and Ansi vs. Unicode APIs which both
-          introduce significant complexity. Adding support for a CPU emulator
-          inside Wine would introduce at least double that complexity and
-          only serve to slow down the development of Wine.
-        </para>
-        <para>
-          Fortunately another solution exists to run Windows applications
-          on non-x86 platforms: run both Wine and the application inside the
-          CPU emulator. As long as the emulator provides a standard Unix
-          environment, Wine should only need minimal modifications. What
-          performance you lose due to Wine running inside the emulator
-          rather than natively, you gain in complexity inside of Wine.
-          Furthermore, if the emulator is fast enough to run Windows
-          applications, Photoshop for instance, then it should be fast enough
-          to run that same Windows application plus Wine.
-        </para>
-        <para>
-          Two projects have started along those lines: <ulink
-          url="http://fabrice.bellard.free.fr/qemu/">QEMU</ulink>, an
-          open-source project, and <ulink
-          url="http://www.transitives.com/technology.htm">QuickTransit</ulink>,
-          a commercial CPU emulator environment from
-          <ulink url="http://www.transitives.com/">Transitives Technologies</ulink>.
-        </para>
-
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Why-would-anyone-want-Wine-Windows-suck">
-        <para>Why would anyone want Wine? Doesn't Windows suck?</para>
-      </question>
-      <answer>
-        <para>
-          First Wine is not about running Windows but about running Windows 
-          applications.
-        </para>
-        <para>
-          So if all your computing needs are fulfilled by native Unix 
-          applications, then you do not need Wine and should not be using
-          it. However, if you depend on one or more of the tens of 
-          thousands of Windows applications, then Wine is the best way to
-          use it without giving up on Unix. Let's look at the alternatives
-          to see why:
-        </para>
-        <para>
-          The most obvious alternative is to dual-boot. This is the solution
-          that provides the best compatibility. However it requires that you
-          acquire a Windows license and then dedicate a good chunk of your 
-          hard-drive to Windows. But the worst is yet to come. Each time you
-          will want to use that application you will have to reboot to 
-          Windows. This is especially significant if external factors dictate
-          when you must use this application (e.g. credit card to process, 
-          email to retrieve from a Lotus Notes server). Then you will find
-          yourself forced to close all your Linux applications just to run
-          that one Windows application. You may quickly get tired of this, or
-          will find that such a situation is impossible to justify in a 
-          business environment.
-        </para>
-        <para>
-          The next solution is to install virtual machine emulation software
-          such as VMWare, Win4Lin or Plex86. Then you can use windows 
-          applications without suffering such a big disruption. But it still
-          requires that you acquire a Windows license and dedicate as much 
-          disk space to Windows. Furthermore you will pay for the added 
-          convenience: if using VMWare or Win4Lin you have to buy another 
-          license, and more importantly you now have to dedicate a good chunk
-          of your computer's memory to the virtual machine. Performance will
-          take a significant hit too.
-        </para>
-        <para>
-          Using Wine lets you avoid all of that overhead: Windows license,
-          hard-drive space required by Windows, memory and performance hit 
-          taken by emulated virtual machines. Now you can start your Windows
-          application straight from your regular desktop environment, place
-          that application's window side by side with native applications,
-          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 organization,
-          you can't change a 5000 desktop setup overnight without a lot of risk.
-       </para>
-
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Use-Windows-driver-with-Wine">
-        <para>Can I use Wine to make the Windows driver for my network card /
-          graphics card / scanner / etc. work on Unix?</para>
-      </question>
-      <answer>
-        <para>
-          The goal of Wine is to make it possible to run Windows applications
-          on Unix, not Windows drivers or VxDs.
-        </para>
-        <para>
-          Drivers and Windows applications belong to different worlds.
-          Applications run in user mode and use the APIs provided by
-          the kernel and the other user mode dlls. In contrast, drivers
-          are loaded in the Windows kernel, i.e. in ring 0 instead of ring
-          3, drivers have to deal with specific memory management issues, and use
-          instructions not available to regular applications. This means
-          they would not be able to run in Wine since Wine runs entirely
-          in user mode. Rather you would have to modify the Linux kernel.
-          But in addition, drivers use a completely different API from
-          regular Windows applications. So the work performed on Wine would
-          not even be of any use for such a project. In other words, making
-          it possible to use Windows drivers or VxDs on Unix would be a
-          completely separate project.
-        </para>
-        <para>
-          However, if you want to reuse Windows drivers on a non-Microsoft
-          operating system we recommend that you have a look at
-          <ulink url="http://www.reactos.com/">ReactOS</ulink>.
-        </para>
-
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Which-one-of-the-different-Wine-packages">
-        <para>Which one of the different Wine packages out there is good for me?</para>
-      </question>
-      <answer>
-        <para>
-          Currently there is a broad selection of different Wine packages/versions:
-        </para>
-        <variablelist>
-
-	  <varlistentry>
-           <term><ulink url="http://www.winehq.org">Wine</ulink></term>
-           <listitem>
-           <para>
-              This is the "standard" distribution of Wine. Its license is
-              the LGPL, it can be downloaded for free. Both source code and binaries
-              are available in the <ulink url="http://www.winehq.org/site/download">download</ulink> section of the site.
-            </para>
-           </listitem>
-          </varlistentry>
-
-	  <varlistentry>
-          <term><ulink url="http://www.codeweavers.com/site/products/cxoffice/">CodeWeavers' CrossOver Office</ulink></term>
-          <listitem>
-            <para>
-              Wine version with special packaging to make sure almost all 
-              important Office type programs work pretty well. Costs $69.95 
-              for the Pro version and $39.95 for the Standard version.
-              Seems to be well worth it so far according to most comments. 
-              (note: you're supporting a company actively contributing to Wine
-              if you decide to buy CrossOver.)
-            </para>
-          </listitem>
-          </varlistentry>
-          
-          <varlistentry>
-          <term><ulink url="http://www.codeweavers.com/site/products/cxserver/">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/site/products/pricing/">CrossOver Office Server Edition Pricing</ulink>
-            </para>
-          </listitem>
-          </varlistentry>          
-
-        </variablelist>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Whats-the-history-of-Wine">
-        <para>What's the history of Wine?</para>
-      </question>
-      <answer>
-        <para>
-          The Wine project started in 1993 as a way to support running Windows 3.1
-          programs on Linux. Bob Amstadt was the original coordinator, but turned
-          it over fairly early on to Alexandre Julliard, who has run it ever 
-          since. A <ulink url="news:comp.emulators.ms-windows.wine">newsgroup</ulink>
-          was created in July 1994. Over the years, ports for
-          other Unixes have been added, along with support for Win32 as Win32 
-          applications became popular.
-        </para>
-        <para>
-          For more information, see <ulink url="http://www.winehq.com/site/history">
-          http://www.winehq.com/site/history</ulink>
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="What-is-the-current-version-of-Wine">
-        <para>What is the current version of Wine?</para>
-      </question>
-      <answer>
-        <para>
-          A new version of Wine is distributed about every month. You will be 
-          able to keep up on all the latest releases by reading the newsgroup
-          <ulink url="news:comp.emulators.ms-windows.wine">
-          comp.emulators.ms-windows.wine</ulink>, or by visiting the
-          <ulink url="http://www.winehq.org">Wine HQ homepage</ulink>. When
-          downloading Wine from your FTP site of choice (see
-          <ulink url="http://www.winehq.org/site/download">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
-          file name. For instance, the distribution released on August 30, 2005
-          was called Wine-20050830.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.org/site/git">
-          Read-only GIT</ulink> access is also available.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="What-is-the-current-Status-of-Wine">
-        <para>What is the current Status of Wine?</para>
-      </question>
-      <answer>
-        <para>
-          As of mid 2005, Wine consists of about 1.4 million lines of code,
-          written by more than 600 developers from dozens of countries around
-          the world. Wine is in active use by an estimated 200K people. Wine
-          implements more than 90% of the calls in popular Windows 
-          specifications such as ECMA-234 and Open32.
-        </para>
-        <para>
-          You may also want to look at the
-          <ulink url="http://www.winehq.org/site/status">
-          Status page</ulink> for a global view on Wine's implementation progress.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="When-will-Wine-be-finished">
-        <para>When will Wine be finished?</para>
-      </question>
-      <answer>
-        <para>
-          Large software projects are never finished, only released. In any
-          case Wine is chasing a moving target since every new release of 
-          Windows contains new API calls or variations on the existing ones.
-        </para>
-        <para>
-          Because Wine is being developed mainly by a single company (CodeWeavers) and volunteers, it is difficult to
-          predict when it will be ready for general release. But due to the
-          much increased interest by other companies in porting apps via Wine, Wine
-          development is constantly getting more and more active. Right now
-          we are working on releasing Wine 0.9 our schedule has this release around September 30th 2005.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Who-is-responsible-for-Wine">
-        <para>Who is responsible for Wine?</para>
-      </question>
-      <answer>
-        <para>
-          Wine is available thanks to the work of many people. Please see the
-          <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.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="What-undocumented-APIs-are-not-understood">
-        <para>What undocumented APIs / interfaces are not understood? Would
-              seeing Microsoft source help?
-        </para>
-      </question>
-      <answer>
-        <para>
-          The best solution would be if the Windows API were fully documented, so Wine
-          could be a perfect "clean-room" implementation. Seeing the source
-          code might make it harder to prove that no copyright violations have
-          taken place. That said, the documentation is often bad, nonexistent,
-          and even misleading where it exists, so a fair amount of reverse
-          engineering has been necessary, particularly in the shell (Explorer)
-          interface. The biggest problem facing Wine though is simply lack of
-	  manpower. At one point, over 5000 people were working on Windows 2000.
-	  While Wine doesn't need to replicate all of Windows (we only cover the
-	  parts needed to make Windows programs work), that's still nearly 8 times
-	  more people working simply on one release than have <emphasis>ever</emphasis>
-	  worked on Wine, in the history of the project.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Will-there-be-a-Windows-version-of-Wine">
-        <para>Will there be a Windows version of Wine?</para>
-      </question>
-      <answer>
-        <para>
-          Some people are working on getting Wine code to compile on Windows
-          using one of the following projects as a basis:
-        </para>
-        <itemizedlist spacing="compact">
-          <listitem> 
-            <para>
-              Cygwin
-              (<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>)
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              ReactOS
-              (<ulink url="http://www.reactos.com/">http://www.reactos.com</ulink>)
-            </para>
-          </listitem>
-        </itemizedlist>
-        <para>
-          There's some progress, so a Wine version that's usable on Windows
-          might be available at some time in the future.
-        </para>
-        <para>
-          Part of the rationale for these projects is to find out areas where
-          Wine portability is lacking. This is especially true of the
-          ReactOS project which is a reimplementation of the Windows kernel
-          and should thus be able to reuse most of Wine dlls.
-        </para>
-        <para>
-          Another reason for pursuing these projects is to be able to
-          replace a single Windows dll with its Wine counterpart. Besides
-          being a good test for the Wine dll, this lets us detect cases where
-          we made incorrect assumptions about how the dlls interact.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Can-I-use-native-drivers">
-        <para>Can I use Windows printer drivers in Wine?</para>
-      </question>
-      <answer>
-        <para>
-          Native printer drivers are not supported. At one time Wine supported 16bit 
-          native drivers but that was long ago. Wine uses the printers (and other 
-          devices) installed in your operating system. For the most part if you don't 
-          have the device installed on your OS then wine can't use it. 
-        </para>
-      </answer>
-      </qandaentry>
-
-    </qandadiv>
-    <qandadiv id="What-do-I-need-in-order-to-use-Wine">
-      <title>What do I need in order to use Wine?</title>
-      <qandaentry>
-      <question id="Under-what-platforms-will-Wine-run">
-        <para>
-          Under what hardware platform(s) and operating system(s) will
-          Wine(Lib) run?
-        </para>
-      </question>
-      <answer>
-        <para>
-          Wine is being developed specifically to run on the <emphasis>Intel
-          x86</emphasis> class of CPUs under certain UNIXes that run on this
-          platform. Winelib however is capable of porting the Windows
-          applications <emphasis>source code</emphasis> to other platforms
-          also, not only x86.
-        </para>
-        <para>
-          Thus running Windows binaries on other platforms (e.g. Mac OS X on
-          PowerPC) using just Wine is <emphasis>not</emphasis> possible. You
-          would have to either run Wine in an emulated x86 environment or
-          take the Windows application source code and recompile it using
-          Winelib.
-	</para>
-	<para>
-	  These are the platforms supported by Wine.
-	  Winelib support for other platforms keeps evolving,
-	  so it's not specifically listed here.
-	</para>
-        <para>
-          NetBSD, OpenBSD, UnixWare, and SCO OpenServer 5 worked at one time,
-          but Wine now requires kernel-level threads which are not currently 
-          available (or understood by the Wine team) on those platforms.
-        </para>
-        <para>
-          The Wine development team hopes to attract the interest of other
-          commercial UNIX and UNIX clone vendors as well.
-        </para>
-        <para>
-          BeOS: porting efforts (BeWine) used to be pretty strong, but BeOS
-          has severe limitations in Unix call support. The demise of Be
-          further hampered the project though it might come back one day on
-          one of the open BeOS projects. In any case a functional port seems
-          unlikely to ever happen at this stage.
-        </para>
-        <para>
-          Mac OS X / Darwin: The <ulink
-          url="http://darwine.opendarwin.org/">Darwine</ulink> project is
-          currently working on porting Wine to the Darwin/x86 platform.
-          Their goal is to eventually make it possible to run x86 Windows
-          applications on Darwin/PPC and then Mac OS X by using Bochs.
-          In addition, CodeWeavers has focused some of their resources on
-          Intel Mac OS X as well.  With a little luck, Wine will be running on
-          it by the third quarter of 2006.
-        </para>
-        <para>
-          FreeBSD: This port is well maintained and should work with
-          limitations in specific areas (mainly missing device/hardware
-          support).
-        </para>
-        <para>
-          Linux/x86: Works, and as the most popular platform for both
-          developers and users, it is the best supported platform of all.
-        </para>
-      </answer>
-      </qandaentry>
-      <qandaentry>
-      <question id="Will-wine-run-on-macintel">
-        <para>
-          I want to run Wine on an Intel Mac OS X (MacIntel) system, will it
-          work?
-        </para>
-      </question>
-      <answer>
-        <para>
-          (Also see the previous question.)  As of March, 2006, simple
-          applications are just beginning to to run on Intel Mac OS X.
-          It's possible in about 6 months we'll see applications running
-          similarly to how they do on Linux or FreeBSD.
-        </para>
-        <para>
-          There are some complicated issues surrounding Wine on Mac OS X.
-          Working with low-level features, such as signal handling and system
-          registers, are quite different on Mac OS X.  Further hampering
-          the issue are some bugs within the operating system.  Beyond
-          that, integration on Mac OS X becomes difficult because it is
-          vastly different than a traditional *nix desktop.  Menuing
-          and graphics drivers are just two areas that require a complete
-          reimplementation in order to be functional.
-        </para>
-      </answer>
-      </qandaentry>
-      <qandaentry>
-      <question id="What-minimum-CPU-must-I-have">
-        <para>
-          What minimum CPU must I have in my computer to be able to run Wine 
-          and MS Windows applications smoothly?
-        </para>
-      </question>
-      <answer>
-        <para>
-          We need to differentiate between Wine and Winelib here.
-        </para>
-        <para>
-          Wine won't run on any x86 CPU less than an 80386 due to address
-          management limitations.
-        </para>
-        <para>
-          It is known to also work in the 80486 and upwards compatible CPUs.
-          The basic test is, if you can run X11 now, you should be able to run
-          Wine and MS Windows applications under it.
-        </para>
-        <para>
-          As always, the faster your CPU, the better. Having a math coprocessor
-          is unimportant. However, having a graphics accelerated video card
-          supported by X will help greatly.
-        </para>
-        <para>
-          Depending on your application you may find that faster speeds are
-          required for sensible use. We can't give specific advice on that due
-          to the vast range of applications out there. However the rule of
-          thumb is that if your application runs fine on Windows, it should
-          run fine on the same platform in Wine.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="How-much-disk-space-will-Wine-take">
-        <para>
-         How much disk space will the Wine source code and binaries take on my
-         hard drive?
-        </para>
-      </question>
-      <answer>
-        <para>
-          You need approximately 750 megabytes of free hard drive space to
-          store and compile the source code. Wine also needs about 18 megs in
-          your /tmp directory. And about 50 MB are needed to do a make install.
-        </para>
-        <para>
-          Binary packages, especially those not containing debug information,
-          have much lower disk space requirements, usually in the 30MB range.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="How-much-RAM-do-I-need">
-        <para>
-          How much RAM do I need to have on my UNIX system to be able to run 
-          Wine and MS Windows applications smoothly?
-        </para>
-      </question>
-      <answer>
-        <para>
-          If you can run X smoothly on your UNIX system now, you should be 
-          able to run Wine and MS Windows applications just fine too, depending
-          on how memory hungry the application is.
-        </para>
-        <para>
-          Wine's memory requirements will depend on the application or game
-          that you choose to run. You will need to meet the minimum requirements for
-          the application as well as the overhead of your underlying OS.
-          You may want to check with the vendor of the application for its 
-          suggested memory requirements.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="How-long-does-Wine-take-to-build">
-        <para>How long does Wine take to build</para>
-      </question>
-      <answer>
-        <para>
-          Wine is getting to be quite large, and building from scratch takes a
-          lot of processing. As of September 2005, compile times were around 15
-          minutes on a Intel 3.8GHz Laptop with 1 GB of RAM. If you have a Git copy of wine, 
-	  you may not need to rebuild every thing each update.
-        </para>
-      </answer>
-      </qandaentry>
-      <qandaentry>
-      <question id="I-have-a-Drivespaced-partition">
-        <para>
-          I have a Drivespaced, Doublespaced or Stackered DOS partition. Can 
-          Wine run MS Windows binaries located in such a partition?
-        </para>
-      </question>
-      <answer>
-        <para>
-          Yes, but only if the operating system supports mounting those types
-          of drives. There is a Linux file system driver called dmsdos that
-          will allow read/write access to Doublespaced and Drivespace 1.0
-          drives. More specifically, it supports mounting DOS 6.0 and 6.2 
-          Doublespaced, DOS 6.22 Drivespaced, and Windows 95 Doublespaced 
-          compressed partitions (read and write access works fine, but write 
-          access is slow). It can be found at 
-          <ulink url="ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/">
-          ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/</ulink>
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Do-I-need-to-have-a-DOS-partition">
-        <para>Do I need to have a DOS partition on my system to use Wine?</para>
-      </question>
-      <answer>
-        <para>
-          You do not need a licensed and installed copy of DOS or MS Windows to
-          install, configure or run Wine. However, Wine has to be able to 
-          'see' an MS Windows binary (i.e. application) if it is to run it.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="If-Wine-completely-replaces-MS-Windows">
-        <para>
-          If Wine completely replaces MS Windows, will it duplicate all of the
-          functions of MS Windows?
-        </para>
-      </question>
-      <answer>
-        <para>
-          Wine's goal is to make it possible to run Windows applications on
-          Unix. To this end it will provide replacements for just those
-          DLLs and APIs that are needed by these Windows applications.
-          This means that Wine will not provide replacements for DLLs that
-          are not shipped with Windows or are always shipped with Windows
-          application (e.g. the Visual Basic run time). This also
-          means that implementing an API that no application ever uses is not
-          a priority. Similarly, until there are applications out there that
-          use the Win64 API, it will not be a priority. That being said,
-          we will certainly try to keep our options open and to improve our API
-          coverage as we can.
-        </para>
-        <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>,
-          <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>
-          Similarly Wine does not try to be a desktop environment so
-          providing applets such as a calculator, a file manager or even
-          window manager that look like Windows, are low priority or would
-          even best be done as a separate project. Such projects would also
-          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</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>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Will-I-install-on-any-UNIX-file-system">
-        <para> 
-          Will I be able to install MS Windows applications in any flavor of a
-          UNIX file system?
-        </para>
-      </question>
-      <answer>
-        <para>
-          Wine is written to be file system independent, so MS Windows 
-          applications will install and run under virtually any file system
-          supported by your brand of UNIX.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Will-Wine-run-only-under-X">
-        <para>Will Wine run only under X, or can it run in character mode?</para>
-      </question>
-      <answer>
-        <para>
-          Most of Wine's development effort is geared towards MS Windows' GUI,
-          but some limited support for character mode has appeared, by setting
-          <parameter>GraphicsDriver=ttydrv</parameter> in ~/.wine/config's
-          <parameter>[wine]</parameter> section.
-        </para>
-        <para>
-          Wine's infrastructure is already somewhat prepared for supporting
-          other graphics drivers than x11drv, but no real "alternative" 
-          graphics driver has been developed yet.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Will-Wine-run-under-any-X-window-manager">
-        <para>Will Wine run under any X window manager? Does it require a window manager at all?</para>
-      </question>
-      <answer>
-        <para>
-          Wine is window manager independent, so the X window manager you
-          choose to run has (almost) no bearing on your ability to run MS
-          Windows programs under Wine. Wine uses standard X libraries, so no
-          additional ones are needed. Wine has its own window management,
-          which acts like MS Windows. It can be turned off to use the native
-          window manager by modifying Managed or Desktop settings in winecfg.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Will-32-bit-applications-run-under-Wine">
-        <para>Will 32-bit Windows 95/98/ME/NT/2000/XP applications run under Wine?</para>
-      </question>
-      <answer>
-        <para>
-          Yes, 32-bit programs are now well supported.
-        </para>
-      </answer>
-      </qandaentry>
-
-    </qandadiv>
-    <qandadiv id="FAQ-Getting-Wine">
-      <title>Getting Wine</title>
-      <qandaentry>
-      <question id="Where-can-I-get-Wine">
-        <para>Where can I get Wine?</para>
-      </question>
-      <answer>
-        <para>
-          Because of lags created by using a mirror, word of the latest release
-          may reach you before the release is actually available at the ftp
-          sites listed here. The sources are available from the following
-          locations:
-        </para>
-        <itemizedlist>
-          <listitem>
-            <para>
-              <ulink url="http://sourceforge.net/project/showfiles.php?group_id=6241&amp;package_id=77449">
-               http://sourceforge.net/project/showfiles.php?group_id=6241&amp;package_id=77449
-              </ulink>
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              <ulink url="http://ibiblio.org/pub/linux/system/emulators/wine/">
-               http://ibiblio.org/pub/linux/system/emulators/wine/
-              </ulink>
-            </para>
-          </listitem>
-
-        </itemizedlist>
-        <para>
-          It should also be available from any other site that mirrors 
-          ibiblio.org, see <ulink url="http://www.ibiblio.org/pub/Linux/MIRRORS.html">http://www.ibiblio.org/pub/Linux/MIRRORS.html</ulink>.
-          Some of these 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 
-          Wine-YYYYMMDD.tar.gz. Simply replace YYYYMMDD in the distribution
-          file name with the numbers for year, month and date, respectively.
-          The latest one is the one to get.
-        </para>
-        <para>
-          Wine binary packages are available for several OS'es and 
-          distributions. See 
-          <ulink url="http://www.winehq.org/site/download">
-          the download page</ulink> for the most recent list.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Is-there-a-Git-tree">
-        <para>Is there a Git tree?</para>
-      </question>
-      <answer>
-        <para>
-          Current Wine sources are also available via Git
-          You will need Git 1.3.1 or above. If you are coming from behind a
-          firewall, use the http:// protocol.
-        </para>
-        <para>
-          To clone out the entire Wine source tree (which may be slow), use
-        </para>
-        <screen>
-git clone git://source.winehq.org/git/wine.git wine
-        </screen>
-        <para>
-          Be aware, though, that the initial clone of the entire Wine source
-          tree via Git is pretty slow, especially compared to getting Wine from
-          an FTP mirror near you.  Updating to your cloned repository is
-          reasonably fast, however.
-        </para>
-        <para>
-          Patch files are also available, so that you don't have to download,
-          install, and configure the entire distribution each month if you are
-          current to the previous release. Patch file release names follow the
-          same numbering convention as do the general releases, and take the 
-          form
-        </para>
-        <para>
-          Wine-YYYYMMDD.diff.gz  
-        </para>
-        <para>
-          Patch files are available from the same sites that distribute the
-          full release. To upgrade to a new release by using a patch file,
-          first cd to the top-level directory of the release (the one
-          containing the README file), then do a "make clean", and patch the
-          release with
-        </para>
-        <screen>
-gunzip -c patch-file | patch -p1 
-        </screen>
-        <para>
-          where patch-file is the name of the patch file something like
-          Wine-YYYYMMDD.diff.gz. You can then re-run ./configure, and then run
-          make depend && make
-        </para>
-        <para>
-          If you are mirroring the Wine distribution from the tsx-11 site and
-          wish to be listed here in this FAQ, please add it to the 
-          "things to go into the documentation" area.
-        </para>
-      </answer>
-      </qandaentry>
-    </qandadiv>
-
-    <qandadiv id="Installing-And-Configuring-Wine">
-      <title>Installing and Configuring Wine</title>
-      <qandaentry>
-      <question id="How-do-I-compile-the-Wine-source-code">
-        <para>How do I compile the Wine distribution source code?</para>
-      </question>
-      <answer>
-        <para>
-          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).
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="How-do-I-install-Windows-in-Wine">
-        <para>How do I install Windows in Wine under Linux?</para>
-      </question>
-      <answer>
-        <para>
-          Simple answer: you CAN'T. Windows demands direct access to the
-          hardware and cannot get it with Wine and UNIX in the way
-        </para>
-        <para>
-          Wine is supposed to be primarily used WITHOUT Windows. If you want
-          to use a Windows installation, then use an existing installation 
-          alongside the UNIX installation (see the dual-boot HOWTO for your OS
-          for more details). Or alternatively use the cabextract utility to
-          extract Windows install archives to a directory that you want to use
-          as Wine's Windows tree.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="How-do-I-configure-Wine-to-run-on-my-system">
-        <para>How do I configure Wine to run on my system?</para>
-      </question>
-      <answer>
-        <para>
-          As of Wine release 20050725 the config file has been disabled and
-          the values are now stored instead in registry files in your .wine directory.
-          The  preferred method to configure Wine is with winecfg, winecfg is a
-          tool to make it easy for new users to edit some of the contents of there
-          registry files.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="How-do-I-upgrade-configuration">
-        <para>How do I upgrade Wine without losing my working configuration?</para>
-      </question>
-      <answer>
-        <para>
-          Upgrading the wine installation does not affect the existing wine
-          registry settings. So after upgrading wine you still have the old (working )
-          wine registry configuration.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="If-I-use-Windows-which-versions-OK">
-        <para>If I want to use a Windows install, which versions are OK?</para>
-      </question>
-      <answer>
-        <para>
-          Either use a classic no-windows install (Wine is getting better all
-          the time) or use a Win9x install (Win95, 98, 98SE, ME). DON'T 
-          configure Wine to use an NT-based Windows install (NT, Win2K, WinXP, Win2K3).
-        </para>
-	<para>
-	  In general, most Windows installations contain vast quantities of garbage
-	  that can confuse Wine and make it less reliable. If you can, it's best to
-	  install the programs you want into Wine's fake windows drive.
-	</para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="If-I-use-Windows-which-one-works-best">
-        <para>If I use a Windows install with Wine, which one works best?</para>
-      </question>
-      <answer>
-        <para>
-          As of 09/2005:
-        </para>
-        <para>
-          I'd say Win98SE is the best version to use with Wine, as it's fairly
-          widespread amongst developers and relatively old. Using Win2K files
-          is <emphasis>definitely</emphasis> worse than a plain no-windows 
-          Wine install, and Win ME is said to be problematic, too (as probably
-          no developer uses it). In short: all Win9x &lt;= W98SE are good.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Installing-Visual-Basic-apps-wont-run">
-        <para>
-          Installing applications generated by Visual Basic won't run. What
-          should I do?
-        </para>
-      </question>
-      <answer>
-        <para>
-          Make sure you have all the VB run time libraries installed. You can
-          get the latest version from the Microsoft web site.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="When-I-click-on-exe-file-nothing-happens">
-        <para>When I click on *.exe file in my file Manager, nothing happens.</para>
-      </question>
-      <answer>
-        <para>
-          The normal Wine releases don't have .exe extensions registered for
-          Wine in KDE/Gnome yet. You have to open a terminal window instead
-          (often an icon showing a "black screen") and type something like:
-        </para>
-        <screen>
-cd /my/windows/program/directory
-wine myprogram.exe
-        </screen>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="bash-wine-Command-not-found-What-can-I-do">
-        <para>bash says "wine: Command not found" What can I do?</para>
-      </question>
-      <answer>
-        <para>
-          Try to logout and login again into bash. That might fix it.
-        </para>
-        <para>
-          If it doesn't, then make sure the wine binary is in your 
-          <parameter>PATH</parameter>.
-        </para>
-        <para>
-          Run as root:
-        </Para>
-        <screen>
-find / -name "wine" -type f -perm +111
-        </screen>
-        <para>
-          to find the path where the wine binary is in. Then check whether
-        <parameter>PATH</parameter> includes it:
-        </para>
-        <screen>
-echo $PATH 
-        </screen>
-        <para>
-          If not, add that e.g. to <filename>/etc/profile</filename> by doing:
-        </para>
-        <screen>
-export PATH=$PATH:/path/to/wine/binary 
-        </screen>
-        <para>
-          That should help.
-        </para>
-        <para>
-           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>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="How-do-I-remove-Wine-from-my-Computer">
-        <para>How do I remove Wine from my Computer?</para>
-      </question>
-      <answer>
-        <para>
-          It depends on how you installed. If you used an RPM, the right command is this:
-         <command>rpm -e wine (as root)</command>
-        </para>
-       <para>
-         If you installed from source (the .tar.gz file), the right
-         way to do it is to change to the root of the source tree (the directory with the configure script,
-         readme etc) then run as root:
-         <command>make uninstall</command>
-       </para>
-      </answer>
-      </qandaentry>
-    </qandadiv>
-
-    <qandadiv id="About-running-Wine">
-      <title>About running Wine</title>
-      <qandaentry>
-      <question id="How-do-I-run-an-MS-Windows-program">
-        <para>How do I run an MS Windows program under Wine?</para>
-      </question>
-      <answer>
-        <para>
-          When invoking Wine, you must specify the entire path to the
-          executable, or by file name only. For example to run Windows'
-          solitaire, type any of the following:
-        </para>
-        <itemizedlist>
-          <listitem>
-          <para>
-            <command>wine sol</command> or <command>wine sol.exe</command>
-           (using the search path to locate the file).
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            <command>wine c:\\windows\\sol.exe</command> 
-           (using a DOS file name).
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            <command>wine /usr/windows/sol.exe</command>
-           (using a UNIX file name).
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            <command>wine "c:\windows\sol.exe"</command>
-            (using quoted DOS file name).
-          </para>
-          </listitem>
-        </itemizedlist>
-        <para>
-          The path of the file will also be added to the path when a full name
-          is supplied on the command line.
-
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Wine-cannot-find-MS-Windows-on-my-drive">
-        <para>
-          I have installed and configured Wine, but Wine cannot find MS 
-          Windows on my drive. Where did I go wrong?
-        </para>
-      </question>
-      <answer>
-        <para>
-          If you have a DOS partition, first make sure that you have mounted
-          it, either by putting the entry into <filename>/etc/fstab</filename>,
-          or by manually mounting it.
-        </para>
-        <para>
-          Remember too that unless your version of UNIX can see through it, or
-          you are running a utility that can see through it, your DOS
-          partition must not be located on a Drivespaced, Doublespaced or
-          Stackered partition, as neither Linux, FreeBSD, NetBSD or Wine can
-          natively 'see' files located in these compressed DOS partitions.
-        </para>
-        <para>
-          Check your path statements in the <filename>wine.conf</filename> 
-          file. No capital letters may be used in paths, as they are 
-          automatically converted to lowercase.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Parts-of-my-app-do-not-work-What-is-wrong">
-        <para>
-          I was able to get various MS Windows programs to run, but parts of
-          them do not work. What is wrong?
-        </para>
-      </question>
-      <answer>
-        <para>
-          Wine is not complete at this time, so some of each programs' 
-          features may not work. They will in time as more of the MS 
-          Windows API calls are included in Wine.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Menus-do-not-work-how-can-I-exit">
-        <para>
-          I have run various MS Windows programs, but since the program menus
-          do not work, how can I exit these programs?
-        </para>
-      </question>
-      <answer>
-        <para>
-          Menus should be working correctly, if for some reason your applications menus stops responding.
-          You can kill the xterm shell window that you called up to run your MS Windows program, and the X 
-          window that appeared with the program will be killed too. If you started the application from a 
-          shortcut you can open a terminal and start <command>xkill</command> and just click on the application to kill it.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question id="My-app-doesnt-work-what-can-i-do">
-	  <para>
-	    My program doesn't work, what can I do?
-	  </para>
-	</question>
-	<answer>
-	  <para>
-	    If you are a programmer and know C, then start debugging
-	    Wine and help us make it better! If you can't, then you will
-	    have to either convince a Wine developer to try and make your
-	    program work (there must be a downloadable version or demo for that). 
-          </para>
-          <para>  
-            You can submit your application to the <ulink url="http://appdb.winehq.org/">
-            Wine Application DB </ulink> and gather tips on ways to get your app to work its best.
-          </para>
-          <para> 
-            You can also submit your application to the CodeWeavers CrossOver 
-            <ulink url="http://www.codeweavers.com/site/compatibility/"> Compatibility </ulink> Center.
-            Where you can pledge/vote toward future support of your favorite application.
-	  </para>
-          <para>
-          We recommend that you try builtin dlls first and report any errors that you may run across to wine-devel 
-          or to our Bugzilla. If you report problems they can be verified and fixed by the development team 
-          and this helps everyone over the long run by not covering up bugs with the use of native dlls.
-          </para>
-	  <para>
-	    Alternatively, you may be able to get the app working by taking native DLLs from a Microsoft Windows install, 
-            and using them (set the dlls to native with winecgf). Not all DLLs can be replaced that way - in particular 
-            DirectX cannot be, nor can some core system DLLs like gdi32, user, ntdll, kernel32, etc.
-	  </para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Can-I-use-Wine-with-other-Linux-Distros">
-        <para>Can I use Wine with SUSE, RedHat or other Linux Distro's?</para>
-      </question>
-      <answer>
-        <para>
-          You can use Wine on any sufficiently recent Linux installation. The
-          amount of work getting Wine up and running depends on whether you
-          install a binary packages or do a source install.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Does-Wine-work-with-AMD-Processors">
-        <para>Does Wine work with AMD Processors?</para>
-      </question>
-      <answer>
-        <para>
-          Yes, it does. Wine should work on any processor compatible with
-          the Pentium or greater.
-        </para>
-      </answer>
-      </qandaentry>
-
-       <qandaentry>
-      <question id="Can-I-launch-Unix-app-from-Windows-app">
-        <para> Can I launch a Unix program from a Windows program?</para>
-      </question>
-      <answer>
-        <para>
-          Sure, Wine supports that. Just enter the unix program name wherever
-          a program has something that it's supposed to execute, and it
-          should just work.
-        </para>
-      </answer>
-      </qandaentry>
-      <qandaentry>
-      <question id="Error-with-installshield-6">
-        <para>
-          I get <quote>Error installing iKernel.exe: (0x1400)</quote>
-          when running an InstallShield 6 installer.
-        </para>
-      </question>
-      <answer>
-        <para>
-          If you get the error "Error installing iKernel.exe: (0x1400)" at any
-          point, it's probably because there are leftover processes from a
-          previous try. You can verify this with the command
-        </para>
-        <para><prompt>$ </><command>ps augxw | grep wine</command></para>
-        <para>
-          If that command shows old copies of wine running your setup,
-          you need to kill them before you can run the setup program.
-          If there are no other Wine programs running, you can kill them
-          all with the command
-        </para>
-        <para><prompt>$ </><command>killall wine</command></para>
-        <para>
-          If you're also running Wine programs you care about, you'll
-          have to kill off the old Setup instances one by one using
-          kill and the individual PIDs (or perhaps Wine's spiffy Task Manager,
-          which doesn't exist yet).
-        </para>
-        <para>
-          You should repeat the <command>ps</command> to make sure all of the old 
-          Wine processes are gone.
-        </para>
-       </answer>
-      </qandaentry>
-    </qandadiv>
-
-    <qandadiv id="Getting-help">
-      <title>Getting help</title>
-      <qandaentry>
-      <question id="Is-there-any-documentation-for-Wine">
-        <para>Is there any documentation for Wine?</para>
-      </question>
-      <answer>
-        <para>
-          Yes, see <ulink url="http://www.winehq.org/site/documentation">
-          http://www.winehq.org/site/documentation.</ulink>
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="I-have-written-some-documententation">
-        <para>
-          I couldn't find the answer to my question in the documentation, but
-          I've written a document explaining how to solve it. What should I do?
-        </para>
-      </question>
-      <answer>
-        <para>
-          Updates and additions to the Wine documentation directory should be
-          sent to the wine-patches mailing list at 
-          <ulink url="http://www.winehq.org/site/forums">
-          http://www.winehq.org/site/forums</ulink>. Website and FAQ 
-          additions should be added to the appropriate Wine Knowledge base directory.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Is-there-a-Usenet-newsgroup-for-Wine">
-        <para>Is there a Usenet newsgroup for Wine?</para>
-      </question>
-      <answer>
-        <para>
-          Yes, and it's called 
-          <ulink url="news:comp.emulators.ms-windows.wine">
-          comp.emulators.ms-windows.wine</ulink>. The newsgroup serves as a
-          place for users and developers to discuss Wine, and for minor 
-          announcements for the general public. Major announcements will be
-          cross posted to other appropriate newsgroups, such as the following:
-        </para>
-        <itemizedlist>
-          <listitem>
-          <para>
-            <ulink url="news:comp.os.linux.announce">
-            comp.os.linux.announce</ulink>
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            <ulink url="news:ccomp.windows.x.announce">
-            comp.windows.x.announce</ulink>
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            <ulink url="news:ccomp.emulators.announce">
-            comp.emulators.announce</ulink>
-          </para>
-          </listitem>
-        </itemizedlist>
-        <para>
-          If your Usenet site does not carry these newsgroups, please urge 
-          your ISP's sysadmin to add and/or uplink them.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Is-there-a-World-Wide-Web-site-for-Wine">
-        <para>Is there a World Wide Web site for Wine?</para>
-      </question>
-      <answer>
-        <para>
-          Wine HQ (<ulink url="http://www.winehq.org">http://www.winehq.org</ulink>) is the official site.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Is-there-an-IRC-channel-for-Wine">
-        <para>Is there an IRC channel for Wine?</para>
-      </question>
-      <answer>
-        <para>
-          Sure. It's channel <filename>#WineHQ</filename> on 
-          <filename>irc.freenode.net</filename> see 
-          (<ulink url="http://freenode.net">http://freenode.net</ulink>).
-          Usually several knowledgeable Wine users hang out there.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="I-think-I-found-a-bug-How-do-I-report-it">
-        <para>
-          I think I've found a bug. How do I report this bug to the Wine
-          programming team?
-        </para>
-      </question>
-      <answer>
-        <para>
-          Bug reports should be submitted to our online Bugzilla system 
-          (<ulink url="http://bugs.winehq.org/">http://bugs.winehq.org/</ulink>).
-          You should include at least the following:
-        </para>
-        <itemizedlist>
-          <listitem>
-          <para>
-            The Wine version tested
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            The Windows application name, including the version, and, if
-            applicable, a URL the application can be downloaded from
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            A brief description of the bug
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            The relevant part(s) of the output of the Wine debugger
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            A screenshot of the visual problem, if applicable
-          </para>
-          </listitem>
-        </itemizedlist>
-        <para>
-         For more information about reporting bugs please see the 
-         <ulink url="http://www.winehq.org/site/docs/wineusr-guide/bug-reporting">
-         How to report a bug</ulink> section of the Wine Users Guide.
-        </para>
-      </answer>
-      </qandaentry>
-    </qandadiv>
- 
-    <qandadiv id="Helping-Wine-or-becoming-a-Wine-developer">
-      <title>Helping Wine or becoming a Wine developer</title>
-      <qandaentry>
-      <question id="How-do-I-become-a-Wine-developer">
-        <para>How do I become a Wine developer? What do I need to know?</para>
-      </question>
-      <answer>
-        <para>
-          If you can program C, that's a good start. Download the sources via
-          (<ulink url="http://www.winehq.org/site/git">Git,</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.org/site/forums">http://www.winehq.org/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>
-
-      <qandaentry>
-      <question id="How-can-I-contribute-to-the-Wine-project">
-        <para>How can I help contribute to the Wine project, and in what way(s)?</para>
-      </question>
-      <answer>
-        <para>
-          You can contribute programming or documentation skills, or monetary
-          or equipment donations, to aid the Wine developers in reaching their goals.
-        </para>
-        <para>
-          One area where every Wine user can contribute to this project is by sending high quality 
-          bug reports to our Bugzilla and helping the developers with any follow up questions that they
-          may have about a bug that you have come across. It is not only impossible but also impractical 
-          for a developers to have a copy of every program on the market. This is why we need your 
-          help even after you have sent in the initial bug report. If a developer has a good idea what 
-          might be causing the bug he or she may ask if you can try a patch and see if it fixes the problem. 
-          After this patch makes its way into our main development tree the bug report will be closed 
-          and your help will be appreciated by everyone.
-        </para>
-        <para>
-          For a list of ideas of how you can help, please consult the 
-          <ulink url="http://www.winehq.org/site/contributing">
-          Wine contrib page</ulink>.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="I-want-to-help-beta-test-Wine">
-        <para>I want to help beta test Wine. How can I do this?</para>
-      </question>
-      <answer>
-        <para>
-          Wine still consists of some Alpha code at this time. However, anyone
-          is welcome to download the latest version, and try it out at any
-          time.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="I-wrote-some-code-I-would-like-to-submit">
-        <para>
-          I have written some code that I would like to submit to the Wine
-          project. How do I go about doing this?
-        </para>
-      </question>
-      <answer>
-        <para>
-          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.org/mailman/listinfo/wine-patches">http://www.winehq.org/mailman/listinfo/wine-patches</ulink>).
-          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.org/site/sending_patches">how to submit
-          patches</ulink>. This will also give you more details about the whole
-          process and in particular to what will happen to your patch once
-          submitted.
-        </para>
-      </answer>
-      </qandaentry>
-    </qandadiv>
-
-    <qandadiv id="Developing-programs-using-Wine-WineLib">
-      <title>Developing programs using Wine/WineLib</title>
-      <qandaentry>
-      <question id="Can-I-use-Wine-to-port-Win32-sources-to-Unix">
-        <para>Can I use Wine to port my Win32 sources to Unix?</para>
-      </question>
-      <answer>
-        <para>
-          That is the idea of Winelib. Right now you may still have some 
-          difficulties, but this is changing all the time. Read the 
-          <ulink url="http://www.winehq.org/site/docs/winelib-guide/index">Winelib User's Guide</ulink> for info.
-
-        </para>
-      </answer>
-      </qandaentry>
-      <qandaentry>
-      <question id="Will-MFC-work-with-Wine-What-do-I-need-to-do">
-        <para>Will MFC work with Wine? What do I need to do?</para>
-      </question>
-      <answer>
-        <para>
-          Wine is not implementing an MFC replacement nor does it intend to.
-          However it is possible (with a lot of work) to compile the MFC from
-          source and thus produce an <filename>mfc42.dll.so</filename> library.
-        </para>
-        <para>
-          Please refer to the 
-          <ulink url="http://www.winehq.org/site/docs/winelib-guide/index">Winelib User's Guide</ulink> for how to do this.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Are-there-commercial-apps-ported-using-Wine">
-        <para>
-          Are there any commercial applications which have been ported
-          using Wine?
-        </para>
-      </question>
-      <answer>
-        <para>
-          Here are few examples of applications ported using Wine or Winelib:
-        </para>
-        <itemizedlist>
-          <listitem>
-          <para>
-            Corel's WordPerfect Office Suite 2000 was ported to Linux using
-            Wine.
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            Kylix, the Linux version of Delphi, was ported to Linux using
-            Winelib. The IDE actually uses a combination of QT and Winelib
-            which would not have been possible to achieve using only Wine.
-            The generated applications however do not depend on Wine in
-            any way.
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            Vividas Streaming Video
-            (<ulink url="http://www.vividas.com/support/">http://www.vividas.com/support/</ulink>)
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            Ability Office
-            (<ulink url="http://www.ability.com/linux/abilitylinux.php">http://www.ability.com/linux/abilitylinux.php</ulink>)
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            IBM's Websphere
-            (<ulink url="http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p">http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p</ulink>)
-          </para>
-          </listitem>
-          <listitem>
-          <para>
-            <trademark class="registered">BricsCad</>
-            (<ulink url="ftp://ftp0:bricscad@ftp.bricscad.com/pub/Eng-Us/B4L/Readme.htm"><trademark class="registered">BricsCad</> V6 for Linux</ulink>)
-          </para>
-          </listitem>
-        </itemizedlist>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="Can-I-bundle-everything-in-one-huge-exe">
-        <para>
-          Can I build one large Monolithic application?
-        </para>
-      </question>
-      <answer>
-        <para>
-          No. However, if you don't want Wine as a dependency, you can bundle your 
-          private version of Wine into your package (.rpm/.deb). Wine has good
-          support for such a setup via the WINEPREFIX environment variable.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="How-can-I-detect-Wine">
-        <para>How can I detect Wine?</para>
-      </question>
-      <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.
-        </para>
-      </answer>
-      </qandaentry>
-
-
-    </qandadiv>
-
-    <qandadiv id="Wine-HQ-issues">
-      <title>Wine HQ issues</title>
-      <qandaentry>
-      <question id="Why-are-the-maillists-set-to-reply-to-author">
-        <para>
-          Why are the mailing lists set to reply to author, not to mailing list?
-        </para>
-      </question>
-      <answer>
-        <para>
-          There are some very valid reasons for doing so.
-        </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
-      <question id="How-to-unsubscribe-from-the-mailing-lists">
-        <para>How to unsubscribe from the mailing lists?</para>
-      </question>
-      <answer>
-        <para>
-          Please see: <ulink url="http://www.winehq.org/site/forums">http://www.winehq.org/site/forums</ulink>
-          And select [(Un-)Subscribe]
-        </para>
-      </answer>
-      </qandaentry>
-
-    </qandadiv>
- 
-  </qandaset>
-</article>
Index: docs/Make.rules.in
diff -u -p docs/Make.rules.in:1.7 docs/Make.rules.in:1.8
--- docs/Make.rules.in	26 Jun 2007 20:42:55 -0000
+++ /dev/null	26 Jun 2007 20:42:55 -0000
@@ -105,7 +105,6 @@ ALLFORMATS = html pdf sgml ps txt
 $(ALLFORMATS:%=wineusr-guide.%): $(WINEUSR_SRCS)
 $(ALLFORMATS:%=winedev-guide.%): $(WINEDEV_SRCS)
 $(ALLFORMATS:%=winelib-guide.%): $(WINELIB_SRCS)
-$(ALLFORMATS:%=wine-faq.%):      $(WINEFAQ_SRCS)
 
 Makefile: Makefile.in $(TOPSRCDIR)/configure
 	@echo $? is newer than '$@', please rerun $(TOPSRCDIR)/configure!



More information about the wine-cvs mailing list