W3C home > Mailing lists > Public > ietf-charsets@w3.org > October to December 2002

Re: Comments on draft-yergeau-rfc2279bis-00.txt

From: Martin Duerst <duerst@w3.org>
Date: Fri, 04 Oct 2002 07:48:59 +0900
To: Simon Josefsson <simon+ietf-charsets@josefsson.org>
Cc: ietf-charsets@iana.org
Message-id: <4.2.0.58.J.20021004074824.041df570@localhost>

At 15:35 02/10/03 +0200, Simon Josefsson wrote:
>Martin Duerst <duerst@w3.org> writes:

> > Therefore, senders SHOULD NOT use the BOM in larger, usually
> > labeled, pieces of text (e.g. MIME entities), and MUST NOT
> > use it in smaller protocol elements (usually with a fixed
> > encoding). Receivers SHOULD recognize and remove the BOM
> > in larger, usually labeled, pieces of text (e.g. MIME entities).
>
>This still says that implementations should support BOM, which I think
>is bad practice.  If I were to follow this practice in a MUA I would
>break digital signatures on UTF-8 data.  How about changing the last
>sentence into the following:
>
>   Receivers MAY recognize and remove the BOM in larger, usually
>   labeled, pieces of text (e.g. MIME entities), if it requires
>   compability with software that generates it.  Care should be taken
>   to not remove BOM in data that must be preserved correctly (such as
>   digitally signed data).

I think this is fine.     Regards,   Martin.
Received on Friday, 4 October 2002 05:37:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 5 June 2006 15:10:54 GMT