Bug #18666
closed
Encoding problems with $TYPO3_CONF_VARS[SYS][sitename]
0%
Description
If the sitename contains umlauts, and the file is saved in a different charset than what is used by TYPO3, the output gets distorted (e.g. at the BE login screen).
A possible solution would be to allow html entities. Removing htmlspecialchars() would not hurt as the input is coming from a trusted source.
(issue imported from #M8195)
Files
Updated by Martin Kutschker over 16 years ago
As multi-charset setups are deprectated setting BE[forceCharset] to your charset will help if it's not iso-8859-1. In 4.2 it will be used in the login screen and the installer.
Sidenote: it'd be great if we could rename it to SYS[charset] and make it a mandatory configuration option.
Updated by Steffen Kamper over 16 years ago
+1 for renaming to SYS[charset] as it doesn't influence BE only.
If it's mandatory it should appear in 1-2-3-setup as well.
Updated by Benni Mack over 16 years ago
Should go in the new installer along with
- utf8 by default
- DB charset check when installing
Updated by Michael Stucki about 16 years ago
The problem does actually not exist as long as the encoding of localconf.php matches the backend charset defined in $TYPO3_CONF_VARS[BE][forceCharset].
So here is a fix, however it will not go into TYPO3core because it adds unneccessary overhead to every page request.
Updated by Michael Stucki about 16 years ago
If you are still interested in discussing the naming of BE[forceCharset], please move that topic to a new request.