[TYPO3-english] SOLVED (almost) No 'nice text' rendering + GMENU for multilanguage is NOT working ok

[JoH asenau]

>>> It works fine, even if I do not like it, I think I should not need
>>> to add the sys_language_uid = 0.
>>
>> You don't have to :-)
>>
>> select.languageField = sys_language_uid
>>
>> should do the job
>
> yes, it does and it is better. Thanks.
>
> However, my point is that we should not need either solution, since TS
> includes:
>
> config.sys_language_uid = 0
> config.language = it
> config.linkVars = L
>
> [globalVar = GP:L=1]
>  config {
>  sys_language_uid = 1 <<<<< it should be enough, shouldn't?
>  language = en
>  }
> [global]
>
> config.sys_language_overlay = 1
> config.sys_language_mode = content_fallback;0
> -----------
>
> Most likely, I am missing something on how the core code is working
> here.

config.sys_language_uid = 1

This will just trigger the language overlay for pages.
Since you might be using different extensions than CSS-styled-content and
you are able to even use a completely different table for content elements,
the core just can't know in advance which mechanism to use to get the
records in the desired language.

TypoScript is not restricted to the output of tt_content and can be used
with different extensions, different tables and even a different database
could be possible.

Even while using CSS-styled-content you might want records with different
languages on one page.
i.e. showing the original default language and the translation side by side.

There are many other possibilities to use a field other than
sys_language_uid for language selection.

This is why you have to tell the core how to handle this.

HTH

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your gob sometimes!)
Dieter Nuhr, German comedian
Xing: http://contact.cybercraft.de
Twitter: http://twitter.com/bunnyfield
TYPO3 cookbook (2nd edition): http://www.typo3experts.com
TYPO3 workshops: http://workshops.eqony.com