[WineHQ] Assorted spelling fixes
Francois Gouget
fgouget at free.fr
Tue Oct 25 12:11:31 CDT 2005
Changelog:
* wwn/wn20031121_197.xml
wwn/wn20040123_206.xml
wwn/wn20040723_232.xml
wwn/wn20051014_294.xml
wwn/wn20051021_295.xml
Francois Gouget <fgouget at free.fr>
Assorted spelling fixes
--
Francois Gouget fgouget at free.fr http://fgouget.free.fr/
Linux: It is now safe to turn on your computer.
-------------- next part --------------
Index: wwn/wn20031121_197.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20031121_197.xml,v
retrieving revision 1.7
diff -u -p -r1.7 wn20031121_197.xml
--- wwn/wn20031121_197.xml 20 May 2005 17:57:50 -0000 1.7
+++ wwn/wn20031121_197.xml 18 Oct 2005 10:55:02 -0000
@@ -295,10 +295,10 @@ it's not my itch any more.</quote></p>
functions for compilation:</p>
<quote who="Ralf Juengling"><p>
A Makefile created by winemaker & configure adds <tt>
-/whereever/include/wine/windows</tt> to the include paths.
+/wherever/include/wine/windows</tt> to the include paths.
</p><p>
Why doesn't it also add
-<tt>/whereever/include/wine/msvcrt </tt>?
+<tt>/wherever/include/wine/msvcrt </tt>?
</p><p>What is the status of the include files in msvcrt?</p></quote>
Index: wwn/wn20040123_206.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040123_206.xml,v
retrieving revision 1.5
diff -u -p -r1.5 wn20040123_206.xml
--- wwn/wn20040123_206.xml 16 Dec 2004 23:00:57 -0000 1.5
+++ wwn/wn20040123_206.xml 18 Oct 2005 10:53:27 -0000
@@ -789,7 +789,7 @@ Emmanuel's was pretty amusing.)
<topic>Creating Stubs</topic>
<p>Mike McCormack investigated an obscure DLL:</p>
<quote who="Mike McCormack"><p>
-This is a stub implemenation of the undocumented IActiveSetup from
+This is a stub implementation of the undocumented IActiveSetup from
Internet Explorer's INSENG.DLL. I'm not sure that any other software
except for Internet Explorer uses INSENG, however in case anybody is ever
interested in it, I'm posting it here.
Index: wwn/wn20040723_232.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040723_232.xml,v
retrieving revision 1.2
diff -u -p -r1.2 wn20040723_232.xml
--- wwn/wn20040723_232.xml 18 Aug 2004 20:34:30 -0000 1.2
+++ wwn/wn20040723_232.xml 18 Oct 2005 10:53:40 -0000
@@ -215,7 +215,7 @@ Since I am new to this, I was wondering
implementation. As far as I can tell I need to:
<ol>
<li> update the urlmon.idl (add IInternetSecurityManager)</li>
-<li> create a stubbed implemenation in <tt>dlls/urlmon/</tt>; making sure the stubbed
+<li> create a stubbed implementation in <tt>dlls/urlmon/</tt>; making sure the stubbed
interface also gets registered during 'wineprefixcreate'.</li></ol>
</p><p>
Are there any (wine) pointers on implementing a new (stubbed) COM interface?
Index: wwn/wn20051014_294.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20051014_294.xml,v
retrieving revision 1.3
diff -u -p -r1.3 wn20051014_294.xml
--- wwn/wn20051014_294.xml 17 Oct 2005 15:24:35 -0000 1.3
+++ wwn/wn20051014_294.xml 18 Oct 2005 11:26:29 -0000
@@ -153,7 +153,7 @@ existing surface memory. If != NULL is p
WineD3D, and it's not Released on WineD3DSurface_Release</li>
<li> When releasing the WineD3DDevice, don't release the parents of the
RenderTarget, the DepthStencilBuffer, BackBuffer and FrontBuffer, because
-ddraw.dll needs it's surfaces. Instead, release the WineD3DSurfaces only.
+ddraw.dll needs its surfaces. Instead, release the WineD3DSurfaces only.
</li></ul></p><p>
The whole thing is far from being useable, if anyone is interested in the
code, I can send it, but be warned, it's quite a mess at the moment. My plan
@@ -167,13 +167,13 @@ CVS commit and upload a big patch somewh
How do you handle the 'special' case Blits (between surface and texture,
between surfaces, ...) ?</quote></p>
-<p>Stefan hopes there won't need to many changes:</p>
+<p>Stefan hopes they won't need too many changes:</p>
<quote who="Stefan Dosinger"><p>
-Well, I must admit that I don't have an totally detailed plan, but the DDraw
+Well, I must admit that I don't have a totally detailed plan, but the DDraw
surface and the WineD3D surface share the same memory area. So those Blits
will be handled by the original DirectDraw surface implementation in any
-case, and if a WineD3D surface is attached, the DDraw surface implemenation
-updates the WineD3D surface whereever it might be necessary. I hope that I
+case, and if a WineD3D surface is attached, the DDraw surface implementation
+updates the WineD3D surface wherever it might be necessary. I hope that I
can avoid extra memcpy()s
</p><p>
I don't know if there might occur any problems if DGA is used, and I can't
@@ -341,7 +341,7 @@ for bugfixing. Despite that, Wine is a
are common. John Smith wrote to wine-devel to illustrate that point:</p>
<quote who="John Smith"><p>
There was a discussion here about 2 months ago, where I asked for a way to
-embed WINE config strings into Win32 executable (for example, as string
+embed WINE config strings into a Win32 executable (for example, as string
resources). I was told that it is better to fix the problem rather than to
create workarounds, and that fixing bugs is trivial and takes at most 2-3
days as soon as it is reproducible.
@@ -377,15 +377,15 @@ Because of this, we don't usually have t
as other projects to fix them -- there is an infinite stream of
them just around the corner.
</p><p>
-Not an excuse -- I'm just trying to explain why we don't just on
-the bugs when they are filled in Bugzilla. Now that we have 0.9
+Not an excuse -- I'm just trying to explain why we don't just jump on
+the bugs when they are filed in Bugzilla. Now that we have 0.9
on the way (hopefully followed by 1.0), this attitude seems to be
changing.</p></quote>
<p>Marcus Meissner:</p>
<quote who="Marcus Meissner"><p>
Yes, we welcome you to the wonderful world of OpenSource.
</p><p>
-Please understand that a lot of us are not being paid ... and so just chose
+Please understand that a lot of us are not being paid ... and so just choose
what to do. Some of us are paid to work on Wine, but for specific tasks.
</p></quote>
@@ -463,7 +463,7 @@ sense, as 'bugs are usually fixed within
doubts about (it just doesn't work that way), so I've made a little
experiment. I was right, you guys were wrong, and now you're trying to blame
me? I don't really think that after all that heated conversation somebody is
-going to consider my original proposal, but frankly I don't care about WIne
+going to consider my original proposal, but frankly I don't care about Wine
anymore - I definitely don't like this 'pay me' attitude (rather than normal
'sorry, we didn't have time to fix it yet' attitude).</p></quote>
Index: wwn/wn20051021_295.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20051021_295.xml,v
retrieving revision 1.1
diff -u -p -r1.1 wn20051021_295.xml
--- wwn/wn20051021_295.xml 21 Oct 2005 23:28:29 -0000 1.1
+++ wwn/wn20051021_295.xml 25 Oct 2005 17:07:09 -0000
@@ -63,18 +63,18 @@ Its main goal is to throw boomerangs. It
</stats>
<section
- title="News: Newsforge Article"
+ title="News: NewsForge Article"
subject="News"
archive="http://trends.newsforge.com/article.pl?sid=05/10/21/1251200"
posts="1"
>
<topic>News</topic>
-<p>Newsforge picked up on the pending beta release of Wine with an
+<p>NewsForge picked up on the pending beta release of Wine with an
article titled,
<a href="http://trends.newsforge.com/article.pl?sid=05/10/21/1251200">Wine
will go beta next week</a>. Quite a few quotes from Alexandre and Jeremy
White were included. From the article:</p>
-<quote who="Newsforge"><p>
+<quote who="NewsForge"><p>
"Wine has historically had a very frustrating history because it has been
alpha software," White said. "This is really hard work. We're replicating the
work of a billion-dollar company. The reason we're saying it's alpha is
@@ -120,7 +120,7 @@ status of Fedora and Red Hat builds:</p>
We really need binary builds for Fedora for this release.
It would be a pitty to fail to provide binary .rpms for
this one, while we have constantly provided them for
-all the alpha releases for more then one (two?) years now.</p></quote>
+all the alpha releases for more than one (two?) years now.</p></quote>
<p>Vincent Béron seems to be building packages again and said:</p>
<quote who="Vicnent Beron"><p>
@@ -131,7 +131,7 @@ CentOS 4 installation yet). The download
updated yet because it's a mess when all RH-distros are not ready at the
same time.
</p><p>
-I won't be home this week-end, so it'll go to Monday night at the
+I won't be home this week-end, so it'll go in Monday night at the
earliest.
</p></quote>
@@ -284,7 +284,7 @@ done on the swap buffer call) but it cou
for a real OpenGL guru (i.e. not me) to fix using funky extensions :-)
</p></quote>
-<p>Huw then came up with a something to play with:</p>
+<p>Huw then came up with something to play with:</p>
<quote who="Huw Davies"><p>
Ok, here's a patch for fun.
</p><p>
@@ -313,7 +313,7 @@ gurus apply within.
<p>Vitaliy Margolen wanted to know if the process to download and
install the Mozilla ActiveX control could be improved:</p>
<quote who="Vitaliy Margolen"><p>
-At present Wine asks the use it he/she wants to download and install Mozilla
+At present Wine asks the user if he/she wants to download and install Mozilla
ActiveX. But it doesn't work and doesn't tell the user that it didn't work. This
is not right. We either should say that download/install failed, or don't show
this message in the first place, unless we fix it.
@@ -343,7 +343,7 @@ The download functions normally.
Béron thought another problem was hiding:</p>
<quote who="Vincent Beron"><p>
That doesn't solve the capacity problem (which was a real one the last
-time this discussion occured, and is the reason why the address is not
+time this discussion occurred, and is the reason why the address is not
in wine.inf).
</p><p>
Newman wasn't very fond of hosting it on winehq either. Sourceforge
More information about the wine-patches
mailing list