Re: [apps-discuss] Last Call: <draft-ietf-appsawg-mime-default-charset-03.txt> (Update to MIME regarding Charset Parameter Handling in Textual Media Types) to Proposed Standard

Thinking about it more, the far more likely scenario is that a slot for
inline information is available but existing applications don't use it and
cannot be upgraded to use it.

				Ned

> > But ... that is saying that XML recognises the need to be able to auto-detect
> > the character encoding and is designed to do so.  This change to mime default
> > charset imposes the need to auto-detect on all future text/* where the encoding
> > is transported inside the payload, which the old rules did not.

> It does nothing of the sort. The preferential use of inline information is a
> SHOULD, not a MUST. If a given syntax carries such information inline but
> doesn't define a reliable standalone way to extract it (it depends on
> additional external information, for example), that would be more than
> sufficient reason not to use inline information.

> > Perhaps a corner case not worth mentioning.

> It's not even that.

> 				Ned
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss