Andras Timar píše v St 09. 03. 2011 v 00:01 +0100:
Hi,
I created a module called 'translations'. It is at
http://cgit.freedesktop.org/~timar/translations/ now. If you clone
this and link translations directory to master directory structure,
then it is buildable. It converts Hungarian PO files to SDF particles
which are needed by the build. translate-toolkit is a build
requirement.
Andras, you rock! Thanks a lot for all the work and committing the two
test languages into the new main repo
http://cgit.freedesktop.org/libreoffice/translations/
I wish, if I could finish this work by the feature freeze of 3.4 and
we can use this new l10n infrastructure. Please help.
I am going to look at it. The plan is to get rid of the "l10n" repo and
use the new "translations" repo exclusively. My steps will be:
+ download "translations" instead of "l10n" repo
+ allow to build internal translate toolkit (libs-extern repo)
+ set the new L10N_MODULE in solenv/inc/settings.mk
+ modify build.lst in "all" module to depend on
TRANSLATIONS:translations instead of L10N:l10n
+ fix potential build probles
I would like to finish this before we tag for LO-3.4-alpha1.
The only question is how many localizations we would want to support in
alpha1. IMHO, it would be nice to add "de, fr, it" because we have big
communities in these countries. Did I miss any important one? I would
add the others later after we know that it works (for next alpha/beta).
Best Regards,
Petr
Context
- Re: [Libreoffice] l10n based on PO files (continued)
Re: [Libreoffice] l10n based on PO files · Petr Mladek
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.