Re: Charset support (was: Accept-Charset support)i
On Tue, 17 Dec 1996, Larry Masinter wrote:
> To: email@example.com
> # It's mainly the server implementors that I am thinking about.
> Server implementors can use static strings for warning messages, and
> encoding a string using RFC1522 can be done in a few lines of code.
> And no server implementor has complained that RFC 1522 is too
> difficult to implement.
Have any said that they will implement it, or have any already implemented
> # RFC1522 is not inescapable.
> It is if you want to serve something other than Unicode and ISO-8859-1
> (now) or US-ASCII (if you were to get your way). And anyone who wants
> to build software that works for clients who have software that use
> anything other than Unicode (i.e., most of the currently deployed web
> clients) will have to support RFC 1522.
Where else would it be needed, except Warning? (Excluding other
protocols like mail, news)