[TYPO3-templavoila] Localization Guide

[Franz Koch]

> - as the 'new' way for localization also allows to create a independet
>   DS for a language, it'll be nice if the inheritance of CE-fields
>   (the merging-function) would also work the way I tried to use it, so
>   that directly fetched translated CEs can also inherit (like in my
>   wrong bug-report). I think this would be a nice feature and provide
>   more flexibility for inheritance. In this way a localized CE could
>   also act as source for merging.
> 
> - if there is a localized pageDS with content, it doesn't make sense to
>   display allready localized versions of a CE in the default language,
>   does it? Then it should also be restricted to create a localization
>   for a CE in the language in which the independent pageDS does exist as
>   it would be confusing if a record get's translated but is not showing
>   up in FE.
>   Alternatively the translated CE keeps showing in default language, but
>   get's inserted in the pageDS of the foreign language? But this might
>   be even more confusing to ediors

forget those two - I forgot to change my main pageDS.

But now I have a question. What is the suggested way to localize a page 
if the desired foreign language needs for some reason a completely 
different page-structure? Should in this case a pageTS with 
<langDisable>0</langDisable> be provided? Or should a dummy-page be 
used? But a dummy-page will also appear in the menu of the default 
language - if it is not excluded via conditions and TS - which is not 
acceptable.

-- 
Kind regards,
Franz Koch