Changelog:
* wwn/wn19990718_4.xml,
wwn/wn19990905_7.xml,
wwn/wn20000117_26.xml,
wwn/wn20020807_131.xml,
wwn/wn20040109_204.xml
Assorted spelling fixes.
--
Francois Gouget fgouget@xxxxxxx http://fgouget.free.fr/
Dieu dit: "M-x Lumi\xE8re". Et la lumi\xE8re fut.Index: wwn/wn19990718_4.xml
===================================================================
RCS file: /home/cvs/lostwages/wwn/wn19990718_4.xml,v
retrieving revision 1.5
diff -u -r1.5 wn19990718_4.xml
--- wwn/wn19990718_4.xml 15 Dec 2003 15:30:17 -0000 1.5
+++ wwn/wn19990718_4.xml 10 Jan 2004 16:10:02 -0000
@@ -508,7 +508,7 @@
<p />
Patrik didn't think that tunneling through CRTDLL the existing libc
-functions is completly doable, especially when dealing with 64 bit
+functions is completely doable, especially when dealing with 64 bit
Unix platforms providing a 32 bit CRTDLL.
<p />
Index: wwn/wn19990905_7.xml
===================================================================
RCS file: /home/cvs/lostwages/wwn/wn19990905_7.xml,v
retrieving revision 1.2
diff -u -r1.2 wn19990905_7.xml
--- wwn/wn19990905_7.xml 18 Jul 2003 20:50:49 -0000 1.2
+++ wwn/wn19990905_7.xml 10 Jan 2004 16:10:11 -0000
@@ -133,7 +133,7 @@
Some more detailed discussions outlooked the modifications to be applied to
the build tool: Bertho did propose his dllglue code to generate export
tables, import tables and resource embedding (as well as NE & PE headers).
-This would actually completly replace build (which only provides export
+This would actually completely replace build (which only provides export
tables for now). His idea was to create a brand new tool (using lex & yacc
for better readability / maintenance) for elfdlls and only use build for the
soon obsolete built-in DLLs). Ulrich Weigand disagreed and was in favor of
Index: wwn/wn20000117_26.xml
===================================================================
RCS file: /home/cvs/lostwages/wwn/wn20000117_26.xml,v
retrieving revision 1.3
diff -u -r1.3 wn20000117_26.xml
--- wwn/wn20000117_26.xml 18 Jul 2003 20:50:50 -0000 1.3
+++ wwn/wn20000117_26.xml 10 Jan 2004 16:10:21 -0000
@@ -47,7 +47,7 @@
program he tried to make working using winelib. After some
investigations by Ulrich Weigand, it turned out that this program
has global objects whose constructors call into Windows APIs. While
-completly correct under Windows, this doesn't work under Wine.
+completely correct under Windows, this doesn't work under Wine.
<p />
Index: wwn/wn20020807_131.xml
===================================================================
RCS file: /home/cvs/lostwages/wwn/wn20020807_131.xml,v
retrieving revision 1.7
diff -u -r1.7 wn20020807_131.xml
--- wwn/wn20020807_131.xml 16 Dec 2003 17:09:27 -0000 1.7
+++ wwn/wn20020807_131.xml 10 Jan 2004 16:10:30 -0000
@@ -484,7 +484,7 @@
</p><p>
I compiled the wineserver under i386-solaris, and it runs. I do not have the
resources to compile ALL of wine under i386, or on any OS other than Solaris so
- the linux and BSD portions of this code are completly un-tested.
+ the linux and BSD portions of this code are completely un-tested.
</p><p>
ChangeLog:<br/>
Improved wineserver's handling of LWPs by following recommendations from
Index: wwn/wn20040109_204.xml
===================================================================
RCS file: /home/cvs/lostwages/wwn/wn20040109_204.xml,v
retrieving revision 1.2
diff -u -r1.2 wn20040109_204.xml
--- wwn/wn20040109_204.xml 9 Jan 2004 16:14:02 -0000 1.2
+++ wwn/wn20040109_204.xml 10 Jan 2004 16:25:34 -0000
@@ -95,7 +95,7 @@
Xandros 2.0 Deluxe</a> for OSNews.com. He briefly mentions the included
CrossOver products integrated into the system:</p>
<quote who="Barry Smith"><p>
-Codeweavers worked as expected. It ran MS Office and Adobe Photoshop and Paint Shop Pro quite well. Codeweavers did have the potentially annoying habit of trying to automatically install any and all Windows disks that you stuck into either drive, but such is life and the feature can easily be disabled. I call Codeweavers a neutral aspect as far as my use goes. But for someone who really needs to run a few specialized Windows programs, and who cannot or will not setup a dual boot system, this is a good alternative. </p></quote>
+CodeWeavers worked as expected. It ran MS Office and Adobe Photoshop and Paint Shop Pro quite well. CodeWeavers did have the potentially annoying habit of trying to automatically install any and all Windows disks that you stuck into either drive, but such is life and the feature can easily be disabled. I call CodeWeavers a neutral aspect as far as my use goes. But for someone who really needs to run a few specialized Windows programs, and who cannot or will not setup a dual boot system, this is a good alternative. </p></quote>
</section>
<section
@@ -122,7 +122,7 @@
<a href="http://perso.wanadoo.fr/pouech-eric/ep-file.diff.gz";>
http://perso.wanadoo.fr/pouech-eric/ep-file.diff.gz</a> (400 KB uncompressed)
</ul></p><p>
-It's not completly ready yet for inclusion, however some ongoing
+It's not completely ready yet for inclusion, however some ongoing
discussions could overlap with what I've currently done (like how to
configure drive without a config file, SMB handling...). So better
discuss it widely (yet another flame war).
@@ -152,7 +152,7 @@
UNIXCP code page)</li></ul>
</p><p>
-What still need some improvement
+What still needs some improvement
<ul>
<li> fix all the introduced bugs (even if all the current tests actually pass)</li>
<li> setting a first default environment (even if tools/winefs provides it -
@@ -441,7 +441,7 @@
<quote who="Chris Morgan">
Alexandre wanted winebrowser implemented as a winelib application and also to
be more easily configured. Here is the winebrowser winelib application. It
-uses a registry key(I'm not sure if this is the correct path for the key
+uses a registry key (I'm not sure if this is the correct path for the key
since I didn't see any other config keys in the registry) and creates a key
with the defaults if no key exists.
</quote></p>
@@ -505,16 +505,16 @@
I have broken it into 2 patches
</p><p>
wine_wintab.diff is all the wintab work except for the x11drv stuff
-wine_x11_wintab.diff is the changes to x11drv. the reason for this is
+wine_x11_wintab.diff is the changes to x11drv. The reason for this is
because i still have the ime patch that i submitted earlier in my wine
tree so i had to had edit that x11 patch to try to make it not dependent
on the xim stuff being already applied. This make there a chance that
there are bits that may not apply cleanly, and if you are committing
-both of my patches (xim and this) then they wont apply cleanly without a
+both of my patches (xim and this) then they won't apply cleanly without a
bit of fudging.
</p><p>
I am also giving you 2 test applications i used for wintab testing.
-SYSPRESS.EXE and TILTTEST.EXE These applications helped alot on testing
+SYSPRESS.EXE and TILTTEST.EXE These applications helped a lot on testing
things. They where found on the wacom developers site, i think i still
have the source kicking around somewhere.
</p><p>
