A guide for translators
Robert Antoni Buj i Gelonch
robert.buj at gmail.com
Fri Jan 30 18:44:42 UTC 2015
There is also a difference between document and software translations,
software translations are always under upstream-src/po folder whereas that
in document translations use the main upstream-src folder, for that reason
we have to use two different command to get the translations from zanata:
documentation: zanata-cli -B pull --src-dir=./ --trans-dir=./ -l <lang-code>
software: zanata-cli -B pull --src-dir=./po --trans-dir=./po -l <lang-code>
2015-01-30 19:17 GMT+01:00 Robert Antoni Buj i Gelonch <robert.buj at gmail.com
> Great work!
> In Testing section, you can add how to test documentation (getting sources
> from upstream project, getting zanata.ini, getting translated messages,
> building the documentation) as well as the required publican packages for
> doing so. You can also explain how to build a local repo to test software
> translations, or simple doing "sudo cp <lang-code>.mo
> A local repo is very usefull when you are trying to test Anaconda by
> making an installation media with pungi. 
>  http://fedoraproject.org/wiki/Anaconda/Building
> 2015-01-30 16:32 GMT+01:00 tiansworld <tiansworld at fedoraproject.org>:
>> Dear translators,
>> The new L10n guide is now 80% completed. Julie and I are still working on
>> You are welcome to view it now and give your suggestions.
>> Shall we add the link to here when it's done?
>>  https://fedoraproject.org/wiki/L10N/Translate_on_Zanata
>> Fedora Project Contributor
>> trans mailing list
>> trans at lists.fedoraproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the trans