[opensuse-translation] Various Information
Please, Could information be provided about the openSUSE localization deadlines? Also because I'm not used to the new terms, how do we call this in the new decade? Translation Freeze? Is there any process the maintainer of a localization project for openSUSE distribution should know? We didn't have so much work to show for Greek Translation for now but this is why we are proceeding step-by-step understanding how the whole process works and providing this information in Greek for the newcomers. Also some other questions: 1) Is there any suggestion about what program should we use for translating? I use gtranslator. Is there any much more popular among openSUSE members? 2) Is there any suggestion about any translation platform we use for translating? We could probably use Transifex. Also it could be a good opportunity for the whole localisation project to examine if there is a possibility of using universally such a platform as Transifex along with our individual translations on the various programs (lokalize, gtranslator, poedit etc) 3) Are out there any translation memories for Greek openSUSE localisation? We started like building one now from scratch, that's the reason I ask. Because of the very active section in our ambassador team and the following rain of announcements I personally find it a little bit difficult in using the greek team mailing list. I would return to my demand of a separate list for the openSUSE Greek localisation team. Although, the translation of the wiki is open to everybody and not specially restricted to localisation team members. 4) I know its starting not to be amusing but I will post the Greek Team's demand for a fix on the Greek forum. We have a very big issue about the encoding on the newly formed greek section of openSUSE fora. The creation of a greek forum was a process begun in 31/01/2007 and after a period of "stoned-years" and the zombie forum suseforums.gr we finally succeed to have our greek forum together with other language specific forums in openSUSE community wiki. Please, if anyone could provide some help on this could be welcome. Kostas Boukouvalas openSUSE Member & Greek Localization Team Maintainer -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Could information be provided about the openSUSE localization deadlines? Also because I'm not used to the new terms, how do we call this in the new decade? Translation Freeze? Is there any process the maintainer of a localization project for openSUSE distribution should know? I can't say much about "official" workflow, that is something I'd like to find out, too. As of personal opinion I like to think that the
1) Is there any suggestion about what program should we use for translating? I use gtranslator. Is there any much more popular among openSUSE members? I prefer Lokalize and I know I am definitely not alone in this. 2) Is there any suggestion about any translation platform we use for translating? We could probably use Transifex. Also it could be a good opportunity for the whole localisation project to examine if there is a possibility of using universally such a platform as Transifex along with our individual translations on the various programs (lokalize, gtranslator, poedit etc) There is an openSUSE project on transifex.net, I loaded it several months ago for testing purposes. If everything its developers promise will become true than Transifex is perfect translation collaboration
Hi, Kostas. translation should be ready yesterday =) Milestone with "First localised build" tag marks the translation testing start for me, and RC1 marks an end. platform, at least for getting more help from newcomers. I, for one, still use Lokalize.
4) I know its starting not to be amusing but I will post the Greek Team's demand for a fix on the Greek forum. We have a very big issue about the encoding on the newly formed greek section of openSUSE fora. The creation of a greek forum was a process begun in 31/01/2007 and after a period of "stoned-years" and the zombie forum suseforums.gr we finally succeed to have our greek forum together with other language specific forums in openSUSE community wiki. Please, if anyone could provide some help on this could be welcome. If it's the issue I think about, then it's like fighting a windmill, since only Greek, Japanese and Russian are affected. We had this conversation with russian subforum several times, nothing changed. -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Στις 22/12/2010 02:40 μμ, ο/η Александр Мелентьев έγραψε:
Could information be provided about the openSUSE localization deadlines? Also because I'm not used to the new terms, how do we call this in the new decade? Translation Freeze? Is there any process the maintainer of a localization project for openSUSE distribution should know? I can't say much about "official" workflow, that is something I'd like to find out, too. As of personal opinion I like to think that the
Hi, Kostas. translation should be ready yesterday =) Milestone with "First localised build" tag marks the translation testing start for me, and RC1 marks an end.
1) Is there any suggestion about what program should we use for translating? I use gtranslator. Is there any much more popular among openSUSE members? I prefer Lokalize and I know I am definitely not alone in this. 2) Is there any suggestion about any translation platform we use for translating? We could probably use Transifex. Also it could be a good opportunity for the whole localisation project to examine if there is a possibility of using universally such a platform as Transifex along with our individual translations on the various programs (lokalize, gtranslator, poedit etc) There is an openSUSE project on transifex.net, I loaded it several months ago for testing purposes. If everything its developers promise will become true than Transifex is perfect translation collaboration platform, at least for getting more help from newcomers. I, for one, still use Lokalize. 4) I know its starting not to be amusing but I will post the Greek Team's demand for a fix on the Greek forum. We have a very big issue about the encoding on the newly formed greek section of openSUSE fora. The creation of a greek forum was a process begun in 31/01/2007 and after a period of "stoned-years" and the zombie forum suseforums.gr we finally succeed to have our greek forum together with other language specific forums in openSUSE community wiki. Please, if anyone could provide some help on this could be welcome. If it's the issue I think about, then it's like fighting a windmill, since only Greek, Japanese and Russian are affected. We had this conversation with russian subforum several times, nothing changed.
Thank you very much Alexander for the answers. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Tirsdag den 21. december 2010 14:37:40 skrev Kostas Boukouvalas:
Could information be provided about the openSUSE localization deadlines? Also because I'm not used to the new terms, how do we call this in the new decade? Translation Freeze? Is there any process the maintainer of a localization project for openSUSE distribution should know?
There's not much you need to know. If you have the necessary permissions, just checkout from svn and translate like mad. Everything else is between you and your team. Of course it helps to know the roadmap - http://en.opensuse.org/Roadmap - Particularly: Dec. 16: "hard text freeze" and Mar. 2: "Translation Finish". Now, I'm pretty sure the finish date is a mistake. It might apply for Release Notes, but for stuff in the actual distro it seems unrealistic to have translation finish after 11.4RC2. So better count on translation finish in early to mid February (around RC1) for everything other than Release Notes.
1) Is there any suggestion about what program should we use for translating? I use gtranslator. Is there any much more popular among openSUSE members?
If you're happy with gtranslator then use that. Lokalize and POEdit are more popular I think. Personally I'm very happy with Lokalize. I think it's the only editor supporting the "diffs" for fuzzy strings, but I could be wrong. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Στις 23/12/2010 01:13 μμ, ο/η Martin Schlander έγραψε:
Tirsdag den 21. december 2010 14:37:40 skrev Kostas Boukouvalas:
Could information be provided about the openSUSE localization deadlines? Also because I'm not used to the new terms, how do we call this in the new decade? Translation Freeze? Is there any process the maintainer of a localization project for openSUSE distribution should know? There's not much you need to know. If you have the necessary permissions, just checkout from svn and translate like mad. Everything else is between you and your team.
Of course it helps to know the roadmap - http://en.opensuse.org/Roadmap - Particularly: Dec. 16: "hard text freeze" and Mar. 2: "Translation Finish".
Now, I'm pretty sure the finish date is a mistake. It might apply for Release Notes, but for stuff in the actual distro it seems unrealistic to have translation finish after 11.4RC2. So better count on translation finish in early to mid February (around RC1) for everything other than Release Notes.
1) Is there any suggestion about what program should we use for translating? I use gtranslator. Is there any much more popular among openSUSE members? If you're happy with gtranslator then use that. Lokalize and POEdit are more popular I think.
Personally I'm very happy with Lokalize. I think it's the only editor supporting the "diffs" for fuzzy strings, but I could be wrong.
Thank you also Martin for the answers. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Martin Schlander
Tirsdag den 21. december 2010 14:37:40 skrev Kostas Boukouvalas:
Could information be provided about the openSUSE localization deadlines? Also because I'm not used to the new terms, how do we call this in the new decade? Translation Freeze? Is there any process the maintainer of a localization project for openSUSE distribution should know?
There's not much you need to know. If you have the necessary permissions, just checkout from svn and translate like mad. Everything else is between you and your team.
Of course it helps to know the roadmap - http://en.opensuse.org/Roadmap - Particularly: Dec. 16: "hard text freeze" and Mar. 2: "Translation Finish".
Now, I'm pretty sure the finish date is a mistake. It might apply for Release Notes, but for stuff in the actual distro it seems unrealistic to have translation finish after 11.4RC2. So better count on translation finish in early to mid February (around RC1) for everything other than Release Notes.
At the moment, I do not have to time to do the usual localization coordination :-( All in all, this is not that much work, but I cannot promise anything. These steps are usually required (to the tough part always is to figure out when): 1/ Mail Jiri (jsrain at suse cz) to update yast pot files. 2/ Send reminders to the lcn software maintainers; there is a script: 50-tools/maintainer-reminder.sh 3/ Do the merging. I can help with this if needed. 4/ Keep the translators updated by sending mails to this list: opensuse-translation@opensuse.org I'll do my usual packaging (desktop-translations, yast2-trans, slideshow, release-notes, translation-update), if nobody else want to volunteer. -- 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
At the moment, I do not have to time to do the usual localization coordination :-( All in all, this is not that much work, but I cannot promise anything. These steps are usually required (to the tough part always is to figure out when):
1/ Mail Jiri (jsrain at suse cz) to update yast pot files.
2/ Send reminders to the lcn software maintainers; there is a script: 50-tools/maintainer-reminder.sh
3/ Do the merging. I can help with this if needed.
4/ Keep the translators updated by sending mails to this list: opensuse-translation@opensuse.org
I'll do my usual packaging (desktop-translations, yast2-trans, slideshow, release-notes, translation-update), if nobody else want to volunteer. Hi, Carl! If you need a hand of help I am ready to provide it =) I always wanted to document your workflow, but if I need to actually do
2011/1/14 Karl Eichwalder
Александр Мелентьев
Hi, Carl! If you need a hand of help I am ready to provide it =) I always wanted to document your workflow, but if I need to actually do the job, it's all right for me. I have some questions about more detailed description of needed work but we can discuss it personally, just drop me a line at minton@opensuse.org
Kálmán also offered help--thanks to both of you. Please coordinate your work somehow. Everything will be fine with me! :-) -- 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
participants (4)
-
Karl Eichwalder -
Kostas Boukouvalas -
Martin Schlander -
Александр Мелентьев