[TYPO3-core] RFC: css_styled_content & localization

Bernhard Kraft kraftb at kraftb.at
Mon Jul 31 16:18:50 CEST 2006

Hash: SHA1

Michael Stucki wrote:

> Since you will never know which element is referenced by the user, I think
> the most proper solution is to add additional anchors for each translation
> of a record, e.g.
> <a id="c1"></a><a id="c2"></a><a id="c3"></a>
> This is the record with UID 1, translations at UID 2 and 3.
> Might be tricky to implement in TypoScript... :-)

Easy goin'

  innerWrap2 = | <p class="csc-linkToTop"><a href="#">{LLL:EXT:css_styled_content/pi1/locallang.php:label.toTop}</a></p>
  innerWrap2.insertData = 1
  innerWrap2.fieldRequired = linkToTop

# like before:
  dataWrap = <a id="c{field:uid}"></a> |

# new code:
  prepend = TEXT
  prepend.dataWrap = <a id="c{field:_LOCALIZED_UID}"></a>
  prepend.if.isTrue.field = _LOCALIZED_UID

The new code will "prepend" the cObject which is defined. "prepend" happens in stdWrap directly after dataWrap
so the localized-uid anchor will be before the original one.

In my opinion the most clean solution cause if a _LOCALIZED_UID field is available it works either if the
editor has set the link to the original content element or to the translated one - i think both should work
but it can happen both - a editor creates a text element and links to another content element - the CE get's
translated and the translator just replaces the link text but does not "reset" the link to the translated
CE. Another Editor might think it is clever to set it to the translated.

- --
- ----------------------------------------------------------------------
"Freiheit ist immer auch die Freiheit des Andersdenkenden"
Rosa Luxemburg, 1871 - 1919
- ----------------------------------------------------------------------
[[ http://think-open.at | Open source company ]]
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


More information about the TYPO3-team-core mailing list