On Thu, Dec 30, 2010 at 19:53, Freek de Kruijf <f.de.kruijf@gmail.com> wrote:
I download/update my language .po files using svn (with a very simple script)
and use Lokalize with a Translation Memory database, which is now 125M, for
translation and a glossary for words of .5 MB. Uploading is using svn commit.
Compared to using Pootle this is far more easy. Using svn or git for download
and upload is using less bandwith, because only the differences are
transported.
Managing .po files with git is quite fast. As I am a GNOME committer
and manage translations in such way, I totally agree this would be an
ideal solution to get rid of the horrible situation now.
I've tried xliff2po to convert documentation file to po, and it
produces a po file with no header, but many duplicate msgids. We are
lacking tools like msgmerge, msgfmt for xliff/sdf translation files,
which significantly increases the hardness of managing them.
--
Regards,
Aron Xu
--
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
Re: [Libreoffice] [libreoffice-l10n] Re: Update of the localization files · Jan Holesovsky
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.