That's correct gegard, best would be to have a process build in to check before release, but I guess that will not be feasible within typical OpenSource development as long as we make no use of business analysts that have a strong say while developing. Resulting in correction afterward. This is not only labels, but also wrongly named definitions and objects.
This means in practice refactoring the source code, generating updated pot files, update the po files for each language and translate the changes. Refactoring for server, addons, addons-extra, addons-community. We have to think about how we communicate changes to partners as they could have customizations that needs to be re-factored too. Nevertheless we need a list of used Awkward English to correct. This could be a blueprint, where we list all of them. And we need editor for merging the changes. If editor is not willing (perhaps for good reasons) to incorporate the changes then we don't have to start at all. Then we need a other discussion first [Wink] ------------------------ Jan www.veritos.nl www.supportandmaintenance.org -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=45979#45979 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
