2011/5/31 Karl Eichwalder :

Now it is up to us to plan translation and localization related activities: presentations, discussions, or even workshops.  I'll offer to talk about our infrastructure (SVN server and communication channels), involved people (translators, package and component maintainers, coordinators), and selected components (e.g., YaST, desktop files, translation update packages).

It sounds interesting.

What are your ideas?  I think small sessions about the tools you use, would be great.  Do we need a trouble-shooting session, where we can talk about thinks that do not work?

I do not think sessions about tools are useful: the only tools I use, for instance, are svn and poedit (and now also OBS, to fix typos in packages descriptions). Other tools can be lokalize, kbabel or some other editor but is it useful to talk about them? On the contrary, I think it is better to focus sessions on the translation experience in order to inform developers of the problems they may cause to translators, when they use complex messages, when they split messages (using string concatenation instead of placeholders), or when they do not add comments. Sometimes I find that it is difficult to parse messages with several adjectives or nouns that can be related in different ways, in particular when I do not know very well the general context of the message. In this case, sometimes it is sufficient to rephrase the message using "noun2 of noun1" instead of "noun1 noun2" but this can be done in the right way only by the developer.

One of my goals would be to attrack even more translators.  Often teams consist of just one active translator.  It would help a lot, if more would join and, for example, do testing and bug reporting.

I hope you can attrack more translators or translation testers. The problem is that it is not so easy to understand if a translation bug is in our files or upstream. Moreover, some components can not be tested easily (such as the translation of the installation process) or it is difficult to understand why a translated message is not used, given that it is actually translated in both upstream and our files (see [1], for instance). Regards, Andrea [1] http://lists.opensuse.org/opensuse-translation/2011-03/msg00056.html -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org