[opensuse-translation] How to "test" translations of the package "branch"
Hi all, I've done a few translations in French mainly for YaST components. I now work on the package branch. It's really a huge work and I don't know how to check if my translations are fine. I've installed OpenSuse 11 Alpha 2 in French with Virtual Box. RPMs descriptions are still in english (even those who have been commited in svn by team coordinator). It would be helpful because it's sometimes difficult to understand to which package a message belongs to. So I don't have the context to do a better translation. Thanks in advance Benoit Verduyn --------------------------------------------------------------------- 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 Saturday 2008-03-08 at 14:55 -0500, Benoit Verduyn wrote:
I've done a few translations in French mainly for YaST components. I now work on the package branch. It's really a huge work and I don't know how to check if my translations are fine. I've installed OpenSuse 11 Alpha 2 in French with Virtual Box. RPMs descriptions are still in english (even those who have been commited in svn by team coordinator).
For Yast you can make your own rpm of the translation only. It's package "yast2-trans-es" (your language code instead of "es", obviously), and you can create a newer version running "checkinstall" giving a newer version; I did (for 10.3) like this: sudo /usr/sbin/checkinstall --arch=noarch \ --pkggroup=Compilaciones/translations \ --pkgname=yast2-trans-es \ --pkgversion=2.15.6 --pkgrelease=900 Of course, before this (which creates an rpm running "make install") in the yast/{LANG} directory you have to run "make". And before that, make update-po. My notes say: yast install yast2-devtools.rpm cd {LANG} make -f Makefile.cvs cd po make update-po You need to have downloaded the 50-etc 50-html 50-pot and 50-memory directories for all this to work. The lcn branch is more difficult, there is no single rpm you can make with all translations, I understand. I didn't make it. However, you'd still need the update-po: autoreconf --force --install ./configure cd {LANG} make -f Makefile.svn make update-po I wonder what a "make install" would install in this branch :-?
It would be helpful because it's sometimes difficult to understand to which package a message belongs to. So I don't have the context to do a better translation.
True. More so for the lcn branch. Ah, there is a very large file, update-desktop-files.{LANG}.po, that grows almost by the day. I think this one contains descriptions. I "hate" it. Some teams only translate part of this file: those messages used by Yast. Just search for the word "yast" in the comments part. As for the huge task... I assume that Canadian French is different than, what do you call it, European French? And assuming the European French branch is more complete, I suppose you could start copying the French translations over the French Canadian branch, then review and modify whatever is different for you. Still, a daunting task. Another method, preferable, is to train (*) your kbabel on the French branch, then tell it to do a rough (fuzzy) translations of the Canadian files. Only untranslated messages would be rough translated, and left fuzzy for you to review. (*) If you don't know how to train kbabel, I'll explain. Or read it in the Spanish wiki, I wrote it there ;-p - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH08r/tTMYHG2NR9URAiQyAJ9WtdGyHOOW0Nl1JRxwQuQQXaZc3ACeOw52 PdXJDb3z4Bs4uqArEXmwqJ0= =izUP -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
He was talking about the packages descriptions from https://forgesvn1.novell.com/viewsvn/suse-i18n/trunk/packages/ Maybe Karl could help us ! Cheers, Guillaume Carlos E. R. a écrit :
The Saturday 2008-03-08 at 14:55 -0500, Benoit Verduyn wrote:
I've done a few translations in French mainly for YaST components. I now work on the package branch. It's really a huge work and I don't know how to check if my translations are fine. I've installed OpenSuse 11 Alpha 2 in French with Virtual Box. RPMs descriptions are still in english (even those who have been commited in svn by team coordinator).
For Yast you can make your own rpm of the translation only. It's package "yast2-trans-es" (your language code instead of "es", obviously), and you can create a newer version running "checkinstall" giving a newer version; I did (for 10.3) like this:
sudo /usr/sbin/checkinstall --arch=noarch \ --pkggroup=Compilaciones/translations \ --pkgname=yast2-trans-es \ --pkgversion=2.15.6 --pkgrelease=900
Of course, before this (which creates an rpm running "make install") in the yast/{LANG} directory you have to run "make". And before that, make update-po. My notes say:
yast install yast2-devtools.rpm cd {LANG} make -f Makefile.cvs cd po make update-po
You need to have downloaded the 50-etc 50-html 50-pot and 50-memory directories for all this to work.
The lcn branch is more difficult, there is no single rpm you can make with all translations, I understand. I didn't make it.
However, you'd still need the update-po:
autoreconf --force --install ./configure cd {LANG} make -f Makefile.svn make update-po
I wonder what a "make install" would install in this branch :-?
It would be helpful because it's sometimes difficult to understand to which package a message belongs to. So I don't have the context to do a better translation.
True. More so for the lcn branch.
Ah, there is a very large file, update-desktop-files.{LANG}.po, that grows almost by the day. I think this one contains descriptions. I "hate" it.
Some teams only translate part of this file: those messages used by Yast. Just search for the word "yast" in the comments part.
As for the huge task... I assume that Canadian French is different than, what do you call it, European French? And assuming the European French branch is more complete, I suppose you could start copying the French translations over the French Canadian branch, then review and modify whatever is different for you. Still, a daunting task.
Another method, preferable, is to train (*) your kbabel on the French branch, then tell it to do a rough (fuzzy) translations of the Canadian files. Only untranslated messages would be rough translated, and left fuzzy for you to review.
(*) If you don't know how to train kbabel, I'll explain. Or read it in the Spanish wiki, I wrote it there ;-p
-- Cheers, Carlos E. R.
--------------------------------------------------------------------- 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
Guillaume Gardet
He was talking about the packages descriptions from https://forgesvn1.novell.com/viewsvn/suse-i18n/trunk/packages/
Maybe Karl could help us !
coolo already answered :-) -- 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
Am Samstag, 8. März 2008 schrieb Benoit Verduyn:
Hi all,
I've done a few translations in French mainly for YaST components. I now work on the package branch. It's really a huge work and I don't know how to check if my translations are fine. I've installed OpenSuse 11 Alpha 2 in French with Virtual Box. RPMs descriptions are still in english (even those who have been commited in svn by team coordinator).
It would be helpful because it's sometimes difficult to understand to which package a message belongs to. So I don't have the context to do a better translation.
Actually it's a long standing enhancement request to include these informations in the POT file. But I'm afraid you can't test it easily. First problem: the translations are only synced every monday night and the first rebuild _after_ that is synced out with translations. And then it should be in this file: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/se... Greetings, Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Am Sonntag, 9. März 2008 schrieb Stephan Kulow:
Am Samstag, 8. März 2008 schrieb Benoit Verduyn:
Hi all,
I've done a few translations in French mainly for YaST components. I now work on the package branch. It's really a huge work and I don't know how to check if my translations are fine. I've installed OpenSuse 11 Alpha 2 in French with Virtual Box. RPMs descriptions are still in english (even those who have been commited in svn by team coordinator).
It would be helpful because it's sometimes difficult to understand to which package a message belongs to. So I don't have the context to do a better translation.
Actually it's a long standing enhancement request to include these informations in the POT file.
I finally spend an hour today to fix that problem. So the PO files will look like this now: #: a2ps-h (59508) summary #, fuzzy msgid "a2ps Support for Korean PostScript Filter (Python Version)" msgstr "a2ps-Unterstützung für koreanischen PostScript-Filter (Python-Version)" #: a2ps-h (55725) description msgid "a2ps support for Korean PostScript filter (Python version)." msgstr "a2ps-Unterstützung für koreanischen PostScript-Filter (Python-Version)" One thing to remember though: please don't use newline characters in summaries. It's fine in description Greetings, Stephan --------------------------------------------------------------------- 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 Monday 2008-03-10 at 21:54 +0100, Stephan Kulow wrote:
One thing to remember though: please don't use newline characters in summaries. It's fine in description
Remember? I had no idea! I can't remember something I never knew, you know. ;-) Those things should be said somewhere we translators can easily find and read. A readme file in the .po directory, perhaps. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH1e8GtTMYHG2NR9URAjwBAJ9lynBYAXR/m6u9F38ObWKQs4WRSQCfXnks veiYQ3tXqfSCwGUkiWEe7tU= =yIeg -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
participants (5)
-
Benoit Verduyn -
Carlos E. R. -
Guillaume Gardet -
Karl Eichwalder -
Stephan Kulow