[WineHQ] wwn/en: Fix some case and spelling issues, add some missing words.
Signed-off-by: Francois Gouget <fgouget(a)free.fr> --- wwn/en/wn19990829_6.xml | 2 +- wwn/en/wn20010611_97.xml | 6 +++--- wwn/en/wn20010802_101.xml | 10 +++++----- wwn/en/wn20041015_244.xml | 4 ++-- wwn/en/wn20070410_328.xml | 2 +- wwn/en/wn20080106_338.xml | 4 ++-- wwn/en/wn20080922_352.xml | 2 +- wwn/en/wn20140303_364.xml | 12 ++++++------ wwn/en/wn20140314_365.xml | 8 ++++---- wwn/en/wn20140328_366.xml | 8 ++++---- wwn/en/wn20140509_369.xml | 4 ++-- 11 files changed, 31 insertions(+), 31 deletions(-) diff --git a/wwn/en/wn19990829_6.xml b/wwn/en/wn19990829_6.xml index 374c6529..ed2f737b 100644 --- a/wwn/en/wn19990829_6.xml +++ b/wwn/en/wn19990829_6.xml @@ -15,7 +15,7 @@ main goal is to distribute widely what's going on around Wine (the Un*x Windows emulator). <p />Well this week has been very quiet on wine-devel, as if most of the -developpers were on vacation at the same time. Of course, there was the +developers were on vacation at the same time. Of course, there was the O'Reilly conference in Monterey (CA) where Alexandre Julliard was giving a talk. So, I barely had enough material to put an issue together. diff --git a/wwn/en/wn20010611_97.xml b/wwn/en/wn20010611_97.xml index 8a0ddfd3..10b708e5 100644 --- a/wwn/en/wn20010611_97.xml +++ b/wwn/en/wn20010611_97.xml @@ -308,7 +308,7 @@ a 2GB virtual memory space this means you can start a maximum of about 2000 threads. If you increase this to 10MB then you can only start 200 threads (per process).</p> -<p> And that's why you have all the Java developpers complaining that +<p> And that's why you have all the Java developers complaining that Java does not scale because it only support 2000 clients! Let me explain. Until JDK1.4 is out Java does not have asynchronous I/O. So all Java servers are of the 'one thread per client' type. So they all block @@ -320,9 +320,9 @@ very much this affects your application (seems more scientific computing oriented).</p> <p> One more word on Java and threads :-) All (overgeneralization, I now) -Java developpers (and benchmarketers) say Linux is bad because it does +Java developers (and benchmarketers) say Linux is bad because it does not scale well when you have thousands of runnable threads. And all -kernel developpers reply 'you have to be crazy to have thousands of +kernel developers reply 'you have to be crazy to have thousands of threads, your server performance will be bad anyway if you do that' (to which I can only agree). Fortunately, as I said before, JDK 1.4 will finally have asynchronous I/O, and even memory mapped files! So maybe diff --git a/wwn/en/wn20010802_101.xml b/wwn/en/wn20010802_101.xml index 18d230cd..0b22069c 100644 --- a/wwn/en/wn20010802_101.xml +++ b/wwn/en/wn20010802_101.xml @@ -408,12 +408,12 @@ environment for which we no longer have any documentation. Then when someone comes to modify some piece of code which is shared between Win16 and Win32 you have no idea if the fix you made for Win32 is not going to break Win16. If Wine had had good independent documentation of the API -from the start developpers could refer to this documentation to know +from the start developers could refer to this documentation to know whether a change is going to break Win16 or not.</li> <li>MSDN documentation is often incomplete / slightly incorrect (though people working on Wine should maybe look at it a bit more). So what you propose is that this be *the* documentation for the Win32 API. I -think Wine developpers and Winelib users deserve better. And no one +think Wine developers and Winelib users deserve better. And no one using Winelib as a development platform would want to have to go to two places to find documentation.</li> <li>The MSDN documentation is currently freely available on the Web. @@ -429,14 +429,14 @@ this is the only place where they have a remote chance of staying up to date (and also where it's most practical to have it).</p> -<p> Of course developpers are very well-known for hating to document +<p> Of course developers are very well-known for hating to document stuff so it's going to be pretty hard to get proper documentation. But -we should encourage all Wine developpers to write good documentation for +we should encourage all Wine developers to write good documentation for the functions they implement/fix, not dissuade them to do so.</p> <p> Also I agree with you that the strict minimum is to at least document all the undocumented/weird behaviors. Especially since without some sort -of documentation the next developper may be tempted to remove what looks +of documentation the next developer may be tempted to remove what looks like unnecessarily convoluted/obviously wrong code.</p> diff --git a/wwn/en/wn20041015_244.xml b/wwn/en/wn20041015_244.xml index 4779b42a..78ed178d 100644 --- a/wwn/en/wn20041015_244.xml +++ b/wwn/en/wn20041015_244.xml @@ -310,7 +310,7 @@ the private header</li></ul> </section> <section title="COM Inheritance" - subject="COM inheritence" + subject="COM inheritance" archive="//www.winehq.org/hypermail/wine-devel/2004/10/0236.html" posts="4" startdate="10/11/2004" @@ -357,7 +357,7 @@ IJimVtbl Jim_Vtbl = have extern prototypes defined. Basically this is because array initialization requires constant values. </p><p> - However, this would seem something which is so common - i.e. inheritence is + However, this would seem something which is so common - i.e. inheritance is used all over the place. How do people handle this? I've looked through a few places in the code and can't see how this can be done. I could 'pretend' by initializing the Vtbl as I create the com object and do some LoadLibrary diff --git a/wwn/en/wn20070410_328.xml b/wwn/en/wn20070410_328.xml index d32bc717..e461b596 100644 --- a/wwn/en/wn20070410_328.xml +++ b/wwn/en/wn20070410_328.xml @@ -134,7 +134,7 @@ installers. <p>Dan Kegel summarized what a lot of people on wine-devel think about such projects:</p> <quote who="Dan Kegel"><p> -The problem that Wine developers have with recipies +The problem that Wine developers have with recipes like the one you cite is that most of the steps in the recipe are there to work around bugs in Wine. We would prefer to fix the bugs. For instance, diff --git a/wwn/en/wn20080106_338.xml b/wwn/en/wn20080106_338.xml index 654e050b..9b2db7f1 100644 --- a/wwn/en/wn20080106_338.xml +++ b/wwn/en/wn20080106_338.xml @@ -101,7 +101,7 @@ run in Wine. Tom also highlights a new bit of wine software, <a href="http://wine-review.blogspot.com/2008/01/bordeaux-wine-configuration-manager.html">Bordeaux</a>. Bordeaux is a new wine-package manager (for apps running under wine). -I havn't yet had a chance to use it, however many of the wwn's readers may +I haven't yet had a chance to use it, however many of the wwn's readers may find this interesting and useful. </p> <quote> @@ -424,7 +424,7 @@ Roderick Colenbrander writes with an alternative to MD5 <quote> <p> The system on windows doesn't use the md5sum (I think it has one) but it -looks for the product ID which is burried into most executables first. It +looks for the product ID which is buried into most executables first. It also checks for other things but in a hackier way. As there are a lot of different versions of a program but which all need the same override. <br /><br /> diff --git a/wwn/en/wn20080922_352.xml b/wwn/en/wn20080922_352.xml index 4e24ad97..0bcfd323 100644 --- a/wwn/en/wn20080922_352.xml +++ b/wwn/en/wn20080922_352.xml @@ -244,7 +244,7 @@ Jeremy </p></quote> <p> A bit of an editorial:<br /> -So I actually went and downloaded <a href="http://www.codeweavers.com/services/ports/chromium/">CrossOver Chromium Edition</a> and played with it for a bit. I first tried GMail, no issues. I said to myself alright, that is pretty impressive. How about a real test: will flash work? I went to youtube.com and sure enough I got the error "Flash isn't installed." Aww poop. Well, lets try installing it. Clicked the "go to Adobe to get Flash" link, downloaded the executable which ran a really fast installer. I went back to youtube.com and..... no luck. At this point I had lost a bit of hope. But then an idea struck me! I closed the browser and re-opened it. Off to youtube.com and... voila! Working flash video! I watched a rather cute video of a cat smacking a printer with its paw. After about 45 seconds of this the cat hit it hard enough that the paper tray came lose and the cat went flying. Perfect. +So I actually went and downloaded <a href="http://www.codeweavers.com/services/ports/chromium/">CrossOver Chromium Edition</a> and played with it for a bit. I first tried GMail, no issues. I said to myself alright, that is pretty impressive. How about a real test: will flash work? I went to youtube.com and sure enough I got the error "Flash isn't installed." Aww poop. Well, let's try installing it. Clicked the "go to Adobe to get Flash" link, downloaded the executable which ran a really fast installer. I went back to youtube.com and..... no luck. At this point I had lost a bit of hope. But then an idea struck me! I closed the browser and re-opened it. Off to youtube.com and... voila! Working flash video! I watched a rather cute video of a cat smacking a printer with its paw. After about 45 seconds of this the cat hit it hard enough that the paper tray came lose and the cat went flying. Perfect. </p> <p> As a Wine user of many years there are these occasional moments in using Wine when, after getting something seemingly outrageously complex to work, you sit back and go wow: that's really a miracle. This was one of them for me, hats off to the entire Wine and CodeWeavers team. diff --git a/wwn/en/wn20140303_364.xml b/wwn/en/wn20140303_364.xml index 48852ffe..27480757 100644 --- a/wwn/en/wn20140303_364.xml +++ b/wwn/en/wn20140303_364.xml @@ -50,13 +50,13 @@ A user asked about the state of Wine64 on OS X: <p>Where would you find information on wine64 status for running 64 bit windows software under OSX. These days a lot of Windows programs are going 64bit to make use of -the available memory. Its becoming necessary to have this capability.</p> +the available memory. It???s becoming necessary to have this capability.</p> </quote> <p> Stefan gave a good explanation: </p> <quote> -<p>OSX has a ABI incompatibility with Win64 - OSX overwrites a CPU register that Win64 applications expect to remain untouched. Apple can???t change the ABI because there are already 64 bit OSX apps that expect things to work that way. A potential workaround may be to run Wine inside a CPU emulator like qemu, but that is anything but easy.</p> +<p>OSX has an ABI incompatibility with Win64 - OSX overwrites a CPU register that Win64 applications expect to remain untouched. Apple can???t change the ABI because there are already 64 bit OSX apps that expect things to work that way. A potential workaround may be to run Wine inside a CPU emulator like qemu, but that is anything but easy.</p> </quote> </section> @@ -88,7 +88,7 @@ Shortly after the last WWN, Marcus wrote: Wine is an accepted organization for GSoC 2014, would-be students should now discuss project ideas with us as in one week the Student application period opens. </p> <p> -See <a href="https://wiki.winehq.org/SummerOfCode">our Wiki</a> for more informations and project ideas. +See <a href="https://wiki.winehq.org/SummerOfCode">our Wiki</a> for more information and project ideas. </p> </section> @@ -121,10 +121,10 @@ For each article you buy, we donate part of our benefit to Wine HQ. This way we <p><b>Major changes in 20140302 since 20130707</b></p> <ul> <li>dotnet verbs are all now fully automated in -q mode</li> -<li>comctl32ocx: add ActiveX controls</li> +<li>comctl32.ocx: add ActiveX controls</li> <li>flash: udpate to version 12</li> <li>fakechinese: add some more font aliases</li> -<li>Arbitary virtual desktop sizes are now allowed (vd=1024x768, vd=800x600, etc.)</li> +<li>Arbitrary virtual desktop sizes are now allowed (vd=1024x768, vd=800x600, etc.)</li> <li>vcrun2008: also override atl90</li> <li>mingw: new version, automated install</li> </ul> @@ -152,7 +152,7 @@ For each article you buy, we donate part of our benefit to Wine HQ. This way we </ul> <p> -See <a href="http://winetricks.org/">winetricks.org</a> for more informations. +See <a href="http://winetricks.org/">winetricks.org</a> for more information. </p> </section> diff --git a/wwn/en/wn20140314_365.xml b/wwn/en/wn20140314_365.xml index 3347e836..8dae88b8 100644 --- a/wwn/en/wn20140314_365.xml +++ b/wwn/en/wn20140314_365.xml @@ -45,15 +45,15 @@ See <a href="https://wiki.winehq.org/SummerOfCode">our Wiki</a> for more informa
<p> Valve has open sourced their DirectX to OpenGL translator named <a href="//github.com/ValveSoftware/ToGL">ToGL</a>. -The media and even some developers wondered if this is usefull for Wine. Stefan D??singer had a quick look at the code and gave an answer: +The media and even some developers wondered if this is useful for Wine. Stefan D??singer had a quick look at the code and gave an answer: </p> <quote> <p>No, it's not. It is *very* limited. It doesn't even have stateblock -interface declaration, and it's surface implementation is pretty much +interface declaration, and its surface implementation is pretty much nonexistent. It doesn't care about any of the corner cases that make d3d9 interesting.</p> <p>Note that this is not an exhaustive review of this code. It's just the -first two things I found in a 2 minute look.</p> +first two things I found in a 2 minutes look.</p> <p>Those limitations make sense as design decisions for Valve's purposes, but they make this wrapper useless for anything other than a cheap compile-time abstraction layer between d3d and gl. Releasing this code @@ -70,7 +70,7 @@ though.</p>
<p> Jeremy White finally got annoyed enough by the remaining <a href="//test.winehq.org/data/">test failures</a> on Windows and pushed people to fix them. -This also had the fact that other developers were afraid to get shamed and also fix test failures :) +This also had the effect of making other developers afraid of getting shamed and so they too fixed test failures :) </p> <p> We already made good progress, but there are some strange behaviours of Windows, other hard to analyze failures and problems caused by <a href="https://wiki.winehq.org/WineTestBotVMs">the way</a> the WineTestBot works. diff --git a/wwn/en/wn20140328_366.xml b/wwn/en/wn20140328_366.xml index 05ee3923..b482ada5 100644 --- a/wwn/en/wn20140328_366.xml +++ b/wwn/en/wn20140328_366.xml @@ -43,8 +43,8 @@ See <a href="https://wiki.winehq.org/SummerOfCode">our Wiki</a> for more informa posts="0"
<p> -Finally i cleaned out the Recent News Queue page, either by posting the story or removing it for being outdated. -Also i tried hard to find potential news myself, but that is nothing i'm good at and steals my time i could spend coding for Wine. +Finally I cleaned out the Recent News Queue page, either by posting the story or removing it for being outdated. +Also I tried hard to find potential news myself, but that is nothing i'm good at and steals my time I could spend coding for Wine. </p> <p> So please, if you find something interesting and Wine related, post it <a href="https://wiki.winehq.org/RecentNewsQueue">there</a>. At best you also add some text, but meanwhile i'm also happy for simple suggestions. @@ -71,14 +71,14 @@ At the moment WineCE is based on the stable version 1.6.2 and with the new chang
<topic>CN102364433</topic> <p> -Last week i was told about the chinese Patent CN102364433. It claims that <a href="https://wiki.winehq.org/ARM">Wine on ARM</a> was invented by five chinese people and that they want to protect that procedure. +Last week I was told about the chinese Patent CN102364433. It claims that <a href="https://wiki.winehq.org/ARM">Wine on ARM</a> was invented by five chinese people and that they want to protect that procedure. While from my point of view there are no facts in that potential Patent that should be patented, there is also a Problem with the timing. As you can see <a href="//source.winehq.org/git/wine.git/search/HEAD?pg=1;s=+ARM;st=commit">here</a>, the main commits <a href="https://wiki.winehq.org/AndreHentschel">from me</a> to support the ARM architecture in Wine were published 2010 <a href="//www.winehq.org/announce/1.3.4">(and ARM was supported with Wine 1.3.4)</a>. But that potential Patent seems to be from June 2011 and tries to describe the procedure of porting Wine to ARM using Wine 1.3.13 which clearly has ARM support. </p> <p> -Meanwhile i try to find a good way to do something about that potential Patent and stop the process of granting it to those liars. +Meanwhile I try to find a good way to do something about that potential Patent and stop the process of granting it to those liars. </p> </section> diff --git a/wwn/en/wn20140509_369.xml b/wwn/en/wn20140509_369.xml index 5ea06d12..dd347366 100644 --- a/wwn/en/wn20140509_369.xml +++ b/wwn/en/wn20140509_369.xml @@ -43,7 +43,7 @@ i suggest to simply open a Forum thread, name it e.g. WWN369 and ask questions o Mostly Kai Tietz and I are currently (finally) working on MinGW-w64 targeting ARMv7. </p> <p> -You might ask why. Well, there are multible reasons, but i'll just cover the Wine related ones here. +You might ask why. Well, there are multiple reasons, but i'll just cover the Wine related ones here. </p> <p> At some point we really want to compile and run our test suite not only in Wine, but also on Windows RT. @@ -60,7 +60,7 @@ to recompile most applications and libraries and run it in Wine on ARM (or a jai </p> <p> While we develop it we use the triple armv7-w64-mingw32ce which is quite misleading, later it will be something like -armv7-w64-mingw. But at the moment i really don't recommend to try it out. Most things don't work, build system is not +armv7-w64-mingw. But at the moment I really don't recommend to try it out. Most things don't work, build system is not ready and so on. Still, with some effort it's possible to translate a very basic application and get a Windows RT compatible executable. </p> </section> -- 2.20.1
participants (1)
-
Francois Gouget