Re: [opensuse-lxde] LXDE translations
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 26/05/2010 07:40, Karl Eichwalder ha scritto:
Guido Berhoerster
writes: It also doesn't seem to allow source code comments for translators (like gettext), does it?
That's a rather serious issue. I'd like to stick with .pot/.po in the openSUSE translation SVN. There are already other projects that convert their private format to .pot and take the provided .po files.
that's the reason why i attached on my first mail, lxcc and lxdm-conf pot files.
An exception are .html files--but that does not work that great. If really needed we could arrange something similar for .moo.
In the long run we may switch to xlif, though.
of course, there is no problem, i am just worried to provide translation for 11.3. .moo are simple text files like: string_original=string_translated you can just publish and sync the pot files i provided you. as soon as we have translations, we can easly move back from poes to .moo with 2 simple shell commands... the only thing we need, is maybe a simple script to do it, for each language... Andrea - -- - ------------------------------------------ Andrea Florio QSI International School of Brindisi Sys Admin CISCO CCNA Certified openSUSE-Education Administrator openSUSE Official Member (anubisg1) Email: andrea@opensuse.org Packman Packaging Team Email: andrea@links2linux.de Web: http://packman.links2linux.org/ Cell: +39-328-7365667 - ------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkv824sACgkQyCZT87TFPuhdcgCeOyQbHZYuD8OP0KuCZk0qS5LT KGgAn3qGQEendj4DyZn8eScIGRZwJuVS =jeyN -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-lxde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-lxde+help@opensuse.org
* Andrea Florio
That's a rather serious issue. I'd like to stick with .pot/.po in the openSUSE translation SVN. There are already other projects that convert their private format to .pot and take the provided .po files.
that's the reason why i attached on my first mail, lxcc and lxdm-conf pot files.
Please test the attached scripts.
of course, there is no problem, i am just worried to provide translation for 11.3. .moo are simple text files like:
string_original=string_translated
you can just publish and sync the pot files i provided you. as soon as we have translations, we can easly move back from poes to .moo with 2 simple shell commands... the only thing we need, is maybe a simple script to do it, for each language...
Where is this format specified? I am particularly interested how "=" inside translations are escaped, what the expected filen encoding is and wheter there are comments. -- Guido Berhoerster
* Guido Berhoerster
Where is this format specified? I am particularly interested how "=" inside translations are escaped, what the expected filen encoding is and wheter there are comments.
To answer myself, I had a look at the lxdm-conf source and it looks like homebrew. It has no escaping mechanism and just assumes there will never be a string to translate which contains a "=". The moo files are in UTF-8 format, blank lines will be ignored and there is no way to specify comments for translators as with gettext. lxdm-conf also doesn't folllow the convention of giving LC_MESSAGES precedence over LANG. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-lxde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-lxde+help@opensuse.org
participants (2)
-
Andrea Florio
-
Guido Berhoerster