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.
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? On May 17, 11:17 pm, pierreth <[email protected]> wrote: > On 17 mai, 23:46, Massimo Di Pierro <[email protected]> > wrote: > > > +1 for this. I would take a patch. ;-) > > +1 for this one too? : > > > The second thing that I propose is that web2py put the term is unable > > to translate in other files like "missing-translations-fr.py". Right > > now, web2py adds these translation automatically in the file related > > to T.accepted_language. It does so whiteout even adding a comment so > > it is difficult for translators to know that the translation is coming > > from web2py. The "missing-translations-xx.py" would only exist for > > main languages like 'fr' but not for 'fr-ca' or 'fr-fr'. Web2py would > > automatically consider the main language if this one is missing from > > the request by appending the main language if needed to follow more > > specific languages (for example, imagine a request accepting fr-ca but > > not fr, web2py would add fr after fr-ca). > > And for Jonathan's idea? It seems to be a very good idea for me. > > Any way, this time I'll try to be test driven. I was lazy on that with > my last patches.
