Bug #6385

character converson in BE broken

Added by Martin Kutschker over 3 years ago. Updated over 2 years ago.

Status:Resolved Start date:2010-02-06
Priority:Must have Due date:
Assignee:- % Done:

100%
Category:-
Target version:Extbase 1.0.2
Has patch: Tags:
Votes: 0

Description

The task of Tx_Extbase_Utility_Localization::convertCharset() is to convert a string FROM a specified charset. At least this is what the code does. It takes a string of arbitrary charset and converts it to the current one. So the docs are wrong.

And the feature is broken in the BE. The reason is that the current charset in the BE is $LANG->charSet not $LANG->renderCharset.

convertCharset.patch (1.2 kB) Martin Kutschker, 2010-02-06 20:39

Associated revisions

Revision 0e13a80a
Added by Jochen Rau about 3 years ago

[+BUGFIX] Extbase (Utility): Extbase uses the right BE charset now when forceCharset is not used. Thanks to Martin Kutschker who provided the patch. Resolves #6236.
[+BUGFIX] Extbase (Utility): Fixed broken charset conversion in BE. Thanks to Martin Kutschker who provided the patch. Resolves #6385.
[+BUGFIX] Extbase (Utility): FE translation now uses the right language when a BE session is active. Thanks to Martin Kutschker who provided the patch. Resolves #6725.

History

#1
Updated by Jochen Rau about 3 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Applied in changeset r1984.

Also available in: Atom PDF