Your layout .../en/about ... seems very logical to me. I would go with that.
As far as translating longer blocks of text such as a blog entry, why not use a language indicator in your database table for each entry. For example lang == en title == 'My title' blog_entry == my entry then for another language lang == fr title == sujet ici blog_entry == mes choose, mais, en francais... C. On Fri, Dec 14, 2012 at 7:59 AM, <[email protected]> wrote: > суббота, 18 апреля 2009 г., 16:14:30 UTC+5 пользователь jiri написал: >> >> Hello, >> >> I am new to web2py and I am working on multi-language site using this >> framework. What is the best way to structure URLs for such site? >> Previously I used this scheme (see below) in Pylons framework, it was >> mapped using routing module to "lang" parameter and then correct >> language was set up just before selected controller function (by URL) >> was called. What I need to do to use this scheme in web2py or what is >> the recommended way to do this? >> >> /en/about/ >> /en/products/ >> ... >> /de/about/ >> /de/products/ >> ... >> /es/about/ >> /es/products/ >> ... >> >> >> Jiri >> > > I also faced such problem. > "T" is not very suitable loya large text (blogs). > Tell us how you coped with this challenge? > This question is very important for me. > > Or do you still have done all through the "T" and used a database for save > large texts. > Can lay out in detail how to multilaguage site. > > ps > I'm new to python and web2py, not much kick :) > and my english is not very > > -- > > > > -- Christopher Steel www.chrissteel.com * * --
