- openSUSE Translation

[opensuse-translation] Bugzilla as a project management tool
by Stanisław Małolepszy 16 Sep '06

16 Sep '06

Hello, During the last several months, the process of localization of OpenSUSE has been improved greatly thanks to efforts of Novell and the SUSE team. We owe you a big 'Thank you' for L10n wiki, mailing lists and - last but not least - SVN access. What I would like to present in this e-mail is yet another enhancement that could improve the process and make our lives easier. I'm talking namely about Novell's Bugzilla, which as of yet, is not at all used to report bugs and mistakes in the translations. For SUSE Linux 10.0, 10.1 and OpenSUSE 10.2 there have been 143 bugs reports submitted in total, for all the languages <http://tinyurl.com/j2747>. Not too many, as it seems to me. I would like that we considered and discussed here on the list the ways to improve this situation. The e-mail is mainly address to Karl and Klára, but it would be obviously beneficial if everybody took part in the discussion. Please :-) I think we could try to use Bugzilla more extensively, not only for reporting bugs about typos and untranslated files, but also as a general project management tool. Pretty much like the Mozilla guys use it now. So that 'bugs' become more like 'tickets', general issues and not only errors. Examples of cases in which bugzilla could be employed: - Tracking L10n of a new version of openSUSE (fixed when l10n is ready) - New localizer requesting a SVN access - A new file / group of files available for translation (assigning translation, tracking it). Real-life example: Packages descriptions in OpenSUSE 10.2 translation of which could be managed via the bugzilla. - Last minute fixes required after the string freeze - Local license policy issues (if any) - Unable to land translations into the system (the reason should determine assignee) - Spelling/style/grammar mistake in application Foo / window Bar To implement these various functions for Bugzilla, I would like to suggest some modifications to the current structure of bugzilla.novell.com. Three proposals follow, together with more detailed info. Proposal 1 no changes to bugzilla, least efficient - Classification: SUSE Linux - Product: OpenSUSE 10.2 - Component: Translations / L10n / I18n - Version: Alfa 4 - Subject: Polish / pl / pl-PL / pl_PL bug (requires precise user's input or moderation so that the bugs are easily findable) Proposal 2 small changes to bugzilla, provides Language component (this way it would be possible to run searches easily and to assign different owner for different components, i.e. languages) - Classification: SUSE Linux - Product: I18n - Component: Polish - Subject: OpenSUSE 10.2 Alfa4 bug (requires precise user's input or moderation so that the bugs are easily findable) Proposal 3 more changes to bugzilla (not time-consuming nonetheless) but also presumably the most efficient - Classification: I18n - Product: Polish - Component: OpenSUSE 10.2 - Version: Alfa 4 The rationale behind Proposal 3 is that internationalization, as a process, concerns many fields of Novell's activity. It includes OpenSUSE, true, but what I would like to propose is a holistic approach to managing the i18n process by means of the bugzilla. I see other "products" such as wiki, mailing list, administration, communication and so on. I know that this might sound like introducing a lot of red tape all around, but in fact it turns out (once again I refer to Mozilla) that it works and that it works well. So, what do you think? Are there any chances that this could become reality in the near future? How do you feel about it, about working through Bugzilla and the proposals I came up with. In particular, what do you think of proposal 3? Looking forward to your comments and ideas. Best regards, Stanisław Małolepszy -- AviaryPL L10n team --------------------------------------------------------------------- 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] croatian translation
by Daniel Radetic 16 Sep '06

16 Sep '06

Hi, I have translated fully about 25 files to croatian so far. The files that were included in croatian language pack were badly translated (i think automation system was used), so i had to review and correct all errors made by previous translators. Where do i comit/upload or send these translated .po files ? Regards, Daniel Radetic -- Daniel Radetic - Quid quid habes hodie, cras te fortasse relinquet aut modo dum lonqueris, dessinit esse tuum. GPG Key fingerprint = 27C1 D27D C64C 95C9 DC89 9F25 AA81 0C3F 00B6 3126 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

3 2

