[WINEHQ] Assorted spelling fixes
fgouget at free.fr
Wed Nov 23 08:17:58 CST 2005
Francois Gouget <fgouget at free.fr>
Assorted spelling fixes
Francois Gouget fgouget at free.fr http://fgouget.free.fr/
War doesn't determine who's right. War determines who's left.
-------------- next part --------------
RCS file: /var/cvs/lostwages/news/2005102503.xml,v
retrieving revision 1.1
diff -u -p -r1.1 2005102503.xml
--- news/2005102503.xml 25 Oct 2005 21:28:26 -0000 1.1
+++ news/2005102503.xml 26 Oct 2005 14:52:39 -0000
@@ -2,7 +2,7 @@
<date>October 25, 2005</date>
<title>CrossOver Office 5.0</title>
- <p>Coinciding with today's beta release of Wine, CodeWeaver's
+ <p>Coinciding with today's beta release of Wine, CodeWeavers
announced version 5.0 of CrossOver Office. See the official
RCS file: /var/cvs/lostwages/wwn/wn20011007_105.xml,v
retrieving revision 1.6
diff -u -p -r1.6 wn20011007_105.xml
--- wwn/wn20011007_105.xml 20 Jun 2005 16:21:07 -0000 1.6
+++ wwn/wn20011007_105.xml 23 Nov 2005 13:31:37 -0000
@@ -96,11 +96,11 @@ with winelib. He was going through the
Well, i compiled the part of mfc which i need for use the program without
erros or unresolved functions and compiled the mfc program with the
libmfc.so without errors or unresolved functions, but when i ran the mfc
- program hapned "Segmentation Fault".
+ program happened "Segmentation Fault".
I tried use gdb and winedbg but i can't run these debuggers, with gdb
- happned "Segmentation Fault" with or without breakpoints in the
- begining of the source and winedbg write only the first line in the
+ happened "Segmentation Fault" with or without breakpoints in the
+ beginning of the source and winedbg write only the first line in the
window and go out.
<p>Francois Gouget wanted to know what kernel and compiler version was being used.
RCS file: /var/cvs/lostwages/wwn/wn20011125_109.xml,v
retrieving revision 1.8
diff -u -p -r1.8 wn20011125_109.xml
--- wwn/wn20011125_109.xml 12 Apr 2004 19:08:35 -0000 1.8
+++ wwn/wn20011125_109.xml 23 Nov 2005 13:22:26 -0000
@@ -286,7 +286,7 @@ settings. Francois Gouget explained in
everyone would be happy with running Windows in a sand-box ala VMWare.
So it may make sense to maintain some parameters separately from the
- X settings (especially when their is not corresponding X setting), but I
+ X settings (especially when there is no corresponding X setting), but I
think the above parameters should be 100% backed by the corresponding X
RCS file: /var/cvs/lostwages/wwn/wn20021101_142.xml,v
retrieving revision 1.9
diff -u -p -r1.9 wn20021101_142.xml
--- wwn/wn20021101_142.xml 31 Aug 2005 15:42:07 -0000 1.9
+++ wwn/wn20021101_142.xml 23 Nov 2005 13:21:35 -0000
@@ -521,7 +521,7 @@ damage than you expected.
The question is...Would you expect that damage from running a windows app
in wine, when you know it could be safely run in Windows?
In just a few embedded bytes in the code it could remove your home directory
-in a single syscall. Would you expect that? - I wouldnt.
+in a single syscall. Would you expect that? - I wouldn't.
Can't we at least try implement some protection in wine against these attacks,
before something really nasty happens. I do think company policy decissions
RCS file: /var/cvs/lostwages/wwn/wn20050218_262.xml,v
retrieving revision 1.3
diff -u -p -r1.3 wn20050218_262.xml
--- wwn/wn20050218_262.xml 2 Nov 2005 22:15:15 -0000 1.3
+++ wwn/wn20050218_262.xml 23 Nov 2005 13:21:15 -0000
@@ -307,7 +307,7 @@ asked,
on the downside..
<li>Shaders aren't working yet, but the DirectX 8 shaders
-can be migrated reasonably easly.</li>
+can be migrated reasonably easily.</li>
<li>Stencil buffers aren't working properly either, which
affects shadows and odd shaped windows etc...</li>
RCS file: /var/cvs/lostwages/wwn/wn20051025_296.xml,v
retrieving revision 1.6
diff -u -p -r1.6 wn20051025_296.xml
--- wwn/wn20051025_296.xml 26 Oct 2005 20:50:41 -0000 1.6
+++ wwn/wn20051025_296.xml 23 Nov 2005 11:20:54 -0000
@@ -220,7 +220,7 @@ discussion began about
the Application Database</a>. By May of 2001,
new AppDB</a> had been written by Newman. The code behind that was eventually
-released publically and the Wine community stepped up with massive
+released publicly and the Wine community stepped up with massive
changes to make the <a href="http://appdb.winehq.org">AppDB</a> what it is
RCS file: /var/cvs/lostwages/wwn/wn20051028_297.xml,v
retrieving revision 1.2
diff -u -p -r1.2 wn20051028_297.xml
--- wwn/wn20051028_297.xml 29 Oct 2005 23:04:57 -0000 1.2
+++ wwn/wn20051028_297.xml 23 Nov 2005 13:32:53 -0000
@@ -198,7 +198,7 @@ You can also find a new thing,
that let you install applications into their own virtual Windows drive. Each
bottle can contain its own custom configuration. Then you can package it up
-into and RPM for installation elsewhere.
+into an RPM for installation elsewhere.
Go <a href="http://www.codeweavers.com/store/?cat=cxof">buy it</a> now and
give yourself the warm, fuzzy feeling of supporting free software development.
@@ -220,7 +220,7 @@ time. Well, my $.02 is that we're no lo
will steal your lunch money. In the past we had things on the to-do list
like "window management rewrite". Well, we knew that would break a lot
of things. We don't really have anything like that on the list now. Sure,
-there's going to be some huge additions to individual DLL's that will
+there's going to be some huge additions to individual DLLs that will
certainly cause regressions, but hopefully those can just be worked out.</p>
@@ -239,7 +239,7 @@ the near future as developers complete p
on during the past few weeks of freeze.</p><p>
While the core internals of Wine are
-now complete, there remains a lot of work fleshing out various DLL's.
+now complete, there remains a lot of work fleshing out various DLLs.
In the course of discussion, Alexandre mentioned some of the things
that need to get fixed before 1.0:</p>
<quote who="Alexandre Julliard"><p>
@@ -274,9 +274,9 @@ just getting into a fresh installation w
ran up winecfg and tried to add a device for my dvd burner.
-editing the device name is unusable. No cursor , then after a first
+editing the device name is unusable. No cursor, then after a first
character is entered the edit seems to jump to insert mode and puts the
-cursor at the begingin of the line. There seems no way enter text normally
+cursor at the beginning of the line. There seems to be no way enter text normally
to enter a device name.
This whole interface seems badly broken. I had to fall back to good old
@@ -339,7 +339,7 @@ It is totally unrealistic to think that
verification -- they lack the software, the context, and the motivation/
Second, we had close to a thousand bugs in that state. They do more
-harm then good lingering about. If the original reporter can not be
+harm than good lingering about. If the original reporter cannot be
bothered to verify it, they should be closed.</p></quote>
@@ -388,7 +388,7 @@ binary packages, it's not necessary to s
(This particularly happens when I get deep into week long debugging
-Patches not sent are listed hereunder long with the reasons...
+Patches not sent are listed hereunder along with the reasons...
@@ -455,11 +455,11 @@ After a lot of heaving and grunting I ma
Naturally Speaking into a fresh user account with the help of sidenet.
This time I carefully documented the steps I took so as to be sure it was
-wine-20050524; sidenet-1.8.1; Dragon NS v7 prefered En. and v7 pref Fr
+wine-20050524; sidenet-1.8.1; Dragon NS v7 preferred En. and v7 pref Fr
Ensoniq 1371 pci "soundblaster"</ul>
@@ -470,11 +470,11 @@ muse5.1 cmipci (too quiet)</ul>
-That it in a nut shell , here's the log:
+That it in a nutshell , here's the log:
-<u>INSTALLATION NOTES FOR NATURALLY SPEAKING 7 PREFERED</u>
+<u>INSTALLATION NOTES FOR NATURALLY SPEAKING 7 PREFERRED</u>
<li>installed wine is 20050524</li>
@@ -516,13 +516,13 @@ PATH=c:\windows;c:\windows\system;c:\win
-<li>installshield says req reboot , ok restarts</li>
+<li>installshield says req reboot, ok restarts</li>
<li>into reg code entry dlg OK.</li>
-<li>#file select dlg crashes , rerun and accept default folders.</li>
+<li>#file select dlg crashes, rerun and accept default folders.</li>
-<li>installation runs cleanly and exits , then throws following to console:
+<li>installation runs cleanly and exits, then throws following to console:
<code>bash # ~/.wine/dosdevices $ fixme:ddeml:DdeConnectList <br />
(1,0xc000,0xc000,(nil),(nil)): stub<br />
@@ -539,7 +539,7 @@ err:wineboot:ProcessRunKeys Error runnin
<li><code>~/.wine/c/Program Files/ScanSoft/NaturallySpeaking/Program $ wine
-"cannot find windows/system/comdlg32 "
+"cannot find windows/system/comdlg32"
OK exits cleanly.
@@ -552,7 +552,7 @@ enter user general training.</li>
use alsamixer or similar to ensure capture is on MIK and capture level
around 80% (YMMV)<br />
-84 vol gives 22 quality rating but message says too high , basic training
+84 vol gives 22 quality rating but message says too high, basic training
req reduce vol to 82: fine
@@ -599,14 +599,14 @@ GPU and send the command buffer to it.
This would need the Wine Expertise of DirectX reimplementation as
well as some good kernel hacker, but in the end maybe the struggle
to have linux specific support from Graphics adapter vendors could
-be one for all removed if we had LDDM driver support and then and
-X build on top of it (same philosofy as Xgl).
+be once and for all removed if we had LDDM driver support and then
+X build on top of it (same philosophy as Xgl).
it could also benefit to the wine project itself as we would have
-really windows driver being used, it should help to increase
+really windows driver being used, it should help increase
-sorry if it sound crazy... </p></quote>
+sorry if it sounds crazy... </p></quote>
<p>Well, that's not as crazy as a it seems. The new graphics
model in Windows Vista will be completely different than any
RCS file: /var/cvs/lostwages/wwn/wn20051104_298.xml,v
retrieving revision 1.1
diff -u -p -r1.1 wn20051104_298.xml
--- wwn/wn20051104_298.xml 6 Nov 2005 00:07:59 -0000 1.1
+++ wwn/wn20051104_298.xml 23 Nov 2005 13:20:49 -0000
@@ -118,7 +118,7 @@ that many people have tried to shoot for
inside various Unixes and Windows 3.0 inside of OS/2, just to name two--and
such emulation has received mixed results in the market because emulators
tend to make emulated applications run slowly and emulators are often cranky
-and buggy. Now is your chance to see if the open source Win Project community
+and buggy. Now is your chance to see if the open source Wine Project community
can--and has done--a better job than prior commercial emulators of the
@@ -178,7 +178,7 @@ publication. Anyone interested can find
cover them as two separate threads. Rob Done had a Winelib app he
wanted to run on Solaris x86:</p>
<quote who="Rob Done"><p>
-Ive been trying to figure how to get a (single) Wine application to be able
+I've been trying to figure how to get a (single) Wine application to be able
to display dialogs on each of 3 monitors in a non xinerama setup (DISPLAY
:0.0, :0.1, and :0.2).
@@ -186,8 +186,8 @@ I am well aware that xinerama mode would
xinerama is not an option, partly since CDE on Solaris will not work in
xinerama mode, and a little thing called Software Requirements Specification.
-I am also aware this isnt specifically a wine issue, but in researching
-what could be done about over the past week, I found several references to
+I am also aware this isn't specifically a wine issue, but in researching
+what could be done about it over the past week, I found several references to
gdi_display, x11drv_thread_data, and various other constructs and class
members in Wine that describe which display to use. This leads me to
believe there is some method to allow Wine to enable the desired functionality.
@@ -213,7 +213,7 @@ There are "WindowStations"</p></quote>
<p>Rob thought about it more and came up with something to try,
<quote who="Rob Done">
-Since alot of the Wine code refers to "thread_display" attributes, I spose
+Since a lot of the Wine code refers to "thread_display" attributes, I spose
I could try to create a separate helper thread for each display, each
somehow kludged to link to a separate display at startup, and marshal
display requests for each, but it seems that there could be an easier way.
@@ -234,9 +234,9 @@ but nothing seemed to work. Then the ne
Someone wanted to know how to get two Windows apps to talk to each
other with Wine:</p>
-I dont know much about the message queue works on Wine but wondered if
-there was means of running two progams in the same context on wine in such
-a way that they use the same message queue and can therefore potencially
+I don't know much about how the message queue works on Wine but wondered if
+there was a means of running two progams in the same context on wine in such
+a way that they use the same message queue and can therefore potentially
As I understand it, running two instance of command line wine is more
@@ -285,7 +285,7 @@ mechanism that could send the output to
<li> Using wininet to open a link to a bespoke client on 127.0.0.1 that
could redirect the output in X.</li></ol>
-As you can see are barely thought out ideas just to map possible ways to
+As you can see these are barely thought out ideas just to map possible ways to
Any comments on the merit of any of these approaches?
@@ -296,27 +296,27 @@ It could be a cool project for someone l
into Linux apps though.</p>
<p>Rob then replied with an idea about his earlier thread concerning
<quote who="Rob Done"><p>
So I could create 2 wine apps that simply duplicate the window creation and
-message handling , and have them use FindWindow and the like to enable
+message handling, and have them use FindWindow and the like to enable
using SendMessage and such to synchronize the windows?
-If so, that would MUCH simpler than the method I had started formulating.
+If so, that would be MUCH simpler than the method I had started formulating.
<p>He replied to himself about four hours later:</p>
<quote who="Rob Done"><p>
-I was going to wait til tomorrow to test this, but couldnt wait.
-This works perfectly for my app and couldnt have came at a better time.
+I was going to wait till tomorrow to test this, but couldn't wait.
+This works perfectly for my app and couldn't have come at a better time.
I just created a simple Win32 dispatcher program for each screen and sent
the window creation messages to the HWNDs from FindWindow instead of the
local app and it creates the dialogs on any screen I want. Joy Joy!!!!!
It worked out perfectly since the threads that create windows have to send
-messages to the main loop for it to create them so that the dialogs dont
-from close when the thread exits anyway.
+messages to the main loop for it to create them so that the dialogs don't
+close when the thread exits anyway.
It is refreshing that after I went through all the battles of getting
multihead display, gcc, and wine running on Solaris that FINALLY something
@@ -337,16 +337,16 @@ Thanks again to the whole Wine crew that
week about the merits of a particular method:</p>
I often have wine finish uncleanly or need to break in if it is
-misbehaving , this leaves some processes lying around and often means wine
+misbehaving, this leaves some processes lying around and often means wine
cannot be restarted correctly.
-I find killing it by hand labourious so I used the following command to
+I find killing it by hand laborious so I used the following command to
clean up and have now defined it as an alias to make life easier.
pgrep wine|while read p; do kill -9 $p ; done;</code></ul>
-It works nicely but just wondered if anyone would say OMG dont do that !
+It works nicely but just wondered if anyone would say OMG don't do that !
<p>That launched a series of people describing their favorite methods for
@@ -378,13 +378,13 @@ signal.</quote></p>
confused with the regular Linux eject command, it gets invoked by <tt>wine
eject</tt>. The idea remains the same though, to eject CD-ROMs. It's
particularly useful for things like multidisc installation programs.
-Christian Cost ran into problems using it:</p>
+Christian Costa ran into problems using it:</p>
<quote who="Christian Costa"><p>
I tried to use the new eject command and this does not seem to work.
-For that, I run a exe on the cdrom and try to eject the cdrom with:
+For that, I run an exe on the cdrom and try to eject the cdrom with:
WINEDEBUG=+eject wine eject</code></ul>
@@ -405,7 +405,7 @@ Is there anything particular to do ?
Morover, it seems eject is not installed so I have to run from the
-I have also found that there is already a eject command in my distro
+I have also found that there is already an eject command in my distro
So this conflict may require renaming the eject command.
@@ -436,13 +436,13 @@ If I set H: to autodetect, GetDriveType
Then you need to figure out why FILE_GetDeviceInfo doesn't recognize
it as a CDROM.</quote></p>
-<p>After more investigation decided to hack it into working:</p>
+<p>After more investigation Christian decided to hack it into working:</p>
<quote who="Christian Costa"><p>
I will hack FILE_GetDeviceInfo just to make it recognize my cdrom as removable
and try to see if it helps.
However, I don't understand well why forcing the drive as cdrom (instead of relying
-on autodetection) is not taken into account. This could be also usefull for ISO images.
+on autodetection) is not taken into account. This could be also useful for ISO images.
Unless this option is planned to be removed !?!
More information about the wine-patches