Bug #16870
closed
Garbage characters displayed in flexform field labels
Added by Dmitry Dulepov almost 18 years ago.
Updated about 6 years ago.
Description
Non-latin1 characters in labels of flexform fields are not displayed properly. The problem is that they are in utf-8 but $LANG-sL tries convert them from local charset (normally iso-88591-1 for English) to UTF-8 thus making complete junk (see attached file).
(issue imported from #M4813)
Files
ff_label_charset.txt - valid for 4.1beta3 and contains other changes by ExtDevEval
ff_label_charset_change_only.txt - contains fix only
Additionally to this resolved bug mentioned above I have another problem with TV.
After forcing the BE to utf-8 and setting german as BE-language the german labels (with umlauts) in the Templavoila BE are displayed wrongly (see attachment | fce.gif). It seems that the labels which are stored in the XML-file typo3conf/ext/templavoila/mod1/locallang.xml are converted to utf-8 despite the fact that they're already present in this charset.
Versions and settings:
-------------------------------
Typo3 4.0.4
TemplaVoila 1.2.1
MySQL 4.1.18 (everything is UTF-8)
PHP 5.1.2
All Configuration in Install Tool: nothing changed, but [BE][forceCharset] = utf-8
Backend language set to german
Thanks for any hint in advance.
Nele
I found out that the labels (with umlauts) in the Templavoila BE are displayed correctly when I changed this line in t3lib/class.t3lib_div.php:
$origCharset = $csConvObj->parse_charset($csConvObj->charSetArray[$langKey] ? $csConvObj->charSetArray[$langKey] : 'iso-8859-1');
to this:
$origCharset = $csConvObj->parse_charset($csConvObj->charSetArray[$langKey] ? $csConvObj->charSetArray[$langKey] : 'utf-8');
But then the other umlauts in the T3 Backend are displayed wrongly.
Hoping that this may help to solve this problem.
After I applied the patch I still had some wrong encoded umlauts in section form elements. I fixed that. See patchfile.patch.
Hm, it seems like the problem isn't solved, right? My umlauts still look scrambled. How can one apply the patch posted above? Do I have to have SSH-Access to apply the patch?
Waits for alternative charset patch from Masi
- Status changed from Resolved to Closed
Also available in: Atom
PDF