Apologies for not replying to the list, José. I just hit reply...

I think I'm starting to understand it now. We're going to use the GlotPress
translation, so by the looks of it I then only have to a these:
tags/x.x/dist/wp-config-sample.php (translated) 
tags/x.x/dist/wp-admin/setup-config.php (translated)

and I won't have to create a .mo file, GlotPress will do that for me when I
build the 3.0.1 version



ForSite Media
WordPress Consultancy, Development & Design
0622-164385 | www.forsite.nu |[email protected]


-----Oorspronkelijk bericht-----
Van: José Fontainhas [mailto:[email protected]] 
Verzonden: zaterdag 31 juli 2010 15:36
Aan: [email protected]; [email protected]
Onderwerp: Re: [wp-polyglots] FW: Creating the Dutch translation via
nl.wordpress.org

Obviously forgot tags/x.x/messages/ms-nl_NL.mo and
tags/x.x/messages/ms-nl_NL.po

Sorry

2010/7/31 José Fontainhas <[email protected]>:
> At the very least you need:
>
> tags/x.x/dist/wp-config-sample.php (translated) 
> tags/x.x/dist/wp-admin/setup-config.php (translated) 
> tags/x.x/messages/continents-cities-nl_NL.mo
> tags/x.x/messages/continents-cities-nl_NL.po
> tags/x.x/messages/nl_NL.mo
> tags/x.x/messages/nl_NL.po
> tags/x.x/messages/twentyten/nl_NL.mo
> tags/x.x/messages/twentyten/nl_NL.po
>
> Keep in mind that if you're building from GP, the whole 
> tags/x.x/messages/ isn't used
>
> To generate a .mo, the easiest way I know of, is to open the .po with 
> PoEdit and then save it. A .mo will be automatically generated
>
> Z
>
> PS-Please post to the list
> (http://lists.automattic.com/mailman/listinfo/wp-polyglots), not 
> directly to me. Thanks.
>
>
> 2010/7/31 Remkus de Vries | ForSite Media <[email protected]>:
>> Oh boy..
>>
>> So let me get this straight. I need to mimic all the folders in the 
>> entire tag and branch like for example the 2.8.5 tag. Additionally I 
>> need to add the corresponding nl_NL.po and nl_NL.mo files as well in
those folders.
>> Then, I need to go into the backend of nl.wordpress.org and select 
>> the proper translation from glotpress, the proper tag (3.0.1) and 
>> then build thus build the .zip and tar.gz which then will 
>> automatically be available on the nl.wordpress.org site.
>>
>> If this is correct, then the only I don't know how to do is how to 
>> get a nl_NL.mo file from the GlotPress .po version.
>>
>> Sorry to ask soo many questions, but this is the first time I'm doing 
>> this and I have no-one here from the former Dutch translation crew to 
>> help me out :(
>>
>> Thanks for your patience,
>> Remkus
>>
>>
>>
>> ForSite Media
>> WordPress Consultancy, Development & Design
>> 0622-164385 | www.forsite.nu |[email protected]
>>
>>
>> -----Oorspronkelijk bericht-----
>> Van: José Fontainhas [mailto:[email protected]]
>> Verzonden: zaterdag 31 juli 2010 14:38
>> Aan: [email protected]; [email protected]
>> Onderwerp: Re: [wp-polyglots] FW: Creating the Dutch translation via 
>> nl.wordpress.org
>>
>> Er... you need to put something in those... like /dist and /messages 
>> and the files that belong in them...
>>
>> Z
>>
>>
>> 2010/7/31 Remkus de Vries | ForSite Media <[email protected]>:
>>> José,
>>>
>>>
>>>
>>> Would you please confirm that what I’ve done now to the 
>>> http://svn.automattic.com/wordpress-i18n/nl/ branches and tags is 
>>> sufficient for me to go to nl.wordpress.org admin and start to build 
>>> the dutch version of 3.0.1?
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Remkus
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ForSite Media
>>>
>>> WordPress Consultancy, Development & Design
>>>
>>> 0622-164385 | www.forsite.nu |[email protected]
>>>
>>>
>>>
>>> Van: José Fontainhas [mailto:[email protected]]
>>> Verzonden: zaterdag 31 juli 2010 13:57
>>> Aan: [email protected]
>>> Onderwerp: Re: [wp-polyglots] FW: Creating the Dutch translation via 
>>> nl.wordpress.org
>>>
>>>
>>>
>>> Depends on what you're using to access the nl repo. Generically it 
>>> means creating those folder/structures locally (on the checked-out
>>> copy) and then committing the changes back to the repo.
>>>
>>>
>>>
>>> Z
>>>
>>>
>>>
>>> 2010/7/31 Remkus de Vries | ForSite Media <[email protected]>
>>>
>>> Ah ok, I can do this myself? That's good to hear, but where can I 
>>> find documentation on how to actually do that :) I have never done 
>>> that before ...
>>>
>>> Thanks,
>>> Remkus
>>>
>>> 2010/7/31 José Fontainhas <[email protected]>
>>>
>>>
>>>
>>> Exactly, you're missing branches/3.0, tags/3.0 and tags/3.0.1
>>>
>>>
>>>
>>> You have commit perms on svn, just add them (with the correct 
>>> structure, of
>>> course)
>>>
>>>
>>>
>>> Z
>>>
>>>
>>>
>>> On 31 July 2010 12:29, Remkus de Vries | ForSite Media 
>>> <[email protected]>
>>> wrote:
>>>
>>> My issue probably has something to do with the fact that there is 
>>> not
>>> 3.0 branch in svn.
>>> http://svn.automattic.com/wordpress-i18n/nl/branches/  How do I need 
>>> to
>> get one there? The 3.0 and the 3.0.1 tag?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ForSite Media
>>>
>>> WordPress Consultancy, Development & Design
>>>
>>> 0622-164385 | www.forsite.nu |[email protected]
>>>
>>>
>>>
>>> Van: Remkus de Vries | ForSite Media [mailto:[email protected]]
>>> Verzonden: zaterdag 31 juli 2010 13:09
>>> Aan: '[email protected]'
>>> Onderwerp: Creating the Dutch translation via nl.wordpress.org
>>>
>>>
>>>
>>> Hi,
>>>
>>>
>>>
>>> We finally have a Dutch version for 3.0.x ready, but when I just 
>>> tried to build it I saw I couldn’t choose the 3.0.1 tag or the 3.0 
>>> branch for that matter. I have enclosed a screenshot which shows 
>>> that when I select to get the translation from 
>>> translate.wordpress.org I can then only select trunk for the Locale 
>>> branch for dist files and not the
>>> 3.0.1 tag
>>>
>>>
>>>
>>> You can also see that the WordPress version would be 
>>> 3.0.1-alpha-15443
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Please advise :)
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Remkus
>>>
>>>
>>>
>>> ForSite Media
>>>
>>> WordPress Consultancy, Development & Design
>>>
>>> 0622-164385 | www.forsite.nu |[email protected]
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> wp-polyglots mailing list
>>>
>>> [email protected]
>>>
>>> http://lists.automattic.com/mailman/listinfo/wp-polyglots
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>

_______________________________________________
wp-polyglots mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-polyglots

Reply via email to