Issue Bug Closed

#91197[BE lang: NL and language files up to date] HTML-markup visible in Systeminformation-Dropdown instead of links

Leonie Philine 04/25/20, 22:15 updated 05/25/24, 15:46

Description

Same as in https://forge.typo3.org/issues/90657 but NL instead of DE, and all language files updated (via the Maintenance module).

Updating the language files had been the fix for #90657 for German language – maybe for Dutch there’s a different issue.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 1

History 4

  1. Georg Ringer changed status New Accepted assigned to Georg Ringer 04/26/20, 07:13

  2. Leonie Philine commented 05/14/20, 05:46

    Excerpt from var/labels/nl/backend/Resources/Private/Language/nl.locallang.xlf:

          <trans-unit id="systemmessage.intro" resname="systemmessage.intro" approved="yes">
            <source><![CDATA[This is a short system overview. For advanced information please head to the <a href="%s">Environment Module</a>.]]></source>
            <target state="final"><![CDATA[Dit is een kort overzicht van het systeem. Voor uitgebreide informatie kan in de &lt;a href="%s"&gt;module Omgeving&lt;/a&gt; gekeken worden.]]></target>
          </trans-unit>

    The htmlentities + CDATA combination breaks the Dutch translation in TYPO3 10 LTS.

    Next to this example string, also the “You have errors in your error log” string is broken:

    var/labels/nl/belog/Resources/Private/Language/nl.locallang.xlf

          <trans-unit id="systemmessage.errorsInPeriod" resname="systemmessage.errorsInPeriod" approved="yes">
            <source><![CDATA[We have found %1$d errors. Please check your <a href="%2$s">system log</a>.]]></source>
            <target state="final"><![CDATA[%1$d fouten gevonden. Controleer het &lt;a href="%2$s"&gt;Logboek&lt;/a&gt;.]]></target>
          </trans-unit>
  3. Georg Ringer changed Related to #90657 05/25/24, 15:46

  4. Georg Ringer commented and changed status Accepted Closed 05/25/24, 15:46

    imo this is fixed, therefore closing the issue. if still relevant, please open a new issue or get in contact with me via slack