- From: Larry Masinter <masinter@parc.xerox.com>
- Date: Mon, 18 May 1998 23:59:33 -0700 (PDT)
- To: erik@netscape.com, Chris Newman <Chris.Newman@INNOSOFT.COM>
- Cc: MURATA Makoto <murata@apsdc.ksp.fujixerox.co.jp>, ietf-charsets@ISI.EDU, murata@fxis.fujixerox.co.jp, Tatsuo_Kobayashi@justsystem.co.jp
> 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 --Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)
Received on Tuesday, 19 May 1998 00:03:51 UTC