I have same ability to translate com-central on mozilla repositories,
but I never use it. It's too unstable and a lot of changes.
If someone thinks it will be useful for him, you can implement it, but I
know I won't use it.
3.12.2014. u 18:27, Sophie je napisao/la:
Another follow-up on the discussion we had, who would be interested to
have a translation workflow based on master?
To understand, that would mean that a new project named 'master' will be
created on Pootle. Once a month, Cloph will extract the strings from
Pootle to the source code. The main translation work will happen on this
project with a timeframe of about 6 month to do the work. When a new
version is branched off, the master translations would be used to create
a release branch project.
Note that if you fix something in master project, it won't automatically
end up in the existing release branch-translations, you will have to fix
it these projects too. But the rule of no addition of strings will still
apply for developers, so there will be few changes and minor corrections
What is your opinion on that?
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy