[TYPO3-dev] Proposal: Advanced Language Settings

[Daniel Pötzinger]

Hello Dimitry

Thanks for your comments.

Idea in general is to have a better maintainable and flexible concept in 
general. I know that some of this requirements can be achived by the use 
of conditions. But I think you agree that there are better maintainable 
ways - and also there are requirements which cannot be achieved.


> Hi!
> 
> Some thoughts/comments.
> 
> Daniel Pötzinger wrote:
>> .    General Localisation and Fallback feautures. (one-tree)
>> .    If there is no translation for Australia the webpage should 
>> fallback to English (default language)
> 
> Possible
> 
>> .    If there is no translation for germany -- the page and also non 
>> translated CE should not be shown.
> 
> Possible with TS conditions
Yes and No:
for pages: ok - with the not so nice errormessage
for tt_content: not for FCE. (they have language setting "all" and DS 
behaviour 0-1)


> 
>> .    If there is no translation for Spanish -- the translation for 
>> mexico should be shown. Means a fallback to language mexico.
> 
> Not sure if possible
Should not be possible, there is a patch in bugtracker with possibility 
for that.


> 
>> .    The translator should be able to explicitly hide or show a 
>> certain CE or page.
>> .    The translator should be possible to explicitly create a page 
>> which is only visible in his language
> 
> These two go against current concept where translator is a technical 
> figure only. I am not saying this is good but you have to consult 
> Kasper's opinion about it. He invented the concept.
yep the translator concept - but in real world its not always 
practicable. Of course there should be the limitation that new created 
elements are only visible in the certain language and not in default.


> 
>> .    Fallback and visibility behaviour can only be set global and 
>> therefore not for certain CE or pages
> 
> They can be set for pages using TS conditions.
Well this is not practicable for editors, and not possible on a CE basis.

> 
>> .    Different global language settings on a per language basis in 
>> nearly impossible.
> 
> Possible using TS conditions?
ok for most cases.

> 
>> .    Define the fallbackorder: Means to define which is the 
>> alternative language that should be shown in the case an element is 
>> not available in this language.
>> .    Fallbackorder can be more than one language. It can also include 
>> the default language or not.
>> .    Define the default setting for new elements (pages and CE)
> 
> This all must work with standard templating and both templavoila 
> localization concepts. Quite difficult I think...
Yep :-(

I know the function like "filterMenuPages"
Is there something similear (hook) for tt_content elements? A way to 
have a function which can decide if a content element should be shown in FE.



>