August 2008 - openSUSE Translation - openSUSE Mailing Lists

[opensuse-translation] openSUSE 11.1 translation round
by Khoem Sokhem 07 Aug '08

07 Aug '08

Hello All members, This is just request to inform about the starting date of translation round for openSUSE 11.1. Please some one help to inform in the list about about the translating date for translators. Thanks, Sokhem --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

2 1

[opensuse-translation] Establishing a Software Proofreading Team
by Karl Eichwalder 07 Aug '08

07 Aug '08

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 "Please wait, while volumes are being detected." 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 "Please wait, while volumes are being detected." msgstr "" If you want to supply a correction, enter a "translation" and remove the fuzzy marker: #: disk/src/disk.ycp:50 msgid "Please wait, while volumes are being detected." msgstr "Wait, while volumes are being detected." 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 "Please wait, while volumes are being detected." msgstr "Wait, while volumes are being detected." . 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(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

1 1

[opensuse-translation] Goodbye but don't worry
by Ladislav Michnovič 06 Aug '08

06 Aug '08

Hello everybody. I'm leaving SUSE company but don't worry. I want to continue participating on translations. I expect my svn access will stay untouched. I hope that you will send me a box of 11.1 under Christmas tree. ;) I wouldn't have so much time for translation coordination. Jan Kupec is my successor. So happy translating. Best Regards Ladislav Michnovič.

2 1

[opensuse-translation] Establishing a Software Proofreading Team
by Karl Eichwalder 06 Aug '08

06 Aug '08

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 "Please wait, while volumes are being detected." 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 "Please wait, while volumes are being detected." msgstr "" If you want to supply a correction, enter a "translation" and remove the fuzzy marker: #: disk/src/disk.ycp:50 msgid "Please wait, while volumes are being detected." msgstr "Wait, while volumes are being detected." 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 "Please wait, while volumes are being detected." msgstr "Wait, while volumes are being detected." . 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(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

5 6