<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body>
    <div class="moz-cite-prefix">On 10/14/20 8:25 AM, Alisdair Meredith
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:BFBD904F-40EF-4A13-9A3C-BCF7CB6F4C2B@me.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      A minor note for clarity.
      <div class=""><br class="">
      </div>
      <div class="">I would better understand the goal of this paper if
        there were an early sentence indicating</div>
      <div class="">whether the target audience of the advice is:</div>
      <div class="">   1) document authors</div>
      <div class="">   2) document processing tools</div>
      <div class="">   3) both equally</div>
      <div class=""><br class="">
      </div>
      <div class="">The advice seems geared strongly towards group (2),
        but we probably want to send a</div>
      <div class="">message to group (1) as well.</div>
    </blockquote>
    <p>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.<br>
    </p>
    <p>Tom.<br>
    </p>
    <blockquote type="cite"
      cite="mid:BFBD904F-40EF-4A13-9A3C-BCF7CB6F4C2B@me.com">
      <div class=""><br class="">
      </div>
      <div class="">AlisdairM</div>
      <div class="">
        <div><br class="">
          <blockquote type="cite" class="">
            <div class="">On Oct 10, 2020, at 14:54, Tom Honermann via
              SG16 <<a href="mailto:sg16@lists.isocpp.org" class=""
                moz-do-not-send="true">sg16@lists.isocpp.org</a>>
              wrote:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <meta http-equiv="content-type" content="text/html;
                charset=windows-1252" class="">
              <div class="">
                <p class="">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 moz-do-not-send="true"
                    href="https://corp.unicode.org/pipermail/unicode/2020-June/008713.html"
                    class="">discussion on the Unicode mailing list</a>
                  back in June.</p>
                <p class="">Feedback is welcome.  I plan to <a
                    moz-do-not-send="true"
                    href="https://www.unicode.org/pending/docsubmit.html"
                    class="">submit</a> this to the UTC in a week or so
                  pending review feedback.<br class="">
                </p>
                <p class="">Tom.<br class="">
                </p>
              </div>
              <span
                id="cid:9F01EC9A-4273-40A2-BB38-63B20B12F41C@nyc.rr.com"><Unicode-BOM-guidance.pdf></span>--
              <br class="">
              SG16 mailing list<br class="">
              <a href="mailto:SG16@lists.isocpp.org" class=""
                moz-do-not-send="true">SG16@lists.isocpp.org</a><br
                class="">
              <a class="moz-txt-link-freetext" href="https://lists.isocpp.org/mailman/listinfo.cgi/sg16">https://lists.isocpp.org/mailman/listinfo.cgi/sg16</a><br
                class="">
            </div>
          </blockquote>
        </div>
        <br class="">
      </div>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>