Ha, finally some (cautious) support for the en_GB file idea! I think the en_GB file on launchpad is ideally suited for contributing the better terms to. We only need to translate the awkward terms (if you use the en_GB file the system will fall back on the original term if there is no translation provided). You can then filter on translated terms in the web interface of Launchpad and see exactly which are the suggested better terms. So the domain experts can contribute right there and we have one central place where all the suggestions are collated (plus you can use them immediately if you so choose to). Terms that need discussion can be discussed on this forum or on the mailing list of the OpenERP terminology team.
Having the suggestions in the en_GB.po files will make it much easier to import the strings back into the code. The new terms are there side by side the original terms. It should not be hard to write a script to update all the original terms in the modules with the new terms with this file as input. Updating can be done several times, for different stages of maturity of the en_GB file. You don't need to use regular expressions as you have the exact strings. Granted, the internal names is a harder job, but this is really not so pressing as the interface problem. For that problem bug reports or blueprints are I guess more suitable. So now how to put the en_GB or en_US language files onto Launchpad? Would en_US also work? That would be preferable. -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=46080#46080 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
