Basic support for multilingual content (Enhancement)

[GoogleCodeExporter]

1. Add-value: 

 * much broader target audience
 * indeed unique feature popping up Pinax in global web-community
 * more users and developer will be attracted to Pinax

2. Reasoning: 

  * more than 50% people understand more than 1 language (see http://en.wikipedia.org/wiki/Multilingualism#cite_note-0)

  * real deficit of multilingual platforms (neither blogs nor forums nor 
CMS!)

  * basic support for this is not expected to take many hours from pinax 
dev team, but will allow the developers using Pinax to make their 
customizations over Pinax easily.

3. Driving requirements:

  R1: allow user to specify the languages the user can read in (see coment 
below)

  R2: allow any content entry to have its translations 

  R3: allow to specify an origin (primary) language for a content entry 
represented in more than 1 language

  R4: allow to list all languages a content entry is available in.

These are indeed basis. Most of these requirements result in changes in 
data model. 

R1 could be even considered as already "done". Indeed, web-browsers allow 
to set content languages with priorities and this feature could naturally be 
re-used. Django has a good use of it already. If these four requirements 
are not accepted then developers making their websites based on Pinax will 
hardly try to get the multilingual feature on their own. Indeed, every 
version upgrade of Pinax may put these heroes into a trouble of getting DB 
inconsistent.

The following requirements rely on the above ones:

  R10: allow user filter out content they can't read in

  R11: allow the automated language detection to set the language of 
entered content automatically 

  R12: allow user to add translations to the content entries

  R13: autodetect user's language preferences and automatically show 
content in languages user can read in.

  R14: allow user to see by default the content entry in its primary 
language if it belongs to the languages user do understand, even if there 
are translations already in more preferred languages. (Personally, I never 
read Russian translations for the articles initially written in English 
although Russian is my mother-tongue and is far better then English)

noteworthly, R10-R14 need no changes to the data model. These requirements 
could be considered as "do it on your own" before Pinax team has time to 
get them in focus.

Personally for me the urgency for this enhancement is "High".

See also:
http://cloud27.com/tribes/tribe/multilinguals/

Original issue reported on code.google.com by khame...@gmail.com on 3 Feb 2009 at 11:53

[GoogleCodeExporter]

if you like this feature please 

1. star it
2. leave "+1" in comments below

thanks!

Original comment by khame...@gmail.com on 3 Feb 2009 at 12:09

[GoogleCodeExporter]

such a feature *is a must*, therefore, +1

Original comment by rocket.m...@gmail.com on 26 Feb 2009 at 3:14

[GoogleCodeExporter]

It will be great, very useful feature of pinax, +1

Original comment by dio...@gmail.com on 9 Mar 2009 at 7:28

[GoogleCodeExporter]

+1, such enhancement will be highly useful

Original comment by inot...@gmail.com on 11 Mar 2009 at 11:52

[GoogleCodeExporter]

Original comment by pyDanny on 13 Mar 2009 at 4:31

• Added labels: Milestone-0.8

[GoogleCodeExporter]

wow... does it mean version 0.8 will address this?!..

Original comment by khame...@gmail.com on 13 Mar 2009 at 5:25

[GoogleCodeExporter]

Original comment by leidel on 13 Mar 2009 at 9:06

• Added labels: Milestone-Post-0.7

[GoogleCodeExporter]

@khamenya Since the milestone was just meant for issue cleanup I changed the 
milestone name to post-0.7. 
Nevertheless I'm certain multilingual content would be a good future 
enhancement. In fact there was an 
interesting discussion about creating a Django app that is able to add 
multilingual features to existing apps.

http://groups.google.com/group/django-multilingual/browse_frm/thread/2fab1d16740
90079

Original comment by leidel on 13 Mar 2009 at 9:21

[GoogleCodeExporter]

@leidel, does Post-0.7 means "after 0.7"? When could one expect this feature to 
be released or at least be usable from trunk?

Also could anyone update Roadmap, please? It says 0.7 is about to appear in 
February 
:)

http://code.google.com/p/django-hotclub/wiki/RoadMap

Original comment by khame...@gmail.com on 15 Mar 2009 at 10:49

[GoogleCodeExporter]

@khamenya Yes, Post-0.7 means after 0.7. We don't have an estimate for that 
particular feature given its 
complex nature. Any contributions are welcome :)

Thanks, we'll update the roadmap soon.

Original comment by leidel on 15 Mar 2009 at 11:21

• Changed state: Accepted
• Added labels: Type-Enhancement, Priority-Low
• Removed labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

When Russian will be added as one of the choices on Clouds27 ? 

Original comment by vinej...@gmail.com on 24 Apr 2009 at 1:34

[GoogleCodeExporter]

@vinejara, Russian should be first added to clouds27' platform, namelly to 
Pinax.

Original comment by khame...@gmail.com on 24 Apr 2009 at 2:57