[WINEHQ] Assorted spelling fixes and small tweaks
fgouget at free.fr
Sat Aug 12 14:42:19 CDT 2006
Francois Gouget <fgouget at free.fr>
Assorted spelling fixes and small tweaks.
Francois Gouget <fgouget at free.fr> http://fgouget.free.fr/
In a world without fences who needs Gates?
-------------- next part --------------
RCS file: /home/wine/lostwages/wwn/wn20020913_135.xml,v
retrieving revision 1.12
diff -u -p -r1.12 wn20020913_135.xml
--- wwn/wn20020913_135.xml 30 Mar 2006 21:39:46 -0000 1.12
+++ wwn/wn20020913_135.xml 12 Aug 2006 19:38:49 -0000
@@ -396,7 +396,7 @@ in the changes Andi mentioned he found a
While the information in itself isn't very useful it
- is an offical header we should IMHO have in Wine.
+ is an official header we should IMHO have in Wine.
Unfortunetly it can't be included at the same time
as ntdef.h and ntddk.h because it partly defines the
@@ -404,7 +404,7 @@ in the changes Andi mentioned he found a
Now, I have the full Microsoft SDK August 2002 contains
over 1000 .h files!!! But ntdef.h and ntddk.h is not
- among them. They doesn't seem to be offical headers or
+ among them. They doesn't seem to be official headers or
at least not any more.
So I'm a little unsure on how the headers should be organised.
@@ -413,9 +413,9 @@ in the changes Andi mentioned he found a
is incomplete but the full enum exists in ntddk.h!!!
Futhermore some of the functions and data structures in ntddk.h
- is defined in no header in the offical Microsoft SDKs!!!
+ is defined in no header in the official Microsoft SDKs!!!
- While we probably should include winternl.h because its an offical
+ While we probably should include winternl.h because its an official
header I'm a little unsure on how or whether we should use it
ourselves and what we should do with ntdef.h/ntddk.h.
RCS file: /home/wine/lostwages/wwn/wn20030314_161.xml,v
retrieving revision 1.6
diff -u -p -r1.6 wn20030314_161.xml
--- wwn/wn20030314_161.xml 24 May 2005 14:44:28 -0000 1.6
+++ wwn/wn20030314_161.xml 12 Aug 2006 19:38:50 -0000
@@ -114,11 +114,11 @@ threads:</p>
I've some major trouble with wine's thread implementation. We're porting a
soundprocessing application to linux/wine. (It will run as Win32 app under
wine in the first step). Sadly the wine thread implementation and/or the
-sheduler does not get the priorities right. The mission critical sound task
+scheduler does not get the priorities right. The mission critical sound task
will not get as much attention as it needs.
We've tried some hacks to improve it (increasing linux kernel priorities
-using set_sheduler/set_priorities) but this doesn't really fix the problem.
+using set_scheduler/set_priorities) but this doesn't really fix the problem.
Then we tried to make it even more ugly by creating a own thread using the
clone() system call. This fixed the timeslice problem but opens up other
strange problems. (Random crashes here and there). Most likely due to
@@ -127,7 +127,7 @@ missing lock issues or something like th
I would appreciate any hints which could make things run more smoothly!
Basically 2 ways are left to go:
-<li> Fix the wine sheduler to obey priorities</li>
+<li> Fix the wine scheduler to obey priorities</li>
<li> Fix the thread (locking?) issues</li>
Thanks a lot for any information!
@@ -138,17 +138,17 @@ help with the problem. Florian wrote ba
<quote who="Florian Schirmer"><p>
I've added some Enter/LeaveCriticalSections
calls around the handler and it seems to make things much better (but still
-far from beeing perfect).
+far from being perfect).
What prevents wine from distributing timeslices correctly? Even if i
-renice/boost linux kernel sheduler of the whole wine process(es) things go
+renice/boost linux kernel scheduler of the whole wine process(es) things go
wrong a lot. The processing thread gets way too little attention.
Do you have some hints on how to boost the processing thread a bit? I'm
perfectly happy with an (even ugly) hack. I've tried to identify the wine
-sheduler, but was unsuccesful :( Maybe you can point me in to right
+scheduler, but was unsuccessful :( Maybe you can point me in to right
direction (file, line #)?
RCS file: /home/wine/lostwages/wwn/wn20030620_175.xml,v
retrieving revision 1.8
diff -u -p -r1.8 wn20030620_175.xml
--- wwn/wn20030620_175.xml 28 Mar 2005 16:22:18 -0000 1.8
+++ wwn/wn20030620_175.xml 12 Aug 2006 19:38:51 -0000
@@ -302,7 +302,7 @@ What I found, and could fix:
Fixed by ensuring tablet driver was functional.
I don't know if the errors need to be caught, or
not, but I think they were causing crashes.
- This is probably related to synchonous/asynchonous
+ This is probably related to synchronous/asynchronous
<li>In Photoshop, an infinite loop in method FindOpenContext
@@ -310,7 +310,7 @@ What I found, and could fix:
<li>In Painter, a number of methods didn't handle NULL prameters
properly, resulting in various crashes.
- Wintab uses NULL paramters to signify a query for size of
+ Wintab uses NULL parameters to signify a query for size of
available data, or to signify a request to flush the Wintab
RCS file: /home/wine/lostwages/wwn/wn20030905_186.xml,v
retrieving revision 1.5
diff -u -p -r1.5 wn20030905_186.xml
--- wwn/wn20030905_186.xml 10 Aug 2005 15:33:11 -0000 1.5
+++ wwn/wn20030905_186.xml 12 Aug 2006 19:38:51 -0000
@@ -262,7 +262,7 @@ and forgotten -- I volunteer to keep tra
In fact, we'll get more work done this way, because different
people enjoy working on different bits. Defining exactly what
we want winecfg to do will help Mike get the job done faster.
-Defining explicitly and granularly the paramter cleanup tasks
+Defining explicitly and granularly the parameter cleanup tasks
will allow others (not interested in winecfg work) pick up
pieces and run with them.
RCS file: /home/wine/lostwages/wwn/wn20031010_191.xml,v
retrieving revision 1.6
diff -u -p -r1.6 wn20031010_191.xml
--- wwn/wn20031010_191.xml 20 Jun 2005 16:21:07 -0000 1.6
+++ wwn/wn20031010_191.xml 12 Aug 2006 19:38:51 -0000
@@ -429,7 +429,7 @@ Windows (Wine). The server should notify
appear, and the client uses the server to get all the needed information
for the start menu.
-I am about half way for the first client, that will run on KDE.
+I am about halfway for the first client, that will run on KDE.
Didn't touch the server yet, seems harder to build. Also didn't think
really hard on the communication between the server and the client.
RCS file: /home/wine/lostwages/wwn/wn20041105_247.xml,v
retrieving revision 1.2
diff -u -p -r1.2 wn20041105_247.xml
--- wwn/wn20041105_247.xml 16 Dec 2004 23:00:57 -0000 1.2
+++ wwn/wn20041105_247.xml 12 Aug 2006 19:38:52 -0000
@@ -353,7 +353,7 @@ customizable (A lot of conditional compi
have fairly special requirements for rsaenh, I could cut down the source code
a lot. However, this would make it harder to incorporate code from a newer
version of libtomcrypt, once it becomes available. Which way is preferable?
-Having less code or beeing easily upgradeable?</li></ol></p></quote>
+Having less code or being easily upgradeable?</li></ol></p></quote>
<p>(On a side note, Michael's rsaenh.dll, covered last week in
RCS file: /home/wine/lostwages/wwn/wn20041126_250.xml,v
retrieving revision 1.5
diff -u -p -r1.5 wn20041126_250.xml
--- wwn/wn20041126_250.xml 20 Jun 2005 16:21:07 -0000 1.5
+++ wwn/wn20041126_250.xml 12 Aug 2006 19:38:52 -0000
@@ -404,7 +404,7 @@ folders, like libwine-alsa.</li>
<li> Making my package looks to be a lot simpler than what's implied in
the (now year out of date) package makers guide. I found that
documentation quite useless (and didn't even find it until I was about
-half way done anyway). Again, this is probably due to advancements in
+halfway done anyway). Again, this is probably due to advancements in
<li> What I didn't find is a standard list of packages that aren't
RCS file: /home/wine/lostwages/wwn/wn20051125_299.xml,v
retrieving revision 1.2
diff -u -p -r1.2 wn20051125_299.xml
--- wwn/wn20051125_299.xml 5 Dec 2005 16:41:54 -0000 1.2
+++ wwn/wn20051125_299.xml 12 Aug 2006 19:38:53 -0000
@@ -1016,7 +1016,7 @@ windows native program.</quote></p>
<quote who="James Liggett">
-I tried modifying the RTL_USER_PROCESS_PARAMATERS settings after
+I tried modifying the RTL_USER_PROCESS_PARAMETERS settings after
creation in dlls/ntdll/thread.c (in thread_init, right after the
structure is allocated,) but that didn't work. So I put the change in
dlls/kernel/process.c, at the end of build_initial_environment, and that
RCS file: /home/wine/lostwages/wwn/wn20051202_300.xml,v
retrieving revision 1.3
diff -u -p -r1.3 wn20051202_300.xml
--- wwn/wn20051202_300.xml 7 Dec 2005 17:25:40 -0000 1.3
+++ wwn/wn20051202_300.xml 12 Aug 2006 19:38:53 -0000
@@ -192,7 +192,7 @@ others so as not to waste (a lot!) of my
<p>Oliver Stieber wrote back:</p>
<quote who="Oliver Stieber"><p>
If wine's WGL implementation is fully implemented then it may be a good idea
-switching to wgl, a wgl implemenatation would also make debugging much easier
+switching to wgl, a wgl implementation would also make debugging much easier
because wined3d can be run under windows to isolate problems.
Nick Burns also started work on a wgl version of wined3d that I haven't got
RCS file: /home/wine/lostwages/wwn/wn20060410_311.xml,v
retrieving revision 1.3
diff -u -p -r1.3 wn20060410_311.xml
--- wwn/wn20060410_311.xml 13 Apr 2006 19:02:55 -0000 1.3
+++ wwn/wn20060410_311.xml 12 Aug 2006 19:38:54 -0000
@@ -100,12 +100,12 @@ at ZDNet <a href="http://blogs.zdnet.com
a different solution</a> will be available:</p>
I'd prefer to run Darwine (a.k.a. Wine for OX) because it will allow me to run
-just the Windows applications that I want without Windows, but in the mean time
+just the Windows applications that I want without Windows, but in the meantime
Boot Camp will suit me just fine. Boot Camp will certainly be a boon for Intel
Mac customers and is sure to drive sales of Apple's newest iron.</p></quote>
<p>Personally, I think OS X support is one of the biggest things that could
-help Wine. For one, it doubles the potential numbers of users of both Wine
+help Wine. For one, it doubles the potential number of users of both Wine
and CrossOver Office. While that might not necessarily translate into more
developers, it seems to be. Second, it also leads to advocacy, and that's
certainly not a bad thing. Even if that's just someone writing in a blog
@@ -142,7 +142,7 @@ a full list of poker clients and their s
<p>The Windows Genuine Advantage came up last year when it was discovered
-Wine was being searched for denied access. See WWN issues
+Wine was being searched for and denied access. See WWN issues
and <a href="http://www.winehq.com/?issue=264#News:%20WGA%20Update">#264</a>
for the background on that. At the time there was a lot of speculation
@@ -206,7 +206,7 @@ Hearn posted a patch to get the sound in
<quote who="Mike Hearn"><p>
This patch gives me rock solid audio in Imperium Galactica 2. No more
-white noise, clicking or destabilising half way through.
+white noise, clicking or destabilising halfway through.
It exposes a race that I'll send a fix for later, for now I am hacking
around it with a sleep(1) at the end of RtlUserCreateThread. The race is
@@ -216,7 +216,7 @@ that you can do this:
and the set_thread_info server call will occur before the thread has
-fully initialized, so, we don't know the UNIX tid and cannot set the
+fully initialized, so we don't know the UNIX tid and cannot set the
priority. My current idea is to fix the race by forcing
RtlUserCreateThread to wait for the thread to sync with the server using
@@ -226,16 +226,16 @@ priorities at a finer level of granulari
Final thing - there has been on/off discussion about the security
implications of this in the past. But, this code needs to be implemented
-anyway, regardless of outcome, and on SuSE at least I think AppArmor can
+anyway, regardless of outcome, and, on SuSE at least, I think AppArmor can
be used to allow for thread prio raising without full root access. So
IMHO the permissions debate layers on top of this. Until an acceptable
solution is found some users may wish to just run Wine as root and play
their games, which they know are trustable.</p></quote>
<p>Then in another patch he took into account whether the thread
-being access was time critical and if so it needed to use the SCHED_FIFO
+being accessed was time critical and if so it needed to use the SCHED_FIFO
mechanism. What is SCHED_FIFO you ask? It's one of three different
-scheduling policies in the kernel, with the other being the default
+scheduling policies in the kernel, with the others being the default
SCHED_OTHER (which Wine normally uses) and the round robin SCHED_RR.
A process using SCHED_FIFO can be set up to always preempt a normal
process using SCHED_OTHER. So when that process needs to run, it does.
@@ -288,7 +288,7 @@ Just using the JACK audio driver won't e
stuttering sound. If dsound is performing hardware emulation then it
has its own internal thread that is performing mixing and other dsound
events. If this thread gets held off then you'll have no sound to
-give to the jack audio drive when it runs.
+give to the jack audio driver when it runs.
Increasing the size of this dsound buffer and ensuring that it runs
seems like the easiest ways to fix issues with the dsound thread being
@@ -369,7 +369,7 @@ Wine is now being checked for bugs. Som
news reports about Coverity and the ability to automatically uncover
subtle bugs in large codebases. Originally referred to as the "Stanford
Checker", Coverity is best known for its original work scanning the
-Linux kernel. Coverity's initial look of Wine
+Linux kernel. Coverity's initial look at Wine
uncovered 830 bugs. In just a few days a bunch of patches have rolled
in and that number is currently down to 749. Ben Chelf from Coverity
announced the news to the wine-devel list this week:</p>
@@ -459,14 +459,14 @@ of issues found and whether or not they
false positives triggered by the checker. </p>
- title="sft2ttf: Getting Rid of Fontforge"
+ title="sft2ttf: Getting Rid of FontForge"
subject="tasklet - sfd2ttf - eliminate dependency on FontForge (for anybody who's interested)"
-<p>Wine's requirement of Fontforge has been a problem lately. Several
+<p>Wine's requirement of FontForge has been a problem lately. Several
"bug" reports have come in that have simply been caused by not having
it installed when compiling. The issue has come up more than once a
week lately. Mike McCormack asked for someone to step up and help remedy
@@ -515,18 +515,18 @@ I have uploaded an updated patch against
It contains a few fixes,
-like yet another refcounting cleanup( Ihope that this works fine now :) ),
-and the performance issue on my radeon card, as well as the mipmap issues(all
+like yet another refcounting cleanup (I hope that this works fine now :) ),
+and the performance issue on my radeon card, as well as the mipmap issues (all
cards) are fixed :)
What is next? I will send patches which create the new WineD3D methods needed
for ddraw. These patches won't contain the implementation, but just the entry
in the vtable and a stub function. So if someone disagrees with a method,
-then we don't have to discuss about the bare existance of a method and it's
+then we don't have to discuss about the bare existence of a method and its
implementation at the same time :)
Additionally, I will now start writing a lot of test cases for all DirectX
-versions, with an eye for reference counting, in hope that we can fix the
+versions, with an eye for reference counting, in the hope that we can fix the
refcounting crashes finally. I have a test for some unimplemented functions
in my local tree too, like ProcessVertices.
@@ -626,7 +626,7 @@ and friends.</p></quote>
<p>That struck a chord with Stefan Dösinger and led him to ask:</p>
<quote who="Stefan Dosinger"><p>
-That would be usefull too for multithreaded direct3d. Somehow we have to bring
+That would be useful too for multithreaded direct3d. Somehow we have to bring
another thread to releasing the glxContext, so we can re-use it in a new
@@ -650,7 +650,7 @@ After we just have to rely that this is
I once wanted to toy with this in the DDraw code base but well, seeing that
-it will phased out pretty soon I did not do any work on it. On the other
+it will be phased out pretty soon I did not do any work on it. On the other
hand I could try for some specific games (like DungeonSiege) as an
experiment to then port it over to WineD3D.</p></quote>
@@ -676,7 +676,7 @@ for Wine's TWAIN to access libghoto:</p>
<quote who="Marcus Meissner"><p>
I have started adding gphoto2 support to twain.dll.
-My current work (before a otherwise busy week begins again),
+My current work (before an otherwise busy week begins again),
I started to break up the currently very sane centric view.
RCS file: /home/wine/lostwages/wwn/wn20060428_312.xml,v
retrieving revision 1.1
diff -u -p -r1.1 wn20060428_312.xml
--- wwn/wn20060428_312.xml 28 Apr 2006 06:53:31 -0000 1.1
+++ wwn/wn20060428_312.xml 12 Aug 2006 19:38:54 -0000
@@ -154,7 +154,7 @@ Its main goal is to attend weddings. It
<p>Wine's Ulrich Czekalla presented at the Toronto LinuxWorld Conference &
-Expo this week. Newsforge was on hand to cover the event and they have
+Expo this week. NewsForge was on hand to cover the event and they have
a <a href="http://business.newsforge.com/business/06/04/27/155209.shtml?tid=18&tid=2">detailed report</a>
of it. Ulrich outlined the current state of Wine and where development
@@ -164,7 +164,7 @@ is its Component Object Model (COM) impl
still not done and is at least six months away from being able to talk to a
Microsoft Exchange server.
-Right now about 70% of programs can install with Wine's implementation of the
+Right now about 70% of the programs can install with Wine's implementation of the
Microsoft Installer (msi.dll) library. In another year, Czekalla expects that
number to be about 90%, though he pointed out that while most programs that
install will work after being installed, there is no guarantee. One problem
@@ -182,7 +182,7 @@ has implemented DRM and will not work in
<p>There was some interesting virus news last week of a new variant that
-could infect both Linux and Windows. Newsforge did
+could infect both Linux and Windows. NewsForge did
testing</a> of it and used Wine in the process. It's not the first time viral
code has been run with Wine, though usually results are mixed. One thing
@@ -304,8 +304,8 @@ another report from the conference.
<p>A few days later he wrote in with more info:</p>
<quote who="Kai Blin"><p>
-Now that SambaXP is officialy over, the samba team a couple of other
-people have retreated to a smaller room to discuss other things.
+Now that SambaXP is officially over, the samba team, and a couple of other
+people, have retreated to a smaller room to discuss other things.
Steve French had a talk about using CIFS on linux as a replacement to
NFS which seems to be pretty cool. A couple of other talks were given,
@@ -318,7 +318,7 @@ cooperation with Wine as discussed on la
Steve asked how exactly we wanted the named pipes exposed and if we
could write up some testcases for that stuff. I think if anybody is
-interested in working on that is to email Steve directly.
+interested in working on that the best is to email Steve directly.
I got some more work on GENSEC done, but in order to really link this
together, some more work is needed. I still have things blowing up on me
@@ -366,7 +366,7 @@ once again sponsoring students to work o
summer. Wine will once again be one of the participating projects and
various Wine developers will serve as mentors for participants. Last year
Google funded 400 students and they mentioned this year they'd like to fund
-even more. Each student will get $4500 paid in three installments; the
+even more. Each student will get $4500 paid in three instalments; the
final portion paid when the project is completed. Applications are due
by May 8th, so it's about time to start putting it together. Oh wait..
I remember college.. never mind, you don't need to worry about it until
@@ -567,7 +567,7 @@ Main Objective: Support for SafeDisc (b
</p><p>Requirements: Needs to have in depth knowledge of Win32 Internals as well as
wine server internals.
</p><p>Difficulty: Moderate to High
-</p><p>Mentors: Vitaly Margolen(vitamin) and Alexander Julliard
+</p><p>Mentors: Vitaly Margolen (vitamin) and Alexander Julliard
To implement the SafeDisc Support.
The progress and details can be found here
@@ -657,7 +657,7 @@ with Wine.
I've tweaked it a bit (some patches still floating around), but:
<li> that's not complete (some items still don't work)</li>
-<li> what's also completly missing is the support of native modules
+<li> what's also completely missing is the support of native modules
(especially when generating backtraces)</li>
<li> 16bit support (but we can safely leave it out for now)</li>
<li> and testing (and fixing) most of the implementations we have</li>
@@ -669,7 +669,7 @@ I've updated the Wiki page accordingly.
<quote who="Rob Shearman"><p>
-It would be really good for valgrind know about our heap implementation
+It would be really good for valgrind to know about our heap implementation
so that it could report memory leaks. A solution I've done in the past
is to change all of the references to HeapAlloc/HeapReAlloc/HeapFree to
malloc/realloc/free so that it can report leaks, but that isn't very
@@ -708,7 +708,7 @@ So I have a couple of questions.
Should we consider using native fonts a "FIX" or is it just a
workaround? Or in other words can we fix our built in fonts to fix this.
-Should These bugs marked a duplicates?
+Should these bugs marked as duplicates?
RCS file: /home/wine/lostwages/wwn/wn20060515_313.xml,v
retrieving revision 1.1
diff -u -p -r1.1 wn20060515_313.xml
--- wwn/wn20060515_313.xml 16 May 2006 06:33:47 -0000 1.1
+++ wwn/wn20060515_313.xml 12 Aug 2006 19:38:55 -0000
@@ -127,10 +127,10 @@ Its main goal is to sit on a lake in Mon
<p>The past few weeks have been a little slow in the world of Wine.
Alexandre went on a 2 week vacation and no new patches were committed to
the main git repository.
-Interestingly, in his abscence Mike McCormack began committing some of
+Interestingly, in his absence Mike McCormack began committing some of
the patches from wine-patches to his git repository and updated
everyone on what it contained. In this respect it allowed something
-we've never had in Alexandre's abscence - a maintained patchset others
+we've never had in Alexandre's absence - a maintained patchset others
could access. It seems to have paid off. Upon Alexandre's return he
began updating the main tree and quickly released Wine 0.9.13. Noted
@@ -208,12 +208,12 @@ Autodetection:
<li> Autodetection has been moved from twain_32.dll to the drivers.
- <li> twain_32.dll itself is no longer dependend on libsane and actually
+ <li> twain_32.dll itself is no longer dependent on libsane and actually
has only minimal knowledge of sane and gphoto2 (the driver names ;)</li>
<li> Detection of multiple devices is in the DG_CONTROL/DAT_IDENTITY/MSG_GET
calls of sane.ds and gphoto2.ds. A little hidden channel detects multiple
- scanners / cameras by calling above function multiple times.
+ scanners / cameras by calling the above function multiple times.
The code is ready for WINE inclusion (tm).
@@ -265,7 +265,7 @@ report on it. A long, long, long time a
mailing list was a gateway to the
-newsgroup. When we switched to using mailman for the mailing list things
+newsgroup. When we switched to using mailman for the mailing list, things
broke. A lot of people were dismayed by that and both the mailing list
and the newsgroup suffered as a result.</p>
<p>Well, last month there was a <i>huge</i> discussion regarding adding
@@ -369,7 +369,7 @@ More details:
all at the same pitch and duration. If you hear any variation
from that, make a note of it, so you can report it.
It's important to listen the whole way through; a tad boring,
- I know, but important; it'll shift to a virtual device half way
+ I know, but important; it'll shift to a virtual device halfway
through and it's important to hear if it keeps on working or not.</li>
<li>Report your results:
@@ -415,19 +415,19 @@ to Jeremy directly (Google should provid
-<p>There's been a huge effort over the past year and half to write our
+<p>There's been a huge effort over the past year and a half to write our
own version of Internet Explorer. Now, IE itself is really just a wrapper
around a couple of big libraries. You might remember the big thing
several years ago when Microsoft "integrated" the browser with its
operating systems. The value, they argued, is that other applications
-could just use those API's to become web enabled. Well, it happened
+could just use those APIs to become web enabled. Well, it happened
and it has been a problem for programs running under Wine that need
-to access those API's. It was somewhat stemmed by using the Mozilla
+to access those APIs. It was somewhat stemmed by using the Mozilla
ActiveX control. However, it's really necessary to have our own since
the ActiveX control has proven to be problematic.
Fortunately, there exists a wonderful HTML rendering engine in Mozilla.
-So Jacek Caban took to the task of building out those API's using that
+So Jacek Caban took to the task of building out those APIs using that
as the backend. The real switch will come when our MSHTML library
switches over to the code he's been submitting. That led Dimi Paun
to ask if it will be better than the current method. Jacek replied:</p>
@@ -466,7 +466,7 @@ stuff.</p>
would be to flesh out our IE program that was recently committed. Currently
the iexplore.exe program is a simple window lacking the typical web
browser controls. Fleshing out the program would involve implementing
-all the wonderful navigation features of a browser using the new API's.
+all the wonderful navigation features of a browser using the new APIs.
@@ -551,7 +551,7 @@ is better done on wine-devel.
accessing the serial port causing a high system load. As the application
uses WaitCommEvent, I fear that my implementation of WaitCommEvent is
inappropriate. In my last posting, I ask Dan to count the calls to
-WaitcommEvent by counting the number of lines containing WaitCommEvent in a
+WaitCommEvent by counting the number of lines containing WaitCommEvent in a
relay log. His results are:
I let the app run for about 2 minutes, at the standard priority -
RCS file: /home/wine/lostwages/wwn/wn20060526_314.xml,v
retrieving revision 1.3
diff -u -p -r1.3 wn20060526_314.xml
--- wwn/wn20060526_314.xml 8 Jun 2006 20:38:53 -0000 1.3
+++ wwn/wn20060526_314.xml 12 Aug 2006 19:38:55 -0000
@@ -120,18 +120,18 @@ I just saw the May issue of Linux Journa
Phillips and it's pretty good. Things seemed to work about as well as
you'd expect, well, maybe even better than a lot of you would expect.
Programs installed ok, audio configuration seemed pretty easy, etc. I
-actually think it's a great that Wine isn't the focus of the article;
+actually think it's great that Wine isn't the focus of the article;
he spends most of the time talking about applications. I guess that
means all the magic was successfully hidden. I half expected the
article to complain about broken things, but there was hardly a
mention of it at all. At the end he did list about 4 applications
-that issues, including one named "Finale" that didn't install.
+that have issues, including one named "Finale" that didn't install.
Dave did mention he'd like to see the JACK audio driver working:
"Hopefully, Wine's JACK driver will work again by the time this
article is printed. JACK is the present and future of Linux audio,
-and it world be a definite Good Thing for the Wine Project. A virtual
+and it would be a definite Good Thing for the Wine Project. A virtual
ASIO driver might be a helpful addition as well."
@@ -172,7 +172,7 @@ Earth is slated to be the next app porte
<quote who="Chris Dibona"><p>
Picasa, founded in 2001, was purchased by Google in July of 2004, and the photo
management tool has seen some extensive use, albeit from Windows users. DiBona
-indicated that Google made a public committment to begin porting two
+indicated that Google made a public commitment to begin porting two
applications to Linux about a year ago. The other application in this project
is Google Earth. Picasa for Linux was announced first simply because it was
finished first. </p><p>
@@ -190,7 +190,7 @@ from fixing that bug. You might be able
Earth on Linux if you start tracking CVS. This seems like the type of
bug only Alexandre can fix, so if you see him mucking around with window
management and/or OpenGL, you might want to try installing the Windows
-verson of Google Earth to see if it'll run.</p><p>
+verson of Google Earth to see if it runs.</p><p>
Now, back in February I conjectured that Google would probably provide a copy
of Wine to run Picasa with and that it would be a straight up Windows app rather
@@ -237,9 +237,9 @@ cameras all could be accessed like a typ
that most can, and as a result, we have Alexandre's patches from a few weeks
ago to add HAL event support to Wine. USB devices will be noticed
and have drive letters assigned to them automatically. Well, Marcus'
-patch utilizes the traditional TWAIN interfaces to link the TWAIN API's
+patch utilizes the traditional TWAIN interfaces to link the TWAIN APIs
to libgphoto. In turn, libghoto can access cameras. This makes image
-acquisition a lot more like Windows but integrating with native Linux code.
+acquisition a lot more like Windows but integrated with native Linux code.
Unbeknownst to Marcus, his code came at a critical time.</p>
<p>Dan Kegel's mail to wine-devel provides an inside perspective on the
@@ -264,7 +264,7 @@ files are created), among others. Fort
already halfway to having an implementation of IWebBrowser
thanks to Jacek Caban's Summer of Code 2005 project. And all
that other stuff couldn't be *that* hard, right? :-) So
-Google engaged Codeweavers to add those features and fix any
+Google engaged CodeWeavers to add those features and fix any
other bugs. This resulted in tons of improvements to Wine (see
the list at
@@ -346,14 +346,14 @@ new ddraw code. I have uploaded a new di
with some updated screenshots. The diff
-is against wine git from May, 26th, 12 am(yep, the site has an older date).
+is against wine git from May, 26th, 12 am (yep, the site has an older date).
It should apply to much older versions too, but it won't work because a few
crucial patches were applied in the last 2 days. 2 games are missing in my
game list, Anarchy Online and Worms 2 are also known to work.
Ok, what to do now? The patch fixes quite a few games, but with all bigger
changes there are problems. I know some games which worked before that are
-broken now(Tibia, Z-Ball, Battlezone 2 and Swat 3). Battlezone 2 and Swat 3
+broken now (Tibia, Z-Ball, Battlezone 2 and Swat 3). Battlezone 2 and Swat 3
have fogging issues, I have to talk to Lionel Ulmer about that, and BZ2 also
needs tripple buffering. Tibia does some Blt Voodoo which doesn't work in
OpenGL yet, z-ball is similar. It's likely that there are other breakages
@@ -366,7 +366,7 @@ So what can we do?
<li> Wait with the merge until WineD3D does lazy linking to libGL</li>
-<li> Wait with the merge until all games that worked before work now(gonna take
+<li> Wait with the merge until all games that worked before work now (gonna take
<li> Merge it now and fix the regressions as they occur. This would have the
@@ -379,20 +379,20 @@ What is missing except of fixing regress
<li> Make all ddraw games working with the OpenGL renderer</li>
-<li> More intelligent texture upload: I have some hacks in that in my tree(Swat
+<li> More intelligent texture upload: I have some hacks for that in my tree (Swat
3!, Half-Life 2 maybe?)</li>
<li> The same for render targets(System shock 2, swat 3, Prince of persia 3D)</li>
<li> Try to write an OpenGL gdi driver which handles TextOut and friends
-directly in OpenGL(Age of Empires, Settlers 3 combined with 1)</li>
+directly in OpenGL (Age of Empires, Settlers 3 combined with 1)</li>
-<li> Rendering fixes: Fog and color keying(Pop3D, Battlezone 2, Swat 3)</li>
+<li> Rendering fixes: Fog and color keying (Pop3D, Battlezone 2, Swat 3)</li>
<li> Better OpenGL state management, this the lack of that takes performance
-<li> Multi-threaded D3D(Need for speed 3, Empire Earth, many others)</li></ol>
+<li> Multi-threaded D3D (Need for speed 3, Empire Earth, many others)</li></ol>
All this will happen in wined3d, and the improvements aren't limited to D3D7
games. They don't have to be done in that order.
@@ -462,7 +462,7 @@ that contain the ChangeLog entry make th
<p>Mike McCormack and Aric Stewart have done most of the work in Wine
-to support the Microsoft Installer file format and API's. The framework
+to support the Microsoft Installer file format and APIs. The framework
they've put in place works well, but there's a need for others to pick
up where they've left off. For example, MSI has a concept of
<i>actions</i>, which might consist of copying or deleting files.
@@ -477,12 +477,12 @@ that's in need of some attention:</p>
Currently the MSI Installer is working backwards, In the file files.c it
reads the files from the msi package and iterates through them and queries
the Media table in order by LastSequence. The sort order for the media table
-should be DiskId according to MSDN. Just changing the sort order wont work
+should be DiskId according to MSDN. Just changing the sort order won't work
unless the msi installer is revamped to work the right way. The code is
-written wrong for this. Currently its using LIST_FOR_EACH_ENTRY in the
+written wrong for this. Currently it's using LIST_FOR_EACH_ENTRY in the
Install Files function for the files and then trying to ready the media per
file using the sequence number of the file in the query on the media table
-using the file sequence as last sequence and returning the results order by
+using the file sequence as last sequence and returning the results ordered by
It should first be reading the Media table first and sorting by DiskId. The
@@ -497,15 +497,15 @@ until it reaches the last sequence as in
working DiskId, then it jumps to the next DiskId 2, 3, and so on. The
lastsequence of the working DiskId should always be greater than that of the
last sequence of the previous DiskId, if not the results should be skipped,
-currently it is trying to read from DiskId's that have zero as the
+currently it is trying to read from DiskIds that have zero as the
LastSequence but 22 as the DiskId. Zero indicates the first entry in the
-media table(if your in DiskId 1). as you increment through the DiskId's the
-LastSequence should increment as well, if it doesnt you skip that install
+media table (if you're in DiskId 1). as you increment through the DiskId's the
+LastSequence should increment as well, if it doesn't you skip that install
This is what causes the cabinet bugs in bugs #4533 and #5139.
-A quick fix , but not the solution would be to change the query so it
+A quick fix, but not the solution would be to change the query so it
doesn't return the results from the media table if the LastSequence is 0 and
the DiskId is greater than 1.
@@ -541,7 +541,7 @@ time to work on it.</p>
-<p>On a different note, Troy Rollo found a problem Wine's font handling:</p>
+<p>On a different note, Troy Rollo found a problem in Wine's font handling:</p>
<quote who="Troy Rollo"><p>
@@ -567,7 +567,7 @@ identifies the glyph as not having been
before), and uploads it as glyph 38 based on its outline in Tahoma.
The problem gets worse later on because some glyphs in the glyphset have been
-uploaded according to their "System" font positions (or in this case ,the
+uploaded according to their "System" font positions (or in this case, the
same character has been uploaded in its position in both fonts). Rendering a
character that uses the other glyph code results in the wrong character. You
can get a mix of Tahoma and System characters appearing on the screen with
RCS file: /home/wine/lostwages/wwn/wn20060605_315.xml,v
retrieving revision 1.1
diff -u -p -r1.1 wn20060605_315.xml
--- wwn/wn20060605_315.xml 5 Jun 2006 07:28:54 -0000 1.1
+++ wwn/wn20060605_315.xml 12 Aug 2006 19:38:55 -0000
@@ -285,7 +285,7 @@ consumed a lot of the rest of the thread
<p>In the end, Dan <a href="http://wiki.winehq.org/DanKegel">provided</a>
a list of things he'd like to see fixed. It included getting Windows
-developers to take Wine seriously by getting IDE's and debuggers working well.
+developers to take Wine seriously by getting IDEs and debuggers working well.
He also listed some broken installers that needed to get working.
@@ -324,7 +324,7 @@ Questions to consider:
<li> Are we turning away potential developers for any reason? Could we do
more to attract new hackers?</li>
- <li> Are the projects fundamental processes serving us well?</li>
+ <li> Are the project's fundamental processes serving us well?</li>
<li> Any other thoughts for improvement?</li></ul>
@@ -340,14 +340,14 @@ app correctly as I was when I first came
nearly take it for granted. Though this may be due to having developed a
feel for what will work and what won't :)
-So clearly we're doing something right ... I also think we are doing OK
+So clearly we're doing something right... I also think we are doing OK
with attracting and keeping new hackers. The influx of new Direct3D talent
lately is fabulous for instance. The experiences of our SoC students will
be useful in assessing how to improve the learning curve and we need to
tap this resource better than we did last year.
In other words, I think we're doing pretty well. I feel more
-positive about the project that I have done for a long time. It seems like
+positive about the project than I have done for a long time. It seems like
as Win32 stagnated and slowed down over the past 6 years we've been able
to turn the tide and add our own code faster than Microsoft can, which is
the tipping point.
@@ -355,7 +355,7 @@ the tipping point.
So areas for improvement?
<li> We seem to be doing very well in recruiting hackers who work on one
- particular DLL or area and solidly improve that, but a less well
+ particular DLL or area and solidly improve that, but less well
when it comes to 'general purpose' hackers who just take random apps
and make them work.
<br /><br />
@@ -364,7 +364,7 @@ So areas for improvement?
XYZ app" followed by 6 patches to 6 different DLLs.
- <li> No clear roadmap to 1.0 - for 0.9 we had Dimis TODO list and it was
+ <li> No clear roadmap to 1.0 - for 0.9 we had Dimi's TODO list and it was
quite satisfying to see them go green as tasks were completed. I guess
we have a 1.0 TODO list too but I never see any updates to it :(</li>
@@ -387,7 +387,7 @@ What do you guys think?
about Wine 1.0. Raphael Junqueira responded with some general comments
about a few of those areas:</p>
<quote who="Raphael Junqueira"><p>
-Well, winecfg need more improvements to be really usable (ie. understandable)
+Well, winecfg needs more improvements to be really usable (i.e. understandable)
by a non-technical end user.
We need to improve the Wine base installation: users should not have to
always use winecfg to configure wine; many things must be detected at
@@ -398,7 +398,7 @@ We must work on (free/gnome/kde) desktop
For developers, i think we miss (in wiki):
<li> Wine developer beginning HowTo</li>
-<li> Wine committing process (explaining why AJ never respond when patches are
+<li> Wine committing process (explaining why AJ never responds when patches are
refused :p )</li>
<li> simili-doxygen APIs (to find what is implemented/how/where some docs, and
@@ -505,7 +505,7 @@ is pretty high, and you need a lot of fr
I'm not sure if I would have stayed around if it wasn't for Summer of
Code 2005. Once you get past this, and figured out how to write your
code so Alexandre will commit it, development is quite fun. I also agree
-that the whole process improves code quality. It still is hard in to get
+that the whole process improves code quality. It still is hard to get
started. Unfortunately I don't really know how this can be changed.
I think that the effort by some of the more experienced coders to
@@ -526,7 +526,7 @@ EnumMonitors (Test + Implementation) nee
<li> No commit, and no comments for my patch for almost two weeks</li>
<li> I asked for comments and got one hint from one person.</li>
<li> Updating, testing and resending the Patch</li>
-<li> next week waiting again without a reaction.</li>
+<li> Next week waiting again without a reaction.</li>
<li> Asking for comments; one hint from a different person</li>
<li> loop again > 5 times</li>
I was frustrated that it needed so many loops from the first patch for the
@@ -575,16 +575,16 @@ notice the instructions are a complete p
involve applying a custom patch to Wine. Nick Law brought it up on
wine-devel last week:</p>
<quote who="Nick Law"><p>
-Opening up the debate again on the World of Warcraft ( WoW ) memory patch.
+Opening up the debate again on the World of Warcraft (WoW) memory patch.
Some facts about WoW that may explain why the AppDB page is pretty
active and the wow patch for wine 0.9.12 was downloaded over 1000 times
from the Appdb page during a 4 week period.... Wow has approximately 6
-million players that each pay about $90/year for the priviledge of
+million players that each pay about $90/year for the privilege of
connecting to a WoW server (Realm). Assuming this figure is broadly
correct, Blizzard therefore receives $500,000,000/year just from this
-game in subscriptions. ( This doesn't include the cost of buying the
-game in the first place ). Perhaps Blizzard would like to employee a
+game in subscriptions. (This doesn't include the cost of buying the
+game in the first place). Perhaps Blizzard would like to employ a
programmer fulltime just to work on the wine project to help make Wow
run 100% ?.
@@ -651,10 +651,10 @@ you can get Wine-0.9.10 by running yum i
that is not totally correct. Usually about a week after Wine Project releases a
version, Fedora Extras updates to the newest version! Currently, it is at
Wine-0.9.13. I believe it will be a week before Fedora Extras releases
-Wine-0.9.14 packages... I will reply when Wine packages are updated you that
-an accurate guage is made of the lag...
+Wine-0.9.14 packages... I will reply when Wine packages are updated so that
+an accurate gauge is made of the lag...
-Note: For Wine-0.9.13, and it only took 3 days after Wine official
+Note: For Wine-0.9.13, it only took 3 days after the Wine official
release to release it on Fedora Extras. It is a good idea to assume anywhere
from 3-5 days for Wine to be updated in Fedora Extras.
@@ -719,11 +719,11 @@ be added). My implementation uses COM ob
provides support for such tasks. Currently there is one interface
(IWineShellIntegration) that acts as a factory for specialized objects.
That could also be implemented using COM Aggregation - when we do that
-we could use QueryInterface instead of GetIntegrationObejct.
+we could use QueryInterface instead of GetIntegrationObject.
Some COM objects can run in the address space of the calling process -
e.g. the trash can be implemented like that. For others it would be a
-waist of resources (e.g. there is no need for every process to watch is
+waste of resources (e.g. there is no need for every process to watch if
the file associations have changed) - it's enough to load them only
once. The explorer seems to be a good candidate to create such objects.
In the attached patch there is one specialized interface - the
@@ -732,8 +732,8 @@ different icon if the file can be trashe
icons as wine's shell32 uses a message box instead of a special dialog)
and calls the trash method then. Currently there is only one built-in
trash that can't trash anything. (note that SHELL_DeleteFile is called
-in the folders that are decendents of My Computer. If choose delete on a
-file that is a decendent of the '/', it will be deleted without a warning).
+in the folders that are descendants of My Computer. If choose delete on a
+file that is a descendant of the '/', it will be deleted without warning).
<p>Ulrich Czekalla replied first:</p>
@@ -753,11 +753,11 @@ cleaner to directly create an IWineTrash
If we integrate more closely with the desktop environments we may need
to have one central object that will know that e.g. KDE 3.4 uses the
-freedesktop.org Trash but KDE 3.3 has it's own Trash implementation. If
+freedesktop.org Trash but KDE 3.3 has its own Trash implementation. If
we read the Trash CLSID from the registry such an implementation would
require creating proxy classes or hacks in the class factory. Also by
storing only one CLSID we don't have a problem which implementation to
-use if a new kind of objects is introduced.
+use if a new kind of object is introduced.
Of course when we use COM aggregation instead of a factory pattern we
will have all the interfaces visible under one CLSID so we will be able
@@ -801,5 +801,5 @@ http://feed43.com/winehq.xml</a>
individual <a href="http://cvs.winehq.com/cvsweb/lostwages/news/">news</a> files.
It probably wouldn't be too difficult and Jeremy Newman probably
wouldn't mind adding such a script to produce it to the webserver. In
-the mean time, Dan's seems to be working pretty well.</p>
+the meantime, Dan's seems to be working pretty well.</p>
RCS file: /home/wine/lostwages/wwn/wn20060611_316.xml,v
retrieving revision 1.2
diff -u -p -r1.2 wn20060611_316.xml
--- wwn/wn20060611_316.xml 21 Jun 2006 19:35:20 -0000 1.2
+++ wwn/wn20060611_316.xml 12 Aug 2006 19:38:56 -0000
@@ -86,13 +86,13 @@ to complete rewrites of certain areas ar
discussion is going on in #winehackers, but some of it trickles to the
mailing list for review. This week we're going to take a look at shaders.</p>
-<p>Shaders are a graphics concept that allow for extremely complex scenes
+<p>Shaders are a graphics concept that allows for extremely complex scenes
to be rendered very quickly. They generally come in two flavors: pixel
shaders and vertex shaders. At the heart of shaders are complex math
operations generally involving things like matrices. Remember all that
-matrix math from calc III? Me either. On modern graphics cards these
+matrix math from calc III? Me neither. On modern graphics cards these
math calculations can be performed directly in the specially designed
-GPU's of the graphics cards rather than using the CPU of the computer.
+GPUs of the graphics cards rather than using the CPU of the computer.
In the end, you get fancy 3D graphics. Shaders are responsible for
creating fog effects, creating lighting and shadowing, etc. </p>
@@ -138,7 +138,7 @@ the patch (it's against the current git
30th). Plus, you'll need a video card and driver capable of using
GLSL (type 'glxinfo' and look for "GL_ARB_shading_language_100") .
You'll also have to set a new registry key in your Wine installation
-(it is case sensitve):
+(it is case sensitive):
<ul><tt>HKEY_CURRENT_USER\Software\Wine\Direct3D\UseGLSL = "enabled"</tt></ul>
@@ -181,7 +181,7 @@ fast as ARB shaders for the ones that ac
gotten a few other things to work correctly. However, I'm still
having issues with certain pixel/vertex shader combinations. Ohsix
caught on that it may have to do with sampler limits on graphics cards
-and how sampling/textures are handled different in GLSL that with ARB.
+and how sampling/textures are handled differently in GLSL than with ARB.
I'm not sure at the moment and could use some help.
@@ -212,9 +212,9 @@ on the wiki. </p>
-<p>Wine's audio has scrutinized lately. There's a lot of issues with
+<p>Wine's audio has been scrutinized lately. There's a lot of issues with
getting sound to Just Work with Wine, not the least of which is
-communicating properly to the underlying hardware. There's also some
+communicating properly with the underlying hardware. There's also some
fragmentation going on with Wine's audio. Rather than having one audio
driver that works properly, we have five drivers subtly (and even
not so subtly) broken. On top of that, other platforms require other
@@ -243,7 +243,7 @@ OpenAL seems to have enough functionalit
Are there any problems with using OpenAL for such a purpose?
-The reason for using OpenAL is for platforms that dont have alsa/oss/esd/...
+The reason for using OpenAL is for platforms that don't have alsa/oss/esd/...
For one it gives a chance to test audio on windows for example -- and on mac
osx (although the winecoreaudio driver is making great progress).
@@ -276,7 +276,7 @@ For recording (1.1 only): start capturin
The dsound mapping stuff I want to understand better (are there any docs for
this?) I am sure we can layer it on OpenAL (hopefully good.)
-PortAudio looks like a good choice as well -- afaict -- but I dont have any
+PortAudio looks like a good choice as well -- afaict -- but I don't have any
experience with it (not that I had any openal exp when i started that driver)
@@ -305,7 +305,7 @@ I would like any feedback ppl out there
tests worked when run in interactive mode. Nick didn't know there was
an interactive mode to the tests and after running them he reported,
<quote who="Nick Burns">
-So I ran dsound_test and winmm_test (interactive mode?) on the command line
+So I ran dsound_test and winmm_test (interactive mode?) on the command line.
There are some failures -- but no crashing
Some games like Carmageddon2 are unhappy with openal atm.</quote></p>
@@ -357,8 +357,8 @@ Out of interest what are the 11 packages
Well from a wine perspective I see that this makes sense, but if you take a look
at all the dependencies it is another story... installing wine is one thing...
ending up with zillion dependencies is a whole different story for lots of
-people where e.g. bandwidth is still a problem or which rather want to have a
-slim system. I as a packager sit between the chairs and in this case I see why
+people where e.g. bandwidth is still a problem or who rather want to have a
+slim system. I, as a packager, sit between the chairs and in this case I see why
splitting up wine made sense in debian and why it made sense for Fedora Extras
as well. The question is what to split and what to leave in. The stuff that has
been split from just having one 'wine' package is stuff that made sense and in
@@ -380,7 +380,7 @@ way it is done now made lots of people h
These are the 10 packages which are relevant for a 'normal' user where wine and
-wine-tools are the major ones. They are build from the wine sources (without
+wine-tools are the major ones. They are built from the wine sources (without
winemp3). Then there is:
@@ -421,7 +421,7 @@ Catching regressions early is critical t
release cycle helps but only if the user upgrades in a timely fashion.
Some programs have been Rock Solid for years (eg: SimCity 3000) while
-others are are not. Myst worked for years and then fell victim the
+others are not. Myst worked for years and then fell victim the
Windows Management rewrite and I have just recently been able to run it
again but it is still very unstable.
@@ -435,26 +435,26 @@ to 0.9.0 as I am sure most of you are aw
1174 in May 2006
Some may call it a flood
-but over all I think this has been a good thing. The real downside to
+but overall I think this has been a good thing. The real downside to
this is that it takes a lot more of my time to go through each email and
see if I can assist and that the proper bug links are in place.
-Going to winecfg has made the product more user friendly but we are
+Going to winecfg has made the product more user friendly but we
still seem to be a long way away from "It Just Works" in a lot of cases.
In the interm I believe the AppDB has helped a lot. I think that the
work that we have put into it has paid off fairly well to a point. So
far we have added:
-<li> Applications Maintantainers that can modify application entries on an
+<li> Application Maintainers that can modify application entries on an
App by App basis.</li>
<li> Notification emails so that people (Administrators, Maintainers and
-Monitors) kept up to date on changes to applications.</li>
+Monitors) are kept up to date on changes to applications.</li>
<li> Bug links to track bugs affecting an application.</li>
-<li> Test results to track how well an application runs on a Wine version.
+<li> Test results to track how well an application runs on a Wine version
and help spot regressions</li>
<li> Lots of small improvements.</li>
@@ -488,25 +488,25 @@ the need for it very well. (trying again
<li> More Maintainers:
If you have an app that you run on a regular basis please consider
-becomeing a maintainer for that app.
+becoming a maintainer for that app.
<li> More Administrators:
The Application Queue is not being processed in a timely fashion.
For myself I am busy with my day job, working on upgrading bugzilla, and
-burnt out/frustrated trying to keep up with Application submitions (I am
-too soft hearted to reject some submittions that probably should be
+burnt out/frustrated trying to keep up with Application submissions (I am
+too soft hearted to reject some submissions that probably should be
rejected). Keeping up with the Application Queue is a tough job (for me
at least, at this time) and at this point just reviewing some of the
-submittions makes my head hurt.
+submissions makes my head hurt.
Alexander Nicolaysen Sornes and KillerTux have picked up some of the
slack but I think we could use some more help.
This job is time consuming, tedious, thankless and does not come with a
paycheck. It requires attention to detail and is a position of trust and
-responsability. On the plus side it does NOT require any programming
+responsibility. On the plus side it does NOT require any programming
skills. So... if this sounds like something you would like to do please
send an email to appdb at winehq.org explaining why you you think you would
be a good AppDB Administrator. (The guys in the white coats will be
@@ -526,9 +526,9 @@ around ASAP)
-<p>This week a serious of patches appeared all at once from Anoni Moose.
+<p>This week a series of patches appeared all at once from Anoni Moose.
That's quite interesting because it shows someone took a lot of time to
-work on Wine and then wait to submit all the work at once... under an
+work on Wine and then went to submit all the work at once... under an
anonymous name. Andi Mohr was thankful for the patches but asked:</p>
<quote who="Andreas Mohr"><p>
I can't help but say that your parents must have been giving you a
@@ -552,7 +552,7 @@ Me, I've been created as an IRC bot happ
without anyone noticing...
Oh, that's not true in fact, people do know that I'm real, since someone
-has been showing up at Codeweavers and various wineconfs pretending to be me ;)
+has been showing up at CodeWeavers and various wineconfs pretending to be me ;)
So I guess it's fully a non-issue after all since the internet is a completely
anonymous space anyway and patches can only be judged by their quality,
RCS file: /home/wine/lostwages/wwn/wn20060619_317.xml,v
retrieving revision 1.2
diff -u -p -r1.2 wn20060619_317.xml
--- wwn/wn20060619_317.xml 19 Jun 2006 20:47:23 -0000 1.2
+++ wwn/wn20060619_317.xml 12 Aug 2006 19:38:56 -0000
@@ -96,8 +96,8 @@ Its main goal is to have a party. It als
<p>An article by Nathan Willis appeared on Linux.com last week titled,
<a href="http://applications.linux.com/applications/06/06/07/1920213.shtml?tid=47"><i>Wine Doors opens Windows under Linux</i></a>.
There's a lot of good information in there and it nicely summarizes some of
-things going on in Wine development. It also discusses a new application
-being developed independent of Wine called
+the things going on in Wine development. It also discusses a new application
+being developed independently from Wine called
<a href="http://www.wine-doors.org"><i>Wine Doors</i></a>:</p>
Like WineTools, Wine Doors is designed to user-friendlify your Wine
@@ -179,7 +179,7 @@ currently have.</p></quote>
<p>Apparently Vitaliy Margolen picked it up recently and announced some
<quote who="Vitaliy Margolen"><p>
-Here is latest installment of safedisc support in Wine.
+Here is latest instalment of safedisc support in Wine.
The major change from last version is the way user space talks to ntoskrnl. Now
I'm passing the information through wineserver with a help of 4 server calls.
@@ -229,7 +229,7 @@ loaded into a vbo.</li>
<li> In Direct3D7 there is no way for the app to specify a range of vertices to
be locked. Because of that DX7 apps are generally slower if they update the
-vertices regularily. To avoid that drawback there is no VBO created for DX7
+vertices regularly. To avoid that drawback there is no VBO created for DX7
apps if they have vertex data that needs conversion. The geometry in DX7 apps
is usually quite simple, so DrawStridedSlow isn't a big performance hit in
@@ -239,10 +239,10 @@ those apps.</li></ul></p></quote>
This is an updated version of the VBO patch. The main difference is the
integration with IWineD3DDevice::ProcessVertices which gives a nice
-performance boost for Half-Life 1 and propably Anarchy Online(not tested
+performance boost for Half-Life 1 and propably Anarchy Online (not tested
-What is missing is work with vertex shaders(awaiting the download of the dx8
+What is missing is work with vertex shaders (awaiting the download of the dx8
sdk for the dolphin demo) and an implementation of
@@ -339,14 +339,14 @@ pass parser, hence a major rewrite of th
<li> a couple of bug fixes from current code</li></ul></p><p>
I'd suggest hence not to apply this patch and to wait for the full solution
-(likely sometimes this weekend).</p></quote>
+(likely sometime this weekend).</p></quote>
<p>He followed that up with 31 patches. He gave a clearer description of the
patches before posting them:</p>
<quote who="Eric Pouech"><p>
-The following series implements a basic support for Dwarf2 debug information.
+The following series implements basic support for Dwarf2 debug information.
Basically, it's a major rewrite/enhancement of the current code.
-At the end of the serie, we should have:
+At the end of the series, we should have:
<li> type information (at least basic types, and struct unions)</li>
<li> functions's parameter and variable handling (1)</li>
<li> line number information</li>
RCS file: /home/wine/lostwages/wwn/wn20060710_318.xml,v
retrieving revision 1.1
diff -u -p -r1.1 wn20060710_318.xml
--- wwn/wn20060710_318.xml 10 Jul 2006 06:29:12 -0000 1.1
+++ wwn/wn20060710_318.xml 12 Aug 2006 19:38:56 -0000
@@ -172,8 +172,8 @@ He wrote in this week to let everyone kn
way the packages are configured:</p>
<quote who="Andreas Bierfert"><p>
some of you might have noticed that building 0.9.16 for Fedora Extras took me
-more time then the releases before. This was because of the discussions from a
-couple of weeks ago on this list. As a result I did spent some time on the
+more time than the releases before. This was because of the discussions from a
+couple of weeks ago on this list. As a result I did spend some time on the
mentioned issues and came across an easy solution:
If you install wine form the Fedora Extras repository via <tt>yum install
@@ -186,7 +186,7 @@ to fewer 'false positives' on bug report
satisfies some of the things you, the wine folks, brought up.
Thanks for the input on this matter. I hope that this is only the first step
-towards a good relation ship between wine and the fedora packages for wine and
+towards a good relationship between wine and the fedora packages for wine and
that emails like the ones from a couple of weeks back won't happen again...
So for the announcement:
@@ -216,7 +216,7 @@ suggested to post it here.
Currently I'm working on a scan-after-write functionality: Whenever a file was
-changed the virusscanner checks the file.
+changed the virus scanner checks the file.
My plan is to hook in NtWriteFile() (dlls/ntdll/file.c), because whenever a
windows program writes to a file this function is called. Within this
@@ -274,7 +274,7 @@ we can't provide such an API.</quote></p
ClamAV to take a file descriptor as input. Kari Hurtta pointed
out that ClamAV already can take a stream of data. Kuba Ober
was concerned that would kill performance, especially since
-there's a lot of case where scanning isn't completely necessary.
+there's a lot of cases where scanning isn't completely necessary.
Chris decided to go back and take a closer look at the functionality
already built into ClamAV.
@@ -356,7 +356,7 @@ until someone teaches GCC the MSVC calli
To prevent confusion: the "normal" 32-bit Wine version runs fine on x86_64
Linux. This is the version you'll want to use, it allows you to run 32-bit
Windows stuff. The remarks above are about running 64-bit Windows
-executables which are virtually non-existant at the moment.
+executables which are virtually nonexistent at the moment.
<p>Kuba Ober agreed to take a stab at looking into the GCC side of things
@@ -382,7 +382,7 @@ and about alternatives to -msvc.
I'd be submitting a patch to mingw32 people as soon as it's done, in addition
to posting it here. Note that the only way for me to test it would be to
-inspect the assembly output, as I'm not running 64 bit environment here (even
+inspect the assembly output, as I'm not running a 64 bit environment here (even
though I'm on a 64 bit AMD processor). So it'd need testing from 64 bit
people here at least.
@@ -397,7 +397,7 @@ though) for about a year now, but it doe
is much more ABI differences including the exception handling (and yes,
I mean exception handling in C, not only C++) where MSVC generates special
unwinding information for the functions. I'm not sure if it would be
-even possible to mix the ABI this way, but I'm open to hear some suggestions.
+even possible to mix the ABI this way, but I'm open to some suggestions.
<p>Kuba asked for any pointers regarding the MSVC x86 ABI. Filip
@@ -433,7 +433,7 @@ the DWARF2 debugging format to Wine (see
He followed that up with a request for testers:</p>
<quote who="Eric Pouech"><p>
As you may have seen, there's now some support for the dwarf2 debug
-format (instead of stabs) in the Wine tree
+format (instead of stabs) in the Wine tree.
I'd like to get some feedback on the overall feedback on how it behaves.
To do so, you need to reconfigure Wine with something like
CFLAGS="$CFLAGS -gdwarf-2" ./configure
@@ -510,9 +510,9 @@ different formatting:
-<p>GUID's, Globally Unique Identifiers, on Windows are used for all
+<p>GUIDs, Globally Unique Identifiers, on Windows are used for all
sort of things, including identifying various components. Detlef
-Riekenberg provided a link to a site that catelogs a ton of them:</p>
+Riekenberg provided a link to a site that catalogs a ton of them:</p>
<quote who="Detlef Riekenberg"><p>
Found a big online GUID-List:
RCS file: /home/wine/lostwages/wwn/wn20060810_319.xml,v
retrieving revision 1.1
diff -u -p -r1.1 wn20060810_319.xml
--- wwn/wn20060810_319.xml 10 Aug 2006 06:12:17 -0000 1.1
+++ wwn/wn20060810_319.xml 12 Aug 2006 19:38:57 -0000
@@ -74,7 +74,7 @@ Its main goal is to procrastinate on pur
- title="News: .9.17, .9.18, CrossOver Mac"
+ title="News: 0.9.17, 0.9.18, CrossOver Mac"
@@ -90,7 +90,7 @@ I'm pretty sure we've seen more patches
We've also had patches rolling in from lots of new developers. (By the
way, welcome aboard!)</p>
-<p>Since the last issue we've had two beta release of Wine. The first,
+<p>Since the last issue we've had two beta releases of Wine. The first,
0.9.17, noted the following changes:</p>
<quote who="Alexandre Julliard"><p><ul>
@@ -203,7 +203,7 @@ the "Drink-making facilities on each cor
for the low low price of about 40 pounds (okay, so the exchange
rate sucks, and that's $75 US, but still...)
-If you <i>don't</i> get me an room request in the next few days, then I'll
+If you <i>don't</i> get me a room request in the next few days, then I'll
have to close down our room reservation, and you'll be stuck
in some sleazy motel on the edge of town paying outrageous
sums of of money. (Okay, they actually all look like nice places
@@ -233,7 +233,7 @@ are known as virtual memory functions.
as commit a series of memory pages within the virtual address space of another
process. CreateRemoteThread can then start a new thread that begins execution
within that address space of the other process. As Alexandre once said,
-<quote who="Alexandre Julliard">it's fairly tricky to do correctly</quote>
+<quote who="Alexandre Julliard">it's fairly tricky to do correctly</quote>.
<p>Thomas Kho came up with an implementation of those functions for Wine.
@@ -248,7 +248,7 @@ VirtualAllocEx/NtAllocateVirtualMemory a
APCs are queued per-thread, so I made minimal changes to add a per-process
APC queue. Of course, this implementation suffers from the limitation that the
-remote process must go into an interuptible wait for the operation to succeed;
+remote process must go into an interruptible wait for the operation to succeed;
an operation targeting a suspended process would block.
Stefan Siebert mentioned that VirtualQueryEx is necessary for Lotus Notes
@@ -258,7 +258,7 @@ simple program that prints a process' me
Lastly, I should mention that I have two pending patches to add conformance
-tests for remote processes operations:
+tests for remote process operations:
@@ -268,11 +268,11 @@ http://www.winehq.org/pipermail/wine-pat
<p>Asynchronous procedure calls seem to be one way to go to attack the
problem. They sort of work like signals on Unix. They can be used
-for timers, notifications, error reporting, and such. When it comes to APC's in
+for timers, notifications, error reporting, and such. When it comes to APCs in
Windows, there's two kinds: kernel-mode and user-mode. Guess which one has
a more privileged level of operation? (By the way, here's a
<a href="http://www.ddj.com/dept/windows/184416590">good</a> page describing
-APC's and some of the low-level stuff they do.) All that led Dan Kegel to
+APCs and some of the low-level stuff they do.) All that led Dan Kegel to
<quote who="Dan Kegel"><p>
Tommy's APC version of his VirtualAllocEx / CreateRemoteThread patch
@@ -292,7 +292,7 @@ but this means they would essentially ne
Windows API, APCs are a feature that could have been useful if it had
been properly thought out...</quote></p>
-<p>So the issue here is that the kernel APC's could run at a point where
+<p>So the issue here is that the kernel APCs could run at a point where
a thread is holding a lock. It led Tommy to ask:</p>
<quote who="Thomas Kho"><p>
@@ -383,7 +383,7 @@ working. Vincent explained:</p>
<quote who="Vincent Povirk"><p>
Windows does not have a fullscreen mode. In Windows, windows that are
Always on Top are on top of panels. Windows applications enter
-"fullscreen mode" by positioning themselves take up the whole screen
+"fullscreen mode" by positioning themselves to take up the whole screen
and being always on top (actually, now I'm not so sure they have to be
always on top; I'm only basing that on my experience as a Windows
@@ -477,7 +477,7 @@ Elijah explained the issue:</p>
Actually, that's because Dmitry was using an older version. The patch
-actually appiled to head would have also applied to 2.14.3. :)
+actually applied to head would have also applied to 2.14.3. :)
Anyway, the returning from fullscreen mode bug makes perfect sense,
and I'm pretty sure I know the cause: metacity tries to return the
window to the size it was before it was fullscreened, and it sounds
@@ -509,7 +509,7 @@ fullscreening within Wine.</p>
<quote who="Pavel Roskin"><p>
Something strange to happened my Wine installation recently. I'm
-getting following messages if I run any program from Wine:
+getting the following messages if I run any program from Wine:
$ winemine<br />
wine_main_preload_info not found<br />
@@ -572,7 +572,7 @@ EXTRA_BINARIES = wine-kthread wine-pthre
<quote who="Pavel Roskin"><p>
It is installed and it is run. If I replace wine-preloader with a
script that logs the arguments and runs the renamed wine-preloader, I
-see it being called twice when an exe file with run with Wine. For
+see it being called twice when an exe file is run with Wine. For
$ wine FarManager170.exe<br />
@@ -663,9 +663,9 @@ be useful:</p>
Good news. One possible "market" for this is in the Debian world
-as currently the Linux Notes client will not install as it can not
+as currently the Linux Notes client will not install as it cannot
work out what version of Mozilla is installed. IBM have never really
-make any of their stuff easy to install on Debian. Of course the
+made any of their stuff easy to install on Debian. Of course the
Debian sid wine will need to be brought up to date (currently .15) and
will need the two patches mentioned above included.</p></quote>
@@ -687,7 +687,7 @@ for more information.
<p>Winelib hasn't gotten much attention lately. In fact, some of you
reading this might not have any idea what Winelib even is. Besides just
letting you run Windows programs, Wine has <i>Winelib</i>, which lets you
-link your program against Wine's own DLL's. That means anywhere you can
+link your program against Wine's own DLLs. That means anywhere you can
run Wine you could recompile your Windows program and it would run. Of
course, that's easier said than done and ports to platforms other than
x86 receive little attention. </p>
@@ -703,7 +703,7 @@ so we'll go with a question/answer style
<i>Luc: is there a definitive list somewhere what API WinLib implements of
Win32, and what it doesn't? I have had some difficulty finding this
-<p>Dan: Each of Wine's DLL's comes with a file which lists which APIs it
+<p>Dan: Each of Wine's DLLs comes with a file which lists which APIs it
The lines that say 'stub' are not really implemented.</p><p>
@@ -717,7 +717,7 @@ Does your app have a regression test or
If so, you can run that under Wine and compare results.
<p><i>Luc: one application we'd like to port uses active scripting (VBScript).
-Basically we wrote some features in VBScript, which in turn automating our
+Basically we wrote some features in VBScript, which in turn automate our
application (like macros in Photoshop CS). What would be our options for this
if we were to use WinLib? (MainWin ships with VBscript and JScript)
@@ -735,7 +735,7 @@ Should be.
<p>Dan: That's supported now, though you may find that Wine's implementation
-has rough edges. Nothing a little support contract with Codeweavers
+has rough edges. Nothing a little support contract with CodeWeavers
couldn't iron out.
More information about the wine-patches