Hello,
Don't ask me why Tiny is not using the channels they set up (if they
don't
use them it doesn't make too much sense to restrict them), but what
imports
is that they just gave official instructions on how to help translating
OpenERP in Launchpad,
please read here:
https://lists.launchpad.net/openerp-community/msg00004.html
I'm also quoting here the essential part of Olivier Dony's mail:
"
The global process is as follows:
* Trunk *
* In trunk, all translations are automatically synchronized between
LP's translation system and the various *.po files that are located in
the source code.
* Whenever someone commits a change to a .po file, LP sees it and
displays it, and whenever someone changes a translation via LP, it is
commited in bazaar per batch after a while.
* Translators can work term by term in LP, or download/upload multiple
terms at once in a .po format via LP too. The translation interface is
easy to locate, e.g
https://translations.launchpad.net/openobject-addons
* Access rights on translations changes and reviews via LP are given
via the various translation teams.
* LP requires PO files to be named with the language code by default,
so all PO were renamed accordingly e.g. from nl_NL.po to nl.po, so that
LP's commits go in the right files.
* When loading the translation for a language, OpenERP (trunk) will
try
to find a country-specific PO first (e.g. nl_NL.po) then fallback to
the
default language one (e.g. nl.po) if there is none. This is compatible
with LP's strategy and allows per-country specific translations.
* Stable *
* In stable, there is no automatic synchronisation of LP's
translations
with the *.po files, because it requires some core changes (partially
outlined above for trunk).
* Even without automatic sync, translations can still be done in LP's
translation interface, but the URL to access it is less obvious.
e.g:https://translations.launchpad.net/openobject-addons/5.0/+translations
* During the few months remaining for 5.0, the synchronization is thus
done manually by the Release Manager at Tiny. Before releasing a new
stable release, the Release Manager must import all LP translations and
commit them in stable. Fortunately this manual process will not be
needed as of 5.2.
* Translators can work in the same fashion as for trunk, term by term
or by .po files, and access rights on translations are managed in the
same way.
* OpenERP 5.0 requires PO files to be named using the full
language+country code (e.g. nl_NL.po), so the Release Manager imports
the updated translations in the correct files.
Finally, regarding the merge of translations between stable and trunk,
there is nothing available to do it automagically in LP. It must be
done
manually during the periodic merges that we perform from stable into
trunk.
However since the LP translation database is common between both,
appropriate suggestions should be displayed if a term has been
translated once (it should never be really lost). Perhaps it would be
possible to copy a batch of identical translations between stable and
trunk via import/export of PO files via LP's interface, but I haven't
tried it.
I hope this clarifies thing a little bit.
"
Raphaël Valyi
http://www.akretion.com
_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-localization
Post to : openerp-expert-localization@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openerp-expert-localization
More help : https://help.launchpad.net/ListHelp
