Module: website Branch: master Commit: 3f7e13efaebaceeb2ee743adeda72835412d011e URL: http://source.winehq.org/git/website.git/?a=commit;h=3f7e13efaebaceeb2ee743a...
Author: Zachary Goldberg zgold550@gmail.com Date: Thu Sep 4 13:26:55 2008 -0500
Typo Fixes
---
wwn/en/wn20080827_351.xml | 29 +++++++++++------------------ 1 files changed, 11 insertions(+), 18 deletions(-)
diff --git a/wwn/en/wn20080827_351.xml b/wwn/en/wn20080827_351.xml index f79ee96..13141a1 100644 --- a/wwn/en/wn20080827_351.xml +++ b/wwn/en/wn20080827_351.xml @@ -5,7 +5,7 @@
<author contact="http://www.bluesata.com">Zachary Goldberg</author> <issue num="351" date="08/26/2008" /> -<intro> <p>This is the 351 issue of the World Wine News publication. +<intro> <p>This is the 351 issue of the Wine Weekly News publication. Its main goal is to update the community on the status of the patchwatcher and other major august developments. If this issue also helps to spread peace in the world the editor will be very content. 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 Windows, as it is a completely alternative implementation consisting of 100% Microsoft-free code, but it can optionally use native system DLLs if they are available. You can find more info at <a href="http://www.winehq.org">www.winehq.org</a></p> </intro> <stats posts="509" size="764" contrib="113" multiples="63" lastweek="28">
@@ -151,7 +151,7 @@ Alexandre Julliard was out on vacation for a week or so in early August and so w In other news, <a href="http://www.thinkgos.com/gos.php">gOS</a>, the 'good' OS, has announced their most recent beta which includes Wine 1.0 built in. We mentioned building up to 1.0 that we suspected that more and more packagers would incorporate Wine into their products and it seems to be coming to pass. </p> <p> -Dan Kegel sent in a link to a <a href="http://www.linuxjournal.com/node/1007221/results">Linux Journal survey</a> of what linux users use to run their windows applications. As of this publication it looks like Wine is in the lead with approximately 40% of the vote, followed by virtualbox, 'none' and vmware each with 15-20%. +Dan Kegel sent in a link to a <a href="http://www.linuxjournal.com/node/1007221/results">Linux Journal survey</a> of what Linux users use to run their windows applications. As of this publication it looks like Wine is in the lead with approximately 40% of the vote, followed by VirtualBox, 'none' and VMWare each with 15-20%. </p>
<p> @@ -228,7 +228,7 @@ template every time a new patch is being built. </p> </quote> <p> -Dan agreed about the security issues, but mentioned that it might be difficult to do. Ambroz offered his assistance as hes familiar with OS architecture. A few days later Ambroz delivered a version 1 patch for patchwatcher to use chroots: +Dan agreed about the security issues, but mentioned that it might be difficult to do. Ambroz offered his assistance as he's familiar with OS architecture. A few days later Ambroz delivered a version 1 patch for patchwatcher to use a chroot: </p> <quote> <p> @@ -252,7 +252,7 @@ continuous building. </p> </quote> <p> -Aside from security concerns there were also concerns about performance, and if it would be possible to simply keep up with the mailing list. In the end it was decided that we would wait and see if its a problem, if so maybe consider using Dan Kegel's parallel test suite patches. +Aside from security concerns there were also concerns about performance, and if it would be possible to simply keep up with the mailing list. In the end it was decided that we would wait and see if it's a problem, if so maybe consider using Dan Kegel's parallel test suite patches. </p> <p> About a week after Dan's original thread he began another one, this time with information about the patchwatcher's online results. @@ -273,7 +273,7 @@ for the next week or so while I work out the kinks. Much praise followed, along with a tiny bit of bikeshed painting about the colors on the site. There also seems to be desire for a way to signal to patchwatcher to ignore the patch. </p> <p> -Finally there remained two issues with the patchwatcher. Patch series's and character set corruptions (from mail clients, from the patchwatcher itself). As of 8/22, exactly 20 days from the introduction of patch watcher Dan proclaims the patchwatcher to be mostly satisfactory: +Finally there remained two issues with the patchwatcher. Patch series and character set corruptions (from mail clients, from the patchwatcher itself). As of 8/22, exactly 20 days from the introduction of patch watcher Dan proclaims the patchwatcher to be mostly satisfactory: </p> <quote> <p> @@ -310,7 +310,7 @@ of Google - so thanks go to them and of course to Dan. You can find the code at <a href="http://repo.or.cz/w/wine/dibeng-hd.git">http://repo.or.cz/w/wine/dibeng-hd.git</a> </p><p> What's supported<br /> ------------------<br /> +---------------<br /> - All dib section depths (including BI_BITFIELD support).<br /> - Single pixel solid and dashed pens.<br /> - The 16 rop2s.<br /> @@ -320,7 +320,7 @@ What's supported<br /> - An extensive test suite for all of the above.<br /> </p><p> What needs to be done<br /> --------------------<br /> +----------------<br /> - Blitting (eg BitBlt, StretchBlt and StretchDIBits) - I have some hacks for these in my tree.<br /> - ExtTextOut<br /> @@ -474,7 +474,7 @@ Vitaliy </quote>
<p> -A couple devs. wrote in with the notion that its likely a Kernel bug, Dmitry Timoshkov writes in definitively: +A couple devs. wrote in with the notion that it's likely a Kernel bug, Dmitry Timoshkov writes in definitively: </p> <quote> <p> @@ -491,7 +491,7 @@ bug, and should be reported appropriately.
<topic>Development Process</topic> <p> -Dan Kegel pointed out an interesting guide over in linux land about development and community which he felt might be a good role model to have for Wine. +Dan Kegel pointed out an interesting guide over in Linux land about development and community which he felt might be a good role model to have for Wine. </p>
<quote> @@ -515,10 +515,10 @@ Discussion following seemed to be positive on the idea of creating such a guide.
<topic>Spore</topic> <p> -So single applications don't usually get much WWN coverage but Spore has been so outstandingly high profile in the gaming world that this may be interesting to many a reader. The <a href="http://appdb.winehq.org/objectManager.php?sClass=version&iId=12558">appdb</a> entry for spore indicates that gamers have had some success with the game. A <a href="http://bugs.winehq.org/show_bug.cgi?id=13988"> very interesting bug</a> was filed with some details on some fixes that are in progress. +So single applications don't usually get much WWN coverage but Spore has been so outstandingly high profile in the gaming world that this may be interesting to many a reader. The <a href="http://appdb.winehq.org/objectManager.php?sClass=version&iId=12558">AppDB</a> entry for Spore indicates that gamers have had some success with the game. A <a href="http://bugs.winehq.org/show_bug.cgi?id=13988"> very interesting bug</a> was filed with some details on some fixes that are in progress. </p> <p> -A patch was submitted to wine-patches but rejected by Stefan Dösinger due to needing some tests. The discussion is slightly technical but not so much that its unreadable. I think its at just the right level to be interesting reading. Andrew Fenn: +A patch was submitted to wine-patches but rejected by Stefan Dösinger due to a lack of conformance tests. The discussion is slightly technical but not so much that its unreadable. I think its at just the right level to be interesting reading. Andrew Fenn: </p> <quote> <p> @@ -724,13 +724,6 @@ start working on it again until mid-september (exams, other projects abbandoned due to GSoC, etc), and then my progress will be much slower. </p><p> -My project didn't go bad, but I was only able to complete around 40% -of what I expected to do in the begining, it turned out to be bigger -than I thought. I'll try to finish it, but I probably won't be able to -start working on it again until mid-september (exams, other projects -abbandoned due to GSoC, etc), and then my progress will be much -slower. -</p><p> I really enjoyed this SoC, I was able to update my skills and learn to work in a big project. Thanks to kblin and to all the people who reviewed my code and bothered to suggest improvements :)