#105816Labels in EXT:lowlevel are broken in french
Description
Because htmlspecialchars is applied on labels in the backend module of the EXT:lowlevel, the labels are broken in french :
clipboard-202412121025-7frys.png
To avoid this bug, htmlspecialchars($label) must be changed to htmlspecialchars($label, ENT_COMPAT, ‘UTF-8’, false).
Thanks
Reviews 3
Related issues 1
Files 1
History 58
-
Xavier Perseguers commented <span data-processor="relativetime" data-value="2024-12-12T13:27:37+00:00" > 12/12/24, 13:27 </span>
-
Eric Chavaillaz commented <span data-processor="relativetime" data-value="2024-12-12T13:31:38+00:00" > 12/12/24, 13:31 </span>
There is no double encoding, the method use “htmlspecialchars” on the known method of the core “sL”.
-
Gerrit Code Review pushed patch set 1 for main to change 87470 status
NewUnder Review <span data-processor="relativetime" data-value="2024-12-12T13:34:28+00:00" > 12/12/24, 13:34 </span> -
Gerrit Code Review pushed patch set 1 for 13.4 to change 87493 <span data-processor="relativetime" data-value="2024-12-15T17:48:29+00:00" > 12/15/24, 17:48 </span>
-
Gerrit Code Review pushed patch set 1 for 12.4 to change 87494 <span data-processor="relativetime" data-value="2024-12-15T17:48:38+00:00" > 12/15/24, 17:48 </span>
-
Georg Ringer commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2024-12-15T17:50:12+00:00" > 12/15/24, 17:50 </span>Applied in changeset commit:3374dee67b3d78498dc57fb6f2632b289a2c6a28.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-08-12T14:36:30+00:00" > 08/12/25, 14:36 </span> -
Benoit Chenu changed Related to #107531 <span data-processor="relativetime" data-value="2025-09-24T12:28:57+00:00" > 09/24/25, 12:28 </span>
The corresponding label is found on Crowdin: https://crowdin.com/editor/typo3-cms/1134/en-fr?view=comfortable&filter=basic&value=0#q=g%C3%A9rer
- A (straight) single apostrophe is in use => that’s standard and what I wanted to double-check (vs “curly” which would be more typographically correct but easily causes similar issues)
- Might be related to either a JS-based encoding, and/or a double encoding at some point
My suggestion is to figure out if there is indeed a double encoding, drop that, and not go down the modification of
htmlspecialchars()calls hole…