<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 10/11/20 11:32 PM, JF Bastien wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CACeCrovAxGyr02DKC5mXK7-tVwTvoMgcmybCa_dmUO4+k9dDvA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">It’s a bit odd: if you assume the default is ascii
        then you don’t need this. If you assume the default is utf8 then
        you don’t need this... so when do you need the BOM? It seems
        like making bad prior choices more acceptable... even though
        they were bad choices. I’m not sure it’s a good idea. <br>
      </div>
    </blockquote>
    <p>A BOM would be needed when:</p>
    <ol>
      <li>The default encoding is ASCII based (ISO-8859-1, Windows-1252,
        etc...) and the UTF-8 text to be produced contains non-ASCII
        characters.  Or,</li>
      <li>The default encoding is not ASCII based (e.g., EBCDIC).</li>
    </ol>
    <p>Both of these cases presume that the default encoding can't be
      made UTF-8 for backward compatibility reasons.<br>
    </p>
    <p>Tom.<br>
    </p>
    <blockquote type="cite"
cite="mid:CACeCrovAxGyr02DKC5mXK7-tVwTvoMgcmybCa_dmUO4+k9dDvA@mail.gmail.com">
      <div><br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Sun, Oct 11, 2020 at 8:22
            PM Tom Honermann via SG16 <<a
              href="mailto:sg16@lists.isocpp.org" moz-do-not-send="true">sg16@lists.isocpp.org</a>>
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">
            <div>
              <div>On 10/10/20 7:58 PM, Alisdair Meredith via SG16
                wrote:<br>
              </div>
              <blockquote type="cite"> One concern I have, that might
                lead into rationale for the current discouragement,
                <div>is that I would hate to see a best practice that
                  pushes a BOM into ASCII files.</div>
                <div>One of the nice properties of UTF-8 is that a valid
                  ASCII file (still very common) is</div>
                <div>also a valid UTF-8 file.  Changing best practice
                  would encourage updating those</div>
                <div>files to be no longer ASCII.</div>
              </blockquote>
              <p>Thanks, Alisdair.  I think that concern is implicitly
                addressed by the suggested resolutions, but perhaps that
                can be made more clear.  One possibility would be to
                modify the "protocol designer" guidelines to address the
                case where a protocol's default encoding is ASCII based
                and to specify that a BOM is only required for UTF-8
                text that contains non-ASCII characters.  Would that be
                helpful?</p>
            </div>
            <div>
              <p><br>
              </p>
              <p>Tom.<br>
              </p>
              <blockquote type="cite">
                <div><br>
                </div>
                <div>AlisdairM<br>
                  <div><br>
                    <blockquote type="cite">
                      <div>On Oct 10, 2020, at 14:54, Tom Honermann via
                        SG16 <<a href="mailto:sg16@lists.isocpp.org"
                          target="_blank" moz-do-not-send="true">sg16@lists.isocpp.org</a>>
                        wrote:</div>
                      <br>
                      <div>
                        <div>
                          <p>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 <a
href="https://corp.unicode.org/pipermail/unicode/2020-June/008713.html"
                              target="_blank" moz-do-not-send="true">discussion
                              on the Unicode mailing list</a> back in
                            June.</p>
                          <p>Feedback is welcome.  I plan to <a
                              href="https://www.unicode.org/pending/docsubmit.html"
                              target="_blank" moz-do-not-send="true">submit</a>
                            this to the UTC in a week or so pending
                            review feedback.<br>
                          </p>
                          <p>Tom.<br>
                          </p>
                        </div>
                        <span
id="m_3223124279792112309cid:958C9297-66AC-4D88-8F0B-577B8BA2589E@nyc.rr.com"><Unicode-BOM-guidance.pdf></span>--
                        <br>
                        SG16 mailing list<br>
                        <a href="mailto:SG16@lists.isocpp.org"
                          target="_blank" moz-do-not-send="true">SG16@lists.isocpp.org</a><br>
                        <a
                          href="https://lists.isocpp.org/mailman/listinfo.cgi/sg16"
                          target="_blank" moz-do-not-send="true">https://lists.isocpp.org/mailman/listinfo.cgi/sg16</a><br>
                      </div>
                    </blockquote>
                  </div>
                  <br>
                </div>
                <br>
                <fieldset></fieldset>
              </blockquote>
              <p><br>
              </p>
            </div>
            -- <br>
            SG16 mailing list<br>
            <a href="mailto:SG16@lists.isocpp.org" target="_blank"
              moz-do-not-send="true">SG16@lists.isocpp.org</a><br>
            <a href="https://lists.isocpp.org/mailman/listinfo.cgi/sg16"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.isocpp.org/mailman/listinfo.cgi/sg16</a><br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>