Why are non-ASCII characters output as numeric character references instead of raw UTF-8?
Firstly, it should be noted that numeric character references are a valid way of representing non-ASCII characters in HTML, so even if you do not perform the action suggested below to address this, Nelson’s output will continue to render correctly. This behaviour is caused by a known bug in older versions of the libxml2 library, a component that comes with the operating system. For example, Mac OS X 10.5.6 (Leopard) comes with version 2.2, manifesting this behaviour. The issue has been found to be corrected at least in versions 2.6.21 and higher.
Related Questions
- My templates are outputting binary data or converting output to a character set other than UTF-8, but the output is getting messed up. What gives?
- Should I use numeric character references to represent characters greater than ASCII 127 in my OAI-PMH responses?
- Why are non-ASCII characters output as numeric character references instead of raw UTF-8?