Jeremy, here's the usual spelling fixes.
Also I noticed that the following files are in DOS format, i.e. with
CR/LF pairs instead of single LFs. Since that was causing us problems
with patching, could you convert them to Unix format?
wwn/wn20010621_98.xml
wwn/wn20010706_99.xml
wwn/wn20010816_102.xml
Then I'll send a couple more spelling fixes with the next batch.
Changelog:
* wwn/wn20001211_73.xml,
wwn/wn20010219_83.xml,
wwn/wn20010611_97.xml,
wwn/wn20031024_193.xml,
wwn/wn20031031_194.xml
Assorted spelling fixes.
--
Francois Gouget fgouget@xxxxxxx http://fgouget.free.fr/
Hiroshima '45 - Czernobyl '86 - Windows '95Index: wwn/wn20001211_73.xml
===================================================================
RCS file: /home/cvs/lostwages/wwn/wn20001211_73.xml,v
retrieving revision 1.4
diff -u -r1.4 wn20001211_73.xml
--- wwn/wn20001211_73.xml 4 Sep 2003 15:39:16 -0000 1.4
+++ wwn/wn20001211_73.xml 7 Nov 2003 16:24:53 -0000
@@ -153,7 +153,7 @@
<p />
-If you're currently writting a thesis on computer idiomatics
+If you're currently writing a thesis on computer idiomatics
semantics, you may be interested in reading the details. Since the
editorial team doesn't target those people as their primary audience,
details will not be covered.</section>
@@ -194,7 +194,7 @@
<p />
-A few days later, Martin had finished writting the first pass of the
+A few days later, Martin had finished writing the first pass of the
code and was starting the test phase. No patch has been submitted yet,
nor improvments figures have been provided.</section>
Index: wwn/wn20010219_83.xml
===================================================================
RCS file: /home/cvs/lostwages/wwn/wn20010219_83.xml,v
retrieving revision 1.2
diff -u -r1.2 wn20010219_83.xml
--- wwn/wn20010219_83.xml 18 Jul 2003 20:50:50 -0000 1.2
+++ wwn/wn20010219_83.xml 7 Nov 2003 16:25:10 -0000
@@ -94,7 +94,7 @@
a index/data pair of files for mail folders ). Also when I try send
email to locate users the mail does not get sent for read/write
errors. This is because local mail delivery is done by the client
-program, by writting into the users maildir. How this is done is under
+program, by writing into the users maildir. How this is done is under
novel you can Create files in directories that you cannot see (if that
permission is granted to you). But you can't do this under unix. So the
need to implement file i/o for novell files arises.</quote>
Index: wwn/wn20010611_97.xml
===================================================================
RCS file: /home/cvs/lostwages/wwn/wn20010611_97.xml,v
retrieving revision 1.8
diff -u -r1.8 wn20010611_97.xml
--- wwn/wn20010611_97.xml 27 Oct 2003 14:36:08 -0000 1.8
+++ wwn/wn20010611_97.xml 7 Nov 2003 16:25:17 -0000
@@ -259,7 +259,7 @@
<p>That said regardless of how good the Stanford checker really
will be I'm pretty there will be a lot of things that
-will be _much_ easier checked by writting a script
+will be _much_ easier checked by writing a script
for the Stanford checker than by extending winapi_check,
because they have fundamentally different design
philosofies.</p>
Index: wwn/wn20031024_193.xml
===================================================================
RCS file: /home/cvs/lostwages/wwn/wn20031024_193.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20031024_193.xml
--- wwn/wn20031024_193.xml 27 Oct 2003 14:31:46 -0000 1.1
+++ wwn/wn20031024_193.xml 28 Oct 2003 02:32:25 -0000
@@ -241,7 +241,7 @@
and integrating it into the current site is dead easy.</quote></p>
<p>
Concerning the ability to comment on a news story, Jeremy thought
-of an simple way to do that,
+of a simple way to do that,
<quote who="Jeremy Newman">
Exactly, whenever a news post, or new WWN, or Wine version is posted, I
can start a new thread in the forum, and link to that thread from the
Index: wwn/wn20031031_194.xml
===================================================================
RCS file: /home/cvs/lostwages/wwn/wn20031031_194.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20031031_194.xml
--- wwn/wn20031031_194.xml 31 Oct 2003 15:36:17 -0000 1.1
+++ wwn/wn20031031_194.xml 7 Nov 2003 15:41:16 -0000
@@ -81,7 +81,7 @@
<topic>News</topic>
<p>CodeWeavers rolled out an updated CrossOver Office this week adding
support for Macromedia products:</p>
-<quote who="Codeweavers"><p>
+<quote who="CodeWeavers"><p>
"Now, with additional support for Macromedia Dreamweaver MX and Flash MX,
combined with our existing support for Adobe Photoshop, CrossOver Office 2.1
gives web developers and design firms the first Linux solution for their
@@ -109,9 +109,9 @@
designed to run on Windows, and only Windows. ...
we were able to run -- albeit not completely-- POPassist on
SuSE Linux Desktop with the help of CrossOver Office. The
-only glitch comes in actually fiding the POPnetserver. That
-function would not work, which left us manually inputting
-the new address e discovered with LiSA and My Network Places."</ul></p>
+only glitch comes in actually finding the POPnetserver. That
+function would not work, which left us manually inputing
+the new address e-discovered with LiSA and My Network Places."</ul></p>
</quote>
@@ -132,7 +132,7 @@
<a href="http://sourceforge.net/project/showfiles.php?group_id=6241";>
http://sourceforge.net/project/showfiles.php?group_id=6241</a></ul></p><p>
This new version contains an updated winedefault.reg, you don't need to run
-regedit winedefault.reg any more, and it's updated to configurate all the
+regedit winedefault.reg any more, and it's updated to configure all the
latest and greatest features of wine.
</p><p>
This release was possible thanks to the help and contributions of
@@ -197,14 +197,14 @@
</p></quote>
</section>
<section
- title="Installshield 7 Notes"
- subject="Installshield7 notes"
+ title="InstallShield 7 Notes"
+ subject="InstallShield7 Notes"
archive="http://www.winehq.com/hypermail/wine-devel/2003/10/0866.html";
posts="2"
startdate="10/29/2003"
>
<topic>Fixes</topic>
-<p>Carlos Lozano shared some info concerning apps using Installshield 7:</p>
+<p>Carlos Lozano shared some info concerning apps using InstallShield 7:</p>
<quote who="Carlos Lozano"><p>
Here goes some notes about how to install installshield 7 programs
with the actual wine releases (sorry, i haven't been able to install
@@ -232,7 +232,7 @@
I have found some programs, what give problems with Desktop mode,
exiting during install with X11 errors (Praetoriams demo for example).
In this cases you can use yet another trick. Disable Desktop, and
-enable "Managed" = "Y", then in the file the file "dlls/x11drv/window.c",
+enable "Managed" = "Y", then in the file "dlls/x11drv/window.c",
you will find the function "inline static BOOL is_window_managed( WND *win )",
in the end of this function, there are this 3 lines:
<ul><code>
@@ -262,7 +262,7 @@
<topic>Internationalization</topic>
<p>Sylvain Petreolle mentioned that although his keyboard works
fine in Wine there seems to be problems detecting it. Dmitry
-Timoshkov explained someone of the issues:</p>
+Timoshkov explained some of the issues:</p>
<quote who="Dmitry Timoshkov"><p>
I think that this topic was explained many times already.
Anyway, here is yet another attempt.
@@ -305,7 +305,7 @@
I have thought of two ways for Wine to do that - either it checks what
name the symbol files is loaded as, or it scans the keymap (as it does
today). Either way - it will have to have some mapping between currently
-loaded keymap and language. Hence the affect it has over X keyboard
+loaded keymap and language. Hence the effect it has over X keyboard
detection.
</p></quote>
<p>Dmitry wondered how that info could be queried from X. Shachar
@@ -318,11 +318,11 @@
<li> Use the XKB name</li></ol></p><p>
2 will mean that we reduce the keyboard source to a table of names, and
-their respective language IDs. I.e - "us" means English, "fr" means
+their respective language IDs. I.e. - "us" means English, "fr" means
French, "he" means Hebrew etc. This will probably make adding new
keyboard easier (and less error prone), but will ONLY work on XKB. Then
again, keyboard selection (also part of the currently missing APIs) will
-only work on XKB anyways, so wer'e probably going to have to soft-depend
+only work on XKB anyways, so we're probably going to have to soft-depend
on XKB whatever we do.</p></quote>
