[TYPO3-templavoila] Continue f. t.team.core: Templavoila localization

[Kasper Skaarhoej]

> I think it is confusing that I can localize anything in the
> "localization disabled" mode. It simply does not sound right. If it is
> "disabled", I should not be able to localize. May be "disabled" is wrong
> name for this mode? Should be changed to "Container"?

You must understand that the localization mode of a container element be it 
the Page or any FCE on the page _only_ defines how the FlexForm structure can 
be localized or not.

It is therefore mistaken to assume that this should have any influence on 
whether the page in itself carries any localized content.

When I propose that all container elements should have localization mode set 
to "Disabled" (that is <langDisable>=1) it is because they represent 
_structure_ which in 99% of all cases is common to all translations of a 
page. Container elements are "universal"! In addition such an element is set 
to the "ALL" language so that this structure is used for any language.

What you _do_ want to translate is the "content carrying" content elements on 
the page (non-containers). They fall into two categories: 
- Normal content elements
- FCEs with values (not container fields)

For both types you can localize them using the cores "localize" command, thus 
creating a new copy which is referencing the original element

But for FCEs another option is to set the DS localization mode to 
"Inheritance" which allows you to localize each value in the FlexForm 
directly (and then you set the overall language of that element to "All" so 
that it is selected and rendered for any language).

Of course, this might sound as if it wouldn't work and that is mainly because 
people seems unfamiliar with the "config.sys_language_overlay=1" option which 
means that any default element that is asked to be rendered when another 
language is selected for display WILL only be rendered if there is a 
localization found (that overlays it!)

Dmitry and Bernhard, since you read the localization guide and this is still 
not clear to you it shows me that we must somehow work on improving my 
document to communicate this point. When at some point we are on the same 
page please think about how people with your "glasses on" can be made to 
understand it so I can improve that document.


> 
>> lDEF | field_content | vDEF => '123(EN),334(EN),456(DK),559(EN)',
> 
> Does not look right for me if it goes to flexform. vXX is for language,
> here we put other languages into default.

Bernhard is right here! Notice that lDEF and vDEF in this case represents a 
"universal" container element.


- kasper