Den Wednesday 18 April 2007 17:59:24 skrev Karl Eichwalder:
Martin Schlander
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-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