[TYPO3-dev] Localisatzion of Flexible Content Elements and Workspaces

[Daniel Pötzinger]

Use-Case:
-----------
Say you have a english page and two editors for the translation (lets 
say french and german)
* both want to translate independently and publish the changes independently
* therefore two seperate workspaces are created.

Problem:
---------
TemplaVoila and FCE have one disadvantage if you want to dial with the 
workspace features:
* It is not possible to work independently in two workspaces regarding:
	* adding new content elements
	* adding new translations

(This should both be possible in the classic templating concept.)

The reason is that for a translation no new database record is required 
for FCE - and therefore it results in a workspace conflict if two people 
want to translated content in two diffrent workspaces. (Because two 
seperate versions are created)

=>The later publishing wins and the translation is lost.

(The same is the case for simply adding new CE to a page in two 
workspaces: because the page itself needs to be versioned it results 
also in a conflict)


Idea (at least for translating):
------
1) kind of mergin for flexforms - but i think thats nearly impossible 
and will break with the versioning concept

2) Use the old classic overlay mode also for FCE: Means flexforms are 
not localised in the XML, but localised via a new overlay record. (Just 
as text / text w image elements)
Therefore I did like to introduce new meta setting for DS like:

<langDatabaseOverlay>1</langDatabaseOverlay>

What do you think?