Re: content-charset & checksums

In case other people didn't notice it, Mark's latest message contained
what I assume to be a deliberately provocative header:

Content-type: TEXT/ISO-2022; charset=US-ASCII

I shudder to think at how any software SHOULD interpret this.  Mine
didn't fare TOO badly, since it really only understands ASCII to begin
with...

Presumably this is not really a provocation, since the charset subtypes
will go away if we move to the charset= syntax.  -- Nathaniel

<Prev in Thread]	Current Thread	[Next in Thread>
Re: checksums (was: content-charset & checksums), (continued) Re: checksums (was: content-charset & checksums), James M Galvin Re: checksums (was: content-charset & checksums), David J. Camp Re: checksums (was: content-charset & checksums), Dave Crocker re: content-charset & checksums, Mark Crispin Re: content-charset & checksums, Nathaniel Borenstein Re: content-charset & checksums, Mark Crispin Re: checksums, James M Galvin Re: checksums, Nathaniel Borenstein Re: content-charset & checksums, Greg Vaudreuil Re: content-charset & checksums, Mark Crispin Re: content-charset & checksums, Nathaniel Borenstein <= Re: content-charset & checksums, Mark Crispin Re: content-charset & checksums, Nathaniel Borenstein Re: content-charset & checksums, Mark Crispin Re: content-charset & checksums, Nathaniel Borenstein Re: content-charset & checksums, Nathaniel Borenstein plain-text checksums considered useless, henry Re: plain-text checksums considered useless, Nathaniel Borenstein Re: plain-text checksums considered useless, Erik E. Fair more content-charset, Harald Tveit Alvestrand Re: more content-charset, Nathaniel Borenstein

Previous by Date:	Re: checksums, Nathaniel Borenstein
Next by Date:	Re: Audio type, Neil Katin
Previous by Thread:	Re: content-charset & checksums, Mark Crispin
Next by Thread:	Re: content-charset & checksums, Mark Crispin
Indexes:	[Date] [Thread] [Top] [All Lists]