Add i18n support

[GoogleCodeExporter]

Potentially we could enable editors to specify names, titles, and content
in different languages and then show users different versions, based on a
setting stored in UserProfile.  This would require considerable changes to
the datastore and the page editing UI.

Perhaps in the short term we could add a link to translate the page to
another language.  I think this would have to be done with JavaScript
unless the google translate proxy can somehow forward authenticated user
requests (unlikely).

Original issue reported on code.google.com by James.Bo...@gmail.com on 6 Oct 2008 at 3:12

[GoogleCodeExporter]

Original comment by James.Bo...@gmail.com on 16 Oct 2008 at 6:46

[GoogleCodeExporter]

Implementation Proposal:

The i18n Django template extension you can load/use in combination with the {% 
trans 
"blah" %} to translate (only) the UI of the app. Unfortunately App Engine does 
not 
support a dynamic (on request) language switch yet: 
http://groups.google.com/group/google-appengine/msg/9b5e08db8e266890

A certain language version of a page can be retrieved by appending a "?
lang=xx_lang_code" suffix to the request.

For both translation approaches you can retrieve the preferred user language 
from 
user's "Accept-Language" browser header.

Original comment by nistem on 5 Feb 2009 at 10:18

[GoogleCodeExporter]

I am also interested in such functionality. IMO, the workaround is not a good 
option.
A true, internationalised CMS is what will make a difference. AFAIK, as of 
today, the
only free CMS to offer this is Joomla (the JoomFish plugin).

Original comment by pavel.ge...@gmail.com on 24 Aug 2009 at 5:15

[GoogleCodeExporter]

didn't suppot gb2312 encoding

Original comment by imaa...@gmail.com on 23 Nov 2010 at 8:59