[WineHQ] wwn333: Fix stray CRLF line endings and wrap lines to a reasonable length so that later diffs are more meaningful. (try 2)

Francois Gouget fgouget at free.fr
Thu Jan 17 05:59:51 CST 2008


---

Jeremy Newman wrote:
> Francois, I think I need the first patch to this set before I can 
> apply this one. It fails otherwise. I didn't see it in the list 
> anywhere.

Yes, I thought it was just slow in getting there but I must have missent 
it. I'm just sending the first patch for wwn333 this time. If it goes 
in without trouble then I'll resend the second one too.


 wwn/wn20071203_333.xml |  889 ++++++++++++++++++++++++++----------------------
 1 files changed, 475 insertions(+), 414 deletions(-)

diff --git a/wwn/wn20071203_333.xml b/wwn/wn20071203_333.xml
index 9b90b7f..4439c97 100644
--- a/wwn/wn20071203_333.xml
+++ b/wwn/wn20071203_333.xml
@@ -1,140 +1,147 @@
-<?xml version="1.0" ?>
-<kc>
-
-<title>Wine Traffic</title>
-
-<author contact="http://www.bluesata.com">Zachary Goldberg</author>
-<issue num="333" date="12/2/2007" />
-<intro> <p>This is the 333rd issue of the Wine Weekly News publication.
-Its main goal is to bring back the WWN!  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="607" size="878" contrib="128" multiples="72" lastweek="0">
-
-<person posts="57" size="63" who="julliard at winehq.org (Alexandre Julliard)" />
-<person posts="41" size="37" who="dank at kegel.com (Dan Kegel)" />
-<person posts="40" size="29" who="stefan at codeweavers.com (Stefan Dosinger)" />
-<person posts="25" size="30" who="rob at codeweavers.com (Robert Shearman)" />
-<person posts="25" size="24" who="dmitry at codeweavers.com (Dmitry Timoshkov)" />
-<person posts="24" size="37" who="truiken at gmail.com (James Hawkins)" />
-<person posts="19" size="19" who="juan.lang at gmail.com (Juan Lang)" />
-<person posts="15" size="15" who="wine.dev at web.de (Detlef Riekenberg)" />
-<person posts="14" size="40" who="fgouget at free.fr (Francois Gouget)" />
-<person posts="14" size="31" who="gerald at pfeifer.com (Gerald Pfeifer)" />
-<person posts="12" size="24" who="kai.blin at gmail.com (Kai Blin)" />
-<person posts="12" size="23" who="infyquest at gmail.com (Vijay Kiran Kamuju)" />
-<person posts="10" size="16" who="winehacker at gmail.com (Steven Edwards)" />
-<person posts="9" size="15" who="mstefani at redhat.com (Michael Stefaniuc)" />
-<person posts="9" size="13" who="jacek at codeweavers.com (Jacek Caban)" />
-<person posts="9" size="7" who="hans at it.vu.nl (Hans Leidekker)" />
-<person posts="8" size="16" who="thunderbird2k at gmx.net (Roderick Colenbrander)" />
-<person posts="8" size="14" who="roy at cs.hmc.edu (Roy Shea)" />
-<person posts="8" size="8" who="hverbeet at gmail.com (H. Verbeet)" />
-<person posts="8" size="8" who="alex at thehandofagony.com (Alexander Nicolaysen Sornes" />
-<person posts="8" size="8" who="wine-devel at kievinfo.com (Vitaliy Margolen)" />
-<person posts="8" size="7" who="leslie_alistair at hotmail.com (Alistair Leslie-Hughes)" />
-<person posts="8" size="6" who="paul.vriens.wine at gmail.com (Paul Vriens)" />
-<person posts="8" size="4" who="thunder.m at email.cz (=?ISO-8859-2?Q?Mirek_Sluge=F2?=)" />
-<person posts="7" size="12" who="devzero at web.de (devzero at web.de)" />
-<person posts="6" size="26" who="twickline at gmail.com (Tom Wickline)" />
-<person posts="6" size="7" who="scott at open-vote.org (Scott Ritchie)" />
-<person posts="5" size="20" who="febaen at gmail.com (feba thatl)" />
-<person posts="5" size="11" who="astrand at cendio.se (=?UTF-8?Q?Peter_=C3=85strand?=)" />
-<person posts="5" size="10" who="patrol at sinus.cz (Pavel Troller)" />
-<person posts="5" size="7" who="ead1234 at hotmail.com (EA Durbin)" />
-<person posts="5" size="6" who="maarten at codeweavers.com (Maarten Lankhorst)" />
-<person posts="5" size="5" who="David.Adam at math.cnrs.fr (David.Adam at math.cnrs.fr)" />
-<person posts="5" size="5" who="jan.wine at zerebecki.de (Jan Zerebecki)" />
-<person posts="5" size="5" who="marcus at jet.franken.de (Marcus Meissner)" />
-<person posts="4" size="6" who="roman at rm.pp.ru (Roman Mamedov)" />
-<person posts="4" size="5" who="stefandoesinger at gmx.at (Stefan =?utf-8?q?D=C3=B6singer?=)" />
-<person posts="4" size="5" who="actong88 at gmail.com (Allan Tong)" />
-<person posts="4" size="4" who="chris.kcat at gmail.com (Chris Robinson)" />
-<person posts="4" size="3" who="frank.richter at gmail.com (Frank Richter)" />
-<person posts="3" size="10" who="chmorgan at gmail.com (Chris Morgan)" />
-<person posts="3" size="5" who="dsh at linux.ucla.edu (Dan Hipschman)" />
-<person posts="3" size="5" who="gav at transgaming.com (Gavriel State)" />
-<person posts="3" size="4" who="tim at ipi.ac.ru (Timofei V. Bondarenko)" />
-<person posts="3" size="4" who="zajec5polish at gmail.com (=?UTF-8?Q?Rafa=C5=82_Mi=C5=82ecki?=)" />
-<person posts="3" size="4" who="a_villacis at palosanto.com (=?ISO-8859-1?Q?Alex_Villac=ED=ADs_Lasso?=)" />
-<person posts="3" size="3" who="staf.verhaegen at skynet.be (Staf Verhaegen)" />
-<person posts="3" size="3" who="thestig at google.com (Lei Zhang)" />
-<person posts="3" size="3" who="m.b.lankhorst at gmail.com (Maarten Lankhorst)" />
-<person posts="3" size="3" who="zac at zacbrown.org (Zac Brown)" />
-<person posts="3" size="2" who="xixsimplicityxix at gmail.com (John Klehm)" />
-<person posts="3" size="2" who="luis.busquets at ilidium.com (luis.busquets at ilidium.com)" />
-<person posts="3" size="2" who="tony.wasserka at freenet.de (tony.wasserka at freenet.de)" />
-<person posts="2" size="6" who="ngompa13 at gmail.com (King InuYasha)" />
-<person posts="2" size="6" who="nlataill at gmail.com (nlataill)" />
-<person posts="2" size="4" who="msclrhd at googlemail.com (Reece Dunn)" />
-<person posts="2" size="3" who="the3dfxdude at gmail.com (Jesse Allen)" />
-<person posts="2" size="3" who="damjan.jov at gmail.com (Damjan Jovanovic)" />
-<person posts="2" size="3" who="lionel.tricon at free.fr (Lionel Tricon)" />
-<person posts="2" size="3" who="m.bosner at c-t-b.info (Martin Bosner)" />
-<person posts="2" size="2" who="bon at elektron.ikp.physik.tu-darmstadt.de (Uwe Bonnes)" />
-<person posts="2" size="2" who="paul at astro.gla.ac.uk (Paul Millar)" />
-<person posts="2" size="2" who="l_bratch at yahoo.co.uk (Luke Bratch)" />
-<person posts="2" size="2" who="pgquiles at elpauer.org (Pau Garcia i Quiles)" />
-<person posts="2" size="2" who="mckillroy at gmail.com (Chris McKillroy)" />
-<person posts="2" size="2" who="jnewman at codeweavers.com (Jeremy Newman)" />
-<person posts="2" size="2" who="ben at atomnet.co.uk (Ben Hodgetts (Enverex))" />
-<person posts="2" size="1" who="trent.waddington at gmail.com (Trent Waddington)" />
-<person posts="2" size="1" who="vostok at etersoft.ru (Anatoly Lyutin)" />
-<person posts="2" size="1" who="huw at codeweavers.com (Huw Davies)" />
-<person posts="1" size="7" who="felix at compsoc.nuigalway.ie (Darragh Bailey)" />
-<person posts="1" size="3" who="mk144210 at bcm.tmc.edu (Koshelev, Misha Vladislavo)" />
-<person posts="1" size="3" who="mpartap at gmx.net (Marcel Partap)" />
-<person posts="1" size="3" who="melbournemark+wine-devel at gmail.com (mark cox)" />
-<person posts="1" size="3" who="stefan at codeweavers.com (Stefan =?utf-8?q?D=C3=B6singer?=)" />
-<person posts="1" size="3" who="mk144210 at bcm.edu (Misha Koshelev)" />
-<person posts="1" size="2" who=" ()" />
-<person posts="1" size="2" who="tom at dbservice.com (Tomas Carnecky)" />
-<person posts="1" size="2" who="mrmessiah at gmail.com (Chris Howe)" />
-<person posts="1" size="2" who="a_villacis at palosanto.com (=?UTF-8?B?QWxleCBWaWxsYWPDrcKtcyBMYXNzbw==?=)" />
-<person posts="1" size="2" who="epssyis at gmail.com (Edward Savage)" />
-<person posts="1" size="2" who="jwhite at winehq.org (Jeremy White)" />
-<person posts="1" size="2" who="meissner at suse.de (Marcus Meissner)" />
-<person posts="1" size="2" who="joshscholar at nightstudies.net (Josh Scholar)" />
-<person posts="1" size="2" who="remco47 at yahoo.com (Remco)" />
-<person posts="1" size="2" who="alfred at valvesoftware.com (Alfred Reynolds)" />
-<person posts="1" size="1" who="kingofallhearts999 at gmail.com (Bryan Haskins)" />
-<person posts="1" size="1" who="infinitei at aapt.net.au (Colin M Inglis)" />
-<person posts="1" size="1" who="cyrix12 at cox.net (darckness)" />
-<person posts="1" size="1" who="jjmckenzie51 at sprintpcs.com (James McKenzie)" />
-<person posts="1" size="1" who="tobert at gmail.com (Al Tobey)" />
-<person posts="1" size="1" who="offer at fastscale.com (Richard Offer)" />
-<person posts="1" size="1" who="lionel_debroux at yahoo.fr (Lionel Debroux)" />
-<person posts="1" size="1" who="junyoung at mogua.com (Bang Jun-young)" />
-<person posts="1" size="1" who="lionel_debroux at yahoo.fr (Lionel_Debroux)" />
-<person posts="1" size="1" who="brian.vincent at gmail.com (Brian Vincent)" />
-<person posts="1" size="1" who="mikolaj at zalewski.pl (=?UTF-8?B?TWlrb8WCYWogWmFsZXdza2k=?=)" />
-<person posts="1" size="1" who="fgallego at dccia.ua.es (=?ISO-8859-1?Q?Francisco_Jos=E9_Gallego_Dur=E1n?=)" />
-<person posts="1" size="1" who="joshscholar at nightstudies.net (Joshua Scholar)" />
-<person posts="1" size="1" who="atheleyen at gmail.com (Athel)" />
-<person posts="1" size="1" who="saulius2 at ar.fi.lt (Saulius Krasuckas)" />
-<person posts="1" size="1" who="wine at electrozaur.com (Boaz Harrosh)" />
-<person posts="1" size="1" who="wp1083627-tobias at platen-software.de (Tobias Platen)" />
-<person posts="1" size="1" who="amaranth at ubuntu.com (Travis Watkins)" />
-<person posts="1" size="0" who="manish.iitm at yahoo.co.in (manish jaiswal)" />
-<person posts="1" size="0" who="alex at thehandofagony.com (Alexander Nicolaysen =?utf-8?q?S=C3=B8rnes?=)" />
-<person posts="1" size="0" who="dank06 at kegel.com (Dan Kegel)" />
-<person posts="1" size="0" who="tj at moka5.com (T.J. Purtell)" />
-<person posts="1" size="0" who="dimi at lattica.com (Dimi Paun)" />
-<person posts="1" size="0" who="pawel.rozanski at gmail.com (=?ISO-8859-2?Q?Pawe=B3_R=F3=BFa=F1ski?=)" />
-<person posts="1" size="0" who="cedar1182 at yahoo.com (Dave Cartright)" />
-<person posts="1" size="0" who="Stefan.Leichter at camline.com (Stefan Leichter)" />
-<person posts="1" size="0" who="research at science.su (L. Rahyen)" />
-<person posts="1" size="0" who="laurent at vromman.org (Laurent Vromman)" />
-<person posts="1" size="0" who="shachar at shemesh.biz (Shachar Shemesh)" />
-<person posts="1" size="0" who="jonathan at ernstfamily.ch (Jonathan Ernst)" />
-<person posts="1" size="0" who="klaus.layer at gmx.de (Klaus Layer)" />
-<person posts="1" size="0" who="jwhite at codeweavers.com (Jeremy White)" />
-<person posts="1" size="0" who="luis.busquets at ilidium.com (=?ISO-8859-1?Q?=22Luis_C=2E_Busquets_P=E9rez=22?=)" />
-<person posts="1" size="0" who="lich at math.spbu.ru (Kirill K. Smirnov)" />
-<person posts="1" size="0" who="mikazkow at tlen.pl (Maciej Kowalczyk)" />
-<person posts="1" size="0" who="jiangyi178 at rogers.com (Jiang,Yi)" />
-<person posts="1" size="0" who="ivg231 at gmail.com (Ivan Gyurdiev)" />
-<person posts="1" size="0" who="Andrew.Talbot at talbotville.com (Andrew Talbot)" />
-<person posts="1" size="0" who="jjmckenzie51 at earthlink.net (James McKenzie)" />
-
+<?xml version="1.0" ?>
+<kc>
+
+<title>Wine Traffic</title>
+
+<author contact="http://www.bluesata.com">Zachary Goldberg</author>
+<issue num="333" date="12/2/2007" />
+<intro> <p>This is the 333rd issue of the Wine Weekly News publication.
+Its main goal is to bring back the WWN!
+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="607" size="878" contrib="128" multiples="72" lastweek="0">
+
+<person posts="57" size="63" who="julliard at winehq.org (Alexandre Julliard)" />
+<person posts="41" size="37" who="dank at kegel.com (Dan Kegel)" />
+<person posts="40" size="29" who="stefan at codeweavers.com (Stefan Dosinger)" />
+<person posts="25" size="30" who="rob at codeweavers.com (Robert Shearman)" />
+<person posts="25" size="24" who="dmitry at codeweavers.com (Dmitry Timoshkov)" />
+<person posts="24" size="37" who="truiken at gmail.com (James Hawkins)" />
+<person posts="19" size="19" who="juan.lang at gmail.com (Juan Lang)" />
+<person posts="15" size="15" who="wine.dev at web.de (Detlef Riekenberg)" />
+<person posts="14" size="40" who="fgouget at free.fr (Francois Gouget)" />
+<person posts="14" size="31" who="gerald at pfeifer.com (Gerald Pfeifer)" />
+<person posts="12" size="24" who="kai.blin at gmail.com (Kai Blin)" />
+<person posts="12" size="23" who="infyquest at gmail.com (Vijay Kiran Kamuju)" />
+<person posts="10" size="16" who="winehacker at gmail.com (Steven Edwards)" />
+<person posts="9" size="15" who="mstefani at redhat.com (Michael Stefaniuc)" />
+<person posts="9" size="13" who="jacek at codeweavers.com (Jacek Caban)" />
+<person posts="9" size="7" who="hans at it.vu.nl (Hans Leidekker)" />
+<person posts="8" size="16" who="thunderbird2k at gmx.net (Roderick Colenbrander)" />
+<person posts="8" size="14" who="roy at cs.hmc.edu (Roy Shea)" />
+<person posts="8" size="8" who="hverbeet at gmail.com (H. Verbeet)" />
+<person posts="8" size="8" who="alex at thehandofagony.com (Alexander Nicolaysen Sornes" />
+<person posts="8" size="8" who="wine-devel at kievinfo.com (Vitaliy Margolen)" />
+<person posts="8" size="7" who="leslie_alistair at hotmail.com (Alistair Leslie-Hughes)" />
+<person posts="8" size="6" who="paul.vriens.wine at gmail.com (Paul Vriens)" />
+<person posts="8" size="4" who="thunder.m at email.cz (=?ISO-8859-2?Q?Mirek_Sluge=F2?=)" />
+<person posts="7" size="12" who="devzero at web.de (devzero at web.de)" />
+<person posts="6" size="26" who="twickline at gmail.com (Tom Wickline)" />
+<person posts="6" size="7" who="scott at open-vote.org (Scott Ritchie)" />
+<person posts="5" size="20" who="febaen at gmail.com (feba thatl)" />
+<person posts="5" size="11" who="astrand at cendio.se (=?UTF-8?Q?Peter_=C3=85strand?=)" />
+<person posts="5" size="10" who="patrol at sinus.cz (Pavel Troller)" />
+<person posts="5" size="7" who="ead1234 at hotmail.com (EA Durbin)" />
+<person posts="5" size="6" who="maarten at codeweavers.com (Maarten Lankhorst)" />
+<person posts="5" size="5" who="David.Adam at math.cnrs.fr (David.Adam at math.cnrs.fr)" />
+<person posts="5" size="5" who="jan.wine at zerebecki.de (Jan Zerebecki)" />
+<person posts="5" size="5" who="marcus at jet.franken.de (Marcus Meissner)" />
+<person posts="4" size="6" who="roman at rm.pp.ru (Roman Mamedov)" />
+<person posts="4" size="5" who="stefandoesinger at gmx.at (Stefan =?utf-8?q?D=C3=B6singer?=)" />
+<person posts="4" size="5" who="actong88 at gmail.com (Allan Tong)" />
+<person posts="4" size="4" who="chris.kcat at gmail.com (Chris Robinson)" />
+<person posts="4" size="3" who="frank.richter at gmail.com (Frank Richter)" />
+<person posts="3" size="10" who="chmorgan at gmail.com (Chris Morgan)" />
+<person posts="3" size="5" who="dsh at linux.ucla.edu (Dan Hipschman)" />
+<person posts="3" size="5" who="gav at transgaming.com (Gavriel State)" />
+<person posts="3" size="4" who="tim at ipi.ac.ru (Timofei V. Bondarenko)" />
+<person posts="3" size="4" who="zajec5polish at gmail.com (=?UTF-8?Q?Rafa=C5=82_Mi=C5=82ecki?=)" />
+<person posts="3" size="4" who="a_villacis at palosanto.com (=?ISO-8859-1?Q?Alex_Villac=ED=ADs_Lasso?=)" />
+<person posts="3" size="3" who="staf.verhaegen at skynet.be (Staf Verhaegen)" />
+<person posts="3" size="3" who="thestig at google.com (Lei Zhang)" />
+<person posts="3" size="3" who="m.b.lankhorst at gmail.com (Maarten Lankhorst)" />
+<person posts="3" size="3" who="zac at zacbrown.org (Zac Brown)" />
+<person posts="3" size="2" who="xixsimplicityxix at gmail.com (John Klehm)" />
+<person posts="3" size="2" who="luis.busquets at ilidium.com (luis.busquets at ilidium.com)" />
+<person posts="3" size="2" who="tony.wasserka at freenet.de (tony.wasserka at freenet.de)" />
+<person posts="2" size="6" who="ngompa13 at gmail.com (King InuYasha)" />
+<person posts="2" size="6" who="nlataill at gmail.com (nlataill)" />
+<person posts="2" size="4" who="msclrhd at googlemail.com (Reece Dunn)" />
+<person posts="2" size="3" who="the3dfxdude at gmail.com (Jesse Allen)" />
+<person posts="2" size="3" who="damjan.jov at gmail.com (Damjan Jovanovic)" />
+<person posts="2" size="3" who="lionel.tricon at free.fr (Lionel Tricon)" />
+<person posts="2" size="3" who="m.bosner at c-t-b.info (Martin Bosner)" />
+<person posts="2" size="2" who="bon at elektron.ikp.physik.tu-darmstadt.de (Uwe Bonnes)" />
+<person posts="2" size="2" who="paul at astro.gla.ac.uk (Paul Millar)" />
+<person posts="2" size="2" who="l_bratch at yahoo.co.uk (Luke Bratch)" />
+<person posts="2" size="2" who="pgquiles at elpauer.org (Pau Garcia i Quiles)" />
+<person posts="2" size="2" who="mckillroy at gmail.com (Chris McKillroy)" />
+<person posts="2" size="2" who="jnewman at codeweavers.com (Jeremy Newman)" />
+<person posts="2" size="2" who="ben at atomnet.co.uk (Ben Hodgetts (Enverex))" />
+<person posts="2" size="1" who="trent.waddington at gmail.com (Trent Waddington)" />
+<person posts="2" size="1" who="vostok at etersoft.ru (Anatoly Lyutin)" />
+<person posts="2" size="1" who="huw at codeweavers.com (Huw Davies)" />
+<person posts="1" size="7" who="felix at compsoc.nuigalway.ie (Darragh Bailey)" />
+<person posts="1" size="3" who="mk144210 at bcm.tmc.edu (Koshelev, Misha Vladislavo)" />
+<person posts="1" size="3" who="mpartap at gmx.net (Marcel Partap)" />
+<person posts="1" size="3" who="melbournemark+wine-devel at gmail.com (mark cox)" />
+<person posts="1" size="3" who="stefan at codeweavers.com (Stefan =?utf-8?q?D=C3=B6singer?=)" />
+<person posts="1" size="3" who="mk144210 at bcm.edu (Misha Koshelev)" />
+<person posts="1" size="2" who=" ()" />
+<person posts="1" size="2" who="tom at dbservice.com (Tomas Carnecky)" />
+<person posts="1" size="2" who="mrmessiah at gmail.com (Chris Howe)" />
+<person posts="1" size="2" who="a_villacis at palosanto.com (=?UTF-8?B?QWxleCBWaWxsYWPDrcKtcyBMYXNzbw==?=)" />
+<person posts="1" size="2" who="epssyis at gmail.com (Edward Savage)" />
+<person posts="1" size="2" who="jwhite at winehq.org (Jeremy White)" />
+<person posts="1" size="2" who="meissner at suse.de (Marcus Meissner)" />
+<person posts="1" size="2" who="joshscholar at nightstudies.net (Josh Scholar)" />
+<person posts="1" size="2" who="remco47 at yahoo.com (Remco)" />
+<person posts="1" size="2" who="alfred at valvesoftware.com (Alfred Reynolds)" />
+<person posts="1" size="1" who="kingofallhearts999 at gmail.com (Bryan Haskins)" />
+<person posts="1" size="1" who="infinitei at aapt.net.au (Colin M Inglis)" />
+<person posts="1" size="1" who="cyrix12 at cox.net (darckness)" />
+<person posts="1" size="1" who="jjmckenzie51 at sprintpcs.com (James McKenzie)" />
+<person posts="1" size="1" who="tobert at gmail.com (Al Tobey)" />
+<person posts="1" size="1" who="offer at fastscale.com (Richard Offer)" />
+<person posts="1" size="1" who="lionel_debroux at yahoo.fr (Lionel Debroux)" />
+<person posts="1" size="1" who="junyoung at mogua.com (Bang Jun-young)" />
+<person posts="1" size="1" who="lionel_debroux at yahoo.fr (Lionel_Debroux)" />
+<person posts="1" size="1" who="brian.vincent at gmail.com (Brian Vincent)" />
+<person posts="1" size="1" who="mikolaj at zalewski.pl (=?UTF-8?B?TWlrb8WCYWogWmFsZXdza2k=?=)" />
+<person posts="1" size="1" who="fgallego at dccia.ua.es (=?ISO-8859-1?Q?Francisco_Jos=E9_Gallego_Dur=E1n?=)" />
+<person posts="1" size="1" who="joshscholar at nightstudies.net (Joshua Scholar)" />
+<person posts="1" size="1" who="atheleyen at gmail.com (Athel)" />
+<person posts="1" size="1" who="saulius2 at ar.fi.lt (Saulius Krasuckas)" />
+<person posts="1" size="1" who="wine at electrozaur.com (Boaz Harrosh)" />
+<person posts="1" size="1" who="wp1083627-tobias at platen-software.de (Tobias Platen)" />
+<person posts="1" size="1" who="amaranth at ubuntu.com (Travis Watkins)" />
+<person posts="1" size="0" who="manish.iitm at yahoo.co.in (manish jaiswal)" />
+<person posts="1" size="0" who="alex at thehandofagony.com (Alexander Nicolaysen =?utf-8?q?S=C3=B8rnes?=)" />
+<person posts="1" size="0" who="dank06 at kegel.com (Dan Kegel)" />
+<person posts="1" size="0" who="tj at moka5.com (T.J. Purtell)" />
+<person posts="1" size="0" who="dimi at lattica.com (Dimi Paun)" />
+<person posts="1" size="0" who="pawel.rozanski at gmail.com (=?ISO-8859-2?Q?Pawe=B3_R=F3=BFa=F1ski?=)" />
+<person posts="1" size="0" who="cedar1182 at yahoo.com (Dave Cartright)" />
+<person posts="1" size="0" who="Stefan.Leichter at camline.com (Stefan Leichter)" />
+<person posts="1" size="0" who="research at science.su (L. Rahyen)" />
+<person posts="1" size="0" who="laurent at vromman.org (Laurent Vromman)" />
+<person posts="1" size="0" who="shachar at shemesh.biz (Shachar Shemesh)" />
+<person posts="1" size="0" who="jonathan at ernstfamily.ch (Jonathan Ernst)" />
+<person posts="1" size="0" who="klaus.layer at gmx.de (Klaus Layer)" />
+<person posts="1" size="0" who="jwhite at codeweavers.com (Jeremy White)" />
+<person posts="1" size="0" who="luis.busquets at ilidium.com (=?ISO-8859-1?Q?=22Luis_C=2E_Busquets_P=E9rez=22?=)" />
+<person posts="1" size="0" who="lich at math.spbu.ru (Kirill K. Smirnov)" />
+<person posts="1" size="0" who="mikazkow at tlen.pl (Maciej Kowalczyk)" />
+<person posts="1" size="0" who="jiangyi178 at rogers.com (Jiang,Yi)" />
+<person posts="1" size="0" who="ivg231 at gmail.com (Ivan Gyurdiev)" />
+<person posts="1" size="0" who="Andrew.Talbot at talbotville.com (Andrew Talbot)" />
+<person posts="1" size="0" who="jjmckenzie51 at earthlink.net (James McKenzie)" />
+
 </stats>
 <section 
 	title="New WWN Author"
