You made good points. I think that it is important to have a process that can support the community we are.
Here is my last idea on the subject: We can support a global translation repository just like Jonathan was proposing. But if an application has not for example a custom dictionary for German, then web2py will not continue its search to try to get another translation in the global repository. Also, when a new application is created with the web interface, web2py will ask what are the languages to be available for the new app. This will avoid trailing dictionaries. This way of doing will avoid partial translations where only a word up and there is translated. Instead, there will be no translation at all and I think this is a lot nicer. Sounds good? A+ ------------- Pierre My blog and profile (http://pierrethibault.posterous.com)<http://pierrethibault.posterous.com> YouTube page (http://www.youtube.com/user/tubetib)<http://www.youtube.com/user/tubetib> Twitter (http://twitter.com/pierreth2) <http://twitter.com/pierreth2>
