Happy to see lots of good suggestions. Correcting a label (or message in gettext parlance) is indeed like a bug fix and we could use the bug reporting system for that. Only I am afraid that we will then have to report a lot of bugs in this way and the whole exercise perhaps becomes too scattered.
Creating a special branch is also a possibility but might be a bit too technical for some of us. Also there is the problem that apart from changing the message in the source code, all the translation files need to be updated every time. IMHO the suggestion of gegard is most practical. Create en_GB.po (or en_US.po if that works) files with the corrected terms as "translations". But this should be added to Launchpad Translations as well (the language is currently not available). In this way we can all contribute and collaborate in a convenient fashion. It has as an added advantage that the (intermediate) results are immediately available for use. You simply put your preferred language as en_GB (or en_US). We could create a translation team on Launchpad around that. Periodically, by using some script the trunk could be updated with the new labels or messages drawn from the 'translations' of this file in one go. After such an update the messages and 'translations' of the en_GB.po file should be the same. As one cannot conveniently discuss in Launchpad Translations perhaps we should have a dedicated terminology forum here. This forum could also be input for a Glossary which I agree with numerigraphe would be an useful and convenient addition to the documentation. I hope you can give feedback whether you think this is a practical approach, so if agreeable we can take it to the next level. -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=45967#45967 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