@@ -143,14 +150,25 @@ Its main goal is to bring back the WWN!  It also serves to inform you of what's
 	posts="0"
 >
 <topic>Wine Weekly Newsletter</topic>
-<p>Hello world!  Okay sorry, I had to say it.  As you may be aware your loyal WWN author Brian Vincent has been unable to write the WWN for some time now.  I approached him a few weeks ago and offered my services to begin the weekly publications again.  He graciously agreed and sent me lots of resources etc. to begin.  And so, here I am. 
-</p>
-<p>
-A bit of shameless self promotion before I dedicate the rest of my life to providing you with quality Wine news.  I'm Zach Goldberg.  I work on a machine called <a href="http://www.bluesata.com">BlueSata</a> which is also my website and web server.  I am a computer science student at the University of Pennsylvania.  I have written some code for the <a href="http://enlightenment.org/">Enlightenment</a> (E17) project, and may perhaps in the future also send in some patches for wine.  So enough about me, I'm boring.  On with the wine!
-</p>
-
-
-
+<p>Hello world!  Okay sorry, I had to say it.  As you may be aware your loyal
+WWN author Brian Vincent has been unable to write the WWN for some time now.
+I approached him a few weeks ago and offered my services to begin the weekly
+publications again.  He graciously agreed and sent me lots of resources etc.
+to begin.  And so, here I am. 
+</p>
+<p>
+A bit of shameless self promotion before I dedicate the rest of my life to
+providing you with quality Wine news.  I'm Zach Goldberg.  I work on a
+machine called <a href="http://www.bluesata.com">BlueSata</a> which is also
+my website and web server.  I am a computer science student at the University
+of Pennsylvania.  I have written some code for the
+<a href="http://enlightenment.org/">Enlightenment</a> (E17) project, and may
+perhaps in the future also send in some patches for wine.  So enough about
+me, I'm boring.  On with the wine!
+</p>
+
+
+
 
 </section>
 
