After all the time I’ve spent on here these last several years, I feel I ought to know the culprit behind oddball font rendering of web pages encoded in non-Western/Unicode fonts.
But this one has me stumped. (Or else my brain is falling apart.)
Take, for instance, an old, questionably-formatted page whose character encoding call-out in the
![1668429415686.png]( "1668429415686.png")
On Mozilla-based browsers running 10.6.8 and later, the page renders as one might expect:
![1668428539657.png]( "1668428539657.png")
Yet, on Mozilla-based browsers (TFF, Interweb-PPC, etc.) running 10.5.8 or earlier (or, heck, even 10.6 SL-PPC), the same page renders as this (or some variation thereof):
![1668428616770.png]( "1668428616770.png")
After eliminating discrepancies in system fonts between major versions of OS X (Korean fonts are part of Leopard, just as they are with later OS X releases), what am I missing here? Do older Mozilla code bases have fundamental issues with mixed character usage that prevent correct rendering of the occasional old web page with peculiar language/encoding call-outs?
But this one has me stumped. (Or else my brain is falling apart.)
Take, for instance, an old, questionably-formatted page whose character encoding call-out in the
<html> page tag is "ko", or Korean, but with mixed Latin characters:On Mozilla-based browsers running 10.6.8 and later, the page renders as one might expect:
Yet, on Mozilla-based browsers (TFF, Interweb-PPC, etc.) running 10.5.8 or earlier (or, heck, even 10.6 SL-PPC), the same page renders as this (or some variation thereof):
After eliminating discrepancies in system fonts between major versions of OS X (Korean fonts are part of Leopard, just as they are with later OS X releases), what am I missing here? Do older Mozilla code bases have fundamental issues with mixed character usage that prevent correct rendering of the occasional old web page with peculiar language/encoding call-outs?
Last edited:
