[opensuse-translation] The "packages" sub-branch, do we have to translate it?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! The "packages" sub-branch, do we have to translate it? I ask because in the stats page it doesn't appear. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHMv2LtTMYHG2NR9URAgCIAJ9yOLxD8p+RWZ+OLhPH7yconYbHEQCffsQN Jd4CXi7uayeYDfSjkP2rQlo= =mjE4 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
"Carlos E. R." <robin.listas@telefonica.net> writes:
The "packages" sub-branch, do we have to translate it? I ask because in the stats page it doesn't appear.
Working on the package descriptions is pointless. But you may consider to work on them in the trunk for 11.0. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Karl Eichwalder wrote:
"Carlos E. R." <robin.listas@telefonica.net> writes:
The "packages" sub-branch, do we have to translate it? I ask because in the stats page it doesn't appear.
Working on the package descriptions is pointless. But you may consider to work on them in the trunk for 11.0.
Pointless... unless someone comes up with a tool that directly modifies binary RPM file headers to update %SUMMARY and %DESCRIPTION(lang), because that way, one could update the translations without rebuilding :) Those could be extracted and converted to gettext format, and then re-merged into the binary RPM files. Not sure that's actually feasible though (and would require removing and re-adding signatures, as well as updating the hash of the package headers.. that's probably not the hardest part though). Either no one had the idea of doing that before (which I'd seriously doubt) or it just isn't feasible for technical reason, because I'm yet to see something like that for any RPM or deb based distribution. cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHM6+Cr3NMWliFcXcRAuJfAJ4tjE+I7EQbKVAiurz09S2AWgsuvgCgsaLZ j7QPKdk9VGqaFg4whKbQ+o4= =xOXR -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-11-09 at 01:53 +0100, Pascal Bleser wrote:
Working on the package descriptions is pointless. But you may consider to work on them in the trunk for 11.0.
Pointless... unless someone comes up with a tool that directly modifies binary RPM file headers to update %SUMMARY and %DESCRIPTION(lang), because that way, one could update the translations without rebuilding :) Those could be extracted and converted to gettext format, and then re-merged into the binary RPM files.
You mean that in order to use the translated "packages" files the whole distro with all the rpms would have to be rebuilt? Wow.
Not sure that's actually feasible though (and would require removing and re-adding signatures, as well as updating the hash of the package headers.. that's probably not the hardest part though).
Either no one had the idea of doing that before (which I'd seriously doubt) or it just isn't feasible for technical reason, because I'm yet to see something like that for any RPM or deb based distribution.
I'm not sure I fully understand. Is it that the translation is hardcoded insisde the rpm package, and can't be pulled from outside files, in a similar way to what binary programs do pulling the translated strings at runtime using gettext calls? I thought this packages branch was used in some "magic" way by Yast when using the software management thing, but I really haven't looked much at it. I simply wondered if it needs to be translated, as the "stats" page doesn't show it: just yast and lcn. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHNESWtTMYHG2NR9URAn2IAJ9FiA+Z2rLLHg7RoTR2umu5CzNIRwCfUs2S raJ93S+PmD6/ZN6kCtBx6qo= =oY2b -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
"Carlos E. R." <robin.listas@telefonica.net> writes:
The Friday 2007-11-09 at 01:53 +0100, Pascal Bleser wrote:
Pointless... unless someone comes up with a tool that directly modifies binary RPM file headers to update %SUMMARY and %DESCRIPTION(lang), because that way, one could update the translations without rebuilding :) Those could be extracted and converted to gettext format, and then re-merged into the binary RPM files.
You mean that in order to use the translated "packages" files the whole distro with all the rpms would have to be rebuilt? Wow.
Yeah, this sounds by far too ambitious.
I'm not sure I fully understand. Is it that the translation is hardcoded insisde the rpm package, and can't be pulled from outside files, in a similar way to what binary programs do pulling the translated strings at runtime using gettext calls?
I thought this packages branch was used in some "magic" way by Yast when using the software management thing, but I really haven't looked much at it.
Yes, translations of package descriptions are not part of the RPMs resp. the RPM database.
I simply wondered if it needs to be translated, as the "stats" page doesn't show it: just yast and lcn.
Thus far, translating package descriptions is not required. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Karl Eichwalder wrote:
"Carlos E. R." <robin.listas@telefonica.net> writes:
The Friday 2007-11-09 at 01:53 +0100, Pascal Bleser wrote:
Pointless... unless someone comes up with a tool that directly modifies binary RPM file headers to update %SUMMARY and %DESCRIPTION(lang), because that way, one could update the translations without rebuilding :) Those could be extracted and converted to gettext format, and then re-merged into the binary RPM files.
You mean that in order to use the translated "packages" files the whole distro with all the rpms would have to be rebuilt? Wow.
Yeah, this sounds by far too ambitious.
No no no, what I was talking about was precisely to *prevent* from having to rebuild the packages to update the localized descriptions. And definitely not "the whole distro" (how stupid do you think I am ?).
I'm not sure I fully understand. Is it that the translation is hardcoded insisde the rpm package, and can't be pulled from outside files, in a similar way to what binary programs do pulling the translated strings at runtime using gettext calls?
Exactly. The package %summary and %description are written+maintained in the .spec file used to build the package. When rpmbuild creates the RPM files, they're written into the RPM headers inside each .rpm file. They can be pulled very easily (rpm -qp --qf '%{SUMMARY}\n%{DESCRIPTION}\n' somepackage.rpm) but they cannot be modified in the package unless modifying the .spec file and rebuilding (which, obviously, is not a very good idea).
I thought this packages branch was used in some "magic" way by Yast when using the software management thing, but I really haven't looked much at it.
Yes, translations of package descriptions are not part of the RPMs resp. the RPM database.
Is that packages thing a copy of the descriptions that are used solely by YaST2 (instead of using the RPMs' %description ?) -- seems we're talking about totally different things and I should just have kept from adding my 2 cents.
I simply wondered if it needs to be translated, as the "stats" page doesn't show it: just yast and lcn.
Thus far, translating package descriptions is not required.
But it would be nice. - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHNKtQr3NMWliFcXcRArJZAJ9lMwxNiPGC+tKoJipW/pkFITwlIwCgpLMt WdUpnaTGSJ6ba52AP0zAFpg= =vOk9 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-11-09 at 19:47 +0100, Pascal Bleser wrote: ...
Is that packages thing a copy of the descriptions that are used solely by YaST2 (instead of using the RPMs' %description ?) -- seems we're talking about totally different things and I should just have kept from adding my 2 cents.
I don't know what it is, that's why I ask. I only translate, my knowledge of how they are handled later I do not know. Some things I know more, but in the case of this "packages" branch I know nothing: I only guesstimate, and ask here for more info ;-)
I simply wondered if it needs to be translated, as the "stats" page doesn't show it: just yast and lcn.
Thus far, translating package descriptions is not required.
But it would be nice.
Of course, it helps users to see the descriptions in their own language. It would be very nice. And it has more than 11000 untranslated messages, and I don't suppose they are single line, either. We simply have to decide what is more worthy/useful of our efforts. And a single comma changed in the original text disables the translation. To do things perfect, each time a maintainer is going to re-package any project he would have to declare a string freeze and request all translators to review the files, and wait some days. Consider security updates in a hurry! The alternative would be to package the translations separately, perhaps different packages for each language, and deliver them as they came available, a week or two later. I'm just thinking aloud :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHNPCrtTMYHG2NR9URAv+uAJ0UwiBjuGbJp7oIgHrt5QKD/YhzoQCeInXp XccYvaK5FiW+X1j72h8hhpo= =YEvW -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Hello, I have a problem with the french po file update-desktop-file.fr.po I translated some fuzzy sentences and I have 1341 errors, always the same error : duplicate message definition. the end of the error log : ********** ... 12:17:30: /home/gardet/openSUSE/suse_lcn/fr/po/update-desktop-files.fr.po:31299: duplicate message definition... 12:17:30: /home/gardet/openSUSE/suse_lcn/fr/po/update-desktop-files.fr.po:31296: ...this is the location of the first definition 12:17:30: msgfmt: found 1341 fatal errors ********** is it a known problem ? How can I solve the problem ? Regards, Guillaume. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
guillaume.gardet@free.fr writes:
I have a problem with the french po file update-desktop-file.fr.po
I translated some fuzzy sentences and I have 1341 errors, always the same error : duplicate message definition.
the end of the error log :
********** ...
12:17:30: /home/gardet/openSUSE/suse_lcn/fr/po/update-desktop-files.fr.po:31299: duplicate message definition... 12:17:30: /home/gardet/openSUSE/suse_lcn/fr/po/update-desktop-files.fr.po:31296: ...this is the location of the first definition 12:17:30: msgfmt: found 1341 fatal errors
**********
is it a known problem ? How can I solve the problem ?
update-desktop-files make use of the extended PO file format with 'msgctxt' keywords. Editors like poedit do not understand this keyword and simply ignore or remove it. You probably must revert the file to the previous version and use kbabel or Emacs/po-mode for editing. If you need help with reverting, just keep me posted. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
hello, Selon Karl Eichwalder <ke@suse.de>:
guillaume.gardet@free.fr writes:
I have a problem with the french po file update-desktop-file.fr.po
I translated some fuzzy sentences and I have 1341 errors, always the same error : duplicate message definition.
the end of the error log :
********** ...
12:17:30: /home/gardet/openSUSE/suse_lcn/fr/po/update-desktop-files.fr.po:31299: duplicate message definition... 12:17:30: /home/gardet/openSUSE/suse_lcn/fr/po/update-desktop-files.fr.po:31296: ...this is the location of the first definition 12:17:30: msgfmt: found 1341 fatal errors
**********
is it a known problem ? How can I solve the problem ?
update-desktop-files make use of the extended PO file format with 'msgctxt' keywords. Editors like poedit do not understand this keyword and simply ignore or remove it.
oh yes ! I remember this problem with poEdit now... Thank you ! Guillaume.
You probably must revert the file to the previous version and use kbabel or Emacs/po-mode for editing. If you need help with reverting, just keep me posted.
-- Karl Eichwalder R&D / Documentation
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Quick question regarding the printer.po file. At line 535 the msgid is '!!! YOUR ENCODING !!!' In the comment box there is '#. TRANSLATORS: #. You may add some text to ascii test page if you want. #. Fill in your encoding here! (e.g. iso-8859-2 for czech) #: src/modules/PrinterTest.ycp:45 src/modules/PrinterTest.ycp:331' What are we supposed to do? Just fill in the language specific encoding or write a small text in our native language, text which will be printed out when the printer is tested? Thank you, Stanciu-Lixandru Alec --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Stanciu-Lixandru Alec <stanciulixandru@gmail.com> writes:
Quick question regarding the printer.po file.
At line 535 the msgid is '!!! YOUR ENCODING !!!'
In the comment box there is '#. TRANSLATORS: #. You may add some text to ascii test page if you want. #. Fill in your encoding here! (e.g. iso-8859-2 for czech) #: src/modules/PrinterTest.ycp:45 src/modules/PrinterTest.ycp:331'
What are we supposed to do?
Just fill in the language specific encoding or write a small text in our native language, text which will be printed out when the printer is tested?
Michal, do you still maintain the printer file? Is this ENCODING thingie still in use? -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-11-30 at 09:19 +0100, guillaume.gardet@free.fr wrote:
update-desktop-files make use of the extended PO file format with 'msgctxt' keywords. Editors like poedit do not understand this keyword and simply ignore or remove it.
oh yes ! I remember this problem with poEdit now...
I have just been told that poedit pre-release 1.3.8 may solve this: - - preserve msgctxt entries in catalogs (#1680554) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHVEJztTMYHG2NR9URAkeOAJ9NFDsCc+IV0rYF+t9DbWMYDztftgCdF2bh KzayXPyVTNZwvAOY9alOOf0= =rjkR -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
2007/12/3, Carlos E. R. <robin.listas@telefonica.net>:
The Friday 2007-11-30 at 09:19 +0100, guillaume.gardet@free.fr wrote:
update-desktop-files make use of the extended PO file format with 'msgctxt' keywords. Editors like poedit do not understand this keyword and simply ignore or remove it.
oh yes ! I remember this problem with poEdit now...
I have just been told that poedit pre-release 1.3.8 may solve this:
- - preserve msgctxt entries in catalogs (#1680554)
You can install Poedit 1.3.8pre1 from my home project in Build Service. http://download.opensuse.org/repositories/home:/lmich/openSUSE_10.3/ BTW. Is there a more appropriate place in Build Service for such package? Regards Ladislav. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
"Ladislav Michnovič" <ladislav.michnovic@gmail.com> writes:
2007/12/3, Carlos E. R. <robin.listas@telefonica.net>:
The Friday 2007-11-30 at 09:19 +0100, guillaume.gardet@free.fr wrote:
update-desktop-files make use of the extended PO file format with 'msgctxt' keywords. Editors like poedit do not understand this keyword and simply ignore or remove it.
oh yes ! I remember this problem with poEdit now...
I have just been told that poedit pre-release 1.3.8 may solve this:
- - preserve msgctxt entries in catalogs (#1680554)
You can install Poedit 1.3.8pre1 from my home project in Build Service. http://download.opensuse.org/repositories/home:/lmich/openSUSE_10.3/
BTW. Is there a more appropriate place in Build Service for such package?
In the past, there was a "translation" BS project. Some weeks ago, I agreed to delete it because only a lonley gettext package (for 10.2) was hanging around. It is probably time to create it again :) -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
2007/12/5, Karl Eichwalder <ke@suse.de>:
You can install Poedit 1.3.8pre1 from my home project in Build Service. http://download.opensuse.org/repositories/home:/lmich/openSUSE_10.3/
BTW. Is there a more appropriate place in Build Service for such package?
In the past, there was a "translation" BS project. Some weeks ago, I agreed to delete it because only a lonley gettext package (for 10.2) was hanging around.
It is probably time to create it again :)
Can you create it, or should we please Adrian? Regards Ladislav. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
2007/12/4, Ladislav Michnovič <ladislav.michnovic@gmail.com>:
2007/12/3, Carlos E. R. <robin.listas@telefonica.net>:
The Friday 2007-11-30 at 09:19 +0100, guillaume.gardet@free.fr wrote:
update-desktop-files make use of the extended PO file format with 'msgctxt' keywords. Editors like poedit do not understand this keyword and simply ignore or remove it.
oh yes ! I remember this problem with poEdit now...
I have just been told that poedit pre-release 1.3.8 may solve this:
- - preserve msgctxt entries in catalogs (#1680554)
You can install Poedit 1.3.8pre1 from my home project in Build Service. http://download.opensuse.org/repositories/home:/lmich/openSUSE_10.3/
The problem is that version 1.3.8pre1 is really buggy. I've tried it and it writes changed msgstr also in neighbouring string. Regards Ladislav.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-11-29 at 10:44 +0100, guillaume.gardet@... wrote:
Hello,
I have a problem with the french po file update-desktop-file.fr.po
I translated some fuzzy sentences and I have 1341 errors, always the same error : duplicate message definition.
Ha! :-)
is it a known problem ? How can I solve the problem ?
Yep. Indeed it is known... we ('es' team) have been bitten by it and we wear proudly our scars. :-P You have to revert to an older version of the file, and restart the translation... The messages in that file have this format: #: /opt/kde3/share/applications/kde/klettres.desktop msgctxt "Comment(klettres.desktop)" msgid " a KDE program to learn the alphabet" msgstr "Un programa de KDE para aprender el alfabeto" ... #: /usr/share/applications/kde4/klettres.desktop msgctxt "Comment(klettres.desktop)" msgid "a KDE program to learn the alphabet" msgstr "Un programa de KDE para aprender el alfabeto" and poedit removes all the "msgctxt" things because it doesn't understand them, as Karl said. Without them there are repeated messages (same msgid) which are differentiated by different "msgctxt" texts - as you can see in the sample above. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHT0GatTMYHG2NR9URAiIpAJ97NfJ8HCA1CVxLs8bgOGZ2RgboTACfZFBF 2Ednk9QrfwGQ4icIMoBB8ak= =oxvs -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Hi ! How often are those translations refreshed ? I mean included in repositories. Apparently, there is an automatic update for *.pot files ( log : "automatic update from PDB"). Is it possible to run an automatic script in order to merge the *.$LL.po files with the *.pot files ? Why don't include this sub-branch in the stat page ? Is it possible to add it ? Cheers, Guillaume Karl Eichwalder a écrit :
"Carlos E. R." <robin.listas@telefonica.net> writes:
The "packages" sub-branch, do we have to translate it? I ask because in the stats page it doesn't appear.
Working on the package descriptions is pointless. But you may consider to work on them in the trunk for 11.0.
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Guillaume Gardet <guillaume.gardet@free.fr> writes:
How often are those translations refreshed ? I mean included in repositories.
I think once a week.
Apparently, there is an automatic update for *.pot files ( log : "automatic update from PDB"). Is it possible to run an automatic script in order to merge the *.$LL.po files with the *.pot files ?
Thanks for asking. If I got it right, the merge will now run at 2:45 CE(S)T every monday morning. ATM, the automatic merging is enable only for the following languages: cs de es fr hu pl I can add more languages, if wanted.
Why don't include this sub-branch in the stat page ? Is it possible to add it ?
We probably can add it. It is not included thus far, because packages translations are not mandatory for SUSE Linux products. Of course, the openSUSE community can decide differently. Cheers, Karl -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Karl Eichwalder a écrit :
Guillaume Gardet <guillaume.gardet@free.fr> writes:
How often are those translations refreshed ? I mean included in repositories.
I think once a week.
Great !
Why don't include this sub-branch in the stat page ? Is it possible to add it ?
We probably can add it. It is not included thus far, because packages translations are not mandatory for SUSE Linux products. Of course, the openSUSE community can decide differently. Cheers, Karl
Ok. If other teams would like to share their mind about it ! Cheers, Guillaume --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
On 1/15/08, Karl Eichwalder <ke@suse.de> wrote:
Guillaume Gardet <guillaume.gardet@free.fr> writes:
How often are those translations refreshed ? I mean included in repositories.
I think once a week.
Apparently, there is an automatic update for *.pot files ( log : "automatic update from PDB"). Is it possible to run an automatic script in order to merge the *.$LL.po files with the *.pot files ?
Thanks for asking. If I got it right, the merge will now run at 2:45 CE(S)T every monday morning. ATM, the automatic merging is enable only for the following languages:
cs de es fr hu pl
I can add more languages, if wanted.
Can you please include Punjabi (pa) for Auto merge? thanks -- AmanAlam Punjabi OpenSource Team --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
"Amanpreet Singh" <apreet.alam@gmail.com> writes:
cs de es fr hu pl
I can add more languages, if wanted.
Can you please include Punjabi (pa) for Auto merge?
Sure, done. Karl -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-01-15 at 11:05 +0100, Karl Eichwalder wrote:
Guillaume Gardet <guillaume.gardet@free.fr> writes:
How often are those translations refreshed ? I mean included in repositories.
I think once a week.
Apparently, there is an automatic update for *.pot files ( log : "automatic update from PDB"). Is it possible to run an automatic script in order to merge the *.$LL.po files with the *.pot files ?
Thanks for asking. If I got it right, the merge will now run at 2:45 CE(S)T every monday morning. ATM, the automatic merging is enable only for the following languages:
cs de es fr hu pl
I can add more languages, if wanted.
What does this all mean? I got lost, I'm afraid. - What does this merge operation do? - Wasn't the packages branch a non-translated branch? - -- Cheers, Carlos E. R. ('es' team) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHjKF4tTMYHG2NR9URAtZSAJwOSA1lNtwyDfc05UpZsq0nJLdWGACfRjc8 OgmCo2m9uEW8QuI9zFD6cH0= =LqNW -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
"Carlos E. R." <robin.listas@telefonica.net> writes:
cs de es fr hu pl
I can add more languages, if wanted.
What does this all mean? I got lost, I'm afraid.
- What does this merge operation do? - Wasn't the packages branch a non-translated branch?
"packages" is not actually a branch, but a directory (module) within each branch and the trunk. If you feel the like, you can translate the packages files in the trunk. It resides on the same level as "yast" and "lcn". The packages translation are meant to appear in the software management of yast. "merge" here simply mean that I will merge the the POTs with the POs as usual. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Karl Eichwalder a écrit :
"packages" is not actually a branch, but a directory (module) within each branch and the trunk. If you feel the like, you can translate the packages files in the trunk. It resides on the same level as "yast" and "lcn". The packages translation are meant to appear in the software management of yast.
The translations made in the trunk branch will appear in the factory or in all branches (10.3 - 10.2 - etc...) ? I think it is only in the factory and if we want to enable those translations for 10.3 for example, we have to copy the files from the trunk to the 10.3 branches. Am I right ? If I am right, is it possible to have a script which copy all the required files from the trunk to the 10.3 branche ? or at least could we copy them ? i18n.opensuse.org is still offline... Cheers, Guillaume --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Guillaume Gardet <guillaume.gardet@free.fr> writes:
The translations made in the trunk branch will appear in the factory or in all branches (10.3 - 10.2 - etc...) ?
Factory.
I think it is only in the factory and if we want to enable those translations for 10.3 for example, we have to copy the files from the trunk to the 10.3 branches. Am I right ? If I am right, is it possible to have a script which copy all the required files from the trunk to the 10.3 branche ? or at least could we copy them ?
No, not necessarily. And esp. the packages stuff is basically factory only. It is rather cumbersome (=~ impossible) to change packages descriptions in release products.
i18n.opensuse.org is still offline...
Yes, we want to install it on a new machine. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-01-17 at 12:47 +0100, Guillaume Gardet wrote:
The translations made in the trunk branch will appear in the factory or in all branches (10.3 - 10.2 - etc...) ?
AFAIK, no.
I think it is only in the factory and if we want to enable those translations for 10.3 for example, we have to copy the files from the trunk to the 10.3 branches. Am I right ?
Yesss... and no.
If I am right, is it possible to have a script which copy all the required files from the trunk to the 10.3 branche ? or at least could we copy them ?
No. It has to be manually done, it could break things. You can replace files of the same name to an older branch, or better, do something like: msgcat --use-first -o NEW-10.3-file.fr.po \ existing-10.3-file.fr.po existing-trunk-file.fr.po This will create a new .po file, which will be invalid. After having all the files replaced, you will have to run "make update-po" so that the msgids from the .pot files are merged, and those that do not exist are removed from the .po file (or inhabilitated). After that, you will have to review all of them with kbabel or whatever, as many of them will be marked fuzzy. Another method is, if you have translated trunk, to train kbabel compendium database on trunk and branches, and let it do an automatic translation on any branch file you want to. This has the advantage that it will use msgs from any file if the msgs match (ie, some msgs are now in a different file). The disadvantage is that ll of those msgs it translates will be marked fuzzy. The best thing, IMO, would be to use both methods one after the other.
i18n.opensuse.org is still offline...
But the svn server is working alright. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHj1eJtTMYHG2NR9URAlveAJ9wkY2R2XszAUF0hP8loY+8jYt8XACeLDpO eTBLvB9i4PZn/vIYP1y2joc= =JB1k -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
participants (8)
-
Amanpreet Singh -
Carlos E. R. -
Guillaume Gardet -
guillaume.gardet＠free.fr
-
Karl Eichwalder -
Ladislav Michnovič -
Pascal Bleser -
Stanciu-Lixandru Alec