Hi, Perhaps I am missing something, and at the risk of appearing stubborn, but I don't see what the problem could be with adding an English variant translation to have improved terms. Sure it is a workaround but at least is something we can start working on immediately in a convenient way and it solves the problem in the mean time. Translators to other languages can refer to this translation if an original term seems ambiguous. A permanent solution can then use the improved terms from this file in one way or the other.
So I would propose adding en_GB translations (or another English variant) to Launchpad. Only I am not yet sure how to go about it. Am I correct in assuming that it involves setting up a branch, adding the new language .po files to it, and submit it as blueprint for merging into the trunk? If accepted, it would then appear in Launchpad Translations automatically? Perhaps the branch can be owned by the OpenERP Terminology Team? In answer to the question of numerigraphe: yes, I do think the team should have a mailing list. -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=45993#45993 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