[opensuse-translation] starting pt_BR translation
by ¡ElCheVive! 15 Sep '06

15 Sep '06

I'll start translating OpenSuSE specific applications (yast & lcn) into pt_BR (Brazilian Portugues) language. Language name - Brazilian Portuguese Language ISO code - pt_BR My name - Luiz Fernando Ranghetti My Novell login - elchevive My e-mail - elchevive(a)bol.com.br regards, Luiz Fernando Ranghetti aka ¡ElCheVive! --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

3 5

[opensuse-translation] Bulgarian translation
by Borislav Mitev 14 Sep '06

14 Sep '06

Language name - Bulgarian Language ISO code - bg My name - Borislav Mitev My Novell login - morbid_viper My e-mail - morbid_viper(a)tkzs.org -- ------------------------------------------------- Blessed are we to taste this life of sin! ------------------------------------------------- Borislav Mitev <morbid_viper(a)tkzs.org> Registered Linux user #251276 <http://counter.li.org> Public key: 0x966B79CA at pgp.mit.edu or subkeys.pgp.net Linux 2.6.16.21-0.13-default i686 GNU/Linux 4:53сл.обед включен 9 дена 2:47, 2 потребителя, средно натоварване: 0,51, 0,12, 0,04

1 0

[opensuse-translation] Punjabi Translation Team
by A S Alam 14 Sep '06

14 Sep '06

Hello, I would like to annouce Punjabi (Gurmukhi) Translation Team for OpenSuse. Files are already available for Translation with Lanuage code (pa) in SVN My name - A P Singh My Novell login - apbrar My e-mail - apbrar(a)gmail.com thanks AP Singh --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

1 0

[opensuse-translation] About OpenSUSE Localization Team: Turkish
by Muhammet Kara 14 Sep '06

14 Sep '06

Hello, I want to join the Turkish Localization Team. Turkish language is listed in the OpenSUSE Localization Teams table but there is no coordinator. -- Regards, Muhammet Kara GTalk: muhammet.k(a)gmail.com GSM: +90 555 5880396

2 1

[opensuse-translation] starting Estonian translation
by Ain Vagula 14 Sep '06

14 Sep '06

Hi, I'll start translating OpenSuSE specific applications into Estonian language. Language name - Estonian Language ISO code - et My name - Ain Vagula My Novell login - avagula My e-mail - avagula(a)gmail.com Ain Vagula --------------------------------------------------------------------- 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] svn procedure
by Olav Pettershagen 14 Sep '06

14 Sep '06

Hello there, I'm now commit authorized for svn and I have been browsing the wiki. In theory svn does not seem too complicated but I still feel a bit uneasy about the procedure. So how about a simple step-by-step explanation for translators who know how to translate po files and have not used svn before. I mean something like: 1. Do this to download the appropriate files to your computer (check out?) with instructions about which files are appropriate. 2. Translate the files - this is the easy part :). 3. Do this to upload translated files to the correct place on the server again (check in?) I think perhaps I would be able to eventually figure this out on my own from the wiki and svn docs. But then again, I'm quite sure that getting the correct files for translation and comitting the translations is the only svn procedure lots of translators will ever perform - so maybe it would be possible to make a straightforward howto for this particular task? I know I would appreciate it. Olav -- http://home.online.no/~olav.pet/current_view.jpg --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

1 0

[opensuse-translation]
by Aleksey Osipov 13 Sep '06

13 Sep '06

Attention please to Russian Translators!!! Please be informed that for inner discussion of work and for easy communication to speedup of our works, we can use the following MailList opensuse-ru(a)opensuse.org To subscribe to the above mentioned mail list you may on following web-page http://en.opensuse.org/Communicate Best regards Aleksey Osipov --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

1 0

[opensuse-translation] Team Coordinator
by ¡ElCheVive! 13 Sep '06

13 Sep '06

hi, I want to translate some .po files in pt_BR After translate for who may I send the files? Who is the team coordinator for pt_BR In the openSuse page there is no coordinator! regards, Luiz Fernando Ranghetti --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

1 0