[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Registration of new charset "UTF-16"

 
> Larry's version seems fine to me. Perhaps a reference to the sections 
> of MIME and HTTP that explain all this could be added to the end of the
> document? He says, giving it one more try.

I sent out a poll to the HTTP working group: are there two independent
interoperable implementations of the HTTP 'exception' that send and
process text types that don't use CR, LF, or CRLF for end of line?
If we can't find two independent interoperable implementations, we
may have to remove the 'feature' before we can progress HTTP/1.1 to
Draft Standard.

So far, I'm not aware of _any_ implementation of a browser _or_ a server
that support UTF-16, much less two implementations of each that have
been tested to be interoperable.

Larry
--
http://www.parc.xerox.com/masinter