|>To go along with this, I would suggest adding a new MIME type -
|>"text/uni-html" that indicates the document is using Unicode. This
|>allows locations that don't need the extra information to not accept
|>unicode versions of the documents (saves on bandwidth). This also
|>means that existing servers work and don't care they are serving up
|>Unicode docs. The HTML definition doesn't change except a remark needs
|>to be added that if the document is a Unicode HTML document, then the
|>BOM will be the first two bytes of the document.
No John, the content type is orthogonal to this the tag you want is :
Content-Encoding: Unicode
Yes we are very interested in Unicode. Main problem in the short term is
the question of generic fonts etc. To work we need Unicode for every
platform. X11 supports 16 bit fonts already.
I would like to adapt quite a bit of libwww to use 16 bit codes internaly
in any case.
-- Phillip M. Hallam-BakerNot Speaking for anyone else.