<div dir="ltr">Down with character: applied Alisdair feedback, added wording for [cpp] and [basic] <a href="https://isocpp.org/files/papers/D2749R0.pdf">https://isocpp.org/files/papers/D2749R0.pdf</a><div><br></div><div>Referencing the unicode standard: applied SG-16 suggestion and the wording suggestion made by Jens on mattermost. I would prefer a solution that does not preserve the term ucs2, i think, but it&#39;s in a deprecated annex so... good enough! <a href="https://isocpp.org/files/papers/D2736R1.pdf">https://isocpp.org/files/papers/D2736R1.pdf</a> </div><div><br></div><div><br></div><div>I&#39;ll keep tweaking tomorrow but it should allow us to make progress during tomorrow&#39;s meeting.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 24, 2023 at 8:55 PM Tom Honermann via SG16 &lt;<a href="mailto:sg16@lists.isocpp.org">sg16@lists.isocpp.org</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div>
    <p>This is your friendly reminder that this meeting is taking place
      tomorrow.</p>
    Tom.
    <p></p>
    <div>On 1/23/23 12:45 PM, Tom Honermann via
      SG16 wrote:<br>
    </div>
    <blockquote type="cite">
      
      <p>SG16 will hold a telecon on Wednesday, January 25th, at 19:30
        UTC (<a href="https://www.timeanddate.com/worldclock/converter.html?iso=20230125T193000&amp;p1=1440&amp;p2=tz_pst&amp;p3=tz_mst&amp;p4=tz_cst&amp;p5=tz_est&amp;p6=tz_cet" target="_blank">timezone conversion</a>).</p>
      <p>The agenda follows.</p>
      <ul>
        <li>Planning for NOT Issaquah.<br>
        </li>
        <li><a href="https://wg21.link/p2736r0" target="_blank">P2736R0</a>:
          Referencing the Unicode Standard.</li>
        <li><a href="https://isocpp.org/files/papers/D2749R0.pdf" target="_blank">D2749R0</a>: Down with ”character”<br>
        </li>
      </ul>
      <p>We agreed to hold a SG16 meeting in Issaquah during the <a href="https://github.com/sg16-unicode/sg16-meetings#january-11th-2023" target="_blank">2023-01-11
          SG16 telecon</a>. Unfortunately, that isn&#39;t going to happen
        due to a lack of conference rooms available during regular
        business hours and previous discussions regarding meeting before
        or after regular business hours did not have consensus. That
        leaves us with just this upcoming telecon currently scheduled to
        dispense with our remaining NB comments. I&#39;m hopeful that we&#39;ll
        be able to poll forwarding P2736 at this meeting, but I&#39;m
        skeptical that we&#39;ll get to a point where we are comfortable
        polling P2749. However, I would be happy to schedule an
        additional telecon for 2023-02-01 if we agree there is a
        reasonable chance that we&#39;ll be able to establish a position on
        that paper by then.<br>
      </p>
      <p>We continued discussion of P2736R0 (Referencing the Unicode
        Standard) during the <a href="https://github.com/sg16-unicode/sg16-meetings#january-11th-2023" target="_blank">2023-01-11 SG16 telecon</a> and
        identified a few issues to be addressed. Corentin has requested
        some assistance, both <a href="https://lists.isocpp.org/sg16/2023/01/3664.php" target="_blank">on the
          SG16 mailing list</a> and <a href="https://chat.isocpp.org/general/channels/sg16-unicode" target="_blank">in
          the SG16 Mattermost channel</a>. If you can help out, please
        do so! (Sorry, Corentin, I&#39;ve been playing too much catchup
        lately). Note that Fraser also <a href="https://lists.isocpp.org/sg16/2023/01/3663.php" target="_blank">expressed
          a view regarding the __STDC_ISO_10646__ macro</a>; it would be
        helpful to have other comments either in agreement or in
        opposition to that view.<br>
      </p>
      <p>D2749R0 (Down with ”character”) was on the agenda for our last
        telecon, but we ran out of time. We last discussed the related
        NB comment during the <a href="https://github.com/sg16-unicode/sg16-meetings#december-14th-2022" target="_blank">2022-12-14 SG16 telecon</a>. This paper
        is relatively long due to its wording impact. Please take the
        time to read the motivation and at least scan through the
        wording changes. I encourage everyone to reacquaint themselves
        with the terminology used in <a href="https://unicode.org/reports/tr17/" target="_blank">UTR #17</a>
        beforehand as well.<br>
      </p>
      Tom. <br>
      <fieldset></fieldset>
    </blockquote>
  </div>

-- <br>
SG16 mailing list<br>
<a href="mailto:SG16@lists.isocpp.org" target="_blank">SG16@lists.isocpp.org</a><br>
<a href="https://lists.isocpp.org/mailman/listinfo.cgi/sg16" rel="noreferrer" target="_blank">https://lists.isocpp.org/mailman/listinfo.cgi/sg16</a><br>
</blockquote></div>

