[Bf-translations-dev] Setting up translation addon

Mark van Dijk mark at vandijkmaatcomputers.nl
Thu Jun 13 08:35:54 CEST 2013


Well, i guess the answer was allready there in the email. Just commit the
po file. (my svn client does it automaticly i see).

Just one more question. I tried to commit with my project credentials, but
it seems i don't have permission to do that.

Kind regards,
Mark


2013/6/11 Mark van Dijk <mark at vandijkmaatcomputers.nl>

> Hi,
>
> It worked, i also had to set the path to l18n Branches under the tab File.
> Translating is working now.
>
> So, if i want to update the po, i need the source code? or is commiting
> the svn repo enough? If so, should i commit the whole repo? or just the
> branches map?
>
> Thanks for your help by the way.
>
> Mark
>
>
> 2013/6/11 Bastien Montagne <montagne29 at wanadoo.fr>
>
>>  Hi Mark,
>>
>> - You have to checkout the whole svn repository (you need both branches
>> and trunk).
>> - Source path should point to the Blender source directory. However, you
>> do not need this if you only want to use the addon to translate existing po
>> (it is used to extract new messages, update the po's…).
>> - Translation path should point to the root of the translation checkout
>> (the dir containing /branches and /trunk ones).
>>
>> Cheers,
>> Bastien
>>
>>
>> On 11/06/2013 07:08, Mark van Dijk wrote:
>>
>> Hi,
>>
>>  Im trying to set up the translation addon, but no succes so far. What i
>> did so far:
>> - installed svn
>> - installed gettext tools
>> - checked out the translation repository, but i don't know for sure what
>> i should checkout. Just the repo? or just /branches? or only the language
>> map?
>>
>>  after that i ran into some questions:
>> - where should the source code path be pointing to? to my blender
>> installation folder? Or do i need to checkout the blender source and point
>> to that?
>> - where should the translation source path be pointing to? To the
>> language .po? Or the whole checked out folder?
>>
>>  Hope you can help me. Thanks in advance!
>>
>>  Mark
>>
>>
>> _______________________________________________
>> 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 listBf-translations-dev at blender.orghttp://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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-translations-dev/attachments/20130613/e2540246/attachment.htm 


More information about the Bf-translations-dev mailing list