Module: website Branch: master Commit: 5f19dab21b6f2e93e5854e1a8630b162e50cc1c7 URL: http://source.winehq.org/git/website.git/?a=commit;h=5f19dab21b6f2e93e5854e1...
Author: Francois Gouget fgouget@free.fr Date: Thu Jun 19 11:16:53 2008 +0200
Assorted spelling fixes.
---
wwn/en/wn20010319_87.xml | 2 +- wwn/en/wn20010816_102.xml | 2 +- wwn/en/wn20011212_110.xml | 2 +- wwn/en/wn20021011_139.xml | 2 +- wwn/en/wn20030117_153.xml | 2 +- wwn/en/wn20050506_273.xml | 4 ++-- 6 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/wwn/en/wn20010319_87.xml b/wwn/en/wn20010319_87.xml index b068ae3..cd89182 100644 --- a/wwn/en/wn20010319_87.xml +++ b/wwn/en/wn20010319_87.xml @@ -165,7 +165,7 @@ interest. It was something quick and dirty to solve a specific problem, so I did not submit it for inclusion into wine. I originally did use a keyboard interface, but needed something extensible allowing for more than just dumping a window list, hence went to more of a -programatic interface. +programmatic interface.
<p />
diff --git a/wwn/en/wn20010816_102.xml b/wwn/en/wn20010816_102.xml index 1d7e2a8..641fd15 100644 --- a/wwn/en/wn20010816_102.xml +++ b/wwn/en/wn20010816_102.xml @@ -208,7 +208,7 @@ of the code. He wrote:</p> <quote who="Phillip Schmitz"><p> I've read most of the developer docs and some relevant source but I'm still having problems grokking the interrelationships between different parts of wine and the role(s) of wineserver. -I have a general understanding of Win32 from a programatic point of view rather than wine's +I have a general understanding of Win32 from a programmatic point of view rather than wine's implementation details. While I'm quite willing to "read the source" there's rather a lot of it :) and rather deep dependencies (even with tags one jumps around for a while trying to understand what does what). </p> diff --git a/wwn/en/wn20011212_110.xml b/wwn/en/wn20011212_110.xml index c8e18c3..42e1ee9 100644 --- a/wwn/en/wn20011212_110.xml +++ b/wwn/en/wn20011212_110.xml @@ -613,7 +613,7 @@ now. Actually, I just download from cvs randomly, and see what happens. </p><p> 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. +occurence was a 'locking' of the screen on a print preview. </p><p> Since then, this 'locking' is the only issue (though I haven't yet attempted to print). diff --git a/wwn/en/wn20021011_139.xml b/wwn/en/wn20021011_139.xml index 7b62516..5db8b67 100644 --- a/wwn/en/wn20021011_139.xml +++ b/wwn/en/wn20021011_139.xml @@ -322,7 +322,7 @@ for the new framework with some actual tests.</p> <topic>Internationalization</topic> <p>Steve Lustbader posted a patch to implement <code>GetUserDefaultUILanguage</code> and -<code>GetSytemDefaultUILanguage</code> but wasn't +<code>GetSystemDefaultUILanguage</code> but wasn't sure of the details of using them:</p> <quote who="Steve Lustbader"><p> I implemented these functions in codepage.c since similar functions diff --git a/wwn/en/wn20030117_153.xml b/wwn/en/wn20030117_153.xml index 1083013..b8901b3 100644 --- a/wwn/en/wn20030117_153.xml +++ b/wwn/en/wn20030117_153.xml @@ -766,7 +766,7 @@ not to use that as a guide. Ever.</p>
<section title="NTFS Filesystem Type" - subject="Add filesytem type NTFS to config" + subject="Add filesystem type NTFS to config" archive="http://www.winehq.org/hypermail/wine-patches/2003/01/0217.html" posts="14" startdate="13 Jan 2003 00:00:00 -0800" diff --git a/wwn/en/wn20050506_273.xml b/wwn/en/wn20050506_273.xml index 00bc0c1..70b7197 100644 --- a/wwn/en/wn20050506_273.xml +++ b/wwn/en/wn20050506_273.xml @@ -354,14 +354,14 @@ window initialization code, etc that goes on inside DialogBoxParam, and I'd need to handle all of that, I think. There even appears to be issues with 16 vs 32 bit handler addresses, etc. Looks really ugly. </p><p> -Is there a simpler way to programatically click "Ok" on a dialog box? +Is there a simpler way to programmatically click "Ok" on a dialog box? (The dialog box coming from code that I don't have source for...) </p></quote>
<p>Shachar Shemesh suggested:</p> <quote who="Shachar Shemesh"><p> For simple things, merely sending the dialog a WM_COMMAND with the right -parameters will do it for you. You can programatically find the dialog +parameters will do it for you. You can programmatically find the dialog using "FindWindow". </p><p> I've done such things before. For simple things, this works very well.