openerp-russian team mailing list archive

[Станислав Ханжин <hanzhin.stas@xxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



- -------- Исходное сообщение --------
Тема: Re: Russian language translators team
Дата: Tue, 22 Feb 2011 13:53:49 +0100
От: Olivier Dony <odo@xxxxxxxxxxx>
Организация: OpenERP s.a.
Кому: Stanislav Hanzhin <hanzhin.stas@xxxxxxxxx>

Le 18/02/11 18:18, Stanislav Hanzhin a écrit :
> https://launchpad.net/~openerp-i18n-ru - Russian subteam to translate
> OpenERP and docs to russian.


привет Станислав,

Sorry for the delay, I am not always able to process these requests in
real-time, as I am also working in OpenERP R&D department.
It is always a pleasure to welcome new contributors and translators to
the OpenERP Community! :-)

I have now assigned your team as the official russion translator team
for OpenERP.

Please keep in mind a few things related to translation teams and
translations, if you aren't aware of them already:

1. Community translations are now restricted
Assigning a translation team to a language restricts the power of other
community translators, because they can only make suggestions if they
are not part of the translation team. As a result, translations teams
should pay attention to suggested translations from the community,
review them regularly via Rosetta's interface, and propose to new
translators to join the translation team.
I see that you are already working in coordination with other members of
the openerp-russian, which is great!


2. Coordination and organization is important
Translating OpenERP completely is a huge task, as there are literally
thousands of terms to translate, and the quality of the final result
depends greatly on the collaborative work of the translators. It is
usually a good idea to ask translators to read the Launchpad Rosetta
guidelines for translators, as well as the OpenERP translation
documentation, for starters:
- - http://doc.openerp.com/contribute/07_improving_translations.html
- - https://help.launchpad.net/Translations
- - https://help.launchpad.net/Translations/StartingToTranslate
- - https://answers.launchpad.net/rosetta/+faqs

3. A glossary could improve quality and consistency
A very useful thing to do is to start writing a common glossary of the
specific OpenERP terms in russion. For example, how have you decided to
translate "Manufacturing" and "Production", and what is the difference?
How do you translate "Fiscal Position", a term not commonly encountered
outside of OpenERP? You could use a simple wiki page to maintain this
glossary, and put the link in the description of your translation team,
so new translators can find it easily.
You can also send me a link to post on the list of translation teams as
your official guidelines.

4. There are multiple branches of OpenERP!
Currently we have 5.0, 6.0 and trunk (the future 6.1) branches, and each
has its own set of translations.
For example for addons:
- - trunk:
https://translations.launchpad.net/openobject-addons/trunk/+lang/ru/
- - 6.0: https://translations.launchpad.net/openobject-addons/6.0/+lang/ru/
- - 5.0: https://translations.launchpad.net/openobject-addons/5.0/+lang/ru/

Our translation system does not allow us to automatically copy
translations from branch to branch, so you should be careful where you
translate.

We are trying to provide tools for helping copying and merging the
translations, but at the moment it is important to pick the right branch
to translate. For example choose 6.0 if you want your translations to be
published in the upcoming 6.0.2 version.
You could also work with PO files directly and upload them in 6.0 and
trunk both using the "Upload translation" button that appears on top of
each module's translations.
For example for "account" in "trunk":
https://translations.launchpad.net/openobject-addons/trunk/+pots/account/ru/+translate
This will work for 6.0 and trunk which are quite similar, but for 5.0
distinct translations are needed, as the terms to translate are too
different.

Do not hesitate to contact me for any further question...

Thank you for helping make OpenERP better for everyone!


- -- 
Olivier Dony
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iF4EAREIAAYFAk1js3sACgkQYiKkMJsRUdu2IAD8CAsMYLd1qrHmkePT3PMERoSO
nL6YHAyzW4vYwDM3afwA/11UL/v+6PGVO8OOTtvRtdNu4V7Cw+bG/aUlXAb6tWZj
=2kJK
-----END PGP SIGNATURE-----