@@ -161,23 +179,33 @@ A bit of shameless self promotion before I dedicate the rest of my life to provi
 	posts="1"
 >
 <topic>DirectX</topic>
-<p><quote who="Roderick Colenbrander">
-wined3d: Use native shader limits instead of the maximum the driver can handle in software.
-This should prevent software fallbacks and and second it will allow for ps2.0/ps3.0 detection.
-
-wined3d: Default to GLSL. This is safe because we now have proper ps2.0/vs2.0 detection.
-</quote></p>
-<p>
-Its rare for the WWN to highlight individual commits however this one by Roderick Colenbrander actually could likely have an impact on the average (gaming) wine user.  This patch allows for natural detection and in combination with the  <a href="http://source.winehq.org/git/wine.git/?a=commit;h=59eba5cb41d165734468dcab0b38b56ff6c40ef0">following commit:</a> we now have the registry key "useGLSL" set to "enabled" by default.  This should mean that for many of us playing games such as <a href='http://appdb.winehq.org/objectManager.php?sClass=application&amp;iId=3150'>Elder Scrolls IV: Oblivion</a> may no longer have to set that key explicitly!  
-</p>
-
-
-
-
-
-
-
-
+<p><quote who="Roderick Colenbrander">
+wined3d: Use native shader limits instead of the maximum the driver can handle
+in software. This should prevent software fallbacks and and second it will
+allow for ps2.0/ps3.0 detection.
+
+wined3d: Default to GLSL. This is safe because we now have proper ps2.0/vs2.0
+detection.
+</quote></p>
+<p>
+Its rare for the WWN to highlight individual commits however this one by
+Roderick Colenbrander actually could likely have an impact on the average
+(gaming) wine user.  This patch allows for natural detection and in
+combination with the
+<a href="http://source.winehq.org/git/wine.git/?a=commit;h=59eba5cb41d165734468dcab0b38b56ff6c40ef0">following
+commit:</a> we now have the registry key "useGLSL" set to "enabled" by
+default.  This should mean that for many of us playing games such as
+<a href='http://appdb.winehq.org/objectManager.php?sClass=application&amp;iId=3150'>Elder
+Scrolls IV: Oblivion</a> may no longer have to set that key explicitly!  
+</p>
+
+
+
+
+
+
+
+
 
 </section>
 
