Martin Schlander
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