[docs] winelib: Assorted spelling fixes.
frederic.delanoy at gmail.com
Fri Jul 5 05:59:35 CDT 2013
en/winelib-bindlls.sgml | 22 +++++++++++-----------
en/winelib-intro.sgml | 16 ++++++++--------
en/winelib-mfc.sgml | 4 ++--
en/winelib-porting.sgml | 6 +++---
en/winelib-toolkit.sgml | 24 ++++++++++++------------
5 files changed, 36 insertions(+), 36 deletions(-)
diff --git a/en/winelib-bindlls.sgml b/en/winelib-bindlls.sgml
index f978780..e72cae8 100644
@@ -5,7 +5,7 @@
For one reason or another you may find yourself with a Linux
- library that you want to use as if it were a Windows Dll. There are
+ library that you want to use as if it were a Windows DLL. There are
various reasons for this including the following:
@@ -32,10 +32,10 @@
The process for dealing with these situations is actually quite simple.
- You need to write a spec file that will describe the library's
- interface in the same format as a Dll (primarily what functions it
+ You need to write a spec file that will describe the library
+ interface in the same format as a DLL (primarily what functions it
exports). Also you will want to write a small wrapper around the
- library. You combine these to form a Wine built-in Dll that links to the
+ library. You combine these to form a Wine built-in DLL that links to the
Linux library. Then you modify the DllOverrides in the wine config
file to ensure that this new built-in DLL is called rather than any
@@ -80,8 +80,8 @@ signed short MyLinuxFunc (unsigned short a, void *b, void *c,
a spec file (e.g. man winebuild).
- In the simple example we want a Wine built-in Dll that corresponds to
- the MyWin Dll. The spec file is <filename>MyWin.dll.spec</filename> and
+ In the simple example we want a Wine built-in DLL that corresponds to
+ the MyWin DLL. The spec file is <filename>MyWin.dll.spec</filename> and
looks something like this:
@@ -190,7 +190,7 @@ signed short WINAPI MyProxyWinFunc (unsigned short a, void *b, void *c,
- So how do we actually build the Wine built-in Dll? The easiest way is
+ So how do we actually build the Wine built-in DLL? The easiest way is
to get Winemaker to do the hard work for us. For the simple example we
have two source files (the wrapper and the spec file). We also have
the 3rd party header and library files of course.
@@ -204,15 +204,15 @@ signed short WINAPI MyProxyWinFunc (unsigned short a, void *b, void *c,
--nosource-fix (requires winemaker version
- 0.5.8 or later) to ensure that the two files are not modified.
- (If using an older version of winemaker then make the two files
- readonly and ignore the complaints about being unable to modify
+ 0.5.8 or later) to ensure that the two files are not modified
+ (if using an older version of winemaker, make the two files
+ read-only and ignore the complaints about being unable to modify
- --dll --single-target MyWin --nomfc to specify the target
+ --dll --single-target MyWin --nomfc to specify the target.
diff --git a/en/winelib-intro.sgml b/en/winelib-intro.sgml
index c5ef38a..ac41b60 100644
@@ -9,7 +9,7 @@
Windows applications on Unix.
- Most of Winelib's code consists of the Win32 API implementation.
+ Most of Winelib code consists of the Win32 API implementation.
Fortunately this part is 100 percent shared with Wine. The remainder
consists of Windows compatible headers and tools like the resource
compiler (and even these are used when compiling Wine).
@@ -20,10 +20,10 @@
applications as well as dynamic libraries.
- What is not supported is 16bit source code as the types it depends on
+ What is not supported is 16 bit source code as the types it depends on
(especially segmented pointers) are not supported by Unix compilers.
- Also missing are some of the more exotic features of Microsoft's
- compiler like native COM support and structured exception handling.
+ Also missing are some of the more exotic features of Microsoft
+ compilers like native COM support and structured exception handling.
So you may need to perform some modifications in your code when
recompiling your application with Winelib. This guide is here to help
you in this task.
@@ -117,7 +117,7 @@
The best way to take care of all these issues is to use winemaker.
- Winemaker is a perl script which is designed to help you bootstrap
+ Winemaker is a Perl script which is designed to help you bootstrap
the conversion of your Windows projects to Winelib. In order to do
this it will go analyze your code, fixing the issues listed above
and generate straight Makefiles.
@@ -261,7 +261,7 @@
Then you'll run winemaker. Here are the options you will most
- likely want to use. For complete list of options see
+ likely want to use. For a complete list of options see
the winemaker man page.
@@ -288,7 +288,7 @@
Winemaker normally makes a backup of all the files in which
- it does more than the standard Dos to Unix conversion.
+ it does more than the standard DOS to Unix conversion.
But if you already have (handy) copies of these files
elsewhere you may not need these so you should use this
@@ -300,7 +300,7 @@
- These option lets winemaker know what kind of target you are
+ These options lets winemaker know what kind of target you are
building. If you have the windows library in your source
hierarchy then you should not need to specify
<option>--dll</option>. But if you have console executables
diff --git a/en/winelib-mfc.sgml b/en/winelib-mfc.sgml
index 08ddccd..3583b19 100644
@@ -146,7 +146,7 @@
Then when compiling it you will indeed need a number of
<literal>_AFX_NO_XXX</literal> macros. But this is not enough
and there are other things you will need to
- '<literal>#ifdef</literal>-out'. For instance Wine's richedit
+ '<literal>#ifdef</literal>-out'. For instance Wine richedit
support is not very good. Here are the AFX options I use:
@@ -165,7 +165,7 @@
- We recommend using Wine's msvcrt headers (<literal>-isystem
+ We recommend using Wine msvcrt headers (<literal>-isystem
$(WINE_INCLUDE_ROOT)/msvcrt</literal>), though it means you
will have to temporarily disable winsock support
(<literal>#ifdef</literal> it out in
diff --git a/en/winelib-porting.sgml b/en/winelib-porting.sgml
index d19af01..881032e 100644
@@ -26,7 +26,7 @@
<title id="C-library.title">C library</title>
- There are 2 choices available to you regarding which C library
+ There are two choices available to you regarding which C library
to use: the native glibc C library or the msvcrt C library.
@@ -141,8 +141,8 @@
overloads that take int and char respectively).
- If you come across a difference between the Windows headers
- and Wine's that breaks compilation, try asking for help on
+ If you come across a difference between Windows and Wine
+ headers that breaks compilation, try asking for help on
<email>wine-devel at winehq.org</email>.
diff --git a/en/winelib-toolkit.sgml b/en/winelib-toolkit.sgml
index cb1073f..3617c1c 100644
@@ -22,8 +22,8 @@
because it offers more information.
- The usage is very easy, just replace the path to the sourcefolder
- with the path to the projectfile.
+ The usage is very easy, just replace the path to the source folder
+ with the path to the project file.
$ winemaker --lower-uppercase myproject.vcproj
@@ -32,7 +32,7 @@
- <title id="source-analysis.title">Winemaker's source analysis</title>
+ <title id="source-analysis.title">Winemaker source analysis</title>
Winemaker can do its work even without a Windows makefile or a
Visual Studio project to start from (it would not know what to do
@@ -145,11 +145,11 @@
you can guess at the items that winemaker may get wrong in
this phase: macro definitions, include path, DLL path, DLLs to
import, library path, libraries to link with. You can deal with
- these issues by using winemaker's <option>-D</>, <option>-P</>,
+ these issues by using winemaker <option>-D</>, <option>-P</>,
<option>-i</>, <option>-I</>, <option>-L</> and <option>-l</>
options if they are
homogeneous enough between all your targets. Otherwise you may
- want to use winemaker's <link linkend="interactive">interactive
+ want to use winemaker <link linkend="interactive">interactive
mode</link> so that you can specify different settings for each
project / target.
@@ -159,7 +159,7 @@
not compile if <varname>STRICT</varname> is not turned on, and
others will not compile if it is. Fortunately all the files in a
given source tree use the same setting so that all you have to do
- is add <literal>-DSTRICT</literal> on winemaker's command line
+ is add <literal>-DSTRICT</literal> on winemaker command line
or in the <filename>Makefile</filename> file(s).
@@ -171,7 +171,7 @@
The target is not importing the right set of DLLs, or is not
being linked with the right set of libraries. You can avoid
- this by using winemaker's <option>-P</>, <option>-i</>,
+ this by using winemaker <option>-P</>, <option>-i</>,
<option>-L</option> and <option>-l</> options or adding these
DLLs and libraries to the <filename>Makefile</>.
@@ -242,7 +242,7 @@ LIBRARIES =
to all the targets in this makefile. The <varname>LIBRARIES</>
variable allows you to specify additional Unix libraries to link
with. Note that you would normally not specify Winelib libraries
- there. To link with a Winelib library, one uses <varname>DLL_IMPORTS</>
+ there. To link with a Winelib library, one uses <varname>DLL_IMPORTS</>.
The exception is for C++ libraries where you currently don't have
a choice but to link with them in the Unix sense. One library you are
likely to find here is <literal>mfc</>.
@@ -268,7 +268,7 @@ hello_exe_CXX_SRCS =
- The above variables list the sources that are used togenerate the
+ The above variables list the sources that are used to generate the
target. Each section will start with a comment indicating the name of
the target. Then come a series of variables prefixed with the name of
that target. Note that the name of the prefix may be slightly
@@ -427,7 +427,7 @@ WRCFLAGS = -r -L
- In Windows applications and libraries contain some
+ In Windows, applications and libraries contain some
information which are necessary to make APIs such as
<function>GetProcAddress</function> work. So it is necessary to
duplicate these data structures in the Unix world to make these
@@ -724,7 +724,7 @@ ORDINAL extern EXPORTNAME SYMBOLNAME
Winelib, you should first try to link it to an executable (but you
would have done that to test it anyway, right?). At this point you
may discover some undefined symbols that you thought were implemented
- by the library. Then, you to the library sources and fix it. But you
+ by the library. Then, you go to the library sources and fix it. But you
may also discover that the missing symbols are defined in, say,
gdi32. This is because you did not link the said library with gdi32.
One way to fix it is to link this executable, and any other that also
@@ -733,7 +733,7 @@ ORDINAL extern EXPORTNAME SYMBOLNAME
As you will quickly notice, this has unfortunately not been
- (completely) done for Winelib's own libraries. So if an application
+ (completely) done for Winelib own libraries. So if an application
must link with ole32, you will also need to link with advapi32,
rpcrt4 and others even if you don't use them directly. This can be
annoying and hopefully will be fixed soon (feel free to submit a
More information about the wine-patches