[Bf-translations-dev] Dutch translation initiative

[Bastien Montagne]

Please read the link I sent you the other day when answering to your 
first mail, 
http://wiki.blender.org/index.php/Dev:Doc/Process/Translate_Blender, 
everything is explained there. :)

Le 12/08/2015 22:57, Jeroen Bakker a écrit :
> Hi Bastien,
>
> The process is a bit unclear to me. Seems to be more automated than I
> thought. What SVN are you referring to?
>
> Regards,
> Jeroen
> On 08/12/2015 10:27 PM, Bastien Montagne wrote:
>> Hi Jeroen,
>>
>> Some quick notes:
>>
>> * blender.pot file is in both /trunk/po and /branches dirs of the svn
>> repository;
>> * svn repository is updated weekly (around monday-tuesday usually) by
>> myself, so all files are kept up-to-date here ;)
>>
>>    From what you’re saying, I’m not sure you got this right, so just
>> insisting on the fact that you should always & only work on the svn
>> /branches/nl part of the repository, other areas (/trunk of svn, and our
>> i18n git repo) are handled (mostly automatically) by myself.
>>
>> Cheers and good luck in the translation project!
>> Bastien
>>
>> Le 12/08/2015 22:15, Jeroen Bakker a écrit :
>>> Hi All,
>>>
>>> We are currently looking into translating blender to dutch using the
>>> dutch community.
>>> The current translation is around 100 translated text and there are
>>> around 22000 different text to translate.
>>>
>>> I want to discuss a bit about a good process to translate this using a
>>> community effort.
>>> As tool Bastien advised using POEdit. It seems to be capable of doing
>>> the job.
>>>
>>> Step 1. Preparation
>>> Update the current nl.po file with the all untranslated text.
>>> I was not able to find any POT file, so I used POEdit to add all text
>>> from the fr.po to the nl.po. The French language has the most translated
>>> text. Doing this I assume that it is up to date, but not sure if this is
>>> the case
>>>
>>> Split the nl.po into smaller parts. Let assume a person can translate
>>> 250 lines of text in an hour. We split the nl.po file into 100 files
>>> containing around 250 lines of text to translate. And place all these
>>> files in a folder named "untranslated"
>>>
>>> Step 2. Giving work to a team member
>>> When a team member ask to work on the translation we send some files to
>>> the member. The send files will be removed from the "untranslated"
>>> folder and punt in the "inprocess/{member_name}". This way we ensure
>>> that we know who works on what and if it does not take too much time
>>>
>>> Step 3. Receiving translated work from a team member.
>>> When receiving the work we move the file to "done/{member_name}" we
>>> remove the file from the "inprocess" folder.
>>>
>>> Step 4. send for review
>>> Occasionally we will merge all po files inside the "done"  folder to the
>>> nl.po. This file would contain only translated/not fuzy translations.
>>> This po file could be reviewed and technically tested in a dev branch.
>>> and committed to the bf-translation git for the next release.
>>>
>>> Is this a good way to do community based translation?
>>> Does anyone have some advice, experience?
>>> Is there any up to date POT file, or what are the instructions to
>>> generate one from trunk?
>>> What order in the po files would be good in order to get more auto matches.
>>> How did you do it? :-)
>>>
>>> Thanks in advance,
>>> Jeroen
>>> _______________________________________________
>>> Remember to *NEVER* commit to our svn's /trunk, but *ALWAYS* to relevant language po file under /branches!
>>>
>>> Found a missing msgid? Edit this doc: http://goo.gl/XcWcr
>>>
>>> Have some disambiguation issue (i.e. same english word that should be translated in more than one way, depending on the context)? Edit this doc: http://goo.gl/VzppJ
>>> _______________________________________________
>>> Bf-translations-dev mailing list
>>> Bf-translations-dev at blender.org
>>> http://lists.blender.org/mailman/listinfo/bf-translations-dev
>>>
>> _______________________________________________
>> Remember to *NEVER* commit to our svn's /trunk, but *ALWAYS* to relevant language po file under /branches!
>>
>> Found a missing msgid? Edit this doc: http://goo.gl/XcWcr
>>
>> Have some disambiguation issue (i.e. same english word that should be translated in more than one way, depending on the context)? Edit this doc: http://goo.gl/VzppJ
>> _______________________________________________
>> Bf-translations-dev mailing list
>> Bf-translations-dev at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-translations-dev
> _______________________________________________
> Remember to *NEVER* commit to our svn's /trunk, but *ALWAYS* to relevant language po file under /branches!
>
> Found a missing msgid? Edit this doc: http://goo.gl/XcWcr
>
> Have some disambiguation issue (i.e. same english word that should be translated in more than one way, depending on the context)? Edit this doc: http://goo.gl/VzppJ
> _______________________________________________
> Bf-translations-dev mailing list
> Bf-translations-dev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-translations-dev