bhikkhu wrote: > ... Once the en_GB.po file is finished... I don't think that it is as simple as this. A year or so ago I had access to the source code and updated all the English terms. This year, unsuitable terms have again permeated the whole code base.
So it's an issue of process, not just content once off. We need to have a way to update all of the English terminology continuously. So we could a) update everything just before a release (which risks the 'stable' branch becoming un-English between releases), or b) insert a 'proofing' stage in the process before each update (which risks delaying every fault fix) or ... ? ------------------------ Regards, Geoff Seath Solutions Ltd (http://www.seathsolutions.com) -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=45976#45976 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