@@ -188,63 +216,70 @@ Its rare for the WWN to highlight individual commits however this one by Roderic
 	posts="7"
 >
 <topic>Applications</topic>
-<p>We all know that of the many uses for wine gaming is one of the more popular ones.  But just how many actual gamers are there using wine to play their favorite games?  Well, lucky for us Valve has begun to conduct surveys of the hardware and software configurations of people using their Steam system.  They've even been kind enough to respond to emails and give us some data.</p>
-<p><quote who="Scott Ritchie">
-Valve regularly runs surveys of steam users, where they profile many
-different things about the hardware.  They're nice enough to publish the
-results:<br />
-<br />
-<a href="http://www.steampowered.com/status/survey.html">http://www.steampowered.com/status/survey.html</a>
-<p>
-Some of these provide a way to detect Wine users.  Everyone using the
-"Wine waveout" audio driver, for instance, must be a Wine user.
-Unfortunately, valve lumps all of these into "other" on the survey
-results page.
-</p><p>
-Worries about sampling bias aside (maybe Wine users are less likely to
-do the steam survey), if we had the raw data from Valve we could
-determine the actual percentage of Steam users playing through Wine.
-</p><p>
-Looking at the data we do have, we may be able to make a good guess from
-examining the video card driver name field.  Excluding NVidia, ATI, and
-Intel leaves just over 4% of respondents using an "other" video driver
-like the Wine one.  If even only a quarter of these "others" are using
-Wine, that still gives us 1% of the entire 10 million+ Steam user base,
-translating into hundreds of thousands of users.
-</p></quote></p><p>
-As you can see, its actually non-trivial to determine who uses wine simply from the drivers and such reported by the Steam survey.  However we seem to have caught a lucky break with the sound driver:</p>
-<p><quote who="Stefan Dosinger"><pre>
-More interesting is the "Video Card Driver Name":
-Video Card Driver Name
-
-nv4_disp.dll  10,269  
-53.43 %#####################################################
-  ati2dvag.dll  5,060  26.33 %##########################
-  nvd3dum.dll  2,698  14.04 %##############
-  atiumdag.dll  571  2.97 %###
-  ialmrnt5.dll  302  1.57 %##
-  Other  319  1.66 %##
-
-This identifies the DLL, and wine has none of them. So we'd show up in the 
-Other section here. Possible others in Windows space are matrox, sis and 
-other chips, as well as the generic vesa driver.
-
-The best identification is the sound card name, or if Wine's display driver 
-shows up as winex11.drv
-</pre>
-</quote></p>
-<p>
-And as of November 24th we have the following update from Alfred Reynolds:
-</p><p><quote who="Alfred Reynolds">
-The numbers are now 0.13% of total reports coming from Wine users.
-</quote></p>
-
-
-
-
-
-
-
+<p>We all know that of the many uses for wine gaming is one of the more
+popular ones.  But just how many actual gamers are there using wine to play
+their favorite games?  Well, lucky for us Valve has begun to conduct surveys
+of the hardware and software configurations of people using their Steam
+system.  They've even been kind enough to respond to emails and give us some
+data.</p>
+<p><quote who="Scott Ritchie">
+Valve regularly runs surveys of steam users, where they profile many
+different things about the hardware.  They're nice enough to publish the
+results:<br />
+<br />
+<a href="http://www.steampowered.com/status/survey.html">http://www.steampowered.com/status/survey.html</a>
+<p>
+Some of these provide a way to detect Wine users.  Everyone using the
+"Wine waveout" audio driver, for instance, must be a Wine user.
+Unfortunately, valve lumps all of these into "other" on the survey
+results page.
+</p><p>
+Worries about sampling bias aside (maybe Wine users are less likely to
+do the steam survey), if we had the raw data from Valve we could
+determine the actual percentage of Steam users playing through Wine.
+</p><p>
+Looking at the data we do have, we may be able to make a good guess from
+examining the video card driver name field.  Excluding NVidia, ATI, and
+Intel leaves just over 4% of respondents using an "other" video driver
+like the Wine one.  If even only a quarter of these "others" are using
+Wine, that still gives us 1% of the entire 10 million+ Steam user base,
+translating into hundreds of thousands of users.
+</p></quote></p><p>
+As you can see, its actually non-trivial to determine who uses wine simply
+from the drivers and such reported by the Steam survey.  However we seem to
+have caught a lucky break with the sound driver:</p>
+<p><quote who="Stefan Dosinger"><pre>
+More interesting is the "Video Card Driver Name":
+Video Card Driver Name
+
+nv4_disp.dll  10,269  
+53.43 %#####################################################
+  ati2dvag.dll  5,060  26.33 %##########################
+  nvd3dum.dll  2,698  14.04 %##############
+  atiumdag.dll  571  2.97 %###
+  ialmrnt5.dll  302  1.57 %##
+  Other  319  1.66 %##
+
+This identifies the DLL, and wine has none of them. So we'd show up in the 
+Other section here. Possible others in Windows space are matrox, sis and 
+other chips, as well as the generic vesa driver.
+
+The best identification is the sound card name, or if Wine's display driver 
+shows up as winex11.drv
+</pre>
+</quote></p>
+<p>
+And as of November 24th we have the following update from Alfred Reynolds:
+</p><p><quote who="Alfred Reynolds">
+The numbers are now 0.13% of total reports coming from Wine users.
+</quote></p>
+
+
+
+
+
+
+
 
 </section>
 
