strings, small words, titles can be used with the T operator.... for full blown articles, posts, etc you can use T too, but if your website is basically content (posts, manuals, etc) it may be a lot easier to maintain a "default content" (file,db row, etc) and all the translations that, if not found, fall back to the "default english" content page.
On Thursday, November 15, 2012 8:26:02 PM UTC+1, David Sorrentino wrote: > > Hi folks! :) > > I am here for asking you an opinion. > Since I am developing a multilanguage website, I am wondering if there is > a best practice for managing the translation of the content. > I mean, now I added in my routers: > >> myapp = dict(languages=['en', 'it', 'pl'], default_language='en') >> >> so I have the chosen language in *request.uri_language* and I can force > the translation in every page. In my mind this applies well to the > translation of the interface, but when it comes to the content it means > that I have to write all the content of the pages in the dictionaries which > are in the folder *languages*. Is that correct? Or should I put the > content on txt files and select them in the controller on the basis of the > chosen language? How would you manage this? > > Thanks in advance for your precious opinions. > Cheers, > David > --
