On Tue, 16 Oct 2007, Karl Eichwalder wrote:
I already had some trouble regarding this topic with main distribution and my own packages so I know this is a major topic.
IIRC, you were told that translations of "official" openSUSE packages are managed in a dedicated suse-i18n directory: https://forgesvn1.novell.com/svn/suse-i18n/trunk/packages
Ah, you remember me. Did I make such a bad impression? :-)
Otherwise you are right, we must address this for Build Service packages, too.
Please not only for packages, but for the buildservice itself (meta information, the interface, ...). English gets accepted more and more, but there are still many people all over the world, who can't speak English. Some of our customers are among them. If I tell them to go to the buildservice and do this and that, the first thing they will do is to tell me all is in english (Ok, I agree this is still better, than to explain them how to solve dependency and install a package themself or even build it :-). BTW: For BuildService there should be an easy way for end users to add/fix translations. No need for any software, but allow them to directly generate patchsets for translations using a web-interface. This would probably increase the number of translated strings a lot. The inputs should not be taken automatically into packages, but it should be easy to use them (e.g. look over them for strange stuff, accept them). Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org