@@ -255,23 +290,29 @@ The numbers are now 0.13% of total reports coming from Wine users.
 	posts="1"
 >
 <topic>Wine</topic>
-<p>Some of you may be very upset at the lack of a wine 0.9.50 last week.  Unfortunately many of the dev's were out stuffing themselves with turkey and hence a release last week made no sense.  However, this week has come and we have 0.9.50:</p>
-<p><quote who="Alexander Juillard"><pre>
-    Wine 0.9.50 was released today, with the following main changes:
-
-        * Completed I/O completion.
-        * Improved user credentials management, including Mac Keychain support.
-        * More Valgrinding.
-        * Lots of bug fixes.
-
-    Binary packages are in the process of being built and it may take a few days for them to appear, but the source is available now. You can find out more about this release in the announcement. Check out our download page for packages for your distribution.
-</pre></quote></p>
-
-
-
-
-
-
+<p>Some of you may be very upset at the lack of a wine 0.9.50 last week.
+Unfortunately many of the dev's were out stuffing themselves with turkey and
+hence a release last week made no sense.  However, this week has come and we
+have 0.9.50:</p>
+<p><quote who="Alexander Juillard"><pre>
+    Wine 0.9.50 was released today, with the following main changes:
+
+        * Completed I/O completion.
+        * Improved user credentials management, including Mac Keychain support.
+        * More Valgrinding.
+        * Lots of bug fixes.
+
+    Binary packages are in the process of being built and it may take a few
+days for them to appear, but the source is available now. You can find out
+more about this release in the announcement. Check out our download page for
+packages for your distribution.
+</pre></quote></p>
+
+
+
+
+
+
 
 </section>
 
