[WineHQ] Assorted spelling and case fixes
Francois Gouget
fgouget at free.fr
Mon Dec 13 06:35:53 CST 2004
Changelog:
* templates/en/developer-cheatsheet.template
templates/en/press.template
wwn/wn19990822_5.xml
wwn/wn20000214_30.xml
wwn/wn20000501_41.xml
wwn/wn20000717_52.xml
wwn/wn20011021_106.xml
wwn/wn20020613_126.xml
wwn/wn20020906_134.xml
wwn/wn20021025_141.xml
wwn/wn20030110_152.xml
wwn/wn20030124_154.xml
wwn/wn20030214_157.xml
wwn/wn20030425_167.xml
wwn/wn20030613_174.xml
wwn/wn20030808_182.xml
wwn/wn20030919_188.xml
wwn/wn20031010_191.xml
wwn/wn20031121_197.xml
wwn/wn20040109_204.xml
wwn/wn20040123_206.xml
wwn/wn20040130_207.xml
wwn/wn20040806_234.xml
wwn/wn20041001_242.xml
wwn/wn20041015_244.xml
wwn/wn20041029_246.xml
wwn/wn20041105_247.xml
wwn/wn20041112_248.xml
wwn/wn20041119_249.xml
wwn/wn20041126_250.xml
wwn/wn20041203_251.xml
wwn/wn20041210_252.xml
wwn/interviews/interview_10.xml
wwn/interviews/interview_4.xml
Assorted spelling and case fixes.
--
Francois Gouget fgouget at free.fr http://fgouget.free.fr/
Good judgment comes from experience, and experience comes from bad judgment
-- Barry LePatner
-------------- next part --------------
Index: templates/en/developer-cheatsheet.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/developer-cheatsheet.template,v
retrieving revision 1.2
diff -u -r1.2 developer-cheatsheet.template
--- templates/en/developer-cheatsheet.template 17 Nov 2004 23:19:13 -0000 1.2
+++ templates/en/developer-cheatsheet.template 30 Nov 2004 10:51:54 -0000
@@ -518,7 +518,7 @@
<h1> Common problems </h1>
<p> Some bugs are easier to fix than others. Here is a quick list
- of the more persistant ones so you know what you're getting into: </p>
+ of the more persistent ones so you know what you're getting into: </p>
<ul>
<li>
Index: templates/en/press.template
===================================================================
RCS file: /var/cvs/lostwages/templates/en/press.template,v
retrieving revision 1.21
diff -u -r1.21 press.template
--- templates/en/press.template 2 Sep 2004 19:09:22 -0000 1.21
+++ templates/en/press.template 12 Dec 2004 20:02:51 -0000
@@ -12,7 +12,7 @@
<li> <a href="http://linuxtoday.com/news_story.php3?ltsn=2004-06-08-031-26-OP-CY">LinuxToday</a> June 8, 2004 - CodeWeavers & CrossOver Office 3.0 on The Linux Show!
<li> <a href="http://www.eweek.com/article2/0,1759,1602124,00.asp">EWeek</a> May 31, 2004 - CrossOver Office Does Windows Better
<li> <a href="http://www.osviews.com/modules.php?op=modload&name=News&file=article&sid=1454">OSViews</a> May 30, 2004 - SpecOpS Labs response to Wine Project
- <li> <a href="http://madpenguin.org/Article1513.html">MadPenguin</a> May 22, 2004 - A First Look at CodeWeaver's CrossOver Office 3.0
+ <li> <a href="http://madpenguin.org/Article1513.html">MadPenguin</a> May 22, 2004 - A First Look at CodeWeavers CrossOver Office 3.0
<li> <a href="http://madpenguin.org/Article1512.html">MadPenguin</a> May 22, 2004 - An Interview with CodeWeavers Fouder Jeremy White
<li> <a href="http://www.orangecrate.com/article.php?sid=710">OrangeCrate</a> May 20, 2004 - An Interview with Jeremy White, CodeWeavers
<li> <a href="http://www.linuxworld.com.au/index.php/id;379130238;fp;2;fpid;1">LinuxWorld</a> May 20, 2004 - Windows-to-Linux: New wave of adoption on its way?
@@ -86,7 +86,7 @@
<li> <a href="http://www.transgaming.com/news.php?newsid=42">TransGaming</a> August 1, 2002 - Play Warcraft III on Linux with TransGaming's Release of WineX 2.1
<li> <a href="http://www.anandtech.com/guides/viewfaq.html?i=127">AnandTech</a> July 14, 2002 - Can I run Windows software on UNIX?
<li> <a href="http://www.linuxplanet.com/linuxplanet/interviews/4202/1/">LinuxPlanet</a> May 15, 2002 - The Many Faces of Wine: Realities of Open Source and Business
- <li> <a href="http://www.linuxworld.com/story/32751.htm">LinuxWorld</a> April 29, 2002 - CodeWeaver's CrossOver Office is the best way to do the wrong thing
+ <li> <a href="http://www.linuxworld.com/story/32751.htm">LinuxWorld</a> April 29, 2002 - CodeWeavers CrossOver Office is the best way to do the wrong thing
<li> <a href="http://www.desktoplinux.com/articles/AT3633344463.html">DesktopLinux</a> April 25, 2002 - The Penguin and the Hare
<li> <a href="http://www.linuxlookup.com/html/reviews/software/transgamingwinex.html">LinuxLookup</a> April 25, 2002 - TransGaming WineX 2.0 Review <i>(covering WineX)</i>
<li> <a href="http://techupdate.zdnet.com/techupdate/stories/main/0,14179,2861562,00.html">ZDNet</a> April 17, 2002 - Four routes to Lin-Win desktops
Index: wwn/wn19990822_5.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn19990822_5.xml,v
retrieving revision 1.4
diff -u -r1.4 wn19990822_5.xml
--- wwn/wn19990822_5.xml 20 Jan 2004 21:08:18 -0000 1.4
+++ wwn/wn19990822_5.xml 12 Dec 2004 22:28:51 -0000
@@ -396,9 +396,9 @@
<li />I would let the server handle at least the handles of the registry.
since you can duplicate registry handles with DuplicateHandle and
-inherit these, this are obviously K32 objects. This would enable us
+inherit these, these are obviously K32 objects. This would enable us
to have change notitifications on keys. (It would be interesting to
-test if CloseHandle() is are working with registy handles to)
+test if CloseHandle() is working with registy handles to)
<li />Let the server handling the values to would give us a durable
mechanism to have consistent data wint more than one process.
Index: wwn/wn20000214_30.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20000214_30.xml,v
retrieving revision 1.4
diff -u -r1.4 wn20000214_30.xml
--- wwn/wn20000214_30.xml 16 Dec 2003 17:09:26 -0000 1.4
+++ wwn/wn20000214_30.xml 12 Dec 2004 20:01:36 -0000
@@ -132,7 +132,7 @@
<p />
-Jeremy White from CodeWeaver put up a $2.500 CoSource
+Jeremy White from CodeWeavers put up a $2.500 CoSource
request to run properly WinBench 99 under Wine: <quote who="Jutta Wrage">It
would be nice to have some real data to counter the FUD (or at least
some real data to indicate what work we have to do).</quote>
Index: wwn/wn20000501_41.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20000501_41.xml,v
retrieving revision 1.3
diff -u -r1.3 wn20000501_41.xml
--- wwn/wn20000501_41.xml 16 Dec 2003 17:09:26 -0000 1.3
+++ wwn/wn20000501_41.xml 12 Dec 2004 14:21:23 -0000
@@ -279,7 +279,7 @@
<quote who="Dmitry Timoshkov">Wine should have only one functional implementation
indeed. I think, it should be implemented like in NT: all actual work
does Unicode version, ANSI version simply converts ANSI to Unicode and
-then calls Unicode work horse. But this transition will consume a lot
+then calls Unicode workhorse. But this transition will consume a lot
of time and efforts.</quote>
<p />
Index: wwn/wn20000717_52.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20000717_52.xml,v
retrieving revision 1.6
diff -u -r1.6 wn20000717_52.xml
--- wwn/wn20000717_52.xml 16 Dec 2003 17:09:26 -0000 1.6
+++ wwn/wn20000717_52.xml 12 Dec 2004 20:01:17 -0000
@@ -211,7 +211,7 @@
<p />
-Jim Graham (CodeWeaver's CTO) gave a long report of his trip to
+Jim Graham (CodeWeavers' CTO) gave a long report of his trip to
BorCon:
<quote who="Jim Graham">
I was at BorCon for CodeWeavers. I hosted the BOF on "Using Wine to
Index: wwn/wn20011021_106.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20011021_106.xml,v
retrieving revision 1.8
diff -u -r1.8 wn20011021_106.xml
--- wwn/wn20011021_106.xml 2 Sep 2004 19:09:22 -0000 1.8
+++ wwn/wn20011021_106.xml 12 Dec 2004 20:03:38 -0000
@@ -185,7 +185,7 @@
build Wine. Otherwise Wine will not work. I believe that not even
"./wine" will work. Do you have warnings about an unresolved main symbol
when you link Wine's dlls? This is one of the symptoms. Another is when
-that strip does not understand "--strip-uneeded".
+that strip does not understand "--strip-unneeded".
</p><p>
Also note that just tweaking the PATH is not enough to switch from
the Solaris toolchain to the GNU toolchain. That's because gcc is
Index: wwn/wn20020613_126.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20020613_126.xml,v
retrieving revision 1.5
diff -u -r1.5 wn20020613_126.xml
--- wwn/wn20020613_126.xml 6 Oct 2004 15:05:11 -0000 1.5
+++ wwn/wn20020613_126.xml 12 Dec 2004 20:00:57 -0000
@@ -83,7 +83,7 @@
<section
- title="News: Updated CodeWeaver's Products, Quickstart Guide"
+ title="News: Updated CodeWeavers' Products, Quickstart Guide"
subject="News"
archive="http://www.codeweavers.com/about/press_releases/?id=20020611"
posts="2"
Index: wwn/wn20020906_134.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20020906_134.xml,v
retrieving revision 1.6
diff -u -r1.6 wn20020906_134.xml
--- wwn/wn20020906_134.xml 6 Oct 2004 15:05:11 -0000 1.6
+++ wwn/wn20020906_134.xml 12 Dec 2004 20:00:45 -0000
@@ -113,7 +113,7 @@
</ul></p>
<p>And LinuxPlanet <a href="http://www.linuxplanet.com/linuxplanet/reviews/4405/1/">
-reviewed</a> CodeWeaver's CrossOver Office. The interviewer was especially
+reviewed</a> CodeWeavers CrossOver Office. The interviewer was especially
interested in Quicken's performance.</p>
<p>Also, I'd like to take a second to plug Zack Brown's
Index: wwn/wn20021025_141.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20021025_141.xml,v
retrieving revision 1.10
diff -u -r1.10 wn20021025_141.xml
--- wwn/wn20021025_141.xml 24 Mar 2004 16:12:19 -0000 1.10
+++ wwn/wn20021025_141.xml 12 Dec 2004 20:00:33 -0000
@@ -135,7 +135,7 @@
<p>But the question really begs, is any of this the least bit new? I mean, we've
been able to buy distributions in the store and online for a heck of a long time.
Automatic updates aren't really new. Even the configuration and management of lots
-of desktops really isn't that cutting edge. CodeWeaver's Wine preview has been
+of desktops really isn't that cutting edge. CodeWeavers' Wine preview has been
available for Mandrake users for years. However, if you think back to when Corel
released their distribution you'll remember that it raised the bar for all
distributions. In general, Linux distributions seem to go through spurts of
Index: wwn/wn20030110_152.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20030110_152.xml,v
retrieving revision 1.7
diff -u -r1.7 wn20030110_152.xml
--- wwn/wn20030110_152.xml 16 Dec 2003 17:09:27 -0000 1.7
+++ wwn/wn20030110_152.xml 12 Dec 2004 20:00:16 -0000
@@ -117,7 +117,7 @@
<a href="http://www.desktoplinux.com/articles/AT8266871610.html">
several Linux distributions</a>, some you may never have heard
of before. The notable Wine reference discusses using
-CodeWeaver's CrossOver Office with the ELX distribution.
+CodeWeavers CrossOver Office with the ELX distribution.
Sadly, the author doesn't mention Wine at all.</p>
</section>
Index: wwn/wn20030124_154.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20030124_154.xml,v
retrieving revision 1.8
diff -u -r1.8 wn20030124_154.xml
--- wwn/wn20030124_154.xml 24 Mar 2004 16:18:47 -0000 1.8
+++ wwn/wn20030124_154.xml 12 Dec 2004 20:00:04 -0000
@@ -137,7 +137,7 @@
<p><a href="http://www.itweek.co.uk/">IT Week</a> has a review
of SuSE's Linux Office Office Desktop. In case you haven't
-heard, this product contains CodeWeaver's CrossOver Office 1.3.1
+heard, this product contains CodeWeavers CrossOver Office 1.3.1
<a href="http://www.itweek.co.uk/Products/Software/1138079">Their
recommendation</a> was for people "who only use Microsoft Word
and Excel" which I found rather strange. Their conclusion:</p>
Index: wwn/wn20030214_157.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20030214_157.xml,v
retrieving revision 1.7
diff -u -r1.7 wn20030214_157.xml
--- wwn/wn20030214_157.xml 16 Dec 2003 17:09:27 -0000 1.7
+++ wwn/wn20030214_157.xml 12 Dec 2004 19:59:47 -0000
@@ -91,7 +91,7 @@
<topic>News</topic>
<p>Looks like a new advocacy committee is in town - the Linux Desktop
Consortium. What makes this notable (from a Wine perspective) is
-that CodeWeaver's Jeremy White is the interim chairman. PC World has
+that CodeWeavers' Jeremy White is the interim chairman. PC World has
an article discussing
<a href="http://www.pcworld.com/news/article/0,aid,109266,00.asp">the
role of the new organization</a>. Anyone else not excited?</p>
Index: wwn/wn20030425_167.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20030425_167.xml,v
retrieving revision 1.7
diff -u -r1.7 wn20030425_167.xml
--- wwn/wn20030425_167.xml 16 Dec 2003 17:09:27 -0000 1.7
+++ wwn/wn20030425_167.xml 12 Dec 2004 19:59:35 -0000
@@ -133,7 +133,7 @@
Some of additions mentioned, such as file locking and
file change notification, have been in the LGPL Wine tree for a while
now. We can also expect more changes merged back into the tree as the
-CodeWeaver's patches get cleaned up and committed by Alexandre.</p>
+CodeWeavers patches get cleaned up and committed by Alexandre.</p>
<p>Other news about CodeWeavers can be found in this week's
<a href="http://www.winehq.org/?interview=4">interview with Jeremy White</a>.
@@ -439,7 +439,7 @@
I think the rule should be that if someone says they're working on
something then anyone who wants to work on the same area should contact
them.
-This is a rule everyone should keep in mind, not just Codeweaver
+This is a rule everyone should keep in mind, not just CodeWeavers
employees.
</p><p>
Index: wwn/wn20030613_174.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20030613_174.xml,v
retrieving revision 1.8
diff -u -r1.8 wn20030613_174.xml
--- wwn/wn20030613_174.xml 16 Dec 2003 17:09:27 -0000 1.8
+++ wwn/wn20030613_174.xml 12 Dec 2004 19:58:46 -0000
@@ -104,7 +104,7 @@
<mention>CodeWeavers</mention>
<p><a href="http://www.suse.com/us/company/press/press_releases/archive03/sld.html">SuSE
-announced</a> their "Linux Desktop" product this week. CodeWeaver's
+announced</a> their "Linux Desktop" product this week. CodeWeavers
CrossOver Office 2.0.1 is integrated into it:</p>
<quote who="SuSE"><p>
SuSE Linux Desktop gives users the choice between deploying Linux
Index: wwn/wn20030808_182.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20030808_182.xml,v
retrieving revision 1.5
diff -u -r1.5 wn20030808_182.xml
--- wwn/wn20030808_182.xml 16 Dec 2003 17:09:27 -0000 1.5
+++ wwn/wn20030808_182.xml 12 Dec 2004 19:58:32 -0000
@@ -103,7 +103,7 @@
<p>Linux Magazine put together a small article about
<a href="http://www.linux-mag.com/2003-05/linuxdesktop_01.html">Linux
on the desktop</a>. TransGaming is briefly mentioned on the first
-page. The third page has quotes from CodeWeaver's Jeremy White and
+page. The third page has quotes from CodeWeavers' Jeremy White and
Alexandre Julliard.</p>
</section><section
Index: wwn/wn20030919_188.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20030919_188.xml,v
retrieving revision 1.3
diff -u -r1.3 wn20030919_188.xml
--- wwn/wn20030919_188.xml 16 Dec 2003 17:09:27 -0000 1.3
+++ wwn/wn20030919_188.xml 12 Dec 2004 14:02:39 -0000
@@ -424,7 +424,7 @@
check that the signatures are ok. Tweaking the amount of extra memory
can cause you to not corrupt the heap structure at some point, which
will allow you reliable pin-pointing the buffer in which the overflow
-occures.
+occurs.
</p><p>
I have never worked with valgrind (though I love the principle behind
it), so I can't say whether it is more effective at this sort of
Index: wwn/wn20031010_191.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20031010_191.xml,v
retrieving revision 1.3
diff -u -r1.3 wn20031010_191.xml
--- wwn/wn20031010_191.xml 16 Dec 2003 17:09:27 -0000 1.3
+++ wwn/wn20031010_191.xml 12 Dec 2004 19:58:11 -0000
@@ -94,7 +94,7 @@
installing Wine.
<a href="http://insight.zdnet.co.uk/business/0,39020481,39116972,00.htm">He
ran into some problems</a> and gives a thumbs down for usability. He
-does recommend CodeWeaver's CrossOver Office as an alternative to the
+does recommend CodeWeavers CrossOver Office as an alternative to the
free version.</p>
Index: wwn/wn20031121_197.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20031121_197.xml,v
retrieving revision 1.4
diff -u -r1.4 wn20031121_197.xml
--- wwn/wn20031121_197.xml 20 Jan 2004 21:08:18 -0000 1.4
+++ wwn/wn20031121_197.xml 12 Dec 2004 19:57:56 -0000
@@ -80,7 +80,7 @@
<p>It seems like a lot of the patches from CodeWeavers appeared on
wine-patches this time. In the past it seemed like a lot of them
were culled from the CodeWeavers codebase and committed by Alexandre.
-Over the past month there's been patches from the CodeWeaver's staff
+Over the past month there's been patches from the CodeWeavers' staff
submitted to wine-patches first. Enough rambling..
<a href="http://sourceforge.net/project/showfiles.php?group_id=6241">go
download.</a>
Index: wwn/wn20040109_204.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040109_204.xml,v
retrieving revision 1.5
diff -u -r1.5 wn20040109_204.xml
--- wwn/wn20040109_204.xml 26 Jan 2004 22:57:41 -0000 1.5
+++ wwn/wn20040109_204.xml 12 Dec 2004 19:57:45 -0000
@@ -492,7 +492,7 @@
startdate="01/08/2004"
>
<topic>Graphics</topic>
-<p>CodeWeaver's Aric Stewart put together some work he's
+<p>CodeWeavers' Aric Stewart put together some work he's
done to better support tablets:</p>
<quote who="Aric Stewart"><p>
Sorry all, This is way way way _way_ overdue. But it is really the first
Index: wwn/wn20040123_206.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040123_206.xml,v
retrieving revision 1.4
diff -u -r1.4 wn20040123_206.xml
--- wwn/wn20040123_206.xml 6 Feb 2004 16:01:17 -0000 1.4
+++ wwn/wn20040123_206.xml 12 Dec 2004 19:57:35 -0000
@@ -110,7 +110,7 @@
<p>CodeWeavers announced a new initiative this week to help software
vendors port applications to Linux. Jeremy White also started a thread
about part of this on wine-devel, I'll cover that next (which will clear
-up some details concerning it.) CodeWeaver's
+up some details concerning it.) CodeWeavers'
<a href="http://www.codeweavers.com/site/about/general/press/?id=20040120">announced
the CodeWeavers Desktop Linux Certification Program</a> on Tuesday. From
the press release:</p>
Index: wwn/wn20040130_207.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040130_207.xml,v
retrieving revision 1.3
diff -u -r1.3 wn20040130_207.xml
--- wwn/wn20040130_207.xml 6 Feb 2004 16:01:17 -0000 1.3
+++ wwn/wn20040130_207.xml 12 Dec 2004 19:56:55 -0000
@@ -93,7 +93,7 @@
enddate="01/30/2004"
>
<topic>News</topic>
-<p>Last week we announced the creation of CodeWeaver's
+<p>Last week we announced the creation of CodeWeavers'
<a href="c4.codeweavers.com">C4</a> project. After just
one week it's interesting to go back and look at
@@ -268,7 +268,7 @@
interesting stat to look are the increases in mailing list messages. Over
the same period where the amount of source code has grown quicker than the
5 year trend we've seen a corresponding increase in posts to both wine-patches
-and wine-devel. Until recently, CodeWeaver's patches haven't really appeared
+and wine-devel. Until recently, CodeWeavers' patches haven't really appeared
on wine-patches. Alexandre did the merges directly.
</p><p>
Does that make us the largest open source project without an official release?
Index: wwn/wn20040806_234.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20040806_234.xml,v
retrieving revision 1.3
diff -u -r1.3 wn20040806_234.xml
--- wwn/wn20040806_234.xml 2 Sep 2004 19:09:22 -0000 1.3
+++ wwn/wn20040806_234.xml 12 Dec 2004 19:55:54 -0000
@@ -95,7 +95,7 @@
<p>Also appearing in the news this week was more vaporous discussion of
<i>Project David</i>. Network World Fusion
<a href="http://www.nwfusion.com/news/2004/0803linuxstart.html">reported
-more details</a> on the project, including some quotes from CodeWeaver's
+more details</a> on the project, including some quotes from CodeWeavers'
Jeremy White:</p>
<quote who="Jeremy White"><p>
Part of the problem has been the secrecy surrounding the David development,
Index: wwn/wn20041001_242.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20041001_242.xml,v
retrieving revision 1.2
diff -u -r1.2 wn20041001_242.xml
--- wwn/wn20041001_242.xml 6 Oct 2004 15:05:11 -0000 1.2
+++ wwn/wn20041001_242.xml 12 Dec 2004 19:55:38 -0000
@@ -69,7 +69,7 @@
Namely, how can you get new users to use Linux without having a lot of
applications available; and likewise, how can you get a lot of applications
without a large userbase? The article sums up some of Linux's strengths
-and areas that do migrate easily. Some quotes from CodeWeaver's Jeremy White
+and areas that do migrate easily. Some quotes from CodeWeavers' Jeremy White
are included in the discussion.
</p>
Index: wwn/wn20041015_244.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20041015_244.xml,v
retrieving revision 1.3
diff -u -r1.3 wn20041015_244.xml
--- wwn/wn20041015_244.xml 10 Nov 2004 00:23:31 -0000 1.3
+++ wwn/wn20041015_244.xml 12 Dec 2004 19:57:22 -0000
@@ -415,7 +415,7 @@
<topic>Multimedia</topic>
<p>Hell may not be freezing over, but the temperature dropped
a little this past week: some patches from Jeremy White,
-CodeWeaver's CEO, made it into Wine. This isn't the first
+CodeWeavers' CEO, made it into Wine. This isn't the first
time it's happened, though as Jeremy likes to point out, his patches
usually find their way to Alexandre's patch dumpster based on
comment style alone. One in question generated some discussion
Index: wwn/wn20041029_246.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20041029_246.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20041029_246.xml
--- wwn/wn20041029_246.xml 29 Oct 2004 05:40:39 -0000 1.1
+++ wwn/wn20041029_246.xml 12 Dec 2004 23:08:32 -0000
@@ -140,7 +140,7 @@
<quote who="Juan Lang">
No. Generally, creating static libs is something we
avoid in wine. More specifically, these functions are
- already exported by advapi32, and you already link
+ already exported by advapi32, and you already link to
advapi32 (to get access to the registry) so there's no
advantage to having a copy in both places.</quote></p>
@@ -362,7 +362,7 @@
<p>Mike McCormack cautioned:</p>
<quote who="Mike McCormack"><p>
-GradientFill is pretty slow, as it files the rectangle line by line.
+GradientFill is pretty slow, as it fills the rectangle line by line.
I'm not sure how much this is going to slow down a normal application.
It used to draw pixel by pixel, and that was a very noticable
slowdown... line by line is much faster than that, but it still may
@@ -456,7 +456,7 @@
might find helpful:</p>
<quote who="Nikolas"><p>
While browsing the web i found a little tool which i expect to be quite
-helpfull: the opengl extension viewer. Though its written for windows,
+helpful: the opengl extension viewer. Though it's written for windows,
it runs perfectly on wine and allows people working on d3d and so on to
have a quick overview of the functions.
</p><p>
Index: wwn/wn20041105_247.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20041105_247.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20041105_247.xml
--- wwn/wn20041105_247.xml 7 Nov 2004 00:03:12 -0000 1.1
+++ wwn/wn20041105_247.xml 12 Dec 2004 22:49:38 -0000
@@ -134,7 +134,7 @@
</section>
<section
title="InstallShield Status"
- subject="COM / Installshield status?"
+ subject="COM / InstallShield status?"
archive="http://www.winehq.com/hypermail/wine-devel/2004/10/0669.html"
posts="3"
startdate="10/31/2004"
@@ -147,10 +147,10 @@
years and we've gone from no-chance of installation to, well, a chance.
It led Dan Kegel to wonder what the current status on all this is,
<quote who="Dan Kegel">
-what's the current status of Installshield support,
+what's the current status of InstallShield support,
and how much work would it be to fully support
-Installshield-based installers? I don't see any
-open Installshield bug reports, maybe I should file
+InstallShield-based installers? I don't see any
+open InstallShield bug reports, maybe I should file
one against the apps I have that don't install at
the moment. (Or would that be overkill?)</quote>
</p><p>
@@ -217,7 +217,7 @@
<p>Alexandre replied,
<quote who="Alexandre Julliard">
- Actually I already did a similar hack in the Crossover tree; it's not
+ Actually I already did a similar hack in the CrossOver tree; it's not
merged because it's full of races (which at first glance seems to be
the case with yours too).
</quote></p>
@@ -300,7 +300,7 @@
the caveat and also answered Andi's question:</p>
<quote who="Michael Stefaniuc"><p>
There are plenty of signals available to applications besides SIGUSR1
-and SIGUSR2. This are the real time signals in the range SIGRTMIN ...
+and SIGUSR2. These are the real time signals in the range SIGRTMIN ...
SIGRTMAX specified by POSIX 1003.1-2001. The only main difference to the
"normal" signals is that these signals can be queued.
</p><p>
@@ -315,7 +315,7 @@
</p><p>
The question now is how portable this is. Linux has SIGRTMIN ...
SIGRTMAX at least in the 2.4 and 2.6 kernels, Solaris and Irix (from
-Google hits) seem to have it too, but i don't know about the *BSD
+Google hits) seem to have it too, but I don't know about the *BSD
variants including Darwin.
</p></quote>
@@ -367,7 +367,7 @@
I think the way is to leave the original headers on there, and add the
LGPL header above it, perhaps with a note saying something like:
<ul>
-<code>/* This file was derived from code written by Tom St. Denis which the
+<code>/* This file was derived from code written by Tom St. Denis with the
following license: */</code></ul></p></quote>
<p>With regard to cutting down code, Mike explained:</p>
<quote who="Mike McCormack"><p>
@@ -376,12 +376,12 @@
isn't relevant to the WIN32 platform.
</p><p>
It's likely that the code will diverge from libtomcrypt over time
-anyway, and there maybe be win32 "features" that we wish to implement...
+anyway, and there may be win32 "features" that we wish to implement...
NSAKEY anybody? ;)
</p></quote>
<p>Alexandre thought removing any unnecessary code was desirable
-as a long as it was a noticable amount. </p>
+as a long as it was a noticeable amount. </p>
</section>
@@ -397,9 +397,9 @@
<p>Years ago Wine was often criticized and the
argument usually sounded something like, <i>"Windows
-is evil therefore Wine is evil."</i>. Hearing
+is evil therefore Wine is evil"</i>. Hearing
that gets boring pretty quick and a few years
-ago we put together two article about
+ago we put together two articles about
<a href="http://www.winehq.com/site/why">why Wine
is important</a> and
<a href="http://www.winehq.com/site/myths">debunking
@@ -435,7 +435,7 @@
I am a pure Linux user; I began my migration a year and a half ago,
moving from a dual-boot, to a multi-boot (2 versions of Windows and 5
distributions of Linux on one system), and finally ditched all alternate
-boots except the Linux a few months ago.
+boots except the Linux one a few months ago.
</p><p>
So I'm not all that far from the migration mindset, since I used Windows
for over 10 years, but as a pure Linux user, I'm not all that close to
@@ -537,7 +537,7 @@
source for success stories,
<quote who="Scott Ritchie">
This exact story is on the CodeWeavers page somewhere, as an
- advertisement for Crossover. At the least, read it first :)
+ advertisement for CrossOver. At the least, read it first :)
</quote></p>
<p>Anyone out there have a success story they'd like to
Index: wwn/wn20041112_248.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20041112_248.xml,v
retrieving revision 1.2
diff -u -r1.2 wn20041112_248.xml
--- wwn/wn20041112_248.xml 14 Nov 2004 18:28:00 -0000 1.2
+++ wwn/wn20041112_248.xml 12 Dec 2004 19:56:32 -0000
@@ -99,9 +99,9 @@
Wine <a href="http://appdb.winehq.org">AppDB</a> this week and added
support for maintainers. One problem with the database is simply
keeping it up to date. The hope is that people will sign up to become
-maintainers of an application and then make sure comments are up to date
-and any other relevant info. This is actually quite similar to how
-CodeWeaver's
+maintainers of an application and then make sure comments and any other
+relevant info are up to date. This is actually quite similar to how
+CodeWeavers'
<a href="http://www.codeweavers.com/site/compatibility/">Compatibility
Center</a> works. For instance, if you check out Wine's page on
<a href="http://appdb.winehq.org/appview.php?appId=10&versionId=67">
@@ -111,11 +111,11 @@
</p><p>
If you regularly use an application it would really help to maintain
a page in the AppDB. The time commitment is minimal and it could really
-help others. For instance, on the Word 2000 you'll find something like
-136 comments. A bunch of them are from 2001 one and clearly aren't
+help others. For instance, on Word 2000 you'll find something like
+136 comments. A bunch of them are from 2001 and clearly aren't
relevant. There's also no screenshot. By maintaining the app you
can clean up the comments, post comments of your own, and soon you'll
-be able to add your own screenshot. Lastly, if you're a PHP hacker
+be able to add your own screenshots. Lastly, if you're a PHP hacker
you might be interested in working on the AppDB itself. If so,
contact <a href="mailto:chmorgan_at_charter.net">Chris Morgan</a>. </p>
@@ -158,7 +158,7 @@
</p></quote>
<p>That makes a lot of sense. If you think about it though,
-Wine also has a NTDLL and we also have a Direct3D implementation
+Wine also has an NTDLL and we also have a Direct3D implementation
so in theory you could use those instead of the native Windows
ones. It just so happens Dimi Paun spent some time doing a
Winelib port. He reported this week,
Index: wwn/wn20041119_249.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20041119_249.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20041119_249.xml
--- wwn/wn20041119_249.xml 19 Nov 2004 21:01:58 -0000 1.1
+++ wwn/wn20041119_249.xml 12 Dec 2004 14:36:10 -0000
@@ -89,7 +89,7 @@
Office was released this week. This time the version number was bumped up to
4.0 to signify a major release. New applications are now supported which
the press release describes:</p>
-<quote who="Codeweavers"><p>
+<quote who="CodeWeavers"><p>
iTunes, which recently celebrated its 100 millionth music download,
allows users to import music in AAC, MP3 or Apple Lossless formats
and convert unprotected WMAs to MP3. Users can sync with their iPod,
@@ -99,9 +99,9 @@
popular iTunes Music Store, accessible from iTunes, currently contains
more than 700,000 tracks and 450 independent labels with 30-second previews.
</p><p>
-Adobe Framemaker (www.adobe.com) is an enterprise-class authoring and
+Adobe FrameMaker (www.adobe.com) is an enterprise-class authoring and
publishing solution that combines the simplicity of word processing
-with the power of XML. Framemaker support under CrossOver will allow
+with the power of XML. FrameMaker support under CrossOver will allow
Linux users to develop professional-looking documents for both print
and the web.
</p><p>
@@ -160,7 +160,7 @@
<quote who="Jesse Allen"><p>
For the past two weeks I've been tracking an issue that I found with kernels
greater than 2.6.8 / 2.6.8.1 and wine. Starting with kernel 2.6.9-rc1,
-Warcraft III copy protection would not work -- ie please insert disc. I found
+Warcraft III copy protection would not work -- i.e. please insert disc. I found
changes to the cdrom driver in rc1. Reversing them did not work. For a while
I was lost to what could have changed. Then I had an idea: search for
changes that could affect the way processes run. That led me to reverse
@@ -224,18 +224,18 @@
<ul>
<li> the handler is wine's implementation to send the single step event to wineserver</li>
<li> our code implies that the handler is not seen from wineserver (basically, that
-after executing the single step, the debugging event is sent to wine server)</li>
+after executing the single step, the debugging event is sent to wineserver)</li>
</ul></p><p>
To sum up, it's not a wine bug nor a linux bug, it's just a change in linux
behavior that breaks wine. Linux's new approach is to say a signal handler is part
of the application, and should be traced (in a debugger for example) as a
-regular function. Wine sees signal handler (at least SIGTRAP, SIGSEGV...) as
+regular function. Wine sees signal handlers (at least SIGTRAP, SIGSEGV...) as
kernel plugs put in the application (NTDLL) and used to send back information to
Wine server. Those two options are not compatible.
</p><p>
IMO, the best option would be to add an option to turn on/off the behavior in
ptrace (to allow or not single stepping in signal handlers).
-Fixing Wine would be doable, but somehow ugly (ie it would mean turning the TF
+Fixing Wine would be doable, but somehow ugly (i.e. it would mean turning the TF
off in Wine server to let our handlers run...)
</p></quote>
@@ -271,7 +271,7 @@
<p>Profiling has been a topic that's popped up from time
to time as being an area Wine needs to tackle. Some of
the major architectural issues, such as DLL separation
-and stabilizing wineserver, have been slowly become reality.
+and stabilizing wineserver, have been slowly becoming reality.
What's now evident is there are bottlenecks that could
be identified leading to an increase in performance.
Brian Gunlogson started a thread this week about just
@@ -329,7 +329,7 @@
<p>Jason Edmeades outlined the current direction of Direct3D:</p>
<quote who="Jason Edmeades"><p>
-Firstly thanks for the profiling info - its something I have been waiting to
+Firstly thanks for the profiling info - it's something I have been waiting to
try when I get through the d3d9 changes. We have always known that routine
was bad (hence the name 'slow'!) but that confirms it.
</p><p>
@@ -365,7 +365,7 @@
startdate="11/16/2004"
enddate="11/17/2004"
>
-<topic>Codeweavers</topic>
+<topic>CodeWeavers</topic>
<p>Almost every thread covered in the Wine Weekly News comes
from the
<a href="http://www.winehq.com/hypermail/wine-devel/">wine-devel</a> mailing list.
@@ -384,7 +384,7 @@
When adding files to the library, the dialog box that is up showing the
progress of the import is supposed to be an application modal box,
which, should stop you from bringing the iTunes app to the forefront but
-you can, requiring an ALT+TAB to bring it the dialog to the front.
+you can, requiring an ALT+TAB to bring the dialog to the front.
</p><p>
Still receiving the the error about the CD/DVD burning driver not being
installed properly. I know it is not supported, but there must be some
@@ -404,8 +404,8 @@
mechanics in how it delivers sound to the audio system (and Wine's
audio system is imperfect, at best).
</p><p>
-You can improve the situation in several ways; the faqs on Quicktime
-sound settings can help (set Quicktime sound output to waveOut
+You can improve the situation in several ways; the faqs on QuickTime
+sound settings can help (set QuickTime sound output to waveOut
and to the sound frequency supported by your sound card, which
might be 48khz). Also, the mini player seems less affected
(although it's still not great).
@@ -418,7 +418,7 @@
changes (Linux timing is different than that of Windows,
to my dismay).
</p><p>
-Mike and Alexandre and I worked on this all through the weekend
+Mike, Alexandre and I worked on this all through the weekend
and could not get to the bottom of it; Mike and Alexandre
are continuing on in the hope that we can have a fix.
</p><p>
@@ -480,13 +480,13 @@
<quote who="Roderick Colenbrander"><p>
Now that I have thought about it a while longer perhaps it is the right idea
to already start using uxtheme. If I remember correctly uxtheme is already
- usable the only problem is that we don't use it to actually modify the look
+ usable, the only problem is that we don't use it to actually modify the look
of wine widgets. Kevin Koltzau, the original uxtheme author, made the dll
able to parse original windows xp themes and further he used it to theme his
- own app with it (atleast the color part). It might be a good idea to stick
+ own app with it (at least the color part). It might be a good idea to stick
to the old wine colors and add a winelook uxtheme option. When the option is
enabled we use uxtheme to parse a theme file and it will then adjust the
- colors. The theme file will be then of the same type as the files used on
+ colors. The theme file would be of the same type as the files used on
windows, so you could even use windows themes. After this a gtk/qt backend
could be added to uxtheme.</p></quote>
@@ -497,7 +497,7 @@
loaded it can for example be used to load a bitmap and draw as for example
the background of a window or it can change the color of controls.
</p><p>
- Uxtheme can be used in two ways. Useally all theming is done by windows
+ Uxtheme can be used in two ways. Usually all theming is done by windows
itself. To do the theming microsoft ships a new version of the user and
common dialog dlls which use uxtheme to do the theming. In the other case
you can call uxtheme yourself and then you can decide yourself what you want
@@ -505,7 +505,7 @@
</p><p>
Not sure if I said it all correctly. Likely Kevin Koltzau knows it a bit
better as he is working on uxtheme. Not sure what the current status of the
- dll is but atleast our controls aren't using it for theming yet.
+ dll is but at least our controls aren't using it for theming yet.
</p></quote>
<p>The big issue with using uxtheme seems to center on Wine's controls
@@ -517,7 +517,7 @@
for Win95 it will always draw with the old style as it has no manifest.
However, the color scheme of the theme will still be applied to all applications
</p><p>
-It is possible to add a a manifest for an existing application without modifying
+It is possible to add a manifest for an existing application without modifying
the executable by placing a <app>.exe.manifest file in the same directory
as the application executables, but your mileage may vary on this approach.
</p><p>
@@ -584,7 +584,7 @@
first, which isn't trivial out here... So yes, updates are going to
be a bit painful over the next couple of weeks. The good news is that
it's all part of an evil plan to prevent Jer from getting in touch
- with me so that I can concentrate on the wm [<i>ed note: window manager</i>]
+ with me so that I can concentrate on the wm [<i>ed note: window management</i>]
work for a while <g>
</quote></p>
Index: wwn/wn20041126_250.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20041126_250.xml,v
retrieving revision 1.2
diff -u -r1.2 wn20041126_250.xml
--- wwn/wn20041126_250.xml 26 Nov 2004 09:01:26 -0000 1.2
+++ wwn/wn20041126_250.xml 12 Dec 2004 13:13:44 -0000
@@ -154,7 +154,7 @@
cases Wine would need to use something like this:</p>
<quote who="Eric Pouech"><p>
we have (to control what's generated inside the
-various exception) to ptrace from our NT-kernel-like process (the ptracer) to
+various exceptions) to ptrace from our NT-kernel-like process (the ptracer) to
get the context of the exception. Restart from the ptracer is done with
PTRACE_SINGLESTEP.</p></quote>
@@ -296,12 +296,12 @@
old kernel and then under a new one. Eric Pouech went through them
and deciphered the differences:</p>
<quote who="Eric Pouech"><p>
-For the linux folks, here a small comparison of what happens in the working
+For the linux folks, here is a small comparison of what happens in the working
(old) case and in the non-working (new) case:
</p><p>
-In both case
+In both cases
<ol>
-<li> Wine gets a first SIGTRAP (in it's sig_trap handler)
+<li> Wine gets a first SIGTRAP (in its sig_trap handler)
<ul>
<li> Wine converts it into a Windows exception (w-exception in short).
This includes creating a context for the generic CPU registers</li>
@@ -317,7 +317,7 @@
the SIGTRAP.</li>
<li> Wine server wait4:s on the SIGSTOP (after ptrace:attach)</li>
<li> modify (with ptrace) the debug registers</li>
- <li>> and resumes excution (ptrace: cont)</li></ul>
+ <li> and resumes execution (ptrace: cont)</li></ul>
</li>
<li> wine terminates the sig trap handler and resumes the execution with
the modified basic registers (from the saved context), and the
@@ -326,10 +326,10 @@
<li> a second sig trap is generated
<ul><li> since the wine server is still ptrace:attached, it gets the signal.</li></ul>
</li></ol></p><p>
-What differs then in both execution:
+What differs then in both executions:
in the working case, the sig trap handler is called on the client side,
whereas it's never called in the non-working case. We do have a couple of
-protection (to avoid some misbehaving apps), but none of them get triggered. So
+protections (to avoid some misbehaving apps), but none of them gets triggered. So
it seems like the trap handler is not called (ugh).
</p><p>
A couple of notes:
@@ -392,8 +392,8 @@
<ol>
<li> There were a lot of old hacks in the package that are probably no
longer necessary, due to advancements in wine like wineprefixcreate and
-such. There was also the remenants of a very old problem with compiling
-using flex (which I remember experiencing the old days) in the form of a
+such. There was also the remnants of a very old problem with compiling
+using flex (which I remember experiencing in the old days) in the form of a
special exception for installing newer flex packages.</li>
<li> Very old packages like winesetuptk should now be officially obsoleted
@@ -413,12 +413,12 @@
These are all things that should be included in the build dependencies
for the package.</li></ol>
</p><p>
-So far, my list of build dependant packages is the following:
+So far, my list of build dependent packages is the following:
flex, bison, libx11-dev, libasound2-dev, libxt-dev, libicu28-dev
</p><p>
However, I'm not sure if this means the wine binary package should
depend on them, since it's compiled in. So, should I make libicu28 a
-dependancy for wine?
+dependency for wine?
</p><p>
Now, this leads to the question: is it worth even having a package
maintainers guide? If so, who wants to update it?
@@ -460,7 +460,7 @@
needed.
</p><p>
It's not just my script. Wine and Windows programs sometimes assume these
-applets are present too (eg notepad, wineboot, regedit, regsvr32).
+applets are present too (e.g. notepad, wineboot, regedit, regsvr32).
</p><p>
The packaging on Red Hat/SuSE/Mandrake etc didn't have this problem
because they mostly followed upstream conventions.
@@ -593,7 +593,7 @@
.... and of course, the big cheese ....
<ul>
-<li> Write the migration code to pull the users current config across to the
+<li> Write the migration code to pull the user's current config across to the
new registry branch so we can actually start thinking about switching
the config file off once and for all. Bonus points for adding an
explanation of what happened to the old config file itself!
@@ -604,7 +604,7 @@
<p>Robert then presented a dilemna:</p>
<quote who="Robert van Herk"><p>
-Thanks to Mike's help, I succeeded in showing a SHBrowseForFolder
+Thanks to Mike's help, I succeeded in showing an SHBrowseForFolder
thingy, in the winecfg program, so that people can pick a directory they
want to use as virtual C drive.
</p><p>
@@ -633,27 +633,27 @@
OK, so how to do this? I see 3 ways:
<ol>
-<li> Implement an extra api that do the same as the normal file open/save
+<li> Implement an extra api that does the same as the normal file open/save
and browse for folder api, but then with the Unix file system</li>
<li> Implement a thread local variable so that threads can put the Wine
file dialogs into unix file system mode / windows file system mode</li>
<li> Define some magic wine flags in the file dialogs that make the
dialogs appear in Unix mode</li></ol></p><p>
-There are some pro's and con's to all of them:
+There are some pros and cons to all of them:
<ol>
<li> Well, basically, we have to make an extra api :-), so there are more
functions exported. Probably the existing and new functions will need to
call each other, so this means an extra level of indirection.</li>
<li> Kinda ugly hacking, though we don't loose win32 compatibility</li>
<li> Nice, but we loose strict win32 compatibility, since there will be a
-magic flags that doesn't exist in win32.</li></ol></p></quote>
+magic flag that doesn't exist in win32.</li></ol></p></quote>
<p>Mike suggested the 3rd approach,
<quote who="Mike Hearn">
This is the most lightweight so I'd go for it for now. If we find that the
flag value we pick is already in use we can just change it, no big deal.
-We already use custom Wine flags in other parts of the code (eg
+We already use custom Wine flags in other parts of the code (e.g.
WS_EX_TRAYWINDOW).</quote></p>
</section>
@@ -679,11 +679,11 @@
<quote who="Mike McCormack"><p>
RICHEDIT_CLASS20A is provided by riched20.dll, not riched32.dll. The
windows 2000 implementation uses riched20.dll to implement riched32.dll
- (ie. moves the richedit code to riched20.dll and implements the
+ (i.e. moves the richedit code to riched20.dll and implements the
RICHEDIT_CLASS10A class using the new RICHEDIT_CLASS20A class.
</p><p>
In short, the existing code registers the correct class name, but we
-need to make a new dll dlls/riched20, and do alot of work on the
+need to make a new dll dlls/riched20, and do a lot of work on the
richedit control :)
</p><p>
Actually, since we need to work on riched20, we might as will implement
@@ -728,7 +728,7 @@
it:</p>
<quote who="Mike McCormack"><p>
We have an empty implementation of riched20 that simply forwards
-requests to edit. That is the wrong, and the existing riched32 code is
+requests to edit. This is the wrong way, and the existing riched32 code is
broken too (since it uses the edit control).
</p><p>
CrossOver's riched20 code is attached... it's a quick and easy way to
Index: wwn/wn20041203_251.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20041203_251.xml,v
retrieving revision 1.2
diff -u -r1.2 wn20041203_251.xml
--- wwn/wn20041203_251.xml 3 Dec 2004 21:52:03 -0000 1.2
+++ wwn/wn20041203_251.xml 9 Dec 2004 16:57:45 -0000
@@ -127,7 +127,7 @@
to Wine development for anybody who has been lurking on the sidelines and
wants to get involved.
</p><p>
-As usual no guarantees these patches would be accepted, that's Alexandres
+As usual no guarantees these patches would be accepted, that's Alexandre's
call. But they probably would be, and you'll learn something while doing
them! :)
</p><p>
@@ -138,7 +138,7 @@
explanation of how to do this.
<br /><br />
I think it'd be ok to grab $HOME using the UNIX getenv() and then using
-the libwine APIs to map them to a Win32 path. If the mapping fails (ie
+the libwine APIs to map them to a Win32 path. If the mapping fails (i.e.
$HOME is not accessible given the users dosdevices) then just fail with a
WARN().
</ul></p><p>
@@ -168,7 +168,7 @@
Task 3:<ul>
The freedesktop.org icon theme specification shows us how to find icons
- for many different types of thing. Implement support for loading and
+ for many different types of things. Implement support for loading and
using the following icons from the icon theme (it should be OK to use
native libraries for this like GdkPixbuf, just fall back to the compiled
in defaults if it's missing):
@@ -183,7 +183,7 @@
mime types not extensions, and it'd make our file dialogs even slower than
they already are.
<br /><br />
- You may be tempted to use eg, libpng to implement this. Don't! Use
+ You may be tempted to use e.g., libpng to implement this. Don't! Use
GdkPixbuf instead, stock icons are allowed to be in many formats including
SVG.
<br /><br />[<i>ed note: and later he added...</i>]
@@ -205,7 +205,7 @@
</ul></p><p>
Task 5:<ul>
-Try improving the winebrowser script to take into account the users
+Try improving the winebrowser script to take into account the user's
preferred applications. At the moment it just tries every browser it
knows about in a hard coded order. Hint: in modern GNOME desktops you can
use the "gnome-open" program to make this automatic. There is a KDE
@@ -225,16 +225,16 @@
<p>Alban Browaeys had a suggestion for task #4:</p>
<quote who="Alban Browaeys"><p>
- wineshelllink support update-menu which itself build xdg complient menu
- (via /etc/menu-methos/menu-xdg).
+ wineshelllink supports update-menu which itself builds xdg compliant menus
+ (via /etc/menu-methods/menu-xdg).
</p><p>
I know mandrake and debian distro use "menu", need confirmation for
RH/Novell newest releases.
</p><p>
It would be more elegant to let menu manage gnome/kde/xgd/wmaker ... than
- reimplementing them in wineshellink . The strongest point is that menu
+ reimplementing them in wineshelllink . The strongest point is that menu
build menu via methods which are tweakable by distro builder. Thus it will
- avoid to upgrade wineshellink whenever we want ot support gnustep xdg
+ avoid to upgrade wineshelllink whenever we want to support gnustep xdg
version 12 and the like.</p></quote>
<p>Steven Edwards added another idea:</p>
@@ -270,7 +270,7 @@
With Z: mapped to /
</code> </ul></p><p>
I selected KMail as the default Mail application, and when I open an Mail
-Address in MSIE kmail pops up. The same happens when I enter a maito: address
+Address in MSIE kmail pops up. The same happens when I enter a mailto: address
in Task Manager->New task.</p></quote>
<p>Then Mike came up:</p>
@@ -310,7 +310,7 @@
where, at a designated time, a group of wine developers would get
together on #winehackers (or some other channel). We would pick a bug
(or maybe more) from wine's bug tracker and work together to fix the
- bug(s). This would serve several good purposed. First, we would be
+ bug(s). This would serve several good purposes. First, we would be
giving more attention to wine's bugzilla and getting rid of a lot of
those bugs. Second, many newcomers can witness and take part in the
wine development process. I'm sure everyone can remember how daunting
@@ -335,14 +335,14 @@
<p>Tony Lambregts expanded on some of those ideas:</p>
<quote who="Tony Lambregts"><p>
There is nothing wrong with fixing a bug for its own sake and any bug we fix
- will ultimately improve wine and provide some insites into debugging wine.
+ will ultimately improve wine and provide some insights into debugging wine.
</p><p>
That being said, I would agree that at least to some degree this should be a
- training execise and that whatever bug(s) we go after, some (budding?) developer
+ training exercise and that whatever bug(s) we go after, some (budding?) developer
would like to have fixed. However there should be a bug report in bugzilla so
that developers can research the bug in the first place and we can keep track of
what was done for these sessions. I have created a key word "BugBuster" in
- Bugzilla to keep track of candidates. Hopefully after several sesions we will
+ Bugzilla to keep track of candidates. Hopefully after several sessions we will
have a list of fixed bugs that new developers can use as a reference.
</p></quote>
@@ -425,7 +425,7 @@
<p>Mike encouraged Krzysztof to just make it available:</p>
<quote who="Mike McCormack"><p>
I have been working on richedit a little also, and am quite keen to get
-the ball rolling by having some richedit 2.0 code in winehq that others
+the ball rolling by having some richedit 2.0 code in winehq so that others
can help work on it. I'm quite interested to see the source for this.
</p><p>
Whether you show us or not, the copyright for the source still belongs
@@ -443,8 +443,8 @@
problems if you wish to incorporate other people's code.
</p><p>
Frankly speaking, people promising to release their source code "at a
-later date" is an impedement to development, because nobody is motivated
-to work on the promised feature in the mean time.
+later date" are an impedement to development, because nobody is motivated
+to work on the promised feature in the meantime.
</p><p>
Please consider "release early, release often", so we can work together
on this :)
@@ -467,7 +467,7 @@
announced:</p>
<quote who="Hajime Segawa"><p>
I changed the install script a bit and it does not depend on DCOM98,
-MFC4.0, etc... anymore. So, you can run IE6 completely out-of-box.
+MFC4.0, etc... anymore. So, you can run IE6 completely out-of-the-box.
</p><p>
New script is here :
<ul><a href="http://sidenet.ddo.jp/winetips/files/wine-config-sidenet-1.5.3.tgz">
@@ -510,9 +510,9 @@
<topic>Winelib</topic>
<topic>Ports</topic>
<p>Wine and Winelib, although intricately bound together, really
-serve two different audiences. Whereas Wine is normally use to just
+serve two different audiences. Whereas Wine is normally used to just
run existing Windows binaries, Winelib holds the promise of
-being able to take the source code to a Windows application
+being able to take the source code of a Windows application
and recompile it as a native application. In theory, Microsoft
could use it to make Word run on Solaris.
</p><p>
Index: wwn/wn20041210_252.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/wn20041210_252.xml,v
retrieving revision 1.1
diff -u -r1.1 wn20041210_252.xml
--- wwn/wn20041210_252.xml 11 Dec 2004 16:22:33 -0000 1.1
+++ wwn/wn20041210_252.xml 12 Dec 2004 23:41:38 -0000
@@ -117,7 +117,7 @@
Is this expected?</li></ol></p><p>
Buttom line: painting looks great, somehow it seems a bit
-better then before (in terms of correctness, but I can't
+better than before (in terms of correctness, but I can't
quite put my finger on it). If we can solve the speed issue,
we have a winner.</p></quote>
@@ -173,7 +173,7 @@
was hoping you would get rid of WS_EX_TRAYWINDOW instead of adding
even more uses of it.</quote></p>
-<p>Thet went back and forth a bit, then Mike agreed to make the changes.</p>
+<p>They went back and forth a bit, then Mike agreed to make the changes.</p>
</section>
<section
title="Header Cleanup"
@@ -194,7 +194,7 @@
files to be rebuilt, I whipped up a quick perl script to identify
unneeded header files. This series of patches is the result.
</p><p>
-There are a large number of uneeded includes, so these patches should
+There are a large number of unneeded includes, so these patches should
reduce your build time for those trying to stay current with cvs.
</p><p>
I have split the patches up on a per-dll basis to avoid merge
@@ -214,16 +214,16 @@
that break portability. Jon took that into account and described
what his changes were limited to:</p>
<quote who="Jon Griffiths"><p>
-I deliberately made my script remove only Wines own headers for this
+I deliberately made my script remove only Wine's own headers for this
reason. It will not remove system header files. I also manually
checked that nothing within an #ifdef block was deleted. So this
shouldn't cause any problems for other *nices.
</p><p>
If there is an issue it will be with mingw or VC++. But that would
-point out an incompatability in our headers with theirs, and that
+point out an incompatibility in our headers with theirs, and that
would be a good thing, IMHO.
</p><p>
-Yes, its a little crufty as-is. My reasoning is that anything that
+Yes, it's a little crufty as-is. My reasoning is that anything that
reduces my compile times after updates is good, and my laptop takes
quite a while to rebuild Wine, Minimising dependencies helps that.
</p><p>
@@ -276,7 +276,7 @@
the files that need them, then b) start removing the non-standard
headers (possibly much later).
</p><p>
-If so, thats probably a worthwhile project.</p></quote>
+If so, that's probably a worthwhile project.</p></quote>
<p>Alexandre explained a problem with that too,
<quote who="Alexandre Julliard">
@@ -294,16 +294,16 @@
since it will need to be added in again to the files that use the
private headers, I am suggesting removing the inclusion of winuser.h
from e.g. winpos.h and win.h, and including them in the files that
-need them directly. If we hide the source files dependencies in
-header files its impossible to remove any uneeded dependencies from
+need them directly. If we hide the source file dependencies in
+header files it's impossible to remove any unneeded dependencies from
them.
</p><p>
I'll post the script I'm using to clean up the headers and as the
private headers are removed (or periodically) it can be run to weed
-out any uneeded dependencies remaining.
+out any unneeded dependencies remaining.
</p><p>
In the meantime, I've updated my script to only remove headers that
-reduce a files dependencies and will be posting the revised patches
+reduce a file's dependencies and will be posting the revised patches
shortly.</p></quote>
</section>
@@ -320,18 +320,18 @@
<a href="http://appdb.winehq.org">AppDB</a> lately by
Tony Lambregts, Chris Morgan, and a newcomer, Jonathan Ernst.
It's actually picked up even more steam now that Chris has CVS access to
-WineHQ. This week Tony posted another patch and asned for comments:</p>
+WineHQ. This week Tony posted another patch and asked for comments:</p>
<quote who="Tony Lambregts"><p>
-Over two years ago this was discussed and the concensus at the time was that
+Over two years ago this was discussed and the consensus at the time was that
integrating the AppDB and Bugzilla would be a Good Idea (TM). This patch is my
attempt to get it started.
</p><p>
I am submitting this to wine devel first because I KNOW this patch can be
controversial. I have tried to make this patch as small as possible but it still
-covers quite a few files. I am using Globals and that should be improved. and I
+covers quite a few files. I am using Globals and that should be improved. And I
am sure there are other things that are wrong with it. ;^) Also the code in
preferences.php does not do anything except show that this works.
</p><p>
-Please try it out and get back to me..
+Please try it out and get back to me...
</p></quote>
</section></kc>
Index: wwn/interviews/interview_10.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/interviews/interview_10.xml,v
retrieving revision 1.3
diff -u -r1.3 interview_10.xml
--- wwn/interviews/interview_10.xml 16 Dec 2003 17:09:29 -0000 1.3
+++ wwn/interviews/interview_10.xml 12 Dec 2004 20:01:54 -0000
@@ -430,7 +430,7 @@
<question><p><i>BV:</i>
- It seems like CodeWeaver's has done some interesting work in
+ It seems like CodeWeavers has done some interesting work in
usability and integrating with different distros. Should it be up
to Wine to integrate with the desktop, or is that up to the
individual distributions?
Index: wwn/interviews/interview_4.xml
===================================================================
RCS file: /var/cvs/lostwages/wwn/interviews/interview_4.xml,v
retrieving revision 1.1
diff -u -r1.1 interview_4.xml
--- wwn/interviews/interview_4.xml 22 Apr 2003 14:35:33 -0000 1.1
+++ wwn/interviews/interview_4.xml 12 Dec 2004 20:02:09 -0000
@@ -352,7 +352,7 @@
<question><p><i>BV: </i>
In addition to everything else, you're pretty active on the
- CodeWeaver's support mailing lists. Does that consume a lot
+ CodeWeavers support mailing lists. Does that consume a lot
of your time? </p></question>
<answer><p><i>Jeremy:</i>
More information about the wine-patches
mailing list