Bug #93220
closed
German translation of "User XY started editing this site" contains HTML
0%
Description
The german translation of the label "The BE-User XY began to edit this record Z min ago." contains HTML output. Instead of the quotes, the html entity " ; is shown.
This works in several translations, but not for german.
Files
Updated by Philipp Kuhlmay almost 4 years ago
This neither works for TYPO3 10.4.9 nor for 10.4.12
Updated by Philipp Kuhlmay almost 4 years ago
This is related to https://forge.typo3.org/issues/88801
Updated by Georg Ringer almost 4 years ago
- Related to Bug #88801: Incorrect formatting of help text added
Updated by Georg Ringer almost 4 years ago
- Status changed from New to Needs Feedback
Did you reload the translations already in the Install Tool?
Updated by Philipp Kuhlmay almost 4 years ago
Georg Ringer wrote in #note-7:
Did you reload the translations already in the Install Tool?
Yes I reload the translation and cleared all caches.
We still have this issue in several installations of TYPO3 10.
I just realize that this issue is only inside an installation on an external webserver. Inside my local DDEV installation it works.
I have this inside the labels files:
DDEV : /var/labels/de/core/Resources/Private/Language/de.locallang_core.xlf
<trans-unit id="labels.lockedRecord" resname="labels.lockedRecord" approved="yes"> <source>The user '%s' began to edit this record %s ago.</source> <target state="final">Der Benutzer '%s' hat mit der Bearbeitung dieses Datensatzes vor %s begonnen.</target> </trans-unit>
Webserver: /var/labels/de/core/Resources/Private/Language/de.locallang_core.xlf
<trans-unit id="labels.lockedRecord" resname="labels.lockedRecord" approved="yes"> <source>The user '%s' began to edit this record %s ago.</source> <target state="final">Der Benutzer "%s" hat mit der Bearbeitung dieses Datensatzes vor %s begonnen.</target> </trans-unit>
DDEV has single quotes and webserver has double quotes. Maybe its only an issue with my webserver but it is still strange.
Updated by Benni Mack about 1 year ago
can you recheck this with v11/v12 and the updated language packs?
Updated by Philipp Kuhlmay 8 months ago
I don't get this error in TYPO3 11.5.36 and 12.4.12. So this seems to be fixed and therefore can be closed.
I haven't tested it in TYPO3 10 because I have no current installation to test at the moment.
Updated by Riccardo De Contardi 8 months ago
- Status changed from Needs Feedback to Closed
@Philipp Kuhlmay thank you for your quick answer. I close this issue for now as it seems solved on recent TYPO3 installation .
If you think that this is the wrong decision or experience the issue again or think that there is still work to be done here, please open a new issue with a reference to this one. Thank you.