On Thu, Jun 30, 2005 at 05:43:53PM -0700, Philip Guenther wrote:
Comparisons are performed in Unicode. Implementations convert
text from header fields in all charsets [HEADER-CHARSET] to
Unicode as input to the comparator (see 2.7.3). Implementations
must be capable of decoding US-ASCII, ISO-8859-1, the US-ASCII
subset of ISO-8859-* character sets, and UTF-8.
That sounds good.
Hmm, I think the paragraph needs to also specify that text in unknown
charsets never matches, no?
Either that or not decoding it, if it can not be converted.
But now that you cited the scope of 3028bis, can we do that?
If implementations fail to support the above behavior, they MUST
conform to the following:
No two strings can be considered equal if one contains octets
greater than 127.
If we agree that this only concers implementations that do not support
Unicode at all, of course we are free to specify what the result of
unicode supporting implementations is, if the conversion to it fails.
But I am not sure how exactly this is meant.
Michael