On Thu, Dec 30, 2010 at 19:53, Freek de Kruijf <f.de.kru...@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+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/l10n/ *** All posts to this list are publicly archived for eternity ***
