[TYPO3-irre] RFC #6087: Localization of child records with IRRE

[Steffen Kamper]

Hi Olly,

first - great that you take care of this really complex issue.

some additional hints:
 * when automatic create translations they have to be hidden first because 
they have to be proofed by an editor
 * if parent has 3 translations, all 3 translations of childs should be 
created. If they are hidden it should be no problem
 * possible delete of single translation
 * may be there could be a selector to view a selected language with quick 
edit setting and hiding/unhiding

I know this is easy to say and hard to code, but user doesn't care, they 
want to handle it as quick and easy as possible :-)

vg  Steffen

"Oliver Hader" <oh at inpublica.de> schrieb im Newsbeitrag 
news:mailman.1.1200926667.17504.typo3-project-irre at lists.netfielders.de...
> Hi Georg,
>
> Georg Ringer schrieb:
>> thanks a lot for opening this thread and for restarting the whole topic 
>> because it is a real important one!
>
> Thanks for your feedback! I'd like to create a broad feature which is not 
> only for my own purpose or that of my customers.
>
>> As I already wrote in the bugtracker: I am using the patch of Bernhard 
>> which is (out of an administrators view) nearly perfect and your ideas 
>> make it 100% perfect!
>>
>> I guess the most important mode would be "select". Where will the icons 
>> be to translate a record?
>> I guess it would behave like this: You translate the parent record in the 
>> list view and you get the parend record already localized. The child 
>> records are still in the default language and there is one button/link 
>> "Translate all" (like the "Copy all content elements" in page view) but 
>> where is the link to translate a single child?
>> - An additional icon next to move/delete/hide/... ?
>> - Another possible way: Open the default child record and use the 
>> language dropdown there (?)
>
> Yes, I had a similar intention and it could be somehow be compared to the 
> language view of pages with the "Copy default content elements". I can 
> imagine the following:
> * global button for all children of an IRRE parent: "localize all"
> * an additional button next to move/hide/... "localize this record"
>
>> I like the first idea better but this won't work if you got many 
>> languages in the BE because you would see many flags.
>
> In the IRRE view (editing a parent record) there will only be one language 
> that could be used for localization. If the parent was translated to 
> German, also the child records have to be German.
>
> What is your feeling about the 1:1 translation? Let's call it 
> "synchronized localization". What would you expect in this case?
> * different sorting of children in the different languages
> * what should happen if the parent record of the default language got a 
> new child record - should all localized versions get this new record 
> automatically or by a user action (e.g. clicking on icon "synchronize")?
> * the same is question for deletion of a child record
>
> Maybe these automatically created records should be set to hidden by 
> default since it could lead to some confusion when editing live content.
>
> olly
> -- 
> Oliver Hader
> http://inpublica.de/