Re: ISO/IEC 10646 as Document Character Set

Larry Masinter (masinter@parc.xerox.com)
Wed, 3 May 95 22:45:47 EDT

> 1. We need language in the RFC that specifies what to do in the default
> case that the CHARSET parameter is not present in the Content-Type response.

Actually, I disagree, if by "the RFC" you mean the HTML RFC. I think
this is transport dependent. If you get HTML by SMTP mail, the default
should be what the mail transport says it is (US-ASCII) while if you
get something by HTTP the default can be something else.

How about if we don't try to solve this problem in the HTML working
group.