[TYPO3-core] RFC: Templavoila feature

[Bernhard Kraft]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dmitry Dulepov wrote:

>>>But currently you do not see the translated content of FCE's. And it is
>>>also not possible to create translations of
>>>FCEs (meaning: insert a reference to them into the translated pages)
> 
> 
> This is not needed, FCEs are translated differently. You need to have
> <langDisable>0</langDisable> and you can translate fields inside the
> flexform.

I start to get angry. Dmitry. I use TV for almost 2 years now. I changed code in it
and it worked properly. I supplied patches which got incorporated into the new versions
and a lot of other stuff.

BELIEVE ME. I KNOW HOW FCEs WORK AND GET TRANSLATED.

I guess you didn't even try my patch nor even take a look on it. So how do you know
how it handles translation of FCEs ?

If you would have read correctly I wrote "insert a reference". Even when I did how you
wrote (have langDisable 0 - which is a must of course) and translate the fields inside
the flexform - then it still will not be inserted in the others language content-fields.

And THIS get's fixed (made possible) by this patch - if you click the "insert reference
for tranlsation" link just like with normal CE's the element get's inserted into the translated
language just that it DOESN'T get copied cause this is not required with FCE's as they have,
as you wrote, another way of getting translated.



greets,
Bernhard
- --
- ----------------------------------------------------------------------
"Freiheit ist immer auch die Freiheit des Andersdenkenden"
Rosa Luxemburg, 1871 - 1919
- ----------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEFYDKIl4dkVkDMFkRAjWsAJ9Rad9WaAhUDgZ0jXfMyTqpuBa19wCeNL9p
Zj2Avo5hKXVvMkaBubvzj4k=
=lupY
-----END PGP SIGNATURE-----