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


Hi Andras,

I'm not sure if you were informed, but Pootle will be moved to another server soon. Should we perhaps wait for that move to happen before introducing new modules?

Rimas

2011.03.25 10:55, Andras Timar rašė:
Hi Rimas,

LibreOffice 3.4 is approaching, we need to deal with localization. The
big merges from Oracle's source were done a few days ago, so I don't
expect big changes in translatable strings. We should update the files
in Pootle.

I created LibreOffice 3.4 modules in Pootle but it is extremely slow to
work with the web interface. Maybe it is quicker from shell. Can you
help me?

For the time being we should keep LibreOffice 3.3 modules in Pootle,
because it is possible that LibreOffice 3.3.3 will be released later, so
we can update the translations there.

Files from "LibreOffice 3.3.x – Merged Help" and from "LibreOffice 3.3.x
– Merged UI" should be copied to "LibreOffice 3.4.x – Help" and
"LibreOffice 3.4.x – UI" respectively, then all languages should be
updated from templates.

For the rest of the languages what would be the best workflow? I
extracted the po files from LibreOffice 3.3.2 source, I can send you
those files.

Thanks,
Andras


--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***

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.