Martin Schlander <martin.schlander@gmail.com> writes:
Tirsdag 05 august 2008 13:50:11 skrev Karl Eichwalder:
In addition to the well established translations teams, we'd also like to build a software proofreading team.
I think if we had a simpler/faster way to report typos and errors in msgids, like via e-mail or a wiki page or something, the translators would be much more helpful in this respect.
Yes, I did not want to enforce this process by all means. If the Proofreading Team comes up with a better workflow, that would be fine, too. The process I described is basically a proposal how we could do things.
At least personally I come across quite a few mistakes when translating, and am generally too lazy to file a full fledged bugzilla report per typo/error.
In KDE translation project typos are reported to the mailinglist and the l10n coordinators then fix them in svn. Maybe we could come up with a similar quick and dirty proces.
Of course, that's also possible, at least during the development phase up to beta3, I'd say. Unfortunately, this only works if you know the developer or if you subscribe to a ML; without subscription mail will just bounce back. Anyway, besides reporting typos we will also need systematic proofreading at well-defined times during the development cycle. I'll start a wiki page ([[Proofreadin_Team]]?) where we can start collecting ideas. -- 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