Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 173 by khamenya: Basic support for multilingual content (Enhancement) http://code.google.com/p/django-hotclub/issues/detail?id=173
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/ -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pinax-updates" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pinax-updates?hl=en -~----------~----~----~----~------~----~------~--~---
