[TYPO3-50-general] Typo3 5 and Multilanguage-Support

Robert Lemke robert at typo3.org
Wed Feb 11 09:58:23 CET 2009

Hi Andreas,

I'll have to keep my answer a bit short, so:

yes, we have thought about the multilanguage support in TYPO3 v5.  
Because we are currently working on other parts, I'd like to postpone  
this topic a bit, but here are some general ideas already:

  - there's no "default" language anymore
  - we use the CLDR for proper locale support (http://www.unicode.org/cldr/ 
  - in trees we distinguish between the structure and contents  
attached to structure nodes: gives us all the flexibility of  
TemplaVoila but with less complexity
  - there will be a dedicated module for translation
  - we'll support plural forms and other niceties

We haven't discussed user rights yet, but that'll surely be a topic  
once we're at it.


Am 10.02.2009 um 19:11 schrieb Andreas Prucha:

> First Hi to everybody - I am new on this list.
> I hope I am on the right place to make my comments:
> During my last T3-Project I ran into several problems with  
> multilanguage-support in T3. Primarily the problem was, that the  
> site could not be strictly single-tree because local departments of  
> the company wanted to maintain special pages. But since the majority  
> of the pages were common pages, maintaining multiple tress was also  
> not the right approach.
> Are there plans for changes of the concept of multilanguage-support  
> in T35? If yes, are there already some ideas?
> My primary issues with the current concept are:
> - Default Language.
> I'd hope that we could get rid of the "Default" language, in order  
> to bring all languages on an equal level. Definition of a default or  
> fallback-language could be done by configuration. (I had the problem  
> that a customer first wanted German as default langauge against my  
> recommendation, but later notified that English would be a better  
> idea).
> - User Access Rights
> At the moment, a user may access data of a specific language, or  
> not. If the user may access Default language, he can also edit it.  
> If he does not have the right, he cannot create a a new local page  
> because there is no page in the Default language. Getting rid of the  
> "Default language"-concept would also solve this problem. But  
> independend of this, it would be nice if access rights could be fine- 
> tuned, giving a user right to *read* data of a specific language  
> (including the right to translate from it), or to edit data of a  
> specific language.
> I have a few more ideas about multilanguage-support, but these are  
> my primary wishes. What do you guys think?
> Andreas
> -- 
> Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL
> für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/? 
> ac=OM.AD.PD003K11308T4569a
> _______________________________________________
> TYPO3-project-5_0-general mailing list
> TYPO3-project-5_0-general at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-5_0-general

More information about the TYPO3-project-5_0-general mailing list