On Wed, May 20, 2009 at 8:33 PM, mdipierro <mdipie...@cs.depaul.edu> wrote: > I am not in favor of this because it mixes two different levels of > web2py that should be separate. The reason they should be separate is > that T is thought for static strings not for dynamic strings. You will > run into all kind of issues otherwise.
Hey! The patch that I sent (and is in 1.62) enable programmers to translate dynamic content. :-) One idea: store translation strings in DB. It needs a little modification in T and would be optional (default to file) - but it will help people running web2py on GAE. What do you think? -- Álvaro Justen Peta5 - Telecomunicações e Software Livre 21 3021-6001 / 9898-0141 http://www.peta5.com.br/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
