WineHQ: Assorted spelling fixes
Francois Gouget
fgouget at free.fr
Wed Mar 24 08:21:15 CST 2004
This patch includes some parts that I submitted before but which
coudlnt' be applied because the patch was partly corrupted. Sorry about
that :-(
Changelog:
* wwn/wn20011102_107.xml
wwn/wn20020719_129.xml
wwn/wn20021025_141.xml
wwn/wn20021101_142.xml
wwn/wn20030509_169.xml
wwn/wn20040213_210.xml
wwn/wn20040220_211.xml
wwn/wn20040227_212.xml
wwn/wn20040305_213.xml
wwn/wn20040312_214.xml
wwn/wn20040319_215.xml
Assorted spelling, case fixes, etc.
--
Francois Gouget fgouget at free.fr http://fgouget.free.fr/
Avoid the Gates of Hell - use Linux.
-------------- next part --------------
Index: wwn/wn20011102_107.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20011102_107.xml,v
retrieving revision 1.5
diff -u -r1.5 wn20011102_107.xml
--- a/wwn/wn20011102_107.xml 16 Dec 2003 17:09:27 -0000 1.5
+++ b/wwn/wn20011102_107.xml 24 Mar 2004 10:44:40 -0000
@@ -232,7 +232,7 @@
how hard will it be to make it working under Linux without
rewriting it all.
</p><p>
- I belive I have the sources for complete OWL of course.
+ I believe I have the sources for complete OWL of course.
</p><p>
Q2: With You expirience what would You say to that statment:
If my OWL-based program works under Wine it should be convertable
Index: wwn/wn20020719_129.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20020719_129.xml,v
retrieving revision 1.5
diff -u -r1.5 wn20020719_129.xml
--- a/wwn/wn20020719_129.xml 16 Dec 2003 17:09:27 -0000 1.5
+++ b/wwn/wn20020719_129.xml 10 Feb 2004 17:42:27 -0000
@@ -170,7 +170,7 @@
the entire file API. His work should be available in two weeks or so.
</p><p>
The blocker for #1 is to convince Alexandre that NT really deals with
-pathes the way my patch does... which involves writing some test
+paths the way my patch does... which involves writing some test
programs on NT. We need to understand the NtQueryDirectoryFile function
in more detail to do this.
</p></quote>
Index: wwn/wn20021025_141.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20021025_141.xml,v
retrieving revision 1.9
diff -u -r1.9 wn20021025_141.xml
--- a/wwn/wn20021025_141.xml 16 Dec 2003 17:09:27 -0000 1.9
+++ b/wwn/wn20021025_141.xml 10 Mar 2004 22:48:15 -0000
@@ -412,7 +412,7 @@
<p>
This code was audited for completeness against the documented features
of Comctl32.dll version 6.0 on Oct. 21, 2002, by Christian Neumair.
-Unless otherwise noted, we belive this code to be complete, as per
+Unless otherwise noted, we believe this code to be complete, as per
the specification mentioned above.
If you discover missing features, or bugs, please note them below.
</p><p>
Index: wwn/wn20021101_142.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20021101_142.xml,v
retrieving revision 1.7
diff -u -r1.7 wn20021101_142.xml
--- a/wwn/wn20021101_142.xml 16 Dec 2003 17:09:27 -0000 1.7
+++ b/wwn/wn20021101_142.xml 10 Mar 2004 01:08:52 -0000
@@ -523,7 +523,7 @@
In just a few embedded bytes in the code it could remove your home directory
in a single syscall. Would you expect that? - I wouldnt.
</p><p>
-Cant we atleast try implement some protection in wine against these attacks,
+Can't we at least try implement some protection in wine against these attacks,
before something really nasty happens. I do think company policy decissions
againt using wine, will do just as much damage to the wine movement as too
the free software movement at large.
Index: wwn/wn20030509_169.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20030509_169.xml,v
retrieving revision 1.4
diff -u -r1.4 wn20030509_169.xml
--- a/wwn/wn20030509_169.xml 16 Dec 2003 17:09:27 -0000 1.4
+++ b/wwn/wn20030509_169.xml 10 Mar 2004 01:09:02 -0000
@@ -264,7 +264,7 @@
<section
title="Broken flex"
- subject="Cant compile wine.. CVS or release."
+ subject="Can't compile wine.. CVS or release."
archive="http://www.winehq.org/hypermail/wine-devel/2003/04/0014.html"
posts="5"
startdate="05/01/2003"
Index: wwn/wn20040213_210.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040213_210.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20040213_210.xml
--- a/wwn/wn20040213_210.xml 14 Feb 2004 22:07:49 -0000 1.1
+++ b/wwn/wn20040213_210.xml 16 Feb 2004 02:05:44 -0000
@@ -124,7 +124,7 @@
Linux-isms: exec shield and prelinking.
<a href="http://lwn.net/Articles/31032/">Exec shield</a> is a security
mechanism to prevent overflows from being exploited. It relies on
-changing the memory layout of an executable.. unfortunately Wine
+changing the memory layout of an executable... unfortunately Wine
requires a very particular layout.
<a href="http://www.crast.us/james/articles/prelink.php">Prelinking</a>
is a method to speed up application startup time by having a preferred
@@ -343,7 +343,7 @@
</p><p>
Here are the list of icons:
(Please note that to get these you'll need to build wine. These
-resources are not includes "as is" in the code, rather they are
+resources are not included "as is" in the code, rather they are
hex encoded as text in resource files (.rc). The build process
extracts them from there into the files listed below, via a tool
of ours (tools/bin2res). If you modify these extracted files,
@@ -484,7 +484,7 @@
<p>Anyone wanting to help Terry may want to contact him,
his email address is on his
-<a href="http://www.winehq.org/hypermail/wine-devel/2004/02/0174.html">original post</a>
+<a href="http://www.winehq.org/hypermail/wine-devel/2004/02/0174.html">original post</a>.
</p>
</section>
Index: wwn/wn20040220_211.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040220_211.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20040220_211.xml
--- a/wwn/wn20040220_211.xml 20 Feb 2004 06:22:40 -0000 1.1
+++ b/wwn/wn20040220_211.xml 10 Mar 2004 00:54:34 -0000
@@ -102,12 +102,12 @@
<p>Some newsworthy items came out of TransGaming this week.
The biggest story is the release of WineX 3.3:</p>
-<quote who="Transgaming"><p>
+<quote who="TransGaming"><p>
The majority of the technical improvements in WineX 3.3 have been
driven by the implementation of support of Steam. Support for its
online games has resulted in improved socket and pipe support as well
as a major enhancement to font support. In addition to Steam, this
-release contains copyprotection enhancements and support for Dark Age
+release contains copy protection enhancements and support for Dark Age
Of Camelot as well some success in making a number of other titles
functional with workarounds, although not yet to a point where we can
say that they are supported. You will find some of these titles
@@ -167,7 +167,7 @@
<p>Kevin Koltzau is making progress on adding theming to Wine.
In a patch on Sunday he remarked,
<quote who="Kevin Koltzau">
-With this some apps may start looking partly themed (eg. the toolbar buttons
+With this some apps may start looking partly themed (e.g. the toolbar buttons
in newer versions of mIRC are themed), and we can start adding theming code
to widgets</quote></p>
@@ -298,7 +298,7 @@
apart in its directory while also creating summary.txt. If an error
occurs the directory is renamed to errXXXXX to avoid future attempts
at processing this report. If everything goes flawlessly the whole
-directory is renamed (based on the information learned in the process)
+directory is renamed (based on the information learnt in the process)
to $datadir/BUILD/VERSION_TAG_DIGIT where DIGIT is for resolving name
clashes and $datadir/BUILD/outdated is created to signal the change in
the given build. Allowed builds are those in $builds. See also the
@@ -308,7 +308,7 @@
<li> gather
<ul>
This program is intended to run as a second stage. See the sample
-crontab file, races and concurrency problems must be dealed with on
+crontab file, races and concurrency problems must be dealt with on
that higher level. The program looks for a file matching
$datadir/*/outdated, creates index.html in the same directory and
removes the outdated file. See also the head of the file.
@@ -337,7 +337,7 @@
<topic>Patches</topic>
<p>Marcus spent some time this week getting Windows kernel
drivers loading. Specifically, he tried to get SafeDisc working
-so that copy protection on games would be support. This was
+so that copy protection on games would be supported. This was
discussed a bit at WineConf and various ideas were kicked
around. SafeDisc isn't working yet, and it's not even clear
it's possible to support it, but Marcus took a stab at it.
@@ -355,9 +355,9 @@
Added a possibility to load Windows WDM kernel drivers,
a bit hackish.
<br />
- Implemented a seperate PE loader for WDMs, but reuse
+ Implemented a separate PE loader for WDMs, but reuse
common functionality from normal PE loader (relocation
- fixup, relayhandling, module override.) Uses NtLoadDriver.
+ fixup, relay handling, module override.) Uses NtLoadDriver.
<br />
Implemented DeviceIoControl passing to kernel drivers.
</ul></p></quote>
@@ -453,7 +453,7 @@
Here is a first pass at replacing winedefault.reg with a windows inf file and
dll registration. The registry entries in the inf file are not complete.
Other than quite a few missed entries I've also left out the keys for
-Codepages and the Country List entries as these are pretty large(lots of
+Codepages and the Country List entries as these are pretty large (lots of
typing, I'm lazy).
</p><p>
setupregistry is a shell script that registers dlls with regsvr32 and then
Index: wwn/wn20040227_212.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040227_212.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20040227_212.xml
--- a/wwn/wn20040227_212.xml 27 Feb 2004 08:51:37 -0000 1.1
+++ b/wwn/wn20040227_212.xml 10 Mar 2004 00:58:49 -0000
@@ -93,7 +93,7 @@
<p>Later he reported on cross-compiling all of Wine:</p>
<quote who="Hans Leidekker"><p>
-I spent some time cross compiling all of Wine with MinGW according
+I spent some time cross-compiling all of Wine with MinGW according
to this recipe:
<ul> <a href="http://winehq.com/?issue=123#Cross-compiling%20Wine">
http://winehq.com/?issue=123#Cross-compiling Wine</a></ul></p><p>
@@ -186,7 +186,7 @@
enddate="02/26/2004"
>
<topic>Multimedia</topic>
-<p>Yorick Hardy created a sounddriver for NetBSD:</p>
+<p>Yorick Hardy created a sound driver for NetBSD:</p>
<quote who="Yorick Hardy"><p>
This patch adds the audio driver winenbsd using the native NetBSD
audio system as an alternative to OSS. On the one hand
Index: wwn/wn20040305_213.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040305_213.xml,v
retrieving revision 1.2
diff -u -r1.2 wn20040305_213.xml
--- a/wwn/wn20040305_213.xml 7 Mar 2004 00:15:17 -0000 1.2
+++ b/wwn/wn20040305_213.xml 10 Mar 2004 01:07:39 -0000
@@ -158,7 +158,7 @@
Wine. Their addition is also nicely compartmentalized. Miguel de Icaza
hoped it would get integrated,
<quote who="Miguel de Icaza">We are running some SWF applications now
-with Mono and this patch; And we are fairly happy, since its a small
+with Mono and this patch; And we are fairly happy, since it's a small
patch to maintain this time. Of course, it would be best to make it
part of Wine, so the user does not need two separate Wine installations.
</quote></p>
@@ -185,17 +185,17 @@
so far.
</p><p>
I was thinking the other day that ReactOS and WINE/Linux might get a
-big boost if we can push support in the embedded enviroment so I
+big boost if we can push support in the embedded environment so I
started taking a look at WinCE and Microsoft Embedded Visual C++ 4.0
-.BTW: Its a free download now.
+.BTW: It's a free download now.
<a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=1dacdb3d-50d1-41b2-a107-fa75ae960856&DisplayLang=en">
http://www.microsoft.com/downloads/details.aspx?FamilyID=1dacdb3d-50d1-41b2-a107-fa75ae960856&DisplayLang=en</a>
</p><p>
I started looking at WinCE and thought it would be nice if we could be
source compatible with WinCE apps and binary compatbile on x86. Well it
-seems that WinCE apps dont differ much from standard Win32 apps execpt
-the subsystem ID is differnt. If you attempt to run a WinCE application
-on Windows it will say that its not able to run. Ok no problem, we just
+seems that WinCE apps don't differ much from standard Win32 apps except
+the subsystem ID is different. If you attempt to run a WinCE application
+on Windows it will say that it's not able to run. Ok no problem, we just
run "editbin /subsystem:windows blah.exe" and check it out. Now the app
is looking for coredll.dll. No problem there I have created a stub
coredll.dll that just forwards all calls to the proper Win32 dlls such
@@ -205,13 +205,13 @@
soon then I go and run the same test on ReactOS but this time I run a
copy of messagebox without changing the subsystem ID...Hey what do you
know. It works =). I talked with Alexandre about it a bit and he said
-that WINE like ReactOS also shouldnt care about the subsystem ID so if
+that WINE like ReactOS also shouldn't care about the subsystem ID so if
someone is interested in testing just drop the messagebox programs and
coredll.dll in to a directory and give it a shot.
</p><p>
I am having trouble getting more complex apps (hello world) to work atm
so I think i am just going to take a break and clear my head for a few
-days. Some of the WinCE API and Win32 is not 100% compatible so we cant
+days. Some of the WinCE API and Win32 is not 100% compatible so we can't
just forward all parts to the Win32 implementation but I think we can
do it for most of it. If anyone is interested in helping out the source
is in the ROS CVS tree and attached to this email......
Index: wwn/wn20040312_214.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040312_214.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20040312_214.xml
--- a/wwn/wn20040312_214.xml 13 Mar 2004 07:40:34 -0000 1.1
+++ b/wwn/wn20040312_214.xml 24 Mar 2004 13:41:07 -0000
@@ -92,7 +92,7 @@
been implemented yet.
</p>
-<p>Vincent Béron pointed out that RedHat RPM's wouldn't
+<p>Vincent Béron pointed out that RedHat RPMs wouldn't
be available for a few days. Otherwise,
<a href="http://www.winehq.org/site/download">go download it</a>.
</p>
@@ -224,7 +224,7 @@
libraries. The general solution right now is to make
a Winelib program that does it. Writing a Winelib program
is a bit of overhead though. Most people would just like
-to dynamically load the library and rsuh off to use the
+to dynamically load the library and rush off to use the
API. Boaz Harrosh wondered how general of a solution this
was and Mike Hearn replied with some of the deficiencies of
the approach:</p>
@@ -246,7 +246,7 @@
and call a method in there to have Wine initialize itself. After this
you can call the API as a library.
</p><p>
-Now, this might not be as helpful to others as you might thinkg, unless
+Now, this might not be as helpful to others as you might think, unless
they dlopen/dlsym every symbol they want to import (this is what we do
with Mono: every symbol we need has to be explicitly invoked).
</p><p>
@@ -409,7 +409,7 @@
<p>A lot of Wine options are being moved into environment variables -
DLL overrides have been gone for a while and debug messages are next.
Mike Hearn posted a small script to allow changing the options on the
-commandline easier. If you call the script "vino" as Mike suggested,
+commandline more easily. If you call the script "vino" as Mike suggested,
you can invoke it with "vino +relay ole32=n [program.exe]" for example.
The script:</p>
<quote who="Mike Hearn"><p>
Index: wwn/wn20040319_215.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040319_215.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20040319_215.xml
--- a/wwn/wn20040319_215.xml 19 Mar 2004 00:27:39 -0000 1.1
+++ b/wwn/wn20040319_215.xml 24 Mar 2004 13:58:24 -0000
@@ -72,7 +72,7 @@
developed and latency issues in games such as <i>Medal of Honor:
Allied Assault</i> have been fixed. The top ranked technology
items in February were:</p>
-<quote who="Transgaming"><p>
+<quote who="TransGaming"><p>
<ul>
<li> Improved ALSA Support</li>
<li> DirectX 9</li>
@@ -122,7 +122,7 @@
<quote who="Mike Hearn"><p>
Perhaps Wine should start considering a kernel-like approach with some
developers having their own trees where some experimental patches are
-tried out first then percolate up to Alexandres tree?
+tried out first then percolate up to Alexandre's tree?
</p><p>
Another thing I'd really like to see is a move to GNU arch version control
- it makes distributed development and branching a *lot* easier. I
@@ -171,7 +171,7 @@
</p></quote>
<p>This led Mike to put together a really nice list of things
-that arch could for Wine and how development could be improved.
+that arch could do for Wine and how development could be improved.
Some of the tools Dimi wanted replacements for already exist:</p>
<quote who="Mike Hearn"><p>
@@ -185,9 +185,9 @@
fundamentally different way to CVS - it's based on applying changesets
in order rather than keeping track of HEAD and working backwards.
</p><p>
-ie running <tt>tla get wine</tt> or whatever actually downloads the first
+i.e. running <tt>tla get wine</tt> or whatever actually downloads the first
checkin then all the patches and applies them in turn. Obviously that's
-too slow for most projects so you can stow cached revisions (ie tree
+too slow for most projects so you can stow cached revisions (i.e. tree
snapshots) along the way so it only downloads the last revision then
works from there. That only occurs on initial checkout of course.
</p><p>
@@ -214,19 +214,19 @@
</p><p>
<u>OK, so why should we use arch?</u></p><p>
-Wine is a project that operates similar to the Linux kernel. There is a
+Wine is a project that operates similarly to the Linux kernel. There is a
benign dictator, who controls CVS. We all grab CVS, hack in our own
branches, separate the changes out into a patch and email it to
wine-patches. Normally, if we got it right, Alexandre will check it in
forming a logical changeset, and we then all run cvs update which
-downloads everyones changes.
+downloads everyone's changes.
</p><p>
This works OK but has a number of disadvantages:
<dl>
<dt> No branches. </dt>
<dd>Some Wine work would be best done in parallel to the main tree. For
-instance, the filesystem work, the WM rewrite etc. Wines current modus
+instance, the filesystem work, the WM rewrite etc. Wine's current modus
operandi makes this very hard, as effectively CVS HEAD must be at least
dogfoodable at all times. This also makes it hard to do R&D projects
like the shared memory wineserver while keeping the results of that R&D
@@ -237,7 +237,7 @@
working on Wine. Sometimes because those patches are incomplete or
wrong, sometimes because they get forgotten or missed, sometimes because
Alexandre doesn't agree that the code belongs in the main Wine tree
-(things like the system tray patch, delayed debug tracing patch etc
+(things like the system tray patch, delayed debug tracing patch, etc
spring to mind).
<br />
Over time, a particular checkout of wine will accumulate debugging
@@ -392,7 +392,7 @@
and some PHP skills is welcome to help improve it.
</p><p>
The tree has not been touched in over a year. I did some work to clean
-it up for this import, and thats about it. I will be available to answer
+it up for this import, and that's about it. I will be available to answer
any questions on it.
</p><p>
Check it out:
@@ -477,13 +477,13 @@
Is there a reason rundll32 needs user32 and cannot delayimport it?
</p></quote>
-<p>Ove åven had a workaround for using the console driver, ttydrv,
+<p>Ove Kåven had a workaround for using the console driver, ttydrv,
instead of X:</p>
<quote who="Ove Kaaven"><p>
You're not going to gain anything by letting rundll32 not import user32,
because it has to load all the dlls it's telling to self-register
anyway, and many of them will import user32 themselves even if rundll32
-don't.
+doesn't.
</p><p>
In my debian packages I go the ttydrv route, with the
<a href="http://www.winehq.org/hypermail/wine-devel/2004/03/0298.html">following
More information about the wine-patches
mailing list