@@ -282,70 +323,78 @@ The numbers are now 0.13% of total reports coming from Wine users.
 	posts="9"
 >
 <topic>Code</topic>
-<p>Kai Blin brings up the topic of planning out this summer's Google Summer of Code projects.  The problem, he explains, is that projects were not extremly well defined and communication was not as good as it could have been.  All easily solvable.</p>
-<p><quote who="Kai Blin">
-Hi folks,<br />
-<p>
-from what we discussed at the last WineConf, we wanted to work on our
-procedures for the Google Summer of Code a little.
-I'm sending this email in hope to start some discussion about this, so we have
-it out of the way until the 2008 version is announced so we can talk about
-proposed projects then.
-</p><p>
-The goal of Wine's SoC procedures should be to get high-quality proposals that
-can be completed by the student proposing the project in the time allocated
-for GSoC, so both scope and difficulty should be checked.
-I haven't been on the mentoring side of things, but my understanding from the
-WineConf side of things was that we had some problems getting this right the
-past years.
-</p><p>
-I was thinking about strongly encouraging people to post their project
-proposal to wine-devel prior to applying, so more developers can have a look
-at it and see if it's doable or not and offer suggestions.<br />
-</p><p>
-I know some projects did an introductory quiz to figure out the student's
-coding skills, I'm not convinced the knowledge needed for Wine can be tested
-in a quiz. What do you think?<br />
-</p><p>
-Another thing that didn't turn out too well last time is that it was really
-hard to figure out what was going on during the summer. I have a few ideas on
-how we could address this.
-</p><p>
-Lots of other projects had their student write a weekly public progress
-report. I think we should require the same. This will probably help keeping
-people updated, and might help spotting problems early.
-</p><p>
-According to the wiki page, we already require a post-mortem report on the
-project, however I can't remember seeing much of those this year. We should
-make sure those are written next time. We might think of a better name for
-the report, post-mortem sounds like the project is dead after the summer, we
-want people to keep working.
-</p><p>
-Last year, some of the students set up a public git repo on repo.or.cz. I was
-thinking about making that a requirement for next year. This would allow
-people to review work in progress.
-</p><p>
-Comments?
-Kai
-</p></quote></p>
-<p>
-General response is that 'organization sounds like a good idea'.  Maarten Lankhorst recommended that instead of a quiz to screen students, there be a requirement that they submit small patches.
-</p>
-<p><quote who="Maarten Lankhorst">
-I don't like the idea of a quiz as well, what would be a better test is
-to get a small patch into wine, perhaps adding a testcase to the
-component they want to work on. It shouldn't be big, but it proves they
-can get code into wine.
-</quote></p>
-
-Jesse Allen then wrote in to discuss his experience working as a student in GSoC 2006.  In general he explains that if some of the discussed features were implemented (public blogs, public git repositories etc.) they most certainly would have been used and been a great resource.
-
-
-
-
-
-
-
+<p>Kai Blin brings up the topic of planning out this summer's Google Summer
+of Code projects.  The problem, he explains, is that projects were not
+extremly well defined and communication was not as good as it could have
+been.  All easily solvable.</p>
+<p><quote who="Kai Blin">
+Hi folks,<br />
+<p>
+from what we discussed at the last WineConf, we wanted to work on our
+procedures for the Google Summer of Code a little.
+I'm sending this email in hope to start some discussion about this, so we have
+it out of the way until the 2008 version is announced so we can talk about
+proposed projects then.
+</p><p>
+The goal of Wine's SoC procedures should be to get high-quality proposals that
+can be completed by the student proposing the project in the time allocated
+for GSoC, so both scope and difficulty should be checked.
+I haven't been on the mentoring side of things, but my understanding from the
+WineConf side of things was that we had some problems getting this right the
+past years.
+</p><p>
+I was thinking about strongly encouraging people to post their project
+proposal to wine-devel prior to applying, so more developers can have a look
+at it and see if it's doable or not and offer suggestions.<br />
+</p><p>
+I know some projects did an introductory quiz to figure out the student's
+coding skills, I'm not convinced the knowledge needed for Wine can be tested
+in a quiz. What do you think?<br />
+</p><p>
+Another thing that didn't turn out too well last time is that it was really
+hard to figure out what was going on during the summer. I have a few ideas on
+how we could address this.
+</p><p>
+Lots of other projects had their student write a weekly public progress
+report. I think we should require the same. This will probably help keeping
+people updated, and might help spotting problems early.
+</p><p>
+According to the wiki page, we already require a post-mortem report on the
+project, however I can't remember seeing much of those this year. We should
+make sure those are written next time. We might think of a better name for
+the report, post-mortem sounds like the project is dead after the summer, we
+want people to keep working.
+</p><p>
+Last year, some of the students set up a public git repo on repo.or.cz. I was
+thinking about making that a requirement for next year. This would allow
+people to review work in progress.
+</p><p>
+Comments?
+Kai
+</p></quote></p>
+<p>
+General response is that 'organization sounds like a good idea'.  Maarten
+Lankhorst recommended that instead of a quiz to screen students, there be a
+requirement that they submit small patches.
+</p>
+<p><quote who="Maarten Lankhorst">
+I don't like the idea of a quiz as well, what would be a better test is
+to get a small patch into wine, perhaps adding a testcase to the
+component they want to work on. It shouldn't be big, but it proves they
+can get code into wine.
+</quote></p>
+
+Jesse Allen then wrote in to discuss his experience working as a student in
+GSoC 2006.  In general he explains that if some of the discussed features
+were implemented (public blogs, public git repositories etc.) they most
+certainly would have been used and been a great resource.
+
+
+
+
+
+
+
 
 </section>
 
