--- Daniel Mayer maveric149@yahoo.com wrote:
OIC. Well a person should /not/ be using fancy things like curly quotes and long hyphens because many browsers (especially on non-MS systems) display them as question makes. These should be fixed, not allowed to propagate. The fact that some browsers break these codes should be a good hint that they should not be used to begin with (esp. since ASCII quotes and regular hyphens can be used instead).
Isn't there a "approved characters page" somwhere?
But a way around the larger issue is to sniff whether or not a browser is UTF-8-aware and then serve a page in either UTF-8 or in Latin-1 (whatever the ISO) based on that. When a UTF-8 page is displayed it shows the actual non-Latin characters, when the Latin-1 page is displayed it shows the codes the represent those characters.
Please, no browser sniffing.
That at least will prevent pages from getting damaged, but the special characters will still show up as question marks for people with older browsers, so things like curly quotes and long hyphens should be automatically converted to their ASCII counterparts.
I would rather see code that changes the latin chars to utf-8 chars at article save.
===== Christopher Mahan chris_mahan@yahoo.com 818.943.1850 cell http://www.christophermahan.com/
__________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree