I think it would be a good default for when a new language file is created On Dec 1, 12:22 pm, villas <villa...@gmail.com> wrote: > You mean it would iterate through all the T strings for any chosen > languages. That would be great! > > I guess the result would not always be an appropriate or good > translation, but at least it would be a head start. Especially where > someone knows enough of a language to spot any serious mis- > translations. > > Please let us know, if you ever get it working. Thanks. > > On Nov 23, 9:53 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > > > I am doing a case study on determining the viability for integrating google > > translate into web2py. > > > I would like any input or ideas from the community, currently my line of > > thinking is to have a controller that will post queries to googles translate > > form, and then place the results in the languages/...py files. > > > Google also has the following, javascript page translator. There is a little > > lag as google translates the page, however everything seems to work > > perfectly after the fact. Any reasons for not including this in your page? > > How does it effect international users to your site, would they appreciate > > it or hate it? > > >http://translate.google.com/translate_tools > > > -Thadeus
-- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@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.