<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Ballontekst Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.E-mailStijl17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BallontekstChar
        {mso-style-name:"Ballontekst Char";
        mso-style-priority:99;
        mso-style-link:Ballontekst;
        font-family:"Tahoma","sans-serif";
        mso-fareast-language:NL;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=NL link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks for your answers Milan and José! How could I’ve missed that? :0<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>One question though.. whenever I upload a new .pos file will this override all current translations for a given field? Or does everything get wiped clean? In some cases translation have been made for certain fields in the 3.0.x branch which have not been translated in the development trunk.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>ForSite Media<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>WordPress Consultancy, Development &amp; Design<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>0622-164385 | www.forsite.nu |info@forsite.nu<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Van:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Milan Dinić [mailto:liste@srpski.biz] <br><b>Verzonden:</b> vrijdag 30 juli 2010 13:43<br><b>Aan:</b> remkus@forsite.nu; wp-polyglots@lists.automattic.com<br><b>Onderwerp:</b> Re: [wp-polyglots] Dutch translation mergin of trunk translation with development<o:p></o:p></span></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>For now, you need to export translations from trunk and import them in 3.0.x. There is a ticket ( <a href="http://trac.glotpress.org/ticket/66">http://trac.glotpress.org/ticket/66</a> ) in GlotPress for enabling copying between two translations sets which would make this process easier.<o:p></o:p></p><div><p class=MsoNormal>2010/7/30 Remkus de Vries | ForSite Media &lt;<a href="mailto:info@forsite.nu">info@forsite.nu</a>&gt;<o:p></o:p></p><p class=MsoNormal>Hi, it's me again :)<br><br>I have requested a chat with somebody in charge of the GlotPress<br>translations a few weeks back but I have gotten no response yet... Right now<br>the main issue is that we would like to merge the translation of the<br>development trunk with 3.0.x branch. Most of the translations have been done<br>in the development area and it just seems like a huge waste of time to have<br>to that for the 3.0.x branch as well..<br><br>If there is a way I can do this myself that would be great but I don't see<br>it :(<br><br>Thanks,<br>Remkus<br><br><br><br>ForSite Media<br>WordPress Consultancy, Development &amp; Design<br>0622-164385 | <a href="http://www.forsite.nu" target="_blank">www.forsite.nu</a> |<a href="mailto:info@forsite.nu">info@forsite.nu</a><br><br><br>-----Oorspronkelijk bericht-----<br>Van: <a href="mailto:wp-polyglots-bounces@lists.automattic.com">wp-polyglots-bounces@lists.automattic.com</a><br>[mailto:<a href="mailto:wp-polyglots-bounces@lists.automattic.com">wp-polyglots-bounces@lists.automattic.com</a>] Namens<br><a href="mailto:wp-polyglots-request@lists.automattic.com">wp-polyglots-request@lists.automattic.com</a><br>Verzonden: vrijdag 30 juli 2010 11:47<br>Aan: <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>Onderwerp: wp-polyglots Digest, Vol 66, Issue 43<br><br>Send wp-polyglots mailing list submissions to<br>&nbsp; &nbsp; &nbsp; &nbsp;<a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br>&nbsp; &nbsp; &nbsp; &nbsp;<a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>or, via email, send a message with subject or body 'help' to<br>&nbsp; &nbsp; &nbsp; &nbsp;<a href="mailto:wp-polyglots-request@lists.automattic.com">wp-polyglots-request@lists.automattic.com</a><br><br>You can reach the person managing the list at<br>&nbsp; &nbsp; &nbsp; &nbsp;<a href="mailto:wp-polyglots-owner@lists.automattic.com">wp-polyglots-owner@lists.automattic.com</a><br><br>When replying, please edit your Subject line so it is more specific than<br>&quot;Re: Contents of wp-polyglots digest...&quot;<br><br><br>Today's Topics:<br><br>&nbsp; 1. Re: WordPress 3.0.1 expected around mid July (Peter Holme)<br>&nbsp; 2. Re: WordPress 3.0.1 expected around mid July (Peter Holme)<br>&nbsp; 3. Re: WordPress 3.0.1 expected around mid July (Xavier Borderie)<br>&nbsp; 4. Re: WordPress 3.0.1 expected around mid July (Mattias Tengblad)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Fri, 30 Jul 2010 07:12:31 +0200<br>From: Peter Holme &lt;<a href="mailto:peter@holme.se">peter@holme.se</a>&gt;<br>Subject: Re: [wp-polyglots] WordPress 3.0.1 expected around mid July<br>To: <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>Message-ID:<br>&nbsp; &nbsp; &nbsp; &nbsp;&lt;AANLkTim=<a href="mailto:Z0We9V2oJAfCBtWyeQgTc84ETUDGN8WTNpUk@mail.gmail.com">Z0We9V2oJAfCBtWyeQgTc84ETUDGN8WTNpUk@mail.gmail.com</a>&gt;<br>Content-Type: text/plain; charset=&quot;utf-8&quot;<br><br>Sorry.. read through the revision statements - it seems we should use 15480.<br>I'll go with that.<br><br>Peter<br><br>On Fri, Jul 30, 2010 at 07:09, Peter Holme &lt;<a href="mailto:peter@holme.se">peter@holme.se</a>&gt; wrote:<br><br>&gt; So what revision are we supposed to use? 15477 or 15480? (I suspect I<br>&gt; might have used the wrong one for 3.0, 'cause the &quot;upgrade available&quot;<br>&gt; message has appeared sporadically since I upgraded)<br>&gt;<br>&gt; Peter (nb_NO)<br>&gt;<br>&gt;<br>&gt; On Fri, Jul 30, 2010 at 02:55, Milan Dini? &lt;<a href="mailto:liste@srpski.biz">liste@srpski.biz</a>&gt; wrote:<br>&gt;<br>&gt;&gt; Dear Andrew,<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; Please don't think of this e-mail as of some attempt to blame you,<br>&gt;&gt;&gt; I'm only agreeing on the point quoted. Sorry if you got me wrong!<br>&gt;&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; Just to clarify that I too wasn't meaning just on Andrew but to all<br>&gt;&gt; developers.<br>&gt;&gt;<br>&gt;&gt; 2010/7/30 Wac?aw Jacek &lt;<a href="mailto:mail@waclawjacek.com">mail@waclawjacek.com</a>&gt;<br>&gt;&gt;<br>&gt;&gt; On Thu, Jul 29, 2010 at 08:02:06PM -0400, Andrew Nacin wrote:<br>&gt;&gt;&gt; &gt; 2010/7/29 Wac?aw Jacek &lt;<a href="mailto:mail@waclawjacek.com">mail@waclawjacek.com</a>&gt;<br>&gt;&gt;&gt; &gt;<br>&gt;&gt;&gt; &gt; &gt; On Fri, Jul 30, 2010 at 02:36:18AM +0300, Rasheed Bydousi wrote:<br>&gt;&gt;&gt; &gt; &gt; &gt; I think translators should know about new releases much earlier.<br>&gt;&gt;&gt; &gt; &gt; That's true, in order for us to translate stuff on time and take<br>&gt;&gt;&gt; proper<br>&gt;&gt;&gt; &gt; &gt; care of the regional communities by providing on-time<br>&gt;&gt;&gt; &gt; &gt; translations we<br>&gt;&gt;&gt; need<br>&gt;&gt;&gt; &gt; &gt; to know of expected upgrades earlier than they are released.<br>&gt;&gt;&gt; Obviously this<br>&gt;&gt;&gt; &gt; &gt; shouldn't apply if and update is a crucial bug fix. :)<br>&gt;&gt;&gt; &gt;<br>&gt;&gt;&gt; &gt;<br>&gt;&gt;&gt; &gt; Demetris emailed this list 19 days ago, and we haven't changed a<br>&gt;&gt;&gt; &gt; string since. I also alerted the list to string changes as they<br>&gt;&gt;&gt; &gt; occurred. Your translations should be complete; you only need to push<br>a button now.<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; Dear Andrew,<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; Please don't think of this e-mail as of some attempt to blame you,<br>&gt;&gt;&gt; I'm only agreeing on the point quoted. Sorry if you got me wrong!<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; Cheers!<br>&gt;&gt;&gt; WJ<br>&gt;&gt;&gt; _______________________________________________<br>&gt;&gt;&gt; wp-polyglots mailing list<br>&gt;&gt;&gt; <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>&gt;&gt;&gt; <a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>&gt;&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; _______________________________________________<br>&gt;&gt; wp-polyglots mailing list<br>&gt;&gt; <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>&gt;&gt; <a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>&gt;&gt;<br>&gt;&gt;<br>&gt;<br>&gt;<br>&gt; --<br>&gt; +47 920 42 782<br>&gt;<br><br><br><br>--<br>+47 920 42 782<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL:<br>&lt;<a href="http://lists.automattic.com/pipermail/wp-polyglots/attachments/20100730/55d%0A3b700/attachment-0001.htm" target="_blank">http://lists.automattic.com/pipermail/wp-polyglots/attachments/20100730/55d<br>3b700/attachment-0001.htm</a>&gt;<br><br>------------------------------<br><br>Message: 2<br>Date: Fri, 30 Jul 2010 07:18:23 +0200<br>From: Peter Holme &lt;<a href="mailto:peter@holme.se">peter@holme.se</a>&gt;<br>Subject: Re: [wp-polyglots] WordPress 3.0.1 expected around mid July<br>To: <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>Message-ID:<br>&nbsp; &nbsp; &nbsp; &nbsp;&lt;<a href="mailto:AANLkTinGETn9s5__PeBcM3qGppCNhSHAs2pKPmVTSHPY@mail.gmail.com">AANLkTinGETn9s5__PeBcM3qGppCNhSHAs2pKPmVTSHPY@mail.gmail.com</a>&gt;<br>Content-Type: text/plain; charset=&quot;utf-8&quot;<br><br>nope. that didn't work...<br><br>These are the settings I use:<br>- Where to take translations from: <a href="http://translate.wordpress.org" target="_blank">translate.wordpress.org</a><br>- Locale branch for dist-files: tags/3.0.1<br>- Project: Development (trunk)<br>- WordPress revision: HEAD (15480)<br>- WordPress version: 3.0.1<br><br>When these settings are used, version.php says 3.1-alpha...<br><br>Peter<br><br><br>On Fri, Jul 30, 2010 at 07:12, Peter Holme &lt;<a href="mailto:peter@holme.se">peter@holme.se</a>&gt; wrote:<br><br>&gt; Sorry.. read through the revision statements - it seems we should use<br>&gt; 15480. I'll go with that.<br>&gt;<br>&gt; Peter<br>&gt;<br>&gt;<br>&gt; On Fri, Jul 30, 2010 at 07:09, Peter Holme &lt;<a href="mailto:peter@holme.se">peter@holme.se</a>&gt; wrote:<br>&gt;<br>&gt;&gt; So what revision are we supposed to use? 15477 or 15480? (I suspect I<br>&gt;&gt; might have used the wrong one for 3.0, 'cause the &quot;upgrade available&quot;<br>&gt;&gt; message has appeared sporadically since I upgraded)<br>&gt;&gt;<br>&gt;&gt; Peter (nb_NO)<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; On Fri, Jul 30, 2010 at 02:55, Milan Dini? &lt;<a href="mailto:liste@srpski.biz">liste@srpski.biz</a>&gt; wrote:<br>&gt;&gt;<br>&gt;&gt;&gt; Dear Andrew,<br>&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt; Please don't think of this e-mail as of some attempt to blame you,<br>&gt;&gt;&gt;&gt; I'm only agreeing on the point quoted. Sorry if you got me wrong!<br>&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; Just to clarify that I too wasn't meaning just on Andrew but to all<br>&gt;&gt;&gt; developers.<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; 2010/7/30 Wac?aw Jacek &lt;<a href="mailto:mail@waclawjacek.com">mail@waclawjacek.com</a>&gt;<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; On Thu, Jul 29, 2010 at 08:02:06PM -0400, Andrew Nacin wrote:<br>&gt;&gt;&gt;&gt; &gt; 2010/7/29 Wac?aw Jacek &lt;<a href="mailto:mail@waclawjacek.com">mail@waclawjacek.com</a>&gt;<br>&gt;&gt;&gt;&gt; &gt;<br>&gt;&gt;&gt;&gt; &gt; &gt; On Fri, Jul 30, 2010 at 02:36:18AM +0300, Rasheed Bydousi wrote:<br>&gt;&gt;&gt;&gt; &gt; &gt; &gt; I think translators should know about new releases much earlier.<br>&gt;&gt;&gt;&gt; &gt; &gt; That's true, in order for us to translate stuff on time and<br>&gt;&gt;&gt;&gt; &gt; &gt; take<br>&gt;&gt;&gt;&gt; proper<br>&gt;&gt;&gt;&gt; &gt; &gt; care of the regional communities by providing on-time<br>&gt;&gt;&gt;&gt; &gt; &gt; translations<br>&gt;&gt;&gt;&gt; we need<br>&gt;&gt;&gt;&gt; &gt; &gt; to know of expected upgrades earlier than they are released.<br>&gt;&gt;&gt;&gt; Obviously this<br>&gt;&gt;&gt;&gt; &gt; &gt; shouldn't apply if and update is a crucial bug fix. :)<br>&gt;&gt;&gt;&gt; &gt;<br>&gt;&gt;&gt;&gt; &gt;<br>&gt;&gt;&gt;&gt; &gt; Demetris emailed this list 19 days ago, and we haven't changed a<br>&gt;&gt;&gt;&gt; string<br>&gt;&gt;&gt;&gt; &gt; since. I also alerted the list to string changes as they occurred.<br>&gt;&gt;&gt;&gt; Your<br>&gt;&gt;&gt;&gt; &gt; translations should be complete; you only need to push a button now.<br>&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt; Dear Andrew,<br>&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt; Please don't think of this e-mail as of some attempt to blame you,<br>&gt;&gt;&gt;&gt; I'm only agreeing on the point quoted. Sorry if you got me wrong!<br>&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt; Cheers!<br>&gt;&gt;&gt;&gt; WJ<br>&gt;&gt;&gt;&gt; _______________________________________________<br>&gt;&gt;&gt;&gt; wp-polyglots mailing list<br>&gt;&gt;&gt;&gt; <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>&gt;&gt;&gt;&gt; <a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; _______________________________________________<br>&gt;&gt;&gt; wp-polyglots mailing list<br>&gt;&gt;&gt; <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>&gt;&gt;&gt; <a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>&gt;&gt;&gt;<br>&gt;&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; --<br>&gt;&gt; +47 920 42 782<br>&gt;&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt; --<br>&gt; +47 920 42 782<br>&gt;<br><br><br><br>--<br>+47 920 42 782<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL:<br>&lt;<a href="http://lists.automattic.com/pipermail/wp-polyglots/attachments/20100730/690%0A24555/attachment-0001.htm" target="_blank">http://lists.automattic.com/pipermail/wp-polyglots/attachments/20100730/690<br>24555/attachment-0001.htm</a>&gt;<br><br>------------------------------<br><br>Message: 3<br>Date: Fri, 30 Jul 2010 11:27:02 +0200<br>From: Xavier Borderie &lt;<a href="mailto:xavier@borderie.net">xavier@borderie.net</a>&gt;<br>Subject: Re: [wp-polyglots] WordPress 3.0.1 expected around mid July<br>To: <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>Message-ID:<br>&nbsp; &nbsp; &nbsp; &nbsp;&lt;<a href="mailto:AANLkTik17G%2B8KGuyR7TK0%2BUU2peXGMeQwV05XdXGdfit@mail.gmail.com">AANLkTik17G+8KGuyR7TK0+UU2peXGMeQwV05XdXGdfit@mail.gmail.com</a>&gt;<br>Content-Type: text/plain; charset=UTF-8<br><br>Don't use trunk, use the 3.0.1 tag, or at least the 3.0 branch.<br><br>-x.<br><br>On 30 July 2010 07:18, Peter Holme &lt;<a href="mailto:peter@holme.se">peter@holme.se</a>&gt; wrote:<br>&gt; nope. that didn't work...<br>&gt; These are the settings I use:<br>&gt; - Where to take translations from: <a href="http://translate.wordpress.org" target="_blank">translate.wordpress.org</a><br>&gt; - Locale branch for dist-files: tags/3.0.1<br>&gt; - Project: Development (trunk)<br>&gt; - WordPress revision: HEAD (15480)<br>&gt; - WordPress version: 3.0.1<br>&gt; When these settings are used,?version.php says 3.1-alpha...<br>&gt; Peter<br>&gt;<br>&gt; On Fri, Jul 30, 2010 at 07:12, Peter Holme &lt;<a href="mailto:peter@holme.se">peter@holme.se</a>&gt; wrote:<br>&gt;&gt;<br>&gt;&gt; Sorry.. read through the revision statements - it seems we should use<br>&gt;&gt; 15480. I'll go with that.<br>&gt;&gt; Peter<br>&gt;&gt;<br>&gt;&gt; On Fri, Jul 30, 2010 at 07:09, Peter Holme &lt;<a href="mailto:peter@holme.se">peter@holme.se</a>&gt; wrote:<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; So what revision are we supposed to use? 15477 or 15480? (I suspect<br>&gt;&gt;&gt; I might have used the wrong one for 3.0, 'cause the &quot;upgrade available&quot;<br>&gt;&gt;&gt; message has appeared sporadically since I upgraded) Peter (nb_NO)<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; On Fri, Jul 30, 2010 at 02:55, Milan Dini? &lt;<a href="mailto:liste@srpski.biz">liste@srpski.biz</a>&gt; wrote:<br>&gt;&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt;&gt; Dear Andrew,<br>&gt;&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt;&gt; Please don't think of this e-mail as of some attempt to blame you,<br>&gt;&gt;&gt;&gt;&gt; I'm only agreeing on the point quoted. Sorry if you got me wrong!<br>&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt; Just to clarify that I too wasn't meaning just on Andrew but to all<br>&gt;&gt;&gt;&gt; developers.<br>&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt; 2010/7/30 Wac?aw Jacek &lt;<a href="mailto:mail@waclawjacek.com">mail@waclawjacek.com</a>&gt;<br>&gt;&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt;&gt; On Thu, Jul 29, 2010 at 08:02:06PM -0400, Andrew Nacin wrote:<br>&gt;&gt;&gt;&gt;&gt; &gt; 2010/7/29 Wac?aw Jacek &lt;<a href="mailto:mail@waclawjacek.com">mail@waclawjacek.com</a>&gt;<br>&gt;&gt;&gt;&gt;&gt; &gt;<br>&gt;&gt;&gt;&gt;&gt; &gt; &gt; On Fri, Jul 30, 2010 at 02:36:18AM +0300, Rasheed Bydousi wrote:<br>&gt;&gt;&gt;&gt;&gt; &gt; &gt; &gt; I think translators should know about new releases much earlier.<br>&gt;&gt;&gt;&gt;&gt; &gt; &gt; That's true, in order for us to translate stuff on time and<br>&gt;&gt;&gt;&gt;&gt; &gt; &gt; take proper care of the regional communities by providing<br>&gt;&gt;&gt;&gt;&gt; &gt; &gt; on-time translations we need to know of expected upgrades<br>&gt;&gt;&gt;&gt;&gt; &gt; &gt; earlier than they are released.<br>&gt;&gt;&gt;&gt;&gt; &gt; &gt; Obviously this<br>&gt;&gt;&gt;&gt;&gt; &gt; &gt; shouldn't apply if and update is a crucial bug fix. :)<br>&gt;&gt;&gt;&gt;&gt; &gt;<br>&gt;&gt;&gt;&gt;&gt; &gt;<br>&gt;&gt;&gt;&gt;&gt; &gt; Demetris emailed this list 19 days ago, and we haven't changed a<br>&gt;&gt;&gt;&gt;&gt; &gt; string since. I also alerted the list to string changes as they<br>&gt;&gt;&gt;&gt;&gt; &gt; occurred.<br>&gt;&gt;&gt;&gt;&gt; &gt; Your<br>&gt;&gt;&gt;&gt;&gt; &gt; translations should be complete; you only need to push a button now.<br>&gt;&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt;&gt; Dear Andrew,<br>&gt;&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt;&gt; Please don't think of this e-mail as of some attempt to blame you,<br>&gt;&gt;&gt;&gt;&gt; I'm only agreeing on the point quoted. Sorry if you got me wrong!<br>&gt;&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt;&gt; Cheers!<br>&gt;&gt;&gt;&gt;&gt; WJ<br>&gt;&gt;&gt;&gt;&gt; _______________________________________________<br>&gt;&gt;&gt;&gt;&gt; wp-polyglots mailing list<br>&gt;&gt;&gt;&gt;&gt; <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>&gt;&gt;&gt;&gt;&gt; <a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt; _______________________________________________<br>&gt;&gt;&gt;&gt; wp-polyglots mailing list<br>&gt;&gt;&gt;&gt; <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>&gt;&gt;&gt;&gt; <a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>&gt;&gt;&gt;&gt;<br>&gt;&gt;&gt;<br>&gt;&gt;&gt;<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; --<br>&gt;&gt;&gt; +47 920 42 782<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; --<br>&gt;&gt; +47 920 42 782<br>&gt;<br>&gt;<br>&gt;<br>&gt; --<br>&gt; +47 920 42 782<br>&gt;<br>&gt; _______________________________________________<br>&gt; wp-polyglots mailing list<br>&gt; <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>&gt; <a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>&gt;<br>&gt;<br><br><br>------------------------------<br><br>Message: 4<br>Date: Fri, 30 Jul 2010 11:46:28 +0200<br>From: Mattias Tengblad &lt;<a href="mailto:mst@eyesx.com">mst@eyesx.com</a>&gt;<br>Subject: Re: [wp-polyglots] WordPress 3.0.1 expected around mid July<br>To: <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>Message-ID: &lt;<a href="mailto:4C529F74.6030509@eyesx.com">4C529F74.6030509@eyesx.com</a>&gt;<br>Content-Type: text/plain; charset=&quot;utf-8&quot;; Format=&quot;flowed&quot;<br><br>&nbsp;Well written Milan, I totally agree with you. This has been discussed a<br>couple of times over the years but nothing has really changed.<br><br>*Mvh*<br>/Mattias Tengblad/<br>Webbplats: <a href="http://eyesx.com" target="_blank">eyesx.com</a> &lt;<a href="http://eyesx.com" target="_blank">http://eyesx.com</a>&gt;<br>E-post/Live Messenger: <a href="mailto:mst@eyesx.com">mst@eyesx.com</a> &lt;mailto:<a href="mailto:mst@eyesx.com">mst@eyesx.com</a>&gt;<br><br><br>Milan Dini? skrev 2010-07-30 02:26:<br>&gt;<br>&gt; &nbsp; &nbsp; You should subscribe to the RSS feed at<br>&gt; &nbsp; &nbsp; <a href="http://wordpress.org/news/category/releases/" target="_blank">http://wordpress.org/news/category/releases/</a>.<br>&gt;<br>&gt;<br>&gt; You are changing mind :)<br>&gt; <a href="http://lists.automattic.com/pipermail/wp-polyglots/2010-June/004672.html" target="_blank">http://lists.automattic.com/pipermail/wp-polyglots/2010-June/004672.html</a> :<br>&gt;<br>&gt; &nbsp; &nbsp; I don't see a reason to develop a notification service other<br>&gt; &nbsp; &nbsp; than us manually sending an email as we are prepping everything for<br>release.<br>&gt;<br>&gt;<br>&gt; Problem with relying on RSS from <a href="http://wp.org/news" target="_blank">wp.org/news</a> &lt;<a href="http://wp.org/news" target="_blank">http://wp.org/news</a>&gt; is<br>&gt; that it is very slow process. We need faster notification via email.<br>&gt;<br>&gt; &nbsp; &nbsp; Demetris emailed this list 19 days ago, and we haven't changed a<br>&gt; &nbsp; &nbsp; string since. I also alerted the list to string changes as they<br>&gt; &nbsp; &nbsp; occurred. Your translations should be complete; you only need to<br>&gt; &nbsp; &nbsp; push a button now.<br>&gt;<br>&gt; You first need to know how this process works:<br>&gt; - we need to check if there is any new string since last update and if<br>&gt; files for direct translation were changed<br>&gt; - we commit translations to SVN and need to wait around 10 minutes<br>&gt; before we can build a locale package at locale site<br>&gt; - we need to wait xx minutes before locale version will appear on<br>&gt; upgrade screen even if it was hours before last check to api was made<br>&gt; (I just tested this again today: I didn't have notification about<br>&gt; update until I went to upgrade screen where I only got option to<br>&gt; update to en_US even though locale package was already available on<br>&gt; <a href="http://locale.wp.org" target="_blank">locale.wp.org</a> &lt;<a href="http://locale.wp.org" target="_blank">http://locale.wp.org</a>&gt;)<br>&gt; - if we updated to en_US while there wasn't locale package, we will<br>&gt; again receive notification about new version, this time with option to<br>&gt; upgrade to locale package<br>&gt;<br>&gt; So even if we have ready translations and see news about release the<br>&gt; same moment as it is posted, we still need xx minutes before new<br>&gt; locale version will appear at upgrade screen. And what if we don't<br>&gt; release a locale package for several hours or day(s) because we were<br>&gt; offline, unaware that new version will be released? Users will update<br>&gt; to en_US, some strings will be untranslated (depending if it is<br>&gt; version from new branch and how many changes there are in new<br>&gt; version), and when new locale version is release they'll again get<br>&gt; notification about update and they'll ask &quot;WTF!? I already updated to<br>&gt; this version!&quot;<br>&gt;<br>&gt; We need a different process related to releases. Translators should be<br>&gt; warned when new version will be released, not just because they need<br>&gt; to update translations, but because they need to be ready to &quot;push a<br>&gt; button&quot; (if it was that simple). I could understand if there was need<br>&gt; for unplanned release because of discovery of huge security issue that<br>&gt; needs to be fixed as soon as possible, but those releases are not that<br>&gt; often and you don't have a reason to not inform us in advance.<br>&gt;<br>&gt; You must be aware that this process is not friendly for translators<br>&gt; and for users of locale versions. You must be aware that there are<br>&gt; users who use locale version (check for stats for exact percent) and<br>&gt; you can't ignore that fact in release process. If you really want to<br>&gt; fully support i18n and l10n in automatic upgrades and notification<br>&gt; about upgrades, you must stop with current practice and make strict<br>&gt; rules with translators about release process which should be followed<br>&gt; by everyone.<br>&gt;<br>&gt; 2010/7/30 Andrew Nacin &lt;<a href="mailto:wp@andrewnacin.com">wp@andrewnacin.com</a><br>&gt; &lt;mailto:<a href="mailto:wp@andrewnacin.com">wp@andrewnacin.com</a>&gt;&gt;<br>&gt;<br>&gt; &nbsp; &nbsp; 3.0.1 has been released.<br>&gt;<br>&gt; &nbsp; &nbsp; I had an email drafted to polyglots, but we made a last minute<br>&gt; &nbsp; &nbsp; change and I got sidetracked.<br>&gt;<br>&gt; &nbsp; &nbsp; It hasn't been several hours; WordPress 3.0.1 proper was released<br>&gt; &nbsp; &nbsp; 72 minutes ago, but I digress. You should subscribe to the RSS<br>&gt; &nbsp; &nbsp; feed at <a href="http://wordpress.org/news/category/releases/" target="_blank">http://wordpress.org/news/category/releases/</a>.<br>&gt;<br>&gt; &nbsp; &nbsp; Cheers!<br>&gt;<br>&gt; &nbsp; &nbsp; Nacin<br>&gt;<br>&gt;<br>&gt; &nbsp; &nbsp; On Thu, Jul 29, 2010 at 7:04 PM, Milan Dini? &lt;<a href="mailto:liste@srpski.biz">liste@srpski.biz</a><br>&gt; &nbsp; &nbsp; &lt;mailto:<a href="mailto:liste@srpski.biz">liste@srpski.biz</a>&gt;&gt; wrote:<br>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; Again no notification in advance (I mean at least several<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; hours) and no notification after release is made (so we still<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; need to use external notification services).<br>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; I would expect that Nacin would inform us, he was active on<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; this list last months.<br>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; 2010/7/10 Demetris &lt;<a href="mailto:kikizas@gmail.com">kikizas@gmail.com</a><br>&gt; &lt;mailto:<a href="mailto:kikizas@gmail.com">kikizas@gmail.com</a>&gt;&gt;<br>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Hello, polyglots!<br>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; This is a note that WordPress 3.0.1 is expected to be<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; released around mid July.<br>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Like all maintenance releases, it will be a very good<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; opportunity for<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; translation teams to push<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; improvements/additions/corrections/etc. in<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; their localizations.<br>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (I know that I try to take advantage of maintenance<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; releases for that<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; purpose?fixing strings, localizing more strings, etc.?,<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; and I imagine<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; other WordPress translators do the same thing.)<br>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Note also that 3.0.1 has a few changes in strings (mainly<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; to correct<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; typos, if I remember correctly). &nbsp;So, remember to update<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; your PO files<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; too!<br>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Cheers,<br>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Demetris<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href="http://op111.net/76" target="_blank">http://op111.net/76</a> ? See what is new in WordPress 3.0!<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; _______________________________________________<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; wp-polyglots mailing list<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;mailto:<a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>&gt;<br>&gt;<br>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; _______________________________________________<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; wp-polyglots mailing list<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &lt;mailto:<a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; <a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>&gt;<br>&gt;<br>&gt;<br>&gt; &nbsp; &nbsp; _______________________________________________<br>&gt; &nbsp; &nbsp; wp-polyglots mailing list<br>&gt; &nbsp; &nbsp; <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>&gt; &nbsp; &nbsp; &lt;mailto:<a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a>&gt;<br>&gt; &nbsp; &nbsp; <a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>&gt;<br>&gt;<br>&gt;<br>&gt; _______________________________________________<br>&gt; wp-polyglots mailing list<br>&gt; <a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>&gt; <a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL:<br>&lt;<a href="http://lists.automattic.com/pipermail/wp-polyglots/attachments/20100730/78a%0A65705/attachment.htm" target="_blank">http://lists.automattic.com/pipermail/wp-polyglots/attachments/20100730/78a<br>65705/attachment.htm</a>&gt;<br><br>------------------------------<br><br>_______________________________________________<br>wp-polyglots mailing list<br><a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br><a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br><br><br>End of wp-polyglots Digest, Vol 66, Issue 43<br>********************************************<br><br>_______________________________________________<br>wp-polyglots mailing list<br><a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br><a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><o:p></o:p></p></div><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>