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

Dmitry Dulepov typo3 at fm-world.ru
Thu Mar 16 07:50:10 CET 2006


Hi!

Bernhard Kraft wrote:
> The thread continues ...

For those who do not understand what goes on - there were big changes in
recent TV version in CVS. They affect how localization works. In
general, they can make existing sites behave completely different after
new version is taken from CVS. However this is not fatal because proper
behaviour can be achieved with one of three combinations of langDisable
and langChildren parameters.

> I think the switch for this should be langDisabel 0/1 ... where 1=kaspers version and
> 0 = robert's version (i think robert has meant langDisable=1 only when no translation
> shall happen)

This is what I though too. If I understood Kasper correctly, this is
wrong. Page localization depends only and only on the existence of
"Alternative page language" records. There is no way to prevent page
from being translated.

langDisable=1 now means that corresponding _element_ cannot be
localized. After playing yesterday with TV I did not really understand this.

I had langDisable set to 0 and langChildren to 1 in my page template
(so, it is "Inheritance" mode). Previously I could localize content
elements on this page just fine. They were visible on localized pages.

Now they are not visible in such mode but if I remove langChildren and
set langDisable to 1, this behaves exactly like old settings (but for
unknown reason it is now called "Disabled" mode).

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"?

> 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.

Also Kasper wrote his reason to disagree: this will not ensure proper
order of translated elements... Personally I do not see it important, I
think localizaed elements should only be _created_ in proper order but
Kasper thinks they always should in sync.

Dmitry.
-- 
"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)



More information about the TYPO3-project-templavoila mailing list