From 6e061f51846b0d85c08505f27299405c9868e24d Mon Sep 17 00:00:00 2001
From: "Edward Z. Yang"
The other possibility is to set Accept-Encoding to UTF-8, which @@ -640,7 +640,7 @@ set the encoding correctly using %Core.Encoding):
This behaviour is quite unsatisfactory. It is a deal-breaker for -I18N applications, and it can be mildly annoying for the provincial +international applications, and it can be mildly annoying for the provincial soul who occasionally needs a special character. Since 1.4.0, HTML Purifier has provided a slightly more palatable workaround using %Core.EscapeNonASCIICharacters. The process now looks like:
@@ -671,7 +671,7 @@ to be smart and only convert non-ASCII characters that weren't supported by the target encoding, but that would require reimplementing iconv with HTML awareness, something I will not do. -So there: either it's UTF-8 or crippled I18N support. Your pick! (and I'm +
So there: either it's UTF-8 or crippled international support. Your pick! (and I'm not being sarcastic here: some people could care less about other languages)
MediaWiki, a very prominent I18N application, uses binary fields +
MediaWiki, a very prominent international application, uses binary fields for storing their data because of point three.
There are drawbacks, of course: