On 22-jun-2006, at 9:21, Tom.Petch wrote:
<inline>
Where else?
I think this is closer to what an RFC with Unicode line art would
look like than trying to present an example in email. For me, the
UTF-8 encoding isn't immediately decoded properly by my browser, but
the UTF-16 version is. I also can't get this displayed properly on
the command line on my Mac. Still, it's not _too_ hard to have the
Unicode characters displayed properly.
I agree in principle that adding a selected subset of Unicode would
address the
most pressing issues. But, for whatever reason, I get gibberish on
both the
URLs you give. By contrast, the figure embedded in an e-mail
earlier displayed
perfectly (until it got mangled when included in a reply). This
suggests to me
that the world is not quite ready for Unicode yet (I am using
vanilla Windows
software, as most of the world does:-(.
Well, apparently Windows isn't, although I gather that it does
actually support Unicode to a more noticable degree than I've seen.
As someone else observed, my server adds an ISO-8859-1 header (thank
you Apache for guessing (wrong) what the file contains and then
overwrite what's specified in the file or what the client may guess
correctly, wasting a little bandwidth for every request). I've done
some additional experimenting, most notably at:
http://www.muada.com/drafts/utf8-art.php
http://www.muada.com/drafts/utf8-art-html.php
These both result in something workable on the Mac with Safari,
something that works to varying degrees in Firefox on Mac/Linux/
Windows but no luck on Windows with Internet Explorer. (The right
header in gets stuffed into the HTTP reply with PHP.) Apart from IE's
ineptitude the main problem is that most systems have a hard time
getting all the characters the same width.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf