-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi karl, hi lists, the lxde team finally completed a "workflow" to translate the only two applications without an upstream translation. i'm talking about lxcc and lxdm-conf attached the pot files generated from lxdmconf.moo and lxcc.moo actually this is the workflow we follow to move from .moo files to .pot and back from .po to .moo (generate .ini file) moo2ini lxdmconf_template.moo > lxdmconf.ini (generate .pot file we can easly translate) ini2po lxdmconf.ini lxdmconf.pot those two steps has just been done. once you got the translations you do: (come back to .ini, not translated) po2ini -t lxdmconf.ini lxdmconf.po lxdmconf.ini (merge translations (into ini) with template moo) ini2moo lxdmconf.ini lxdmconf_template.moo > lxdmconf.moo the point is... can we do it? there is any way (a bash script) able to make our life easier? infos about: tools ini2po and po2ini http://translate.sourceforge.net/wiki/toolkit/ini2po those are provided by package python-translate-toolkit that i found only into an home repo home:thomas-schraitle (that miss anyway, at least, python-iniparse dependency that you need to manually install) Best regards 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/ iEYEARECAAYFAkv73bYACgkQyCZT87TFPuiBpACggeuN+vSQ2Mc0uDevM0WDawiJ RQ4AmQFu3ROKo8ZDVvHK/HPuNNnlEV7H =RGIk -----END PGP SIGNATURE-----
2010/5/25 Andrea Florio
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi karl, hi lists,
the lxde team finally completed a "workflow" to translate the only two applications without an upstream translation.
i'm talking about lxcc and lxdm-conf
attached the pot files generated from lxdmconf.moo and lxcc.moo
actually this is the workflow we follow to move from .moo files to .pot
and back from .po to .moo
(generate .ini file) moo2ini lxdmconf_template.moo > lxdmconf.ini
(generate .pot file we can easly translate) ini2po lxdmconf.ini lxdmconf.pot
those two steps has just been done.
once you got the translations you do:
(come back to .ini, not translated) po2ini -t lxdmconf.ini lxdmconf.po lxdmconf.ini
(merge translations (into ini) with template moo) ini2moo lxdmconf.ini lxdmconf_template.moo > lxdmconf.moo
the point is... can we do it? there is any way (a bash script) able to make our life easier?
infos about: tools ini2po and po2ini http://translate.sourceforge.net/wiki/toolkit/ini2po
those are provided by package python-translate-toolkit that i found only into an home repo home:thomas-schraitle (that miss anyway, at least, python-iniparse dependency that you need to manually install)
Best regards 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/
iEYEARECAAYFAkv73bYACgkQyCZT87TFPuiBpACggeuN+vSQ2Mc0uDevM0WDawiJ RQ4AmQFu3ROKo8ZDVvHK/HPuNNnlEV7H =RGIk -----END PGP SIGNATURE-----
Hi folks, I have the package python-translate-toolkit in my home repo with all the dependecies and up-to-date (version 1.7.0) http://download.opensuse.org/repositories/home:/elchevive/ Regards, Luiz -- To unsubscribe, e-mail: opensuse-lxde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-lxde+help@opensuse.org
* Andrea Florio
the lxde team finally completed a "workflow" to translate the only two applications without an upstream translation.
i'm talking about lxcc and lxdm-conf
Both are very simplistic python scripts, before going through all the hoops you've mentioned, is there any particluar reason why upstream can't use gettext like everybody else? I mean hacking that in should take 10 minutes and we wouldn't have to worry about all of this in the first place.
attached the pot files generated from lxdmconf.moo and lxcc.moo
actually this is the workflow we follow to move from .moo files to .pot
and back from .po to .moo
(generate .ini file) moo2ini lxdmconf_template.moo > lxdmconf.ini
(generate .pot file we can easly translate) ini2po lxdmconf.ini lxdmconf.pot
those two steps has just been done.
once you got the translations you do:
(come back to .ini, not translated) po2ini -t lxdmconf.ini lxdmconf.po lxdmconf.ini
(merge translations (into ini) with template moo) ini2moo lxdmconf.ini lxdmconf_template.moo > lxdmconf.moo
the point is... can we do it? there is any way (a bash script) able to make our life easier?
If po2ini/ini2po support reading from or writing to stdout you can just pipe them together or put that into my scripts. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-lxde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-lxde+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 25/05/2010 16:56, Guido Berhoerster ha scritto:
Both are very simplistic python scripts, before going through all the hoops you've mentioned, is there any particluar reason why upstream can't use gettext like everybody else? I mean hacking that in should take 10 minutes and we wouldn't have to worry about all of this in the first place.
i have no python knowledge (C only actually), feel free to patch it. the only reason upstream developers gave to me is: .moo doesn't need to be compiled as .po, we won't use poes. 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/ iEYEARECAAYFAkv77TsACgkQyCZT87TFPuivjQCgvSri2TWqqPhvGbXTteqnamI5 kK0AoLb1r0C3jaPcA4TAODTlmqxqWI2F =HMIQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-lxde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-lxde+help@opensuse.org
* Andrea Florio
i have no python knowledge (C only actually), feel free to patch it.
the only reason upstream developers gave to me is:
.moo doesn't need to be compiled as .po, we won't use poes.
In that case changing the awk script to directly take po input and output would probably be the most convenient solution. Is that .moo format documented somewhere? It also doesn't seem to allow source code comments for translators (like gettext), does it? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-lxde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-lxde+help@opensuse.org
participants (3)
-
Andrea Florio -
Guido Berhoerster -
Luiz Fernando Ranghetti