2011/5/19 Massimo Di Pierro <[email protected]> > I am for this and for Jonathan idea. I am a little worried about the > level of complexity this may bring, so I would like to see an > implementation before committing to it. Too many file look-ups could > cause a slow down. >
This stress seems to hide a deeper problem: the lack of automated tests. Personally, and others are too, I am not very satisfy with what web2py has to offer for testing purposes. It an issue I want to explore further before committing other developments. I believe that a good layer of tests would remove a lot a stress when developers are re-factoring the code. It will ensure a smooth evolution with web2py, improve the design and the quality of its implementation. Has for the problem of speed, we can cache things in memory. But I think the first problem to deal with is the stress of re-factoring. > > About Jonathan proposal. It is ok to have a set of global translations > but we need to brainstorm it more. > Should global translations just stay global or propagate to apps? > What if the translation changes in global but not in local app? > I have some second thought on Jonathan proposal. I have some concerns: - By nature, a change in the global dictionary may affect many applications; - A single word in English may have to be translated in many different words in another language; - Once we are commited to support a language, if you add a new word, we must add the word in all the languages supported; - How do we deal with a word that would not be appropriate for a sub-dialect? I think the risks are important. I might not be a very good idea after all. 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>