@@ -356,53 +405,57 @@ Jesse Allen then wrote in to discuss his experience working as a student in GSoC
 	posts="4"
 >
 <topic>Code</topic>
-<p>Gavriel State of Transgaming has been hanging around on one of wine's IRC Channels (#winehackers) and in a conversation with Kai Blin actually offered code for something Transgaming has already begun to implement:
-</p>
-<p><quote author="Gavrial State">
-Hi all,<br />
-<br />
-<p>
-On #winehackers the other day, kblin asked about whether TransGaming had 
-a Direct Play implementation.  The answer is that we have something that 
-was worked on for a while but never completed.  We have had some partial 
-success with it in the initial connection stages, but never pushed it 
-much beyond that.
-</p><p>
-Enclosed here is a patch to today's WineHQ git tree with our dpnet 
-implementation in the hopes that someone finds it useful.  Beyond 
-ensuring that it compiles and links, it has not been tested at all with 
-WineHQ.
-</p><p>
-Take care,<br />
- -Gav
-</p></quote></p>
-Kai is of course quiet happy:
-<p><quote who="Kai Blin">
-Hi Gav,<br />
-<br />
-Thanks for getting back with that one faster than I managed to remind you 
-about it.  I hope to get around playing with it later this week, I'm currently somewhat 
-busy writing code I'm getting paid for. :)
-</quote></p>
-
-Later though, in Kai's attempts to apply the patch there were some small issues.  However, he made Gavriel aware of them and within a day or 2 Gavriel responded with the following:
-<p><quote who="Gavriel State">
-Hi Kai,
-
-Sorry about that - looks like I hadn't in fact updated my git tree quite 
-properly.  Also, I left out a header file I think. Try this patch instead.
-
-Take care,
- -Gav
-</quote>
-</p>
-
-
-
-
-
-
-
+<p>Gavriel State of Transgaming has been hanging around on one of wine's IRC
+Channels (#winehackers) and in a conversation with Kai Blin actually offered
+code for something Transgaming has already begun to implement:
+</p>
+<p><quote author="Gavrial State">
+Hi all,<br />
+<br />
+<p>
+On #winehackers the other day, kblin asked about whether TransGaming had 
+a Direct Play implementation.  The answer is that we have something that 
+was worked on for a while but never completed.  We have had some partial 
+success with it in the initial connection stages, but never pushed it 
+much beyond that.
+</p><p>
+Enclosed here is a patch to today's WineHQ git tree with our dpnet 
+implementation in the hopes that someone finds it useful.  Beyond 
+ensuring that it compiles and links, it has not been tested at all with 
+WineHQ.
+</p><p>
+Take care,<br />
+ -Gav
+</p></quote></p>
+Kai is of course quiet happy:
+<p><quote who="Kai Blin">
+Hi Gav,<br />
+<br />
+Thanks for getting back with that one faster than I managed to remind you 
+about it.  I hope to get around playing with it later this week, I'm
+currently somewhat busy writing code I'm getting paid for. :)
+</quote></p>
+
+Later though, in Kai's attempts to apply the patch there were some small
+issues.  However, he made Gavriel aware of them and within a day or 2 Gavriel
+responded with the following:
+<p><quote who="Gavriel State">
+Hi Kai,
+
+Sorry about that - looks like I hadn't in fact updated my git tree quite 
+properly.  Also, I left out a header file I think. Try this patch instead.
+
+Take care,
+ -Gav
+</quote>
+</p>
+
+
+
+
+
+
+
 
 </section>
 
@@ -413,44 +466,46 @@ Take care,
 	posts="2"
 >
 <topic>Wine</topic>
-<p>Dan Kegel has written in with a bit of an update on the status of Wine 1.0</p>
-<p><quote who="Dan Kegel">
-<pre>[putting on tastemaster hat]
-
-So far, 82 bugs have been nominated to be fixed for 1.0.
-I checked a bunch of them, and so far most look
-reasonable.  Some even look easy or have patches, e.g.
-<a href="http://bugs.winehq.org/show_bug.cgi?id=5402">http://bugs.winehq.org/show_bug.cgi?id=5402</a>
-<a href="http://bugs.winehq.org/show_bug.cgi?id=5884">http://bugs.winehq.org/show_bug.cgi?id=5884</a>
-<a href="http://bugs.winehq.org/show_bug.cgi?id=7544">http://bugs.winehq.org/show_bug.cgi?id=7544</a>
-<a href="http://bugs.winehq.org/show_bug.cgi?id=7571">http://bugs.winehq.org/show_bug.cgi?id=7571</a>
-<a href="http://bugs.winehq.org/show_bug.cgi?id=9104">http://bugs.winehq.org/show_bug.cgi?id=9104</a>
-<a href="http://bugs.winehq.org/show_bug.cgi?id=10147">http://bugs.winehq.org/show_bug.cgi?id=10147</a>
-
-The list looks meaty enough that it's probably worth
-folks going through and seeing what they can pick off.
-
-Stuff that's silly or too hard - just skip it for now,
-we'll defer those for later.
-- Dan
-
-</pre>
-</quote></p>
-Dan also mentions
-<p><quote who="Dan Kegel">
-Forgot to mention:
-http://wiki.winehq.org/WineReleaseCriteria
-has a handy link to a bugzilla query that shows the list of 1.0 bugs.
-</quote></p>
-
-Wine 1.0 is a topic that seems to crop up now and then; hopefully in the near future we'll see that list of ~80 bugs dwindle into the single digits and we'll have a big release (and a party, of course)!
-
-
-
-
-
-
-
+<p>Dan Kegel has written in with a bit of an update on the status of Wine 1.0</p>
+<p><quote who="Dan Kegel">
+<pre>[putting on tastemaster hat]
+
+So far, 82 bugs have been nominated to be fixed for 1.0.
+I checked a bunch of them, and so far most look
+reasonable.  Some even look easy or have patches, e.g.
+<a href="http://bugs.winehq.org/show_bug.cgi?id=5402">http://bugs.winehq.org/show_bug.cgi?id=5402</a>
+<a href="http://bugs.winehq.org/show_bug.cgi?id=5884">http://bugs.winehq.org/show_bug.cgi?id=5884</a>
+<a href="http://bugs.winehq.org/show_bug.cgi?id=7544">http://bugs.winehq.org/show_bug.cgi?id=7544</a>
+<a href="http://bugs.winehq.org/show_bug.cgi?id=7571">http://bugs.winehq.org/show_bug.cgi?id=7571</a>
+<a href="http://bugs.winehq.org/show_bug.cgi?id=9104">http://bugs.winehq.org/show_bug.cgi?id=9104</a>
+<a href="http://bugs.winehq.org/show_bug.cgi?id=10147">http://bugs.winehq.org/show_bug.cgi?id=10147</a>
+
+The list looks meaty enough that it's probably worth
+folks going through and seeing what they can pick off.
+
+Stuff that's silly or too hard - just skip it for now,
+we'll defer those for later.
+- Dan
+
+</pre>
+</quote></p>
+Dan also mentions
+<p><quote who="Dan Kegel">
+Forgot to mention:
+http://wiki.winehq.org/WineReleaseCriteria
+has a handy link to a bugzilla query that shows the list of 1.0 bugs.
+</quote></p>
+
+Wine 1.0 is a topic that seems to crop up now and then; hopefully in the near
+future we'll see that list of ~80 bugs dwindle into the single digits and
+we'll have a big release (and a party, of course)!
+
+
+
+
+
+
+
 
 </section>
 
@@ -461,35 +516,41 @@ Wine 1.0 is a topic that seems to crop up now and then; hopefully in the near fu
 	posts="1"
 >
 <topic>Wine</topic>
-<p>Courtesy of some very complicated patches introduced recently (for SecureROM) Wine will no longer build properly using GCC 4.0.X.  Even as somebody who studies computer science the actual thread discussing the details of these patches and why they break compilation in certain versions of GCC is extremely complicated.  However, if you dare, <a href="http://bugs.winehq.org/show_bug.cgi?id=10273"> this is the link </a> with all the juicy details.
-</p>
-<p><quote who="Dan Kegel"><pre>
-Attention packagers: the default version of gcc on
-many distros happens to generate Wine binaries which
-make some copy protection schemes unhappy.
-At the moment, gcc-3.3.x, gcc-3.4.x, and gcc-4.2.x are
-known to work; gcc-4.0.x is known to not work.
-Please check the compiler you use when building wine
-packages and make sure it's one of the good ones.
-
-To really check, find a retail copy of Photoshop CS or CS2
-(not 7 or CS3) and install from cd-rom.  If it aborts silently
-near the end without offering to activate the product, you
-have an unsupported compiler, and users of your packages
-might run into trouble with apps protected with safedisc.
-
-See <a href="http://bugs.winehq.org/show_bug.cgi?id=10273">http://bugs.winehq.org/show_bug.cgi?id=10273</a> for more info.
-- Dan
-</pre>
-</quote></p>
-
-
-
-
-
-
-
-
+<p>Courtesy of some very complicated patches introduced recently (for
+SecureROM) Wine will no longer build properly using GCC 4.0.X.  Even as
+somebody who studies computer science the actual thread discussing the
+details of these patches and why they break compilation in certain versions
+of GCC is extremely complicated.  However, if you dare,
+<a href="http://bugs.winehq.org/show_bug.cgi?id=10273"> this is the link </a>
+with all the juicy details.
+</p>
+<p><quote who="Dan Kegel"><pre>
+Attention packagers: the default version of gcc on
+many distros happens to generate Wine binaries which
+make some copy protection schemes unhappy.
+At the moment, gcc-3.3.x, gcc-3.4.x, and gcc-4.2.x are
+known to work; gcc-4.0.x is known to not work.
+Please check the compiler you use when building wine
+packages and make sure it's one of the good ones.
+
+To really check, find a retail copy of Photoshop CS or CS2
+(not 7 or CS3) and install from cd-rom.  If it aborts silently
+near the end without offering to activate the product, you
+have an unsupported compiler, and users of your packages
+might run into trouble with apps protected with safedisc.
+
+See <a href="http://bugs.winehq.org/show_bug.cgi?id=10273">http://bugs.winehq.org/show_bug.cgi?id=10273</a> for more info.
+- Dan
+</pre>
+</quote></p>
+
+
+
+
+
+
+
+
 
 </section>
 </kc>
-- 
1.5.3.7




More information about the wine-patches mailing list