[WINEHQ] Assorted spelling fixes
Francois Gouget
fgouget at free.fr
Sun Aug 28 09:48:28 CDT 2005
Changelog:
* templates/en/howto.template
wwn/wn20021101_142.xml
wwn/wn20030418_166.xml
wwn/wn20040910_239.xml
wwn/wn20050812_287.xml
wwn/wn20050819_288.xml
wwn/wn20050826_289.xml
Francois Gouget <fgouget at free.fr>
Assorted spelling fixes
--
Francois Gouget fgouget at free.fr http://fgouget.free.fr/
We are Pentium of Borg. You will be approximated. Division is futile.
-------------- next part --------------
Index: templates/en/howto.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/howto.template,v
retrieving revision 1.18
diff -u -p -r1.18 howto.template
--- templates/en/howto.template 16 Aug 2005 14:38:45 -0000 1.18
+++ templates/en/howto.template 28 Aug 2005 14:31:10 -0000
@@ -3,7 +3,7 @@
<h1>Wine HowTo</h1>
-<p>Before you install Wine, first make sure that there is no previous Wine
+<p>Before you install Wine, make sure that there is no previous Wine
installation on your system, either from a package or from source. If you
haven't yet installed Wine, you should be fine. See the
<a href="{$root}/site/docs/wine-user/installing-wine-source#UNINSTALLING-WINE-SOURCE">Removing old Wine versions</a>
Index: wwn/wn20021101_142.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20021101_142.xml,v
retrieving revision 1.8
diff -u -p -r1.8 wn20021101_142.xml
--- wwn/wn20021101_142.xml 24 Mar 2004 16:12:19 -0000 1.8
+++ wwn/wn20021101_142.xml 16 Aug 2005 16:31:15 -0000
@@ -550,7 +550,7 @@ sophisticated application-level security
</p><p>
We've recently talked about some ways to move forward towards implementing
the NT-style security model in wine. When those plans move forward, one of the
-issues to consider is the tendency of windows to propogate virii, and the
+issues to consider is the tendency of windows to propagate virii, and the
possible need to selectively prohibit wine from accessing resources that
the user invoking wine might have full control of.
</p><p>
Index: wwn/wn20030418_166.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20030418_166.xml,v
retrieving revision 1.8
diff -u -p -r1.8 wn20030418_166.xml
--- wwn/wn20030418_166.xml 20 May 2005 17:57:50 -0000 1.8
+++ wwn/wn20030418_166.xml 16 Aug 2005 16:31:27 -0000
@@ -505,7 +505,7 @@ However, for GUI apps, people need to pr
point instead of main. Maybe we can export some sort of init function,
so that they can keep their main(), and simply call a wine_init().
Doing so, we maintain the appearance of a Unix app. Of course, the
-limitation would be that no Wine-related funtionality can be called
+limitation would be that no Wine-related functionality can be called
before the wine_init() call. So no more static C++ initializers, etc.
Would this be doable?</p></quote>
Index: wwn/wn20040910_239.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040910_239.xml,v
retrieving revision 1.2
diff -u -p -r1.2 wn20040910_239.xml
--- wwn/wn20040910_239.xml 15 Sep 2004 20:03:42 -0000 1.2
+++ wwn/wn20040910_239.xml 16 Aug 2005 19:16:55 -0000
@@ -155,7 +155,7 @@ the website</p></quote>
an application performs an illegal operation (ie crashes) or
occasionally a program will throw their own exceptions. UNIX
signals are converted into SEH exceptions by Wine and you can
- watch their propogation using this channel. It's handy because
+ watch their propagation using this channel. It's handy because
often applications will trap their own crash to, for instance,
perform an emergency save. The most common exception to watch
for is STATUS_ACCESS_VIOLATION or 0xC0000005 which is the closest
@@ -433,7 +433,7 @@ the website</p></quote>
Win32 code uses HeapAlloc(GetProcessHeap(), 0, allocsize)
instead of malloc(allocsize) and therefore so does Wine. In
- pratice this rule isn't strictly enforced so you may see both.
+ practice this rule isn't strictly enforced so you may see both.
</li>
</ul></p>
@@ -499,7 +499,7 @@ the website</p></quote>
most popular C++ compiler on Windows) use the thiscall calling
convention, in which the instance pointer is stored in %ecx. If
you get a crash dereferencing the value of %ecx in a C++
- program, you might be seeing a null pointer deference on an
+ program, you might be seeing a null pointer dereference on an
object instance. </li>
<li> Optimizing compilers do a lot of interesting things, such
Index: wwn/wn20050812_287.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20050812_287.xml,v
retrieving revision 1.4
diff -u -p -r1.4 wn20050812_287.xml
--- wwn/wn20050812_287.xml 16 Aug 2005 02:08:54 -0000 1.4
+++ wwn/wn20050812_287.xml 28 Aug 2005 14:06:29 -0000
@@ -80,7 +80,7 @@ Its main goal is to prove the relativity
for 2005 and 2006. This is significant for a lot of reasons. We
get glimpses of the direction CodeWeavers is heading from time to
time, and if you follow the daily CVS commits and wine-patches you
-can glean even more info. However, rarely do we a concise summary
+can glean even more info. However, rarely do we get a concise summary
of what's going on. CodeWeavers drives a lot of the development
behind Wine, especially when it comes to implementing new features
from the ground up. I would include the
@@ -161,12 +161,12 @@ page has more info. Mike McCormack is m
<li>Theming support being tacked by Frank Richter, alluded to in Alexandre's
last CVS drop and also covered in
<a href="http://www.winehq.com/?issue=285#Theming%20Work">WWN
-#285</a>, has also been progressing. The work centers on hooking into
+#285</a>, has also been progressing. The work centers on hooking
theming into Wine's controls and making them paint the current theme.
This past week saw a lot of patches hit wine-patches and were
subsequently committed by Alexandre. Kevin Koltzau is mentoring this one.</li>
<li>Daniel Remenak has been working on improving DirectInput
-support in Wine. A few weeks ago we talk about the
+support in Wine. A few weeks ago we talked about the
addition of force feedback code that was just starting to appear
(<a href="http://www.winehq.com/?issue=285#Force%20Feedback">WWN #285</a>).
Daniel is behind that work and there's even more stuff to come.
@@ -377,7 +377,7 @@ did the crackling appear in the first pl
hardware pointer was used.
</p></quote>
-<p>A few days later he found the proper fixed and described it:</p>
+<p>A few days later he found the proper fix and described it:</p>
<quote who="Alex Villacis Lasso"><p>
Reading through my own previous explanation, I realized that the
original crackling problem lies in the fact that the hardware pointer is
Index: wwn/wn20050819_288.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20050819_288.xml,v
retrieving revision 1.1
diff -u -p -r1.1 wn20050819_288.xml
--- wwn/wn20050819_288.xml 21 Aug 2005 04:56:17 -0000 1.1
+++ wwn/wn20050819_288.xml 28 Aug 2005 14:42:55 -0000
@@ -69,29 +69,29 @@ problem:</p>
<quote who="Stefan Dosinger"><p>
I am trying(once again) to get Empire Earth running with wine. After
solving a few problems, I've run into a strange access violation crash. It
-looks like a buffer overrun, followed by a return to an invalid adress.
+looks like a buffer overrun, followed by a return to an invalid address.
</p><p>
The crash messages look a little bit different every time, with illegal
instructions / access violations or even a Segmentation Fault without
-starting winedbg at various addreses(Attached file crashes). On very rare
+starting winedbg at various addresses(Attached file crashes). On very rare
occasions, this crash doesn't occur, and the game continues to load and
crashes later in some ddraw function. Instead of crashing it complains about
a corrupted heap:
<ul><code>
err:heap:HEAP_ValidateInUseArena Heap 0x7fd80000: prev arena 0x7fe01640 is
not prev for in-use 0x7fe01cb0</code></ul></p><p>
-I've looked at a +heap trace, but I couldn't find anything usefull.
+I've looked at a +heap trace, but I couldn't find anything useful.
(See ee-nocrash for a log). I've also attached a normal log without any
special debug flags set(ee-normal.log.gz). I've added a few ERR statements
for testing in some functions.
</p>
<p>So my questions are:
<ul><li>
-Am I right with my suspection that the problems are caused by a incorrect
+Am I right with my suspicion that the problems are caused by an incorrect
return?</li>
<li>How can I get a disassembly of Low-Level
-Engine.?Deactivate_at_GERasterizer@@UAEJXZ or simmilar functions. I didn't find
+Engine.?Deactivate_at_GERasterizer@@UAEJXZ or similar functions. I didn't find
this symbol.</li></ul></p></quote>
<p>James Liggett recognized the problem,
@@ -106,11 +106,11 @@ of the problem:</p>
<quote who="Stefan Dosinger"><p>
I was lucky with setting a breakpoint in the wine code. The crash happens in
the DDraw implementation. The return from
-Main_DirectDraw_Release(ddraw_main.c:154) leads to a random adress. The call
+Main_DirectDraw_Release(ddraw_main.c:154) leads to a random address. The call
which leads to this is "HeapFree(GetProcessHeap(), 0, This);" in
Main_DirectDrawSurface_Destroy, surface_main.c:154. If I comment out this
call, Empire Earth continues loading and crashes more or less randomly at
-some later points.
+some later point.
</p><p>
I've edited the IDirectDrawSurfaceImpl structure and added a 2048 byte block
at the beginning and the end. This makes the crashes reliable: With the
@@ -140,10 +140,10 @@ ago. More work showed a way to reproduc
not the same problem:</p>
<quote who="Stefan Dosinger"><p>
This is interesting: Setting the +heap trace flag sets the bad address
-realiably to 0xaaaaaaaa (without my changes to DDraw). Does this say anything?
+reliably to 0xaaaaaaaa (without my changes to DDraw). Does this say anything?
</p></quote>
-<p>Andreas Mohr grepped through the code and pointed out a potentional
+<p>Andreas Mohr grepped through the code and pointed out a potential
culprit:</p>
<quote who="Andreas Mohr"><p>
<code>dlls/ntdll/heap.c:#define ARENA_FREE_FILLER 0xaa</code></p><p>
@@ -188,7 +188,7 @@ contains some bugs with known fixes that
Kevin wondered about it though,
<quote who="Kevin DeKorte">
Well the patch does improve the cursor. I can now see it. Although it is only
-grey. It there any reason why the best cursor selection method always checks
+grey. Is there any reason why the best cursor selection method always checks
for bits == 1. What about color cursors?</quote>
</p><p>
Duane Clark also reported success,
@@ -198,7 +198,7 @@ I don't really understand how the patch
Riven uses a bunch of color cursors (hands pointing various directions).
Without the patch, only the standard pointer cursor was generated. This
cursor appeared and disappeared normally (the cursor is supposed to
-disappear while some Quicktime clips are playing, and then reappear).
+disappear while some QuickTime clips are playing, and then reappear).
With the patch, the color cursors reappeared and all are correct.
</quote></p>
@@ -251,10 +251,10 @@ commctrl doesn't have any effect on this
</p></quote>
<p>Andi Mohr wanted to know if Jesse was running either both of the
-DLL's as native or both as builtin. These DLL's can't be mixed and
+DLLs as native or both as builtin. These DLLs can't be mixed and
matched between native and builtin. Jesse replied that both of them
were in fact native. Mike McCormack didn't think there was a reason
-to still use native DLL's:</p>
+to still use native DLLs:</p>
<quote who="Mike McCormack"><p>
You shouldn't need to use the native comctl32 any longer. Please update
@@ -267,7 +267,7 @@ sweeping the problem under the carpet an
</p></quote>
<p>Jesse described the specific problem he was running into with
-DreamWeaver. Mike supplied a patch:</p>
+Dreamweaver. Mike supplied a patch:</p>
<quote who="Mike McCormack"><p>
OK, there is a patch that is in CrossOver that has not yet been
@@ -349,7 +349,7 @@ Try "kernel32.97;kernel32.98".</p></quot
<quote who="Tom Wickline"><p>
I am in the process of updating our "Acknowledgement" & "Who's Who"
-pages and if anyone here wants to be included and your currently not
+pages and if anyone here wants to be included and you're currently not,
just send me a mail and ask for inclusion.
</p><p>
If you want inclusion on the "Acknowledgement" page let me know what
Index: wwn/wn20050826_289.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20050826_289.xml,v
retrieving revision 1.1
diff -u -p -r1.1 wn20050826_289.xml
--- wwn/wn20050826_289.xml 28 Aug 2005 05:36:09 -0000 1.1
+++ wwn/wn20050826_289.xml 28 Aug 2005 14:42:18 -0000
@@ -109,7 +109,7 @@ showing lots of different controls. Of
apps as well.
<a href="http://www.winehq.org/images/wwn289-theme-2.jpg">Here's</a> Word
Viewer showing a document and drop down menu. All in all, theming seems
-to progressing nicely. The user interface in winecfg could use a little
+to be progressing nicely. The user interface in winecfg could use a little
work, such as browsing for .msstyles files and automatically installing
them, but considering the <i>Appearance</i> tab is only a week old it's
understandable.
@@ -220,7 +220,7 @@ a mirror should be set up, but really it
worth the effort. Ivan Leo Puoti pointed out many things will be
accessible:</p>
<quote who="Ivan Leo Puoti"><p>
-Luckly we've got a CVS mirror, for those who didn't know, you can use the european mirror following
+Luckily we've got a CVS mirror, for those who didn't know, you can use the european mirror following
these instructions
<ul><a href="http://66.102.9.104/search?q=cache:DK5XI0Uyp_MJ:www.winehq.com/site/cvs+&hl=en">
http://66.102.9.104/search?q=cache:DK5XI0Uyp_MJ:www.winehq.com/site/cvs+&hl=en</a></ul></p><p>
@@ -278,17 +278,17 @@ Doing SEH via the application stack is c
Passing exceptions to the debugger via the application stack is not
correct. I've attached a small C file which will demonstrate the
problem. On windows, you can single step through the assembly code
-correctly, on Wine, you can not. The one conclusion that we can draw
+correctly, on Wine, you cannot. The one conclusion that we can draw
is that the method for calling the debugger on Windows must not use
the application stack at all. Furthermore, if an exception does occur
while the stack pointer is bad in windows, the debugger will trap it
-and let you examine the situation. Wine right now crashes.
+and let you examine the situation. Right now Wine crashes.
</p><p>
Moving the calling of the debugger into the signal handler takes away
the dependance on a correct signal stack. It lets us:
<ol>
-<li> Debug a program without having to modify it's memory to call the
+<li> Debug a program without having to modify its memory to call the
debugger.</li>
<li> Set breakpoints and single step through areas where the stack
@@ -306,9 +306,9 @@ It would make sense for the wine debugge
</p><p>
Now, if calling the debugger shifts positions to the signal stack, it
is possible to detect whether we can deliver a corresponding SE to the
-applications SEH. If we can detect when the exception can not
+application's SEH. If we can detect when the exception cannot
actually be delivered, then we can force the debugger to stop, even if
-this is the first notification of a excpetion to the debugger. The
+this is the first notification of an exception to the debugger. The
point behind the non-continuable change was to tell the debugger this.
That patch was wrong. I should have used EH_STACK_INVALID (it would
be impossible to even pass this flag to the debugger if the debugger
@@ -380,7 +380,7 @@ some problems:</p>
Googletalk is a free chat program from Google with integrated VoIP. I
installed the program and received a message saying Googletalk required
Windows 2000, XP or 2003. The program started after installation and
-almost immewdiately crashed.
+almost immediately crashed.
<a href="http://www.winehq.com/hypermail/wine-devel/2005/08/0518.html">Here</a>
is the output.</p></quote>
More information about the wine-patches
mailing list