WineHQ: Assorted spelling fixes
Francois Gouget
fgouget at free.fr
Tue Oct 5 09:43:28 CDT 2004
Changelog:
* templates/404.template
wwn/wn20001106_68.xml
wwn/wn20001211_73.xml
wwn/wn20020613_126.xml
wwn/wn20020906_134.xml
wwn/wn20030829_185.xml
wwn/wn20040917_240.xml
wwn/wn20040924_241.xml
wwn/wn20041001_242.xml
Assorted spelling fixes.
--
Francois Gouget fgouget at free.fr http://fgouget.free.fr/
145 = 1! + 4! + 5!
-------------- next part --------------
Index: templates/404.template
===================================================================
RCS file: /var/cvs/lostwages/templates/404.template,v
retrieving revision 1.3
diff -u -r1.3 404.template
--- templates/404.template 4 Oct 2004 14:34:38 -0000 1.3
+++ templates/404.template 5 Oct 2004 13:26:12 -0000
@@ -13,8 +13,8 @@
<p><img src="{$root}/images/grey_pixel.gif" width="100%" height="1" alt=""></p>
<p>
- If you followed a link from a Winehq.org page and reached this page in error,
- please report it to the Winehq.org
+ If you followed a link from a WineHQ.org page and reached this page in error,
+ please report it to the WineHQ.org
<a href="http://bugs.winehq.org/enter_bug.cgi?product=WineHQ.com">Bugzilla</a>.
</p>
Index: wwn/wn20001106_68.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20001106_68.xml,v
retrieving revision 1.3
diff -u -r1.3 wn20001106_68.xml
--- wwn/wn20001106_68.xml 16 Dec 2003 17:09:27 -0000 1.3
+++ wwn/wn20001106_68.xml 30 Sep 2004 00:07:44 -0000
@@ -758,7 +758,7 @@
<p />
-Anyway, this was a feasability study, and James didn't make his mind
+Anyway, this was a feasibility study, and James didn't make his mind
yet if he would go or not for it.
<p />
Index: wwn/wn20001211_73.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20001211_73.xml,v
retrieving revision 1.6
diff -u -r1.6 wn20001211_73.xml
--- wwn/wn20001211_73.xml 16 Dec 2003 17:09:27 -0000 1.6
+++ wwn/wn20001211_73.xml 30 Sep 2004 00:07:31 -0000
@@ -322,7 +322,7 @@
<p />
-Alexandre Julliard agreed on the feasability, but proposed another way
+Alexandre Julliard agreed on the feasibility, but proposed another way
for the Linux PPC port: <quote who="Alexandre Julliard">since we already support
clone() on i386, using clone() on linuxppc may be easier to do, at
least for the first version.</quote></section>
Index: wwn/wn20020613_126.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20020613_126.xml,v
retrieving revision 1.4
diff -u -r1.4 wn20020613_126.xml
--- wwn/wn20020613_126.xml 16 Dec 2003 17:09:27 -0000 1.4
+++ wwn/wn20020613_126.xml 14 Sep 2004 13:58:22 -0000
@@ -528,7 +528,7 @@
following points:
<li> I followed the autodocumentation instructions. Is this at
all still supported or required?</li>
- <li> The algorythm I used is far from a good one. It still
+ <li> The algorithm I used is far from a good one. It still
doesn't support right to left paragraphs, neutral boundry
characters, and a bunch of other necessary stuff. All it
does, at the moment, is make sure consecutive runs of one
Index: wwn/wn20020906_134.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20020906_134.xml,v
retrieving revision 1.5
diff -u -r1.5 wn20020906_134.xml
--- wwn/wn20020906_134.xml 16 Dec 2003 17:09:27 -0000 1.5
+++ wwn/wn20020906_134.xml 14 Sep 2004 13:58:16 -0000
@@ -194,7 +194,7 @@
I'm original developer of quartz.
I don't want my quartz code to be restored.
</p><p>
- There seems to be many patented algorythms.
+ There seems to be many patented algorithms.
Many codecs like MPEG-1/2/4 are patented.
The ffmpeg library seems to use
many patented codes.
Index: wwn/wn20030829_185.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20030829_185.xml,v
retrieving revision 1.5
diff -u -r1.5 wn20030829_185.xml
--- wwn/wn20030829_185.xml 16 Dec 2003 17:09:27 -0000 1.5
+++ wwn/wn20030829_185.xml 5 Oct 2004 13:25:08 -0000
@@ -422,7 +422,7 @@
</p><p>
But it's as we feared : they explicitely tells us that this interface may
change on each DirectX revision (which is normal as the driver interface
-need to change to accomodate more advanced graphic options). So we may have
+need to change to accommodate more advanced graphic options). So we may have
to rewrite 'old' DirectX code each time a new revision of the DDK comes out.
</p><p>
Anyway, the current code is current not written at all with a DLL / Driver
Index: wwn/wn20040917_240.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040917_240.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20040917_240.xml
--- wwn/wn20040917_240.xml 21 Sep 2004 18:02:00 -0000 1.1
+++ wwn/wn20040917_240.xml 29 Sep 2004 22:29:11 -0000
@@ -216,11 +216,11 @@
<li> (My preference) d3d8 and d3d9 are very similar in lots of respects. I
would like to move all the GL code into the wined3d library, effectively
factorizing d3d8 and d3d9. However, this would mean extra function call
-overhead for dx8 and I really dont know how common they will be. Obviously
+overhead for dx8 and I really don't know how common they will be. Obviously
d3d8 will change during such a transition</li>
<li> I could implement d3d9 from scratch. This would have the advantage of
-being a standalone library and wont affect d3d8, but a disadvantage of
+being a standalone library and won't affect d3d8, but a disadvantage of
having to fix anything twice, and probably they will get out of sync really
quickly. Also, d3d8 still has parts missing, and I'd prefer a single
implementation if possible. If we did this, wined3d could be deleted and a
@@ -240,7 +240,7 @@
My other concern is if I start doing it and have to give up due to work or
other pressures, I could leave a half migrated setup. I assume its
relavitevly easy with cvs to back out changes if this occurs, and I hope it
-wont, but it is a concern.
+won't, but it is a concern.
</p><p>
I'd appreciate thoughts before I start (especially Lionels, AJ's etc) - I'm
only just getting back into wine programming again hence my interest.
Index: wwn/wn20040924_241.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040924_241.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20040924_241.xml
--- wwn/wn20040924_241.xml 24 Sep 2004 04:41:51 -0000 1.1
+++ wwn/wn20040924_241.xml 30 Sep 2004 00:17:37 -0000
@@ -142,7 +142,7 @@
Mike Hearn to ask about TrueType fonts,
<quote who="Mike Hearn">
Are these the ones where they need to be correctly hinted which costs
-bazillions of dollars? Or, is it actually feasable to do them just with
+bazillions of dollars? Or, is it actually feasible to do them just with
volunteer effort?
</quote></p>
@@ -152,7 +152,7 @@
<quote who="Steven Edwards">
We have a Tahoma replacement (Greenville) coming from ReactOS which is
almost done the only problem is the developer is not using fontforge to
-create it. I dont remeber the name of the tool but it is a very
+create it. I don't remember the name of the tool but it is a very
expensive font creation program.
</quote></p>
@@ -256,7 +256,7 @@
to see the code, and Wine is an LGPL project. We welcome new contributors!
</p><p>
If you're looking for cooperation on a product, you'll better contact
-Jeremy White of Codeweavers.
+Jeremy White of CodeWeavers.
</p></quote>
<p>Taking a look at the
@@ -289,7 +289,7 @@
<quote who="Rein Klazes"><p>
Just did not feel like chasing bugs the other day. I decided to have
-some fun with something that I wondering for a long time: the usefulness
+some fun with something that I was wondering about for a long time: the usefulness
of inline i86 assembly in string functions.
</p><p>
<a href="http://www.winehq.com/hypermail/wine-devel/2004/09/0594.html">This</a>
@@ -377,16 +377,16 @@
I'm afraid I won't be a lot of help right now, but I might be able to offer
some moral support. I've spent several weeks last year trying to get
-winelib working on HPUX, but I don't really have anything to show for it.
-Before I could get anything working, I had to abandon HPUX and work on
+winelib working on HP-UX, but I don't really have anything to show for it.
+Before I could get anything working, I had to abandon HP-UX and work on
fixing up Linux and Solaris stuff because it was in higher demand. I'll
-eventually need to get HPUX working also, but I won't be able to devote too
+eventually need to get HP-UX working also, but I won't be able to devote too
much time to it for at least a month.
</p><p>
I was in the same situation as you are... very rusty at x86 assembly, able
to comprehend a little sparc assembly, but I didn't know a thing about
pa-risc. I was simply typing make, letting it run until it had some error
-because HPUX wasn't supported, coming up with some fix for it, and
+because HP-UX wasn't supported, coming up with some fix for it, and
repeating. Some days I felt like I almost grasped what was going on and how
to fix it, and some days it felt like it was miles away. I never got all of
wine compiling, so I have no idea if any of the fixes I made were correct or
Index: wwn/wn20041001_242.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20041001_242.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20041001_242.xml
--- wwn/wn20041001_242.xml 1 Oct 2004 16:23:47 -0000 1.1
+++ wwn/wn20041001_242.xml 5 Oct 2004 14:36:00 -0000
@@ -63,7 +63,7 @@
<topic>News</topic>
<p>Sort of a slow news week, so we'll scrape the bottom of the
news bin for something vaguely related to Wine. Over at PC
-Advisor you ca find an article about
+Advisor you can find an article about
<a href="http://www.pcadvisor.co.uk/index.cfm?go=news.view&news=4151">desktop
Linux migration</a> and the catch-22 posed by not having native applications.
Namely, how can you get new users to use Linux without having a lot of
@@ -194,7 +194,7 @@
Fixed. This simplifies the code enormously. I don't think there's really
any problem with selecting the app you want to edit on the first tab and
-it means there aren't any wierd states anymore where you can have a
+it means there aren't any weird states anymore where you can have a
selection in the treeview that doesn't actually mean anything. The
titlebar now reflects the app you're editing.</ul></p><p>
@@ -286,7 +286,7 @@
much stuff like that removed from the User Guide as possible, we can
simply refer people to WineHQ for more info. (I think the reason for the
duplication is that the website docs simply didn't exist when the User
-Guide was written, now the website has superceded the User Guide.)
+Guide was written, now the website has superseded the User Guide.)
When it's all said and done we should be left with the following sections:
<ul>
<li> Introduction</li>
@@ -327,13 +327,13 @@
a new version of Wine and figure out that something doesn't work the
way it used to. (Of course, most of
you reading this probably fall into the masochist category who actually
-enjoy deleting their entire configuration and recompiling from scatch.)
+enjoy deleting their entire configuration and recompiling from scratch.)
Being able to install a new version and have things automagically work
is important to many people. Mike Hearn brought this topic up and I
have a hunch it's not the last time we'll hear about it:</p>
<quote who="Mike Hearn"><p>
-There are a bunch of different ways we may want to upgrade the users
+There are a bunch of different ways we may want to upgrade the user's
configuration:
<ul>
<li> Changes to $WINEPREFIX (~/.wine), for example:
@@ -363,14 +363,14 @@
</ul></p><p>
This leads to the following questions:
<ul>
-<li> How do we know when to upgrade the users wineprefix?</li>
-<li> How do we avoid disturbing the users configuration?</li>
+<li> How do we know when to upgrade the user's wineprefix?</li>
+<li> How do we avoid disturbing the user's configuration?</li>
<li> What implementation do we use to upgrade it?</li></ul>
</p><p>
One potential implementation for knowing when to upgrade the wineprefix
is to version it in a similar manner to how we version the wineserver
protocol: with a simple incrementing integer. This could be stored in
-the registry, and Wines initialization sequence changed to be:
+the registry, and Wine's initialization sequence changed to be:
<ul>
<li> Does $WINEPREFIX exist?
<ul><li> No, call wineprefixcreate. Continue with startup</li>
@@ -384,10 +384,10 @@
If registry access is too difficult here, a simpler implementation could
be used: just store the number in a .version file.
</p><p>
-How do we avoid disturbing the users configuration? Alexandre already
+How do we avoid disturbing the user's configuration? Alexandre already
laid out the plan for this, which is to have HKLM (HKEY_LOCAL_MACHINE)
devoted to the defaults we cunningly choose for maximum kewlness, and
-HKCU (HKEY_CURRENT_USER) is where the users settings are stored. These
+HKCU (HKEY_CURRENT_USER) is where the user's settings are stored. These
override the defaults, meaning we can change the default settings by
altering wine.inf, then bumping the wineprefix version so triggering a
remerge of the default registry contents.
@@ -479,7 +479,7 @@
set up the wine config upstream! We want Wine to have a good
reputation for reliability, but currently it doesn't - people run
random Foo app, it crashes and burns maybe due to incorrect
- configuration and lk away saying "Oh well, Wine is crap,
+ configuration and walk away saying "Oh well, Wine is crap,
what did I expect?". This happens quite a bit. Ensuring the user
is cleanly and transparently upgraded makes things Just Work to
a greater extent, which is good for everybody.</li>
@@ -704,7 +704,7 @@
<ul><code>
if (delay == 64) delay = 3000;</code></ul></p><p>
-Ie, rule out the possibility that the delay between resume and suspend
+I.e., rule out the possibility that the delay between resume and suspend
is so short Wine can't react in time. Then continue your investigation
from there.
</p><p>
@@ -750,7 +750,7 @@
the existing code, because otherwise it looks really bad with apps
that update the progress bar a lot.</quote></p>
-<p>Dimi Paunagreed:</p>
+<p>Dimi Paun agreed:</p>
<quote who="Dimitrie Paun"><p>
Indeed, IIRC I've tried to have as optimum background drawing code
as possible (in terms of overwriting areas, etc), as flicker in the
@@ -765,7 +765,7 @@
<p>Dmitry Timoshkov was more specific,
<quote who="Dmitry Timoshkov">
-The problem with Rob's patch is that it causes entire background of
+The problem with Rob's patch is that it causes the entire background of
the progress bar to be repainted. Some time ago (3 years or like that)
I wrote tests for progress bar and found that it invalidates background
only when (oldPos < newPos) and it really has a separate WM_ERASEBKGND
More information about the wine-patches
mailing list