Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


Hi, Jan,

2016-12-16 17:38 GMT+01:00 Jan Holesovsky <kendy@collabora.com>:

It does not seem transparent for the few languages that do not use
pootle (sl and sr) please do not forget those.

Thanks for the reminder.  I hope Cloph can do the upgrade for them some
way that fits them too, though?


I do not mind this happening if it does not affect the l10n process.

With that in mind the date/point at which it will be run must be set.

Probably this will happen after 5.3.x branch? It would make sense to do it
after the 5.3.0 release, when most l10n teams finish with their work and
have finished translating help, and still not started translating the 5.x
master. Or maybe after 5.3.1 release?

The sl and sr team would probably send their po files zipped (or they would
be taken from the git) and the script should be run through them and they
would be entered in the git and returned to respective l10n teams.

This conversion process (including the majority of l10n from Pootle) should
happen in a short span (like two working days, maybe more if required by
the scripts to go through all the languages and to check all converted
files for consistency by some other scripts).

Probably one (or a few) languages should be taken first to test this
procedure/the scripts and to have better estimates of time and resources
needed.

Lp, m.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: 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.