Tom, you submitted a patch that splits many words in two. I assume that's because they're not in the dictionary but I'm not sure it's appropriate. Here are some examples:
- Make sure you have all the VB runtime libraries installed. + Make sure you have all the VB run time libraries installed.
- (using a DOS filename). + (using a DOS file name).
- the UNIX kernel supports the DOS/MS Windows filesystem type). + the UNIX kernel supports the DOS/MS Windows file system type).
And some I am absolutely sure are wrong:
- ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/</ulink> + ftp://metalab.unc.edu/pub/Linux/system/file systems/dosfs/</ulink>
- when running an InstallShield 6 installer. + when running an Install shield 6 installer.
- program work (there must be a downloadable version or demo for + program work (there must be a download able version or demo for
Also I'm not sure why you changed the Lycos URL:
- <ulink url="http://search.lycos.com/">Lycos</ulink>. Some of + <ulink url="http://www.compucan.com/Lycos.htm">lycos</ulink> Some of
Actually I'm not sure why we have this link to Lycos at all. How does one find Wine using it?
So I'm submitting a patch fixing the second type of changes directly to wine-patches. And here is a patch that reverts most of the word splitting. Maybe it goes too far. What do you think?
Index: documentation/faq.sgml =================================================================== RCS file: /home/wine/wine/documentation/faq.sgml,v retrieving revision 1.21 diff -u -r1.21 faq.sgml --- documentation/faq.sgml 8 Sep 2003 19:38:45 -0000 1.21 +++ documentation/faq.sgml 9 Sep 2003 19:02:31 -0000 @@ -424,11 +424,11 @@ <ulink url="http://www.winehq.com/download.shtml">the Download page</ulink> for some of these choices), you can make sure that you are getting the latest version by watching the version numbers in the distribution - file name. For instance, the distribution released on August 13, 2003 + filename. For instance, the distribution released on August 13, 2003 was called Wine-20030813.tar.gz. Patch files are also available. If you are current to the previous version, you can download and apply just the current patch file rather than the entire new distribution. - The patch file names follow the same conventions as the monthly + The patch filenames follow the same conventions as the monthly distribution. <ulink url="http://www.winehq.org/site/cvs"> Read-only CVS</ulink> access is also available. </para> @@ -824,8 +838,8 @@ <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 + of drives. There is a Linux filesystem 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 @@ -859,13 +873,13 @@ <answer> <para> Many folks have successfully installed and run programs - in their UNIX file system without having a DOS partition or MS + in their UNIX filesystem 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 + filesystem, 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. </para> @@ -905,7 +919,7 @@ 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). + the UNIX kernel supports the DOS/MS Windows filesystem type). </para> <para> If you edit this file by hand, it should contain something similar @@ -935,7 +949,7 @@ 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 + application (e.g. the Visual Basic runtime). 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, @@ -970,13 +984,13 @@ <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? + UNIX filesystem? </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 + Wine is written to be filesystem independent, so MS Windows + applications will install and run under virtually any filesystem supported by your brand of UNIX. </para> </answer> @@ -1080,12 +1094,12 @@ <para> It should also be available from any other site that mirrors ibiblio.org. For more download locations, see - <ulink url="http://www.compucan.com/Lycos.htm">lycos</ulink> Some of + <ulink url="http://search.lycos.com/">Lycos</ulink>. Some of these ftp sites may archive previous versions of Wine as well as the current one. To determine which is the latest one, look at the - distribution file name, which will take the form + distribution filename, 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. + filename with the numbers for year, month and date, respectively. The latest one is the one to get. </para> <para> @@ -1313,7 +1327,7 @@ </question> <answer> <para> - Make sure you have all the VB run time libraries installed. You may + Make sure you have all the VB runtime libraries installed. You may need to use the native DLL vbrun60.dll. You can get some from dll-files.com. </para> </answer> @@ -1347,7 +1361,7 @@ </question> <answer> <para> - Try to re login into bash. That might fix it. + 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 @@ -1405,14 +1419,14 @@ Make sure that you specify the exact path when using the powerful <command>rm -fR</command> command. If you are afraid that you might delete something important, or might otherwise delete other files - within your file system, <command>cd</command> into each Wine + within your filesystem, <command>cd</command> into each Wine sub directory singly and delete the files found there manually, one file or directory at a time. </para> <para> Neither the Wine developers and programmers, nor the Wine FAQ author/maintainer, can be held responsible for your deleting any - files in your own file system. + files in your own filesystem. </para> </answer> </qandaentry> @@ -1427,7 +1441,7 @@ <answer> <para> When invoking Wine, you must specify the entire path to the - executable, or by file name only. For example to run Windows' + executable, or by filename only. For example to run Windows' solitaire, type any of the following: </para> <itemizedlist> @@ -1440,19 +1454,19 @@ <listitem> <para> <command>wine c:\windows\sol.exe</command> - (using a DOS file name). + (using a DOS filename). </para> </listitem> <listitem> <para> <command>wine /usr/windows/sol.exe</command> - (using a UNIX file name). + (using a UNIX filename). </para> </listitem> <listitem> <para> <command>wine "c:\windows\sol.exe"</command> - (using quoted DOS file name). + (using quoted DOS filename). </para> </listitem> </itemizedlist>