Yes, I see that table -- puzzling, sounds like 4.1.0 implements the option but doesn't support any charsets, or something close to that.
If it doesn't recognize the charset, it'll fail 'softly' -- this is both a good and a bad thing:
- we can actually use the parameter (and I believe we should)
- we cannot be certain of whether it's doing something
We could add some logic when loading the language packs -- or when the admin selects language packs -- to compare charsets and PHP versions and warn the admin.
It's really nasty that there doesn't seem to be a way to query PHP and for its supported charsets.
General developer forum
Patch for charset encoding bug in weblib.php (1.4.3+)
This discussion has been locked because a year has elapsed since the last post. Please start a new discussion topic.