Deseret seems to be in a five-byte corner of UTF-8. That may be part of Safari's problem. They're displayed as if they were unrecognized HTML entities.
Aha, it's more than that-- it's encoded with surrogates, an oddball means of extending the Unicode space to more than two bytes of code numbers. Safari may have trouble handling surrogates. And it turns out that Deseret has a very special role in the history of this part of Unicode, as explained here (http://homepage.mac.com/jhjenkins/Deseret/Unicode.html)! This is undoubtedly the reason why Deseret is included at all.
OK, wait. It works fine on my Jaguar machine in Firebird 0.7.1. But unlike for you, it doesn't work in Camino 0.7.0, nor in the latest Safari. In Safari, I just see the whole literal entity (amper blah blah blah; etc.) and in Camino I just see lots of question marks.
I think that Gecko-based browsers may handle Unicode differently from most other Mac OS X apps. Or maybe some Gecko browsers and not others. It's very confusing.
no subject
Date: 2003-11-20 06:46 am (UTC)no subject
Date: 2003-11-20 06:52 am (UTC)no subject
Date: 2003-11-20 06:56 am (UTC)no subject
Date: 2003-11-20 07:50 pm (UTC)no subject
Date: 2003-11-21 02:30 am (UTC)