[opensuse-translation] openSUSE 10.3 Preliminaries
Do not ask—setting the deadlines is still under consideration ;) Nevertheless during the last days developers updated some .pot files and something new is available for translation. We also got a YaST update just today, and I'm going to merge all this soon. Caveats: . All the new messages are not proofed; expect changes and thus fuzzies during the next weeks. . Fixed translations are still to be merged from the SLE10SP1 branch to the trunk. This applies for the official SLE10 languages only: * pt_BR fr it es de zh_CN zh_TW ja * ru cs hu pl ko fi da nb sv nl * ca ar hi bn gu mr ta zu xh af * sk -- 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
Den Tuesday 17 April 2007 13:49:57 skrev Karl Eichwalder:
. Fixed translations are still to be merged from the SLE10SP1 branch to the trunk. This applies for the official SLE10 languages only: * pt_BR fr it es de zh_CN zh_TW ja * ru cs hu pl ko fi da nb sv nl * ca ar hi bn gu mr ta zu xh af * sk
Interesting and surprising.. and nice, that da is official SLE10 language. I was wondering about the good stats Danish SP1 had. http://i18n.opensuse.org/stats/SLE10-SP1/da/index.php Who's translating the stuff? or is it just 10.2 translations + some scripting magic? Does it have any implications for openSUSE translations? Will professional translators do our job in the future? And does this means that these translations will actually be included in SP1? I think AJ said in the fall that it was not planned to do large translation updates in SP1. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Martin Schlander <suse@linuxin.dk> writes:
Den Tuesday 17 April 2007 13:49:57 skrev Karl Eichwalder:
. Fixed translations are still to be merged from the SLE10SP1 branch to the trunk. This applies for the official SLE10 languages only: * pt_BR fr it es de zh_CN zh_TW ja * ru cs hu pl ko fi da nb sv nl * ca ar hi bn gu mr ta zu xh af * skInteresting and surprising.. and nice, that da is official SLE10 language. I was wondering about the good stats Danish SP1 had.
http://i18n.opensuse.org/stats/SLE10-SP1/da/index.php
Who's translating the stuff? or is it just 10.2 translations + some scripting magic?
That was professional translators.
Does it have any implications for openSUSE translations? Will professional translators do our job in the future?
Not for Danish - that was a one time only action. But you can benefit From it. ;-)
And does this means that these translations will actually be included in SP1? I think AJ said in the fall that it was not planned to do large translation updates in SP1.
It was not planned at that time - but then plans were changed ;-) Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Den Tuesday 17 April 2007 16:01:58 skrev Andreas Jaeger:
Who's translating the stuff? or is it just 10.2 translations + some scripting magic?
That was professional translators.
Does it have any implications for openSUSE translations? Will professional translators do our job in the future?
Not for Danish - that was a one time only action. But you can benefit From it. ;-)
Hmm.. this makes me a little nervous. In the Danish team we have certain conventions we follow to ensure uniformity. I assume the same goes for other tier2 teams that suddenly became "one time only official SLE languages". How many strings are we talking about here? Tens? Hundreds? Thousands? Is there an easy way for us to check the diffs after these "unofficial opensuse translations" are merged with ours? I really hope these "professional" people had a look at our wiki-page and conformed more or less with our conventions, but of course that's probably not likely.
And does this means that these translations will actually be included in SP1? I think AJ said in the fall that it was not planned to do large translation updates in SP1.
It was not planned at that time - but then plans were changed ;-)
Great, maybe now Danish enterprises and government agencies can stfu and switch to GNU/Linux ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Martin Schlander <suse@linuxin.dk> writes:
Den Tuesday 17 April 2007 16:01:58 skrev Andreas Jaeger:
Who's translating the stuff? or is it just 10.2 translations + some scripting magic?
That was professional translators.
Does it have any implications for openSUSE translations? Will professional translators do our job in the future?
Not for Danish - that was a one time only action. But you can benefit From it. ;-)
Hmm.. this makes me a little nervous. In the Danish team we have certain conventions we follow to ensure uniformity. I assume the same goes for other tier2 teams that suddenly became "one time only official SLE languages".
How many strings are we talking about here? Tens? Hundreds? Thousands?
Is there an easy way for us to check the diffs after these "unofficial opensuse translations" are merged with ours?
Yes, it's a svn repository - you can run svn diff.
I really hope these "professional" people had a look at our wiki-page and conformed more or less with our conventions, but of course that's probably not likely.
We did not point them there - sorry ;-( Didn't we announce this translation some months ago? If we didn't sorry ;-(
And does this means that these translations will actually be included in SP1? I think AJ said in the fall that it was not planned to do large translation updates in SP1.
It was not planned at that time - but then plans were changed ;-)
Great, maybe now Danish enterprises and government agencies can stfu and switch to GNU/Linux ;-)
Would be fine, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Andreas, are there any plans about broadening tier1 language list for 10.3? I also wondering about media layout for the next release. How will they be arranged on the media? If in the same manner as in 10.2, won't they all be put on Addon CD? -- Regards, Nikolay Derkach
Nikolay Derkach <nderkach@gmail.com> writes:
Andreas, are there any plans about broadening tier1 language list for 10.3?
I also wondering about media layout for the next release. How will they be arranged on the media? If in the same manner as in 10.2, won't they all be put on Addon CD?
This is something Michael and myself still look for some sane concepts, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Martin Schlander <suse@linuxin.dk> writes:
Is there an easy way for us to check the diffs after these "unofficial opensuse translations" are merged with ours?
I tag the current trunk files before the merge as tags/10.3pre-before-merge-with-sle10sp1/yast. For there you can checkout the files for comparison if needed--for example, as follows: svn co https://forgesvn1.novell.com/svn/suse-i18n/tags/10.3pre-before-merge-with-sl... I made a stupid mistake with German that I'm going fix later. At the moment, the merge is in progress for the tier2 languages. Only "yast", "lcn" will follow later. -- 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
Den Wednesday 18 April 2007 17:59:24 skrev du:
Martin Schlander <suse@linuxin.dk> writes:
Is there an easy way for us to check the diffs after these "unofficial opensuse translations" are merged with ours?
I tag the current trunk files before the merge as tags/10.3pre-before-merge-with-sle10sp1/yast. For there you can checkout the files for comparison if needed--for example, as follows:
svn cohttps://forgesvn1.novell.com/svn/suse-i18n/tags/10.3pre-before-merge-with-s le10sp1/yast/da
Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Karl Eichwalder <ke@suse.de> writes:
I made a stupid mistake with German that I'm going fix later. At the moment, the merge is in progress for the tier2 languages. Only "yast", "lcn" will follow later.
The preliminary "yast" merge is done now and I'm also submitting updated packages to the build system for testing. -- 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
Den Wednesday 18 April 2007 17:59:24 skrev Karl Eichwalder:
Martin Schlander <suse@linuxin.dk> writes:
Is there an easy way for us to check the diffs after these "unofficial opensuse translations" are merged with ours?
I tag the current trunk files before the merge as tags/10.3pre-before-merge-with-sle10sp1/yast. For there you can checkout the files for comparison if needed--for example, as follows:
svn cohttps://forgesvn1.novell.com/svn/suse-i18n/tags/10.3pre-before-merge-with-s le10sp1/yast/da
I'm currently comparing the work. As I feared the SLE translators have broken our consistency in a lot of places - and they're not even consistent with themselves. I assume more persons than one have worked on them - because of the inconsistency and since different kbabel-versions are used. They seem to have fixed some errors that we had made, but they've also introduced new ones. It seems that we'd only lose a few hundred fuzzy/untranslated strings of work by using the pre-merged pos, so I'm seriously considering this. Of course this would become more problematic if things change in trunk, so I'd like to know if more updates of yast po-files are planned for the immediate future? In other words are we in a hurry to make a decision and to possibly re-commit the pre-merge pos to trunk? I'd also like to ask you to do the same thing with pre-merge tagging for the lcn stuff when those are merged. To enable us to have an easy way to discard the SLE lcn-work in case we find it causes more problems than it solves too. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Martin Schlander <suse@linuxin.dk> writes:
It seems that we'd only lose a few hundred fuzzy/untranslated strings of work by using the pre-merged pos, so I'm seriously considering this.
Those questions are to be decided by every language team on its own. If you decide to go this way, just copy the .po files of your language from "tags/10.3pre-before-merge-with-sle10sp1" back to the trunk and check them in.
Of course this would become more problematic if things change in trunk, so I'd like to know if more updates of yast po-files are planned for the immediate future?
Not within the next couple of days. I guess, in the beginning of May or a little bit later we can expect updated YaST .pot files.
In other words are we in a hurry to make a decision and to possibly re-commit the pre-merge pos to trunk?
I'd also like to ask you to do the same thing with pre-merge tagging for the lcn stuff when those are merged. To enable us to have an easy way to discard the SLE lcn-work in case we find it causes more problems than it solves too.
I just populated "tags/10.3pre-before-merge-with-sle10sp1/lcn" and now I will merge the lcn files from the SLE10SP1 branch to the trunk. Once again, only the official SLES and SLED languages are affected. -- 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
Den Monday 23 April 2007 16:14:21 skrev Karl Eichwalder:
I just populated "tags/10.3pre-before-merge-with-sle10sp1/lcn" and now I will merge the lcn files from the SLE10SP1 branch to the trunk. Once again, only the official SLES and SLED languages are affected.
Happened to notice zmd, zen-updater and rug are still there, some poor soul might accidentally waste some time working on it ;-) I've kept some of the SLE lcn-translations, over the pre-merged ones. So at least not all is lost from the point of view of Danish openSUSE translations. Thanks again for making it so easy for us to decide for ourselves. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Martin Schlander <suse@linuxin.dk> writes:
Happened to notice zmd, zen-updater and rug are still there, some poor soul might accidentally waste some time working on it ;-)
Yes, but I think all of them are already 100% translated ;) It's on my agenda to remove obsolete files the next. We are still in the pre-translation state, but of course, help to cleanup the SVN trunk in always appreciated!
I've kept some of the SLE lcn-translations, over the pre-merged ones. So at least not all is lost from the point of view of Danish openSUSE translations. Thanks again for making it so easy for us to decide for ourselves.
It is always good to know about additional copies. Otherwise it is not that difficult to check out a previous version from SVN--you just must know the date. -- 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 <ke@suse.de> writes: Only official SLE10SP1 languages are affected. ATM, I'm merging the yast part from SLE10SP1 to the trunk once again. I do not merge languages for which translator are already active since some time (ru, hu, fi, and da). The lcn part will follow later.
I tag the current trunk files before the merge as tags/10.3pre-before-merge-with-sle10sp1/yast.
This time I forgot to create the tag; but it is possible to do it once the merge is done. -- 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
Den Wednesday 30 May 2007 10:47:50 skrev Karl Eichwalder:
I do not merge languages for which translator are already active since some time (ru, hu, fi, and da).
Good --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Hi, Thanks for the infomations. I plan to translate it very soon (lcn and yast), but I am not sure about the folder "package", there are 9355 untranslated messages and 596 fuzzy messages for Khmer (km). Should it be translated and where will these messages be appeared? I mean that these messages will appear during installation process or in Yast? Thank again for your respone! Sokhem On Tuesday 17 April 2007 6:49:57 pm Karl Eichwalder wrote:
Do not ask—setting the deadlines is still under consideration ;)
Nevertheless during the last days developers updated some .pot files and something new is available for translation. We also got a YaST update just today, and I'm going to merge all this soon.
Caveats:
. All the new messages are not proofed; expect changes and thus fuzzies during the next weeks. . Fixed translations are still to be merged from the SLE10SP1 branch to the trunk. This applies for the official SLE10 languages only: * pt_BR fr it es de zh_CN zh_TW ja * ru cs hu pl ko fi da nb sv nl * ca ar hi bn gu mr ta zu xh af * sk
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Khoem Sokhem <khoemsokhem@khmeros.info> writes:
Thanks for the infomations. I plan to translate it very soon (lcn and yast),
Thanks for your commitment, but there is no need to hurry up now—we are still in the preparation phase.
but I am not sure about the folder "package", there are 9355 untranslated messages and 596 fuzzy messages for Khmer (km). Should it be translated and where will these messages be appeared? I mean that these messages will appear during installation process or in Yast?
In the long run, these are meant to be translated. But at the moment, we do not know when we can add new package translations to the distribution. -- 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
participants (5)
-
Andreas Jaeger -
Karl Eichwalder -
Khoem Sokhem -
Martin Schlander -
Nikolay Derkach