Hey Niphlod, Thank you for replying.
I did understand that for the interface it's beneficial to use T. However I am not that sure I correctly understood your advice about the content like posts, manuals, etc. In practice you mean that I should have a default content and the respective translations on files, db row, etc, and read them according to the chosen language, right? Thanks one more time. Best, David On 15 November 2012 20:40, Niphlod <[email protected]> wrote: > 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 >> > -- > > > > --
