Changelog:
* wwn/wn19990914_8.xml,
wwn/wn19990927_10.xml,
wwn/wn20000424_40.xml,
wwn/wn20001211_73.xml,
wwn/wn20010718_100.xml,
wwn/wn20030718_179.xml,
wwn/wn20030725_180.xml,
wwn/wn20030801_181.xml,
wwn/wn20030808_182.xml,
wwn/wn20030822_184.xml
Fix various spelling errors.
--
Francois Gouget fgouget@free.fr http://fgouget.free.fr/
"Only wimps use tape backup: _real_ men just upload their important stuff on
ftp, and let the rest of the world mirror it ;)" -- Linus Torvalds
Index: wwn/wn19990914_8.xml
===================================================================
RCS file: /home/wine/lostwages/wwn/wn19990914_8.xml,v
retrieving revision 1.3
diff -u -r1.3 wn19990914_8.xml
--- wwn/wn19990914_8.xml 25 Jul 2003 18:45:03 -0000 1.3
+++ wwn/wn19990914_8.xml 30 Aug 2003 13:13:59 -0000
@@ -95,7 +95,7 @@
</ul>
-<li />use of the new glGetProcAddressEXT function to conditionnaly use
+<li />use of the new glGetProcAddressEXT function to conditionally use
extensions:
<ul>
Index: wwn/wn19990927_10.xml
===================================================================
RCS file: /home/wine/lostwages/wwn/wn19990927_10.xml,v
retrieving revision 1.3
diff -u -r1.3 wn19990927_10.xml
--- wwn/wn19990927_10.xml 25 Jul 2003 18:45:03 -0000 1.3
+++ wwn/wn19990927_10.xml 30 Aug 2003 13:14:00 -0000
@@ -34,7 +34,7 @@
<p />
-Some changes also occured with version handling (of .EXE and .DLL); if
+Some changes also occurred with version handling (of .EXE and .DLL); if
you encounter error messages regarding version handling, try to run
wine with the -winver XX option (XX being win31, win95, win98, nt35,
nt40), it helps in some cases.
Index: wwn/wn20000424_40.xml
===================================================================
RCS file: /home/wine/lostwages/wwn/wn20000424_40.xml,v
retrieving revision 1.2
diff -u -r1.2 wn20000424_40.xml
--- wwn/wn20000424_40.xml 18 Jul 2003 20:50:50 -0000 1.2
+++ wwn/wn20000424_40.xml 30 Aug 2003 13:14:00 -0000
@@ -44,7 +44,7 @@
<p />
It turns out that after the very good news from last weeks, evilish
-events came down on us: very low trafic on mailing list (may be
+events came down on us: very low traffic on mailing list (may be
sometimes developers take some rest), master WineHQ server (the one
holding the master information) has been down most of the week, slave
WineHQ server (the one you usually access) also had its moment for
Index: wwn/wn20001211_73.xml
===================================================================
RCS file: /home/wine/lostwages/wwn/wn20001211_73.xml,v
retrieving revision 1.3
diff -u -r1.3 wn20001211_73.xml
--- wwn/wn20001211_73.xml 18 Jul 2003 20:50:50 -0000 1.3
+++ wwn/wn20001211_73.xml 30 Aug 2003 13:14:00 -0000
@@ -304,7 +304,7 @@
that I could be sure was preserved across library calls, and even
consulted Stan Shebs (one of the gcc PPC developers). I couldn't find
anything that seemed appropriate in time, so I just gave up. I have no
-recollection whether using pthreads' local storage even occured to me
+recollection whether using pthreads' local storage even occurred to me
then.
</quote>
Index: wwn/wn20010718_100.xml
===================================================================
RCS file: /home/wine/lostwages/wwn/wn20010718_100.xml,v
retrieving revision 1.2
diff -u -r1.2 wn20010718_100.xml
--- wwn/wn20010718_100.xml 12 Jun 2003 20:48:20 -0000 1.2
+++ wwn/wn20010718_100.xml 30 Aug 2003 13:14:04 -0000
@@ -353,7 +353,7 @@
<p>Lionel Ulmer replied:</p>
<quote who="Lionel Ulmer"><p>
-My first question was : why implement it ? I would personnaly find VERY
+My first question was : why implement it ? I would personally find VERY
annoying to have any Windows app. change the size of my desktop window when
I prefer running my applications 'windowed'.</p>
Index: wwn/wn20030718_179.xml
===================================================================
RCS file: /home/wine/lostwages/wwn/wn20030718_179.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20030718_179.xml
--- wwn/wn20030718_179.xml 18 Jul 2003 20:45:48 -0000 1.1
+++ wwn/wn20030718_179.xml 30 Aug 2003 13:14:24 -0000
@@ -6,7 +6,7 @@
<author contact="http://www.theshell.com/~vinn";>Brian Vincent</author>
<issue num="179" date="07/18/2003" />
<intro> <p>This is the 179th release of the weekly Wine Weekly News publication.
-It's main goal is to ponder why I never knew I there was a real gold mine down the street from where I live. It also serves inform you of what's going on around Wine. You can find more info at <a href="http://www.winehq.com";>www.winehq.com</a></p> </intro>
+Its main goal is to ponder why I never knew there was a real gold mine down the street from where I live. It also serves to inform you of what's going on around Wine. You can find more info at <a href="http://www.winehq.com";>www.winehq.com</a></p> </intro>
<stats posts="198" size="649" contrib="64" multiples="35" lastweek="31">
<person posts="20" size="60" who="Mike Hearn" />
Index: wwn/wn20030725_180.xml
===================================================================
RCS file: /home/wine/lostwages/wwn/wn20030725_180.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20030725_180.xml
--- wwn/wn20030725_180.xml 25 Jul 2003 18:39:51 -0000 1.1
+++ wwn/wn20030725_180.xml 30 Aug 2003 13:14:24 -0000
@@ -6,7 +6,7 @@
<author contact="http://www.theshell.com/~vinn";>Brian Vincent</author>
<issue num="180" date="07/25/2003" />
<intro> <p>This is the 180th release of the weekly Wine Weekly News publication.
-Its main goal is to circumvent the proofreading process so that small grammatical errors will keep the reader attentive. It also serves inform you of what's going on around Wine. Wine is an open source implementation of the Windows API on top of X and Unix. Think of Wine as a Windows compatibility layer. Wine does not require Microsoft Windows, as it is a completely alternative implementation consisting of 100% Microsoft-free code, but it can optionally use native system DLLs if they are available. You can find more info at <a href="http://www.winehq.com";>www.winehq.com</a></p> </intro>
+Its main goal is to circumvent the proofreading process so that small grammatical errors will keep the reader attentive. It also serves to inform you of what's going on around Wine. Wine is an open source implementation of the Windows API on top of X and Unix. Think of Wine as a Windows compatibility layer. Wine does not require Microsoft Windows, as it is a completely alternative implementation consisting of 100% Microsoft-free code, but it can optionally use native system DLLs if they are available. You can find more info at <a href="http://www.winehq.com";>www.winehq.com</a></p> </intro>
<stats posts="240" size="771" contrib="52" multiples="34" lastweek="37">
<person posts="32" size="90" who="Mike Hearn" />
@@ -151,8 +151,8 @@
something and he posted his list asking for feedback:</p>
<quote who="Jonathon Wilson"><p>
After looking at all the things windows provides, I have identified the
-folowing possible programs that I could write for the wine project. Some of
-them are usefull for WINE itself and some of them might be usefull for (for
+following possible programs that I could write for the wine project. Some of
+them are useful for WINE itself and some of them might be useful for (for
example) ReactOS
</p><p>
Things:
@@ -161,33 +161,33 @@
PrintDlgEx and generally make comdlg32.dll behave more like the windows
counterpart (implement a few other things as well, like some of the
currently stubbed out items).</li>
-<li>work on wine notepad. Wont do this until the changes refered to before
+<li>work on wine notepad. Won't do this until the changes referred to before
are merged.</li>
<li>write a clone of fontview.exe (windows font sample viewer). This is
-probobly not usefull for WINE but might be usefull for ReactOS, plus it
+probably not useful for WINE but might be useful for ReactOS, plus it
would be a good excercise in windows GDI programming.</li>
<li>write clones of guidgen.exe and/or uuidgen.exe, 2 different windows SDK
tools for generating GUIDs/UUIDs. (if we are providing an IDL compiler and
-other such OLE-esque things, having a GUID/UUID generator is probobly a
+other such OLE-esque things, having a GUID/UUID generator is probably a
good thing to have, mainly it is just a stub around a call to CoCreateGUID</li>
<li>write a clone of rebase.exe, a win32 PE image rebasing tool. Probobly not
-usefull to WINE but might be helpfull for ReactOS development, dont know.</li>
+useful to WINE but might be helpfull for ReactOS development, don't know.</li>
<li>writing a clone of the cards.dll used by the windows card games. Only
-problem here is that I would need to find a sutably licenced set of card
-images since I dont have the skills to draw them myself :)</li>
+problem here is that I would need to find a suitably licenced set of card
+images since I don't have the skills to draw them myself :)</li>
<li>writing a clone of the card games (solitare,freecell etc) included with
windows to use said cards.dll (hey, we have WineMine...)</li>
-<li>writing a character map applet (basically a clone of charmap.exe). Dont
-know if WINE needs this but ReactOS probobly does (how else are you going
+<li>writing a character map applet (basically a clone of charmap.exe). Don't
+know if WINE needs this but ReactOS probably does (how else are you going
to insert all those fancy foreign language characters and dingbats? :)</li>
-<li>writing a calculaor app (i.e. a calc.exe clone), again dont know if WINE
+<li>writing a calculator app (i.e. a calc.exe clone), again don't know if WINE
needs one but ReactOS might...</li>
-<li>writing a clone of the Win32 volume control applet. Dont think WINE
+<li>writing a clone of the Win32 volume control applet. Don't think WINE
needs this (since the linux sound API has one already) but ReactOS might...</li>
</ol></p><p>
-Which of these should I work on? Which of these are usefull to
+Which of these should I work on? Which of these are useful to
Wine/ReactOS? Are any of these considered "a big beast" (as richedit was
-refered to by Dimitrie O. Paun?)
+referred to by Dimitrie O. Paun?)
</p></quote>
<p>A few people wrote in to discourage working on anything that
@@ -320,9 +320,9 @@
installer to work again correctly. It requires at least < 4.something,
otherwise it refuses to install. As our OLE framework isn't yet up to
scratch for some tasks, being able to install it is important (hopefully
-once I finish digesting Oves work maybe it will be less important).
+once I finish digesting Ove's work maybe it will be less important).
</p><p>
-I suppose we could make it every so slightly below the version DCOM98
+I suppose we could make it ever so slightly below the version DCOM98
requires, but there are only so many versions, and if an app checks for
the version shipped in the DCOM updates, it'd still be too low.
</p><p>
@@ -411,7 +411,7 @@
began running into obstacles. First he reported:</p>
<quote who="Steven Edwards"><p>
On just about every file that is built we are getting this warrning. This is the most minor
-problem we have with the alpha build but I couldnt figure it out.
+problem we have with the alpha build but I couldn't figure it out.
<ul><code>
../../include/wine/debug.h: In function `wine_dbgstr_guid':<br />
../../include/wine/debug.h:152: warning: cast from pointer to integer of different size<br />
@@ -451,10 +451,10 @@
<p>Steven wrote back with more details on the system,
<quote who="Steven Edwards">
-Its gcc on RH 7.1 for Alpha. On a Dec PWS 500 workstation. I dont know anything about Alpha asm so
+Its gcc on RH 7.1 for Alpha. On a Dec PWS 500 workstation. I don't know anything about Alpha asm so
I cannot implement the interlocked* functions or the import and spec support in winebuild so I
have just stubbed it for now. The other issues I am having is with compiling resources. WRC
-doesnot work proplerly on Alpha and I dont know why.</quote></p>
+does not work properly on Alpha and I don't know why.</quote></p>
<p>And in another email added,
<quote who="Steven Edwards">
Index: wwn/wn20030801_181.xml
===================================================================
RCS file: /home/wine/lostwages/wwn/wn20030801_181.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20030801_181.xml
--- wwn/wn20030801_181.xml 1 Aug 2003 15:27:07 -0000 1.1
+++ wwn/wn20030801_181.xml 30 Aug 2003 13:14:24 -0000
@@ -123,7 +123,7 @@
<p>Jeremy wasn't sure how well that would work:</p>
<quote who="Jeremy White"><p>
I'm told (and have been persuaded of this), that Wine's internal
-structures preclue a 'normal' profiler from working properly,
+structures preclude a 'normal' profiler from working properly,
hence the need for a Wine specific one.
</p><p>
I know we toyed with adapting gprof to Wine semantics, but
@@ -161,7 +161,7 @@
exception wine will start a debugger.
</p><p>
I sent some memory dumps to the developer of the security dll, and he
- said that it behaves like it was running under a debugger. He's
+ said that it behaves like it was running under a debugger. His
question was something like does wine have an always "on" debugger?
</p></quote>
@@ -204,7 +204,7 @@
Each sample contains the sourcecode, makefile and screenshots.
I will try to create these samples for each of the controls in SWF
</p><p>
- I will however make seperate projects for controls which use images,
+ I will however make separate projects for controls which use images,
because these don't seem to run on SWF yet. (For example a button with a
background image)
</p><p>
Index: wwn/wn20030808_182.xml
===================================================================
RCS file: /home/wine/lostwages/wwn/wn20030808_182.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20030808_182.xml
--- wwn/wn20030808_182.xml 12 Aug 2003 21:06:14 -0000 1.1
+++ wwn/wn20030808_182.xml 30 Aug 2003 13:14:25 -0000
@@ -93,7 +93,7 @@
<p>Interestingly enough, this release is 2.0.2 which alludes to
some beta versions receiving widespread testing.
Moving over to the LGPL codebase is a very significant change;
- perhaps its an indication a bunch of patches are on the way from
+ perhaps it's an indication a bunch of patches are on the way from
CodeWeavers.
Oh, and this release also has support for
<a href="http://www.codeweavers.com/products/crossover/embedded.php";>embedded
@@ -186,14 +186,14 @@
this work?
</p></quote>
-<p>Mike wrote back with more details on the MSI work and it's direction:</p>
+<p>Mike wrote back with more details on the MSI work and its direction:</p>
<quote who="Mike McCormack"><p>
The documentation for MSI is fairly incomplete. The file format was
mostly undocumented, but it looks like things get better as they get
more abstract ;)
</p><p>
Fortunately it seems fairly well structured. The database and installer
-parts are cleanly seperated from each other.
+parts are cleanly separated from each other.
</p><p>
The next steps are:
<ul>
@@ -223,8 +223,8 @@
<p>Greg thought maybe the code generated by the second parser
would be fine to include even if it wasn't portable
<quote who="Greg Turner">so long as the sources
- to regenerate them are available to those who have the right tools
-</quote>. </p>
+ to regenerate them are available to those who have the right tools.
+</quote> </p>
</section><section
title="Windows API DB"
@@ -357,7 +357,7 @@
which does silly things like jumping and not liking diagonals!
</p><p>
Therefore it is viewable (I started the tutorial and it all seems to display
-fine), but I wouldnt call it playable...
+fine), but I wouldn't call it playable...
</p><p>
Get on with the OLE/DCOM stuff instead :-)
</p></quote>
Index: wwn/wn20030822_184.xml
===================================================================
RCS file: /home/wine/lostwages/wwn/wn20030822_184.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20030822_184.xml
--- wwn/wn20030822_184.xml 22 Aug 2003 13:58:58 -0000 1.1
+++ wwn/wn20030822_184.xml 30 Aug 2003 13:14:25 -0000
@@ -332,7 +332,7 @@
(*) except files starting with a . which get the HIDDEN attribute</p>
</quote>
-<p>Robert North gave a pointer so some work being done at the
+<p>Robert North gave a pointer to some work being done at the
kernel filesystem level:</p>
<quote who="Robert North"><p>
Can't really answer your question,
