LISTSERV mailing list manager LISTSERV 15.5

Help for MHTML Archives


MHTML Archives

MHTML Archives


View:

Next Message | Previous Message
Next in Topic | Previous in Topic
Next by Same Author | Previous by Same Author
Chronologically | Most Recent First
Proportional Font | Monospaced Font

Options:

Join or Leave MHTML
Reply | Post New Message
Search Archives


Subject: Re: Summary of decisions at the Montreal MHTML IETF meeting
From: Martin J Duerst <[log in to unmask]>
Reply-To:IETF working group on HTML in e-mail <[log in to unmask]>
Date:Thu, 4 Jul 1996 11:26:21 +0200
Content-Type:text/plain
Parts/Attachments:
Parts/Attachments

text/plain (23 lines)


Larry Masinter wrote:

>> However, there are some differences as to the default character encoding,
>> specified by the MIME "charset" parameter, if this parameter is omitted.
>> When transferred through HTTP, the default is [HTML2]:
>>         content-type: text/html; charset=iso-8859-1
>> when transferred with electronic mail, the default is [MIME1]:
>>         content-type: text/html; charset=us-ascii
>
>I believe that after some last-minute wrangling, the HTTP/1.1
>specification is going to recommend sending a charset parameter
>ALWAYS. This is also the recommendation for mail. So rather than
>making a big deal about HTML in HTTP vs. mail, I think the mhtml draft
>should just support always sending "charset=" in mail, with a note
>that if you get something text/html from a HTTP that didn't send the
>charset in the first place, you should supply it when you send it out
>in mail.

This is definitely a good idea, as nowadays much stuff is sent without
a charset parameter without conforming to the default. If we can change
mhtml to specify things in this way, this would be a definite improvement.

Regards,        Martin.

Back to: Top of Message | Previous Page | Main MHTML Page

Permalink



LISTSRV.NORDU.NET

CataList Email List Search Powered by the LISTSERV Email List Manager