[opensuse-translation] Establishing a Software Proofreading Team
In addition to the well established translations teams, we'd also like to build a software proofreading team. If you are an (American) English native speaker or someone with deep knowledge in English and you want to improve the software strings of YaST and other tools, join the proofreading team! We will grant you SVN commit rights. The first one who applies will become the team coordinator. So, send me your Novell account name (Bugzilla login) and access your wiki user page at http://developer.novell.com/wiki/index.php/User:<NAME> Replace "<NAME>" with your actual user name. Before starting proofing, you must read the "Style Guide for SUSE Program Texts" (http://forgeftp.novell.com/yast/doc/SL11.0/styleguide/index.html) and proof according to these guidelines. The proofing process works as follows: . Find the files to be proofed in the 50-proof directory (https://forgesvn1.novell.com/svn/suse-i18n/trunk/yast/50-proof). Those are POT files, so you can use known POT or PO files editors such as kbabel, Emacs/po-mode, or poedit. Note, we probably will update the POT files later this week again. . If possible, check file by file completely. Initially, all message strings are empty and marked as fuzzy: #: disk/src/disk.ycp:50 #, fuzzy msgid "<p>Please wait, while volumes are being detected.</p>" msgstr "" If you want a approve a message, just remove the fuzzy marker and keep the msgstr field empty. #: disk/src/disk.ycp:50 msgid "<p>Please wait, while volumes are being detected.</p>" msgstr "" If you want to supply a correction, enter a "translation" and remove the fuzzy marker: #: disk/src/disk.ycp:50 msgid "<p>Please wait, while volumes are being detected.</p>" msgstr "<p>Wait, while volumes are being detected.</p>" In case of doubt, keep the fuzzy for the moment, thus another team members can find and check it: #: disk/src/disk.ycp:50 #, fuzzy msgid "<p>Please wait, while volumes are being detected.</p>" msgstr "<p>Wait, while volumes are being detected.</p>" . Once the proofreading round is finished, the software developers will carryover your corrections into the source code and we will store all approved or improved strings in our string database. -- 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
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. 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. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Selon Martin Schlander <martin.schlander@gmail.com>:
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.
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.
If we have a proofreading team, we could send an email to their mailing list and this team will fix it. It will be simple. Moreover, translators do not see the translated sentences but only the fuzzy or untranslated ones. So, I think this new team could improve the openSUSE translation project. Regards, Guillaume --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
2008/8/5 Martin Schlander <martin.schlander@gmail.com>:
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.
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.
Hear hear. When reading the strings it's quite possible to find literally hundreds of typos. Filing a separate bug report for each is impractical for the reporter. Filing one bug report with all the errors is inconvenient to triage, especially when the typos may be in many different pieces of software. -- Benjamin Weber --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
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
Karl Eichwalder:
... I'll start a wiki page ([[Proofreadin_Team]]?) where we can start collecting ideas.
Done -- someone to proofread this page, please ;) http://en.opensuse.org/Proofreading_Team -- Karl Eichwalder --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
I think that should be a separated team for proofreading. The translators could send them several errors or suggestions together, and the proofreaders could file the bugs, or contact with the developers, or do what have to be done. I think putting more load of the translators shoulders is a very bad idea. You said that the translators only read the fuzzy or untranslated strings, it is true, but there are several languages that have very few translated strings that in the future could translate a lot of them, reading in the process a lot of fuzzy and untranslated strings and seeing the errors. Bye, Leandro Regueiro --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
participants (5)
-
Benji Weber -
Guillaume GARDET -
Karl Eichwalder -
Leandro Regueiro -
Martin Schlander