[SG16] Draft proposal: Clarify guidance for use of a BOM as a UTF-8 encoding signature

Tom Honermann tom at honermann.net
Thu Oct 15 17:32:39 CDT 2020

On 10/14/20 8:25 AM, Alisdair Meredith wrote:
> A minor note for clarity.
> I would better understand the goal of this paper if there were an 
> early sentence indicating
> whether the target audience of the advice is:
>    1) document authors
>    2) document processing tools
>    3) both equally
> The advice seems geared strongly towards group (2), but we probably 
> want to send a
> message to group (1) as well.

Thanks Alisdair.  I'll add more of an introduction.  The suggested 
resolutions do address (1) as well, but one has to read until the end to 
see that.  Good suggestion.


> AlisdairM
>> On Oct 10, 2020, at 14:54, Tom Honermann via SG16 
>> <sg16 at lists.isocpp.org <mailto:sg16 at lists.isocpp.org>> wrote:
>> Attached is a draft proposal for the Unicode standard that intends to 
>> clarify the current recommendation regarding use of a BOM in UTF-8 
>> text. This is follow up to discussion on the Unicode mailing list 
>> <https://corp.unicode.org/pipermail/unicode/2020-June/008713.html> 
>> back in June.
>> Feedback is welcome.  I plan to submit 
>> <https://www.unicode.org/pending/docsubmit.html> this to the UTC in a 
>> week or so pending review feedback.
>> Tom.
>> <Unicode-BOM-guidance.pdf>--
>> SG16 mailing list
>> SG16 at lists.isocpp.org <mailto:SG16 at lists.isocpp.org>
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg16

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20201015/834e4017/attachment.htm>

More information about the Unicode mailing list