[TYPO3-templavoila] Localization Guide

[Franz Koch]

Hi Kasper,
> As you know some localization related concept has recently changed in  
> TemplaVoila (CVS). For some of you this means that your backend Page  
> module "breaks" according to how it worked before. I'm sorting out  with 
> Bernhard and Dmitry to introduce a configuration that can toggle  the 
> old behaviour.
> 
> In the meantime this document (below) is meant as the definitive  guide 
> to localization with TYPO3, including a large discussion about  how to 
> handle localization with FlexForms and TemplaVoila. The  blessings of 
> localization modes in FlexForms can also become a big  curse unless used 
> with care and this document is my general  suggestion for a path to 
> follow. It is also according to this  principle that TV will work in the 
> future.
> 
> http://194.117.233.66/t3dl/localization_guide_2.pdf

Thanks again, and thanks for the guide. It opened my eyes. I must
confess that on my setup I didn't really think about what I was actually
doing inside the TV-Datastructure as I'm not to familiar with
multilingual flexforms. I 'just' followed documentations and the
information found on the wiki.
Now I see that it was totally screwed up. The 'k'-way is definetly the
right way I think.

I finally managed to use CVS and just downloaded the lastest 
CVS-versions of TV and Typo3 and tested it with the suggested typo3-way 
for localization.

What I'm missing from a editors point of view:
- it should be possible to create a localization for
   shortcut-pages as they need translated titles for menus etc.
   Currently this feature is disabled in TV pagemodule and can only be
   done in list view as it seems.

- a 'show content in this language only' mode would be nice
   for 'master-editors' and admins. Not translated CEs from
   default-language could be displayed in a condensed mode - maybe also
   optional applied with a checkbox

- it'll be nice if the "hide" field would be selectable when editing
   the page-propierties on clicking the language-flages in TV.
   Or isn't this allready configurable somewhere? I can't remember.

- the selector-box "show page language version" is missleading as it
   is creating a new data-structure. Maybe a lable like
   "create independet page localization" or something like that would be
   more clearly.

- 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

- in the current version I'm missing the checkbox to enable/disable the
   localization view in the default language. Currently it is permanently
   enabled


-- 
Kind regards,
Franz Koch