Module: website
Branch: master
Commit: 2150589f3baceb21fad4dc63e5ae59ee382c6878
URL: http://source.winehq.org/git/website.git/?a=commit;h=2150589f3baceb21fad4dc…
Author: Francois Gouget <fgouget(a)free.fr>
Date: Wed Jan 23 20:13:27 2008 +0100
Assorted spelling fixes.
---
wwn/interviews/interview_5.xml | 2 +-
wwn/wn20010513_95.xml | 2 +-
wwn/wn20011125_109.xml | 2 +-
wwn/wn20011212_110.xml | 2 +-
wwn/wn20020530_124.xml | 2 +-
wwn/wn20020719_129.xml | 4 ++--
wwn/wn20020824_132.xml | 2 +-
wwn/wn20021206_147.xml | 2 +-
wwn/wn20030117_153.xml | 2 +-
wwn/wn20030124_154.xml | 2 +-
wwn/wn20040109_204.xml | 2 +-
wwn/wn20040206_209.xml | 2 +-
12 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/wwn/interviews/interview_5.xml b/wwn/interviews/interview_5.xml
index 52d9041..9d6f3a4 100644
--- a/wwn/interviews/interview_5.xml
+++ b/wwn/interviews/interview_5.xml
@@ -119,7 +119,7 @@ Since many years, Wine had an internal debugger. At the times when Wine
was a monolithic application (no separated DLLs, all Windows processes
running in the same Unix-address space), the internal debugger had a
direct access to all the memory (Wine internals, Windows-process
-memory). When Wine started to be splitted (wineserver to allow
+memory). When Wine started to be split (wineserver to allow
interprocess exchange, each (32bit) Windows-process having its own
unix-address space), debugger needed some heavy rewriting. Alexandre
Julliard wrote most of the Win32 debugging API (generation of debug
diff --git a/wwn/wn20010513_95.xml b/wwn/wn20010513_95.xml
index 4f1998f..5579d08 100644
--- a/wwn/wn20010513_95.xml
+++ b/wwn/wn20010513_95.xml
@@ -145,7 +145,7 @@ between the wineserver and the application with various kernel patches.
I was reading "Unix Network Programming, volume 2 - IPC" and ran over
a "doors" IPC api that is implemented on Solaris and has the lowest latency.
According to the book it is ~3 times faster than pipe.
-Actual values for Solaris 2.6 in the book are: (in miliseconds)</p>
+Actual values for Solaris 2.6 in the book are: (in milliseconds)</p>
<p><ul><code>
doors: 121<br />
sysv msgq: 260<br />
diff --git a/wwn/wn20011125_109.xml b/wwn/wn20011125_109.xml
index 800b162..41994c5 100644
--- a/wwn/wn20011125_109.xml
+++ b/wwn/wn20011125_109.xml
@@ -202,7 +202,7 @@ threw out some more ideas:</p>
</p><p>
In light of this you could argue that since, I presume, MIDL removes
whitespace and commments which is IIRC the only really expression,
- since the rest the API defintions are just facts, that the MIDL
+ since the rest the API definitions are just facts, that the MIDL
compiled files just contains facts not any part of the protected
expression.
</p><p>
diff --git a/wwn/wn20011212_110.xml b/wwn/wn20011212_110.xml
index 55fa4b0..c8e18c3 100644
--- a/wwn/wn20011212_110.xml
+++ b/wwn/wn20011212_110.xml
@@ -615,7 +615,7 @@ It's been a while, but I decided to try again in October.
At that time, there was an OLE error, but the only other strange
occurance was a 'locking' of the screen on a print preview.
</p><p>
-Since then, this 'locking' is the only issue (though I havn't yet
+Since then, this 'locking' is the only issue (though I haven't yet
attempted to print).
The apps I'm trying are my own, basically just a form is called, the
user puts in a date range, and a report is run. You can view the report
diff --git a/wwn/wn20020530_124.xml b/wwn/wn20020530_124.xml
index e164976..4a00156 100644
--- a/wwn/wn20020530_124.xml
+++ b/wwn/wn20020530_124.xml
@@ -287,7 +287,7 @@ minds. Vincent Beron went on to mention:</p>
<quote who="Vincent Beron"><p>
there are a lot (>20000) of lines which have either some spaces/tabs
or combination of both after the final ";" (or "," in the case of
- function arguments splitted on a couple of lines.)
+ function arguments split on a couple of lines.)
IMHO, it'd be better to remove them (although I admit it's mostly for
esthetics reasons).
</p><p>
diff --git a/wwn/wn20020719_129.xml b/wwn/wn20020719_129.xml
index 8a927e3..7964891 100644
--- a/wwn/wn20020719_129.xml
+++ b/wwn/wn20020719_129.xml
@@ -264,9 +264,9 @@ on Sparc:
</p>
<quote who="Shachar Shemesh"><p>
I'll try, but I only have solaris machines at work, and this is far from
- my main focus on Wine (I'm working on BiDi, if you remeber correctly
+ my main focus on Wine (I'm working on BiDi, if you remember correctly
;-). I am only looking into solaris at all because at work we use some
- windows compat library for solaris (don't remeber the name, but it
+ windows compat library for solaris (don't remember the name, but it
wasn't mainsoft's) for the GUI part of the product. I am sprinkling the
idea to the Unix GUI team here to check Wine out.
</p><p>
diff --git a/wwn/wn20020824_132.xml b/wwn/wn20020824_132.xml
index 6be4e73..f5de007 100644
--- a/wwn/wn20020824_132.xml
+++ b/wwn/wn20020824_132.xml
@@ -263,7 +263,7 @@ say which is the right way is to get something working.
mandatory BiDi support in Wine, as this means (among mere applying the
BiDi algorithm) translating each string printed to UTF-32 and back
(unless we can say for sure that no BiDi is going to be required -
- havn't found a really good algorithm for that yet, but I'm working on
+ haven't found a really good algorithm for that yet, but I'm working on
it). Not having the proper library on your machine is a pretty good way
of indicating that BiDi is not interesting to you (and is, more or less,
the way MS tackled the exact same dillema).</quote></p>
diff --git a/wwn/wn20021206_147.xml b/wwn/wn20021206_147.xml
index 32baf2a..9a90ea1 100644
--- a/wwn/wn20021206_147.xml
+++ b/wwn/wn20021206_147.xml
@@ -300,7 +300,7 @@ interested.
I currently have a working HTML Help viewer, which seems to work pretty
well on everything I've tested so far. It does however need some more work
to conform to the way the real HTML Help system works in Windows (eg, I
-havn't written an ActiveX control for it yet).
+haven't written an ActiveX control for it yet).
</p><p>
Currently the HTML Help viewer requires an IWebBrowser interface, and only
really works with an Internet Explorer installation - so I don't believe
diff --git a/wwn/wn20030117_153.xml b/wwn/wn20030117_153.xml
index d070491..1083013 100644
--- a/wwn/wn20030117_153.xml
+++ b/wwn/wn20030117_153.xml
@@ -212,7 +212,7 @@ some of the work he's been doing:</p>
I've been too busy lately (job hunting mostly, although I've also been
sick and bedridden lately) to do any more work on it, and I was really
waiting for Alexandre to comment on my question about C++ before going any
-further... I havn't seen a reply yet tho.
+further... I haven't seen a reply yet tho.
</p><p>
The current state of my local tree, besides being a mess, is that it has
most QT dependencies removed. Currently it uses a lot of QT stub's around
diff --git a/wwn/wn20030124_154.xml b/wwn/wn20030124_154.xml
index b0786ee..ca50ab3 100644
--- a/wwn/wn20030124_154.xml
+++ b/wwn/wn20030124_154.xml
@@ -660,7 +660,7 @@ I managed to install IE5.5 using the following procedure:
<li> I, personally, made two sessions. One downloading everything, and
the other for installing.</li>
<li> Install just the basic IE. No Connection wizard or anything else.</li>
- <li> When setup finshes (and you get an error in processing the reboot)
+ <li> When setup finishes (and you get an error in processing the reboot)
- wait for all wine instances to exit</li>
<li> run wineboot.</li>
<li> One of the programs initiated by wineboot fails to run (starts
diff --git a/wwn/wn20040109_204.xml b/wwn/wn20040109_204.xml
index 8bd255c..3bfaf56 100644
--- a/wwn/wn20040109_204.xml
+++ b/wwn/wn20040109_204.xml
@@ -134,7 +134,7 @@ instead of kernel32</li>
<li> file IO management can be cleanly separated between kernel32 and ntdll (1)</li>
<li> files/ directory could be removed (not done in the patch (also nuked
include/drive.h and include/file.h)</li>
-<li> homogenous drive & device handling (we no longer store those objects
+<li> homogeneous drive & device handling (we no longer store those objects
in the server). Drive and device are now standard file handles (from a
Windows point of view).</li>
<li> a few current Wine bugs have been fixed (see the todo_wine removed in
diff --git a/wwn/wn20040206_209.xml b/wwn/wn20040206_209.xml
index 5a72528..c71efaf 100644
--- a/wwn/wn20040206_209.xml
+++ b/wwn/wn20040206_209.xml
@@ -780,7 +780,7 @@ win9x, since it did not exist on nt4.</p></quote>
<p>Dimi thought that was odd,
<quote who="Dimitrie Paun">
That makes no sense: we get short names on a system (nt4) that
-fundamentally had long names. Shoudn't we get long names by
+fundamentally had long names. Shouldn't we get long names by
default in that case?</quote></p>
<p>Ove went into more detail:</p>
Module: website
Branch: master
Commit: f29b92376b5610ec51d98719bdcafa47f230856b
URL: http://source.winehq.org/git/website.git/?a=commit;h=f29b92376b5610ec51d987…
Author: Francois Gouget <fgouget(a)free.fr>
Date: Wed Jan 23 20:13:16 2008 +0100
wwn335: Spelling fixes.
---
wwn/wn20071217_335.xml | 38 +++++++++++++++++++-------------------
1 files changed, 19 insertions(+), 19 deletions(-)
diff --git a/wwn/wn20071217_335.xml b/wwn/wn20071217_335.xml
index f96332d..5b39640 100644
--- a/wwn/wn20071217_335.xml
+++ b/wwn/wn20071217_335.xml
@@ -155,7 +155,7 @@ the actual conversation!</p>
<p>
So, a bit of background on these funky acronyms before we dive into the
thread itself (Most of the info from
-<a href="http://wikipedia.org">wikipedia</a></p>
+<a href="http://wikipedia.org">wikipedia</a>):</p>
<quote><p>
<a href="http://en.wikipedia.org/wiki/GLSL">GLSL</a> (Open<b>GL</b>
<b>S</b>hading <b>L</b>anguage): also known as GLslang, is a high level
@@ -176,15 +176,15 @@ in making use of advanced GPU programmability features.
</p></quote>
<p>
The issue is that writing shaders can often be complicated and difficult.
-So GLSL was born, a higher level shading language to hopeuflly make
-programming these things easier. HLSL is another lanuage, similar to GLSL,
+So GLSL was born, a higher level shading language to hopefully make
+programming these things easier. HLSL is another language, similar to GLSL,
from Microsoft; and the translation of HLSL to something workable with
Linux/BSD etc. will be necessary to continue WineD3D. How this will happen
is the subject of this wine devel discussion:
</p>
<quote>
<p>
-hlsl2glsl is the good solution for implementing shaders on directX 10.
+hlsl2glsl is the right solution for implementing shaders on directX 10.
Nevertheless, the hlsl compilation to tokens has to be done for d3d9. On
the other hand, if we implement d3dx9_xx, it is likely that the
application will be using the compile D3DX9CompileShader to get the
@@ -221,7 +221,7 @@ and the most feasible way to implement it I've heard so far would be
to embed GLSL code a comment section inside the shader byte code,
which would be rather ugly.<br /><br />
<br /><br />
-And finally, the actual hardware has it's own hardware specific
+And finally, the actual hardware has its own hardware specific
language for shaders. HLSL or D3D bytecode isn't really any closer to
the actual hardware language than GLSL or ARB asm, so it isn't even
guaranteed to gain us much.
@@ -231,7 +231,7 @@ guaranteed to gain us much.
Keep in mind that getting shaders translated into GLSL, which we can then send
to the card, is only a small part of the whole dx10 topic. We will need our
-own codepath anyway(HLSL -> d3d asm -> GLSL). We have to investigate wether a
+own codepath anyway(HLSL -> d3d asm -> GLSL). We have to investigate whether a
direct HLSL -> GLSL path will gain us any performance. We can optimize the
HLSL -> d3d asm ourselves, and the d3d asm->GLSL->card native code is
lossless in theory. If the GLSL compiler is good, then it will recognise the
@@ -258,20 +258,20 @@ idea, and immediatly caught my attention:
<p>
Hello to all.<br />
<br />
-I have something in mind that I would like to ask to Wine developers.
+I have something in mind that I would like to ask Wine developers.
Is it possible using a hack/trick or a hidden option to change the
-name of wine in the proccess lists?
-I mean, Is it possible to list 'wine' proccess as, for example
+name of wine in the process lists?
+I mean, is it possible to list 'wine' process as, for example
'iexplorer' when I use Internet Explorer under Wine?
<br />
-Thanks a lot for your work, hope my question find the answer here.
+Thanks a lot for your work, hope my question finds the answer here.
</p>
</quote>
<p>
-Apparently this had been thought up of before: Stefan Dosinger writes in:
+Apparently this had been thought of before: Stefan Dosinger writes in:
</p>
<p><quote>
-This is done since quite some time. apps are usually called "iexplore.exe", or
+This is done since quite some time. Apps are usually called "iexplore.exe", or
they have the name of the file that was passed to wine, like C:\Program
Files\Internet Explorer\iexplore.exe
@@ -280,7 +280,7 @@ outdated version of wine.
</quote>
</p>
<p>
-Apparently, this already existed! Alright, so whats the deal? Apparently
+Apparently, this already existed! Alright, so what's the deal? Apparently
it only works on linux! Poor Gonzalo is on FreeBSD. Stefan writes in with
the unfortunate news:
</p>
@@ -288,10 +288,10 @@ the unfortunate news:
Ow, ah, this is a different business. I think we use some Linux-only feature
to set the name, and Alexandre told me that at least MacOS doesn't have it. I
have no idea if there is a way to change the process name under BSD. If there
-is, feel free to implement it and send a patch
+is, feel free to implement it and send a patch.
</p></quote>
<p>
-There are of course ways to do this on FreeBSD, Alex Juillard lets us know
+There are of course ways to do this on FreeBSD, Alexandre Julliard lets us know
that it may be possible:
</p>
<quote><p>
@@ -299,14 +299,14 @@ I wouldn't [accept a hack which involves copying the process to /tmp], but
on FreeBSD you can use setproctitle() for this.
</p></quote>
<p>
-Another important point brought up later in this thread, is that its not wise
-to killall wineserver or killall explorer.exe. Its much smarter to
+Another important point brought up later in this thread, is that it is not wise
+to killall wineserver or killall explorer.exe. It's much smarter to
"wineserver -k". L Rahyen writes:
</p>
<quote><p>
wineserver -k
<br /><br />
- This kills all processes which belongs to current WINE prefix (as
+ This kills all processes which belong to current WINE prefix (as
specified
in WINEPREFIX environment variable or ~/.wine otherwise). For me this works
in 100% of cases so I see no problem here.
@@ -349,7 +349,7 @@ IF this is true, WHY?
<br /><br />
Rich
</p></quote>
-<p>This indeed doesn't seem to make sense; alas we recieve the voice of
+<p>This indeed doesn't seem to make sense; alas we receive the voice of
reason and policy. Bryan Haskins writes:</p>
<quote><p>
It really depends on the case, if a program is entirely superseded by
Module: website
Branch: master
Commit: 29d4691321b85ecc1ff70de6853c5443081d389e
URL: http://source.winehq.org/git/website.git/?a=commit;h=29d4691321b85ecc1ff70d…
Author: Francois Gouget <fgouget(a)free.fr>
Date: Wed Jan 23 20:13:10 2008 +0100
wwn334: Spelling fixes.
---
wwn/wn20071210_334.xml | 60 ++++++++++++++++++++++++------------------------
1 files changed, 30 insertions(+), 30 deletions(-)
diff --git a/wwn/wn20071210_334.xml b/wwn/wn20071210_334.xml
index e65a51d..ca43aba 100644
--- a/wwn/wn20071210_334.xml
+++ b/wwn/wn20071210_334.xml
@@ -6,7 +6,7 @@
<author contact="http://www.bluesata.com">Zachary Goldberg</author>
<issue num="334" date="12/10/2007" />
<intro> <p>This is the 334 issue of the Wine Weekly News publication.
-Its main goal is to introduce the new AppDB Status changer
+Its main goal is to introduce the new AppDB Status changer.
It also serves to inform you of what's going on around Wine.
Wine is an open source implementation of the Windows API on top of X and Unix.
Think of it as a Windows compatibility layer. Wine does not require Microsoft
@@ -90,7 +90,7 @@ available. You can find more info at
<topic>Wine on Linux</topic>
<p>
As you may have read the <a href="http://www.desktoplinux.com/news/NS8454912761.html">Annual
-Linux Desktop Survey Results</a> are in for the year. Theres the usual bit
+Linux Desktop Survey Results</a> are in for the year. There's the usual bit
about what browser people use and their favorite distribution. However, the
folk over at <a href="http://linuxdesktop.com">linuxdesktop.com</a> have also
included some interesting information on how people run windows applications
@@ -113,9 +113,9 @@ used Cedega, while even less, 5 percent, said they used CrossOver.
</p>
</quote>
<p>
-Desktoplinux's Steven Vaughan-Nichols writes in a
-<a href="http://www.desktoplinux.com/news/NS9488592005.html">separate
-article</a> also highlights how linux users feel about applications:
+In a <a href="http://www.desktoplinux.com/news/NS9488592005.html">separate
+article</a>, desktoplinux's Steven Vaughan-Nichols also highlights how Linux
+users feel about applications:
<quote><p>
Given a choice of applications to run on their Linux desktops, most users
would prefer to run a native Linux application rather than a Windows
@@ -127,7 +127,7 @@ list. Autodesk's AutoCAD was number two.
If Linux users can't run a particular application on Linux, and there's no
native program that gives them similar functionality, they're almost perfectly
divided between three different methods to get them their required program.
-These are using WINE, or a software built on WINE, such as Crossover Linux, to
+These are using WINE, or a software built on WINE, such as CrossOver Linux, to
run the Windows application in Linux; virtualization; and switching to a
browser-based application, such as Google Docs.
</p></quote></p>
@@ -150,21 +150,21 @@ The goal of the blog is to post about Wine (and to help people) on any
x86 operating system that Wine will run on e.g
Linux, BSD, X86 Mac, and even Solaris ...
</p><p>
-The goal of the Forum is to to provide a place for people who are
+The goal of the Forum is to provide a place for people who are
interested in Wine to meet and collaborate about
-there favorite applications and games. And to be a source for help and
+their favorite applications and games. And to be a source for help and
suggestions.
</p></p></quote>
<p>
-Tom's blog has done very well thus far; hes quoted to me that he estimates
+Tom's blog has done very well thus far; he's quoted to me that he estimates
nearly 100,000 hits per month. He is also seeking contributors to his blog.
</p>
<quote><p>
-I plan to seek other contributors to the blog as well..... I cant own
+I plan to seek other contributors to the blog as well..... I can't own
every Office app or Game out there
-and I currently don't own a Intel Mac. And whats surprising to me is i
+and I currently don't own an Intel Mac. And what's surprising to me is I
received well over 2500 hits from
-people who run Intel Mac's last month, even tho I don't currently post
+people who run Intel Macs last month, even tho I don't currently post
about Wine on that platform.
</p></quote>
<p><div align="center">
@@ -173,26 +173,26 @@ about Wine on that platform.
</section>
<section
- title="DiB Engine Status"
+ title="DIB Engine Status"
subject="Code"
archive="http://www.winehq.org/pipermail/wine-devel/2007-December/060934.html"
posts="2"
>
-<topic>DiB Engine</topic>
+<topic>DIB Engine</topic>
<p>
-<p>The DiB (Device Independent Bitmap) engine is one of the few remaining
+<p>The DIB (Device Independent Bitmap) engine is one of the few remaining
"large" issues that in general the community believes needs to be implemented.
-The only issue with that is that implementing the DiB is actually very
-difficult. At present WINE gets around having a DiB engine by translating the
+The only issue with that is that implementing the DIB is actually very
+difficult. At present WINE gets around having a DIB engine by translating the
calls into something X can handle, lets X do the legwork and then translates
the results back. This is for the most part an effective solution, however
-its known to be inefficient and not without its problems. Alex Juillard has
-expressed opinion that implementing a proper DiB engine will likely be done
+it's known to be inefficient and not without its problems. Alexandre Julliard has
+expressed the opinion that implementing a proper DIB engine will likely be done
post 1.0. See <a href="http://wiki.winehq.org/DIBEngine">the wiki page</a> on
-DiB for more information.</p>
+DIB for more information.</p>
<p>
In light of all this, Piotr Maceluch writes in to find out the current status
-of the DiB Engine.
+of the DIB Engine.
</p>
<p><quote who="Piotr Maceluch">
<p>Hi,</p>
@@ -365,7 +365,7 @@ That means the hlink test has one fewer error. Yay!
</p>
</quote>
<p>
-Of course, while the new script is nice, its also git its kinks and things Dan
+Of course, while the new script is nice, it also has its kinks and there are things Dan
would like to see improved/changed.
</p>
<quote><p>
@@ -408,8 +408,8 @@ While amusing I do not think this is correct.<br />
Steve Edwards writes in to second that opinion.
</p>
<quote><p>
-Plenty of OEM's change the default IE home page, and we should make it
-easy to do so in Wine. I think a edit box in winecfg is the best route
+Plenty of OEMs change the default IE home page, and we should make it
+easy to do so in Wine. I think an edit box in winecfg is the best route
to go with the default option being about:blank or www.winehq.org
</p><p>
Thanks<br />
@@ -428,7 +428,7 @@ with native, we'd have to move everything from shdocvw.inf to wine.inf
(and that's not the way to go IMO). I've added these registries because
an app I've been working on expected default search page to be present.
Also we should use it in our InternetExplorer and WebBrowser
-implementation. We may consider to handle these keys like we do with IE
+implementation. We may consider handling these keys like we do with the IE
version key. That is, they may be added on iexplore.exe registration. If
one wants to install native IE, he has to unregister iexplore.exe first,
removing the homepage. Then IE installer will probably set its default
@@ -436,11 +436,11 @@ homepage.
</p></quote>
<p>Aric refutes:</p>
<quote><p>
-Humm, maybe i am confused but (at least the win98 version of )
+Humm, maybe I am confused but (at least the win98 version of)
shdocvw.dll implements DllRegisterServer which seems to do a lot of
stuff. But Setting the Start Page is not one of them. In my experience
installing IE does not actually set a Start Page by default, but instead
-the browser seem to handle not having a Start Page by pulling up a
+the browser seems to handle not having a Start Page by pulling up a
default one.
</p></quote>
<p>
@@ -460,7 +460,7 @@ typelib, nothing else like coclasses. I will do more testing later today.
<topic>Wine</topic>
<p>
In addition to the monumental task of implementing and replicating native
-behavior of the Windows API WINE has to also manage to do it with near-native
+behavior of the Windows API, WINE has to also do it with near-native
speeds. Phoronix has recently
<a href="http://www.phoronix.com/scan.php?page=article&item=938&num=1">Benchmarked</a>
a series of different wine versions. Their results are indeed interesting and
@@ -494,11 +494,11 @@ They are hit by the stencil test slowness in 3dmark2k3 though, which we
resolved as a driver bug on geforce 8 cards, since we couldn't reproduce it
elsewhere.<br />
<br />
-I didn't find any info what card they used, so it is a bit hard to say what
+I didn't find any info on the card they used, so it is a bit hard to say what
might be wrong.
</p></quote>
<p>
-Bryan Haskins think's its an 8-Series:
+Bryan Haskins thinks it's an 8-Series:
</p>
<quote><p>
Phoronix often uses the 8 series cards when not testing things like driver