WineHQ: Assorted spelling fixes
fgouget at free.fr
Thu Jul 15 06:48:19 CDT 2004
Assorted spelling fixes.
Francois Gouget fgouget at free.fr http://fgouget.free.fr/
Any sufficiently advanced bug is indistinguishable from a feature.
-- from some indian guy
-------------- next part --------------
RCS file: /var/cvs/lostwages/wwn/wn20010526_96.xml,v
retrieving revision 1.5
diff -u -r1.5 wn20010526_96.xml
--- wwn/wn20010526_96.xml 16 Dec 2003 17:09:27 -0000 1.5
+++ wwn/wn20010526_96.xml 11 Jul 2004 18:58:34 -0000
@@ -61,7 +61,7 @@
> You didn't setup properly the config file for the Wine multimedia modules.<br />
-> Will use the hard-coded setup, but this will disapear soon.<br />
+> Will use the hard-coded setup, but this will disappear soon.<br />
> Please add a WinMM section to your Wine config file.<br />
RCS file: /var/cvs/lostwages/wwn/wn20011224_111.xml,v
retrieving revision 1.6
diff -u -r1.6 wn20011224_111.xml
--- wwn/wn20011224_111.xml 16 Dec 2003 17:09:27 -0000 1.6
+++ wwn/wn20011224_111.xml 11 Jul 2004 18:59:09 -0000
@@ -807,7 +807,7 @@
problem with modal message boxes.
The installer displays at some point a task modal message box, but for some
-reason the box disapears almost instantly, and I'm stuck with a focused
+reason the box disappears almost instantly, and I'm stuck with a focused
InstallShield screen on which I can't do anything as the task modal msgbox is
invisible and unfocused.
RCS file: /var/cvs/lostwages/wwn/wn20030620_175.xml,v
retrieving revision 1.6
diff -u -r1.6 wn20030620_175.xml
--- wwn/wn20030620_175.xml 16 Dec 2003 17:09:27 -0000 1.6
+++ wwn/wn20030620_175.xml 11 Jul 2004 18:59:34 -0000
@@ -457,7 +457,7 @@
<quote who="Jeremy Newman">
Those bug descriptions are gone. I thought I had a recent backup of
them. I thought wrong. The last good backup I have is from Aug 2000. It
- was in daily rotation after that. Whatever caused them to dissapear,
+ was in daily rotation after that. Whatever caused them to disappear,
happened 2 weeks before anyone even noticed. All two weeks of my tape
rotations have those bugs missing.</quote> Then he added,
<quote who="Jeremy Newman">
RCS file: /var/cvs/lostwages/wwn/wn20040604_225.xml,v
retrieving revision 1.2
diff -u -r1.2 wn20040604_225.xml
--- wwn/wn20040604_225.xml 18 Jun 2004 15:06:51 -0000 1.2
+++ wwn/wn20040604_225.xml 11 Jul 2004 18:59:45 -0000
@@ -168,7 +168,7 @@
The biggest changes since from the end user point of view:
-<li> the $regs variable has disapeared</li>
+<li> the $regs variable has disappeared</li>
<li> all the 'walk' commands have now been merged into the 'info' ones.
'walk' is no longer a valid command</li>
<li> module identification in symbol name now has the form of
RCS file: /var/cvs/lostwages/wwn/wn20040709_230.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20040709_230.xml
--- wwn/wn20040709_230.xml 10 Jul 2004 19:20:50 -0000 1.1
+++ wwn/wn20040709_230.xml 11 Jul 2004 19:24:10 -0000
@@ -97,8 +97,8 @@
side of things, and should help with the large set of Wine/GDI+
interactions that we have.
- To support WndProc, this new version uses the most commony used
-WndProc events internally so applications that depend on this works,
+ To support WndProc, this new version uses the most commonly used
+WndProc events internally so applications that depend on this work,
and we will have an optional plugin that would use WineLib to host
@@ -116,9 +116,9 @@
just happened to notice. He wrote back and cc:'ed wine-devel wondering
if there was something that could just be fixed with Wine,
<quote who="Steven Edwards">
- Rather than spending a whole lot of time rewritting things wouldnt it
+ Rather than spending a whole lot of time rewritting things wouldn't it
be better to help the Wine project get stable and move to the 1.0 goal?
- There is a roadmap and TODO on Winehq of things that are needed for
+ There is a roadmap and TODO on WineHQ of things that are needed for
<p>More reasons were listed about problems Wine caused. Most developers
@@ -174,7 +174,7 @@
take a look at them:
<i> Wine is too hard to use as a library. It does complicated things with
-registers and threads, and requires wierd bootstrap code.</i>
+registers and threads, and requires weird bootstrap code.</i>
I'm not sure what to make of this one. The low level code isn't optional,
it's required in order to provide the environment Win32 code requires.
@@ -196,7 +196,7 @@
platforms than Mono itself.</ul></p><p>
-<i> Wines APIs are unstable.</i>
+<i> Wine's APIs are unstable.</i>
See above. I think Peter is right, our exported APIs are not that large,
and making them stable is not that hard either. They don't even have to be
@@ -233,7 +233,7 @@
I think if you had done it the way Microsoft did by writing a GDI+ DLL for
Wine and then mapped that to System.Drawing, there would not need to be
-this constant mapping into System.Drawing contexs and things would go a
+this constant mapping into System.Drawing contexts and things would go a
lot faster. Yes, that means implementing GDI+ in Win32/C, not much fun I
know, but it's the way Microsoft did it and therefore if we want
compatibility the way we must do it too (Wine will have to implement GDI+
@@ -304,7 +304,7 @@
<quote who="Gearoid Donnellan">
I am very shocked that this actually works and you probably know
-already but If you down load and extract the Windows Installer
+already but If you download and extract the Windows Installer
redistributable in the wine directory you can then install MSI's using
"<tt>wine msiexec /i <msiname></tt>".
Tried it with winzip.msi and it worked perfectly.
@@ -328,7 +328,7 @@
We are still missing an implementation of msiexec, but it is a fairly
trivial wrapper around msi.dll, so should not be too hard to implement.
- The native msi dlls (ie. the MS redistributables) have worked in Wine
+ The native msi dlls (i.e. the MS redistributables) have worked in Wine
for more than two years :) They contain a few annoying bugs which are
hard to workaround...
@@ -372,7 +372,7 @@
and before that I used to see deadlocks upon startup of non-trivial
applications (such as Forte Agent, both 16bit and 32bit flavors).
-I believe there are also signficant threadings issues on -CURRENT, so
+I believe there are also significant threading issues on -CURRENT, so
overall Wine is hardly, if at all, usable on any version of FreeBSD I
have access to, even though I'm still working to keep it at least
compilable on FreeBSD 4.9 and 5.2/5.3.
@@ -446,10 +446,10 @@
that FreeBSD never allocates anything above 0x80000000, the
reservation code can't really be made optional.</quote></p>
-<p>So.. that was the status last month and no one has mailed the
-list to report any updates since then. If you're on FreeBSD 4.9
+<p>So... that was the status last month and no one has mailed the
+list to report any updates since then. If you're on FreeBSD 4.9,
things will break if you upgrade to 4.10. If you're on 5.2 things
@@ -479,9 +479,9 @@
for use in the OpenSSL Toolkit.
-This stipulation seems to introduce a incompatibility with the GPL. For
+This stipulation seems to introduce an incompatibility with the GPL. For
normal Wine this is not a big deal but if someone wants to make a
-Winelib application that is GPL or if I want to take Wines Wininet and
+Winelib application that is GPL or if I want to take Wine's Wininet and
Adavapi32 code in to ReactOS this presents a problem. Am I correct in
reading it this way?
@@ -491,15 +491,15 @@
Services for Mozilla and it has recently been tri-licensed MPL/LGPL/GPL
on CVS tip. http://www.mozilla.org/projects/security/pki/nss/
-From the what I understand this lib provides everything we need so all
-it really means is that our soft dependency on OpenSSL in now a soft
+From what I understand this lib provides everything we need so all
+it really means is that our soft dependency on OpenSSL is now a soft
dependency on Mozilla. If we want to use the webbrowser module in Wine
then a Mozilla dependency will be there already so we might as well use
the security implementation while we are at it.
-The discussion hadn't even realyl got started by the time this week's
+The discussion hadn't even really got started by the time this week's
issue was published, but Mike Hearn did mention another alternative,
<quote who="Mike Hearn">
@@ -549,7 +549,7 @@
modern ICU version in Debian, Ove can't really build wine with BiDi.
Maybe we can get our supplied packages to be BiDi enabled, but so long
as we use ICU, and ICU has this horrible linking policy, we can't really
-get it wide-spread. Since I want it widespread, fribidi is where I'm headed.
+get it widespread. Since I want it widespread, fribidi is where I'm headed.
<p>The conversation then continued on IRC, and Shachar summarized that
More information about the wine-patches