<html><head></head><body><div class="ydpac437edfyahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><div dir="ltr" data-setdir="false">My sense was that we wanted to look at the individual cases first.  And use our findings to inform what decision to make on the general case of the particular diacritic.  Rather than deciding to not go for consistency.</div><div><br></div><div class="ydpac437edfsignature">Bill Jouris<br>Inside Products<br>bill.jouris@insidethestack.com<br>831-659-8360<br>925-855-9512 (direct)</div></div>
        <div><br></div><div><br></div>
        
        </div><div id="yahoo_quoted_8267104704" class="yahoo_quoted">
            <div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
                
                <div>
                    On Thursday, September 5, 2019, 08:59:35 AM PDT, Tan Tanaka, Dennis via Latingp <latingp@icann.org> wrote:
                </div>
                <div><br></div>
                <div><br></div>
                <div><div dir="ltr">Well, about consistency. That was the approach that was suggested at the beginning (i.e. decide by diacritic group instead of individual ratings). The idea did not have support. Instead, it was argued that diacritics are not rendered consistently across letters and therefore they needed to be tested individually. That was what the majority supported and the reason we did the spreadsheet. <br clear="none"><br clear="none">The inconsistency in ratings is due in part of the differences in how fonts are rendered in different systems (by system I mean the combination of OS, display, resolution, application, font type, etc.). On top of this, people's perception also play a roll, which renders any conclusion as subjective.<br clear="none"><br clear="none">-Dennis<br clear="none"><br clear="none">On 9/5/19, 8:50 AM, "Latingp on behalf of Michael Bauland" <<a shape="rect" ymailto="mailto:latingp-bounces@icann.org" href="mailto:latingp-bounces@icann.org">latingp-bounces@icann.org</a> on behalf of <a shape="rect" ymailto="mailto:Michael.Bauland@knipp.de" href="mailto:Michael.Bauland@knipp.de">Michael.Bauland@knipp.de</a>> wrote:<br clear="none"><br clear="none">    Hi Bill,<br clear="none">    <br clear="none">    On 04.09.2019 23:42, Bill Jouris wrote:<br clear="none">    > Dear colleagues, <br clear="none">    > <br clear="none">    > As requested, I have updated the Proposal (Section 6.7.1) with our<br clear="none">    > decisions for Variants Due To Underlining.  <br clear="none">    <br clear="none">    thanks for your work.<br clear="none">    <br clear="none">    <br clear="none">    > I would like to note one small inconsistency in our results.  Basic<br clear="none">    > letters are considered variants of the same letter with a cedilla for<br clear="none">    > letters K, L, N, S, and T.  But *not* for letters C, M, and O.  It seems<br clear="none">    > to me that we really ought to be consistent in this.  (As we are for Dot<br clear="none">    > Below, Macron Below, Circumflex Below, Ogonek, etc.)<br clear="none">    <br clear="none">    Good catch. I agree that we should try to be consistent. And in case<br clear="none">    there is a good reason that requires us to be "inconsistent" we at least<br clear="none">    have to argue and comment why we handle those seemingly equivalent cases<br clear="none">    differently.<br clear="none">    <br clear="none">    As mentioned last week, I will be in a car driving to a customer during<br clear="none">    our call and I don't like driving and using the phone (even with a<br clear="none">    hands-free kit) at the same time. So I won't be able to join. Therefore<br clear="none">    my vote (in case you need it in this call) for this case:<br clear="none">    Looking at our original documents my opinion is to not considering base<br clear="none">    characters and characters with cedilla below as variants.<br clear="none">    <br clear="none">    Talk to you next week,<br clear="none">    <br clear="none">    Michael<br clear="none">    <br clear="none">    -- <br clear="none">    ____________________________________________________________________<br clear="none">         |       |<br clear="none">         | knipp |            Knipp  Medien und Kommunikation GmbH<br clear="none">          -------                    Technologiepark<br clear="none">                                     Martin-Schmeisser-Weg 9<br clear="none">                                     44227 Dortmund<br clear="none">                                     Germany<br clear="none">    <br clear="none">         Dipl.-Informatiker          Fon:    +49 231 9703-0<br clear="none">                                     Fax:    +49 231 9703-200<br clear="none">         Dr. Michael Bauland         SIP:    <a shape="rect" ymailto="mailto:Michael.Bauland@knipp.de" href="mailto:Michael.Bauland@knipp.de">Michael.Bauland@knipp.de</a><br clear="none">         Software Development        E-mail: <a shape="rect" ymailto="mailto:Michael.Bauland@knipp.de" href="mailto:Michael.Bauland@knipp.de">Michael.Bauland@knipp.de</a><br clear="none">    <br clear="none">                                     Register Court:<br clear="none">                                     Amtsgericht Dortmund, HRB 13728<br clear="none">    <br clear="none">                                     Chief Executive Officers:<br clear="none">                                     Dietmar Knipp, Elmar Knipp<br clear="none">    _______________________________________________<br clear="none">    Latingp mailing list<br clear="none">    <a shape="rect" ymailto="mailto:Latingp@icann.org" href="mailto:Latingp@icann.org">Latingp@icann.org</a><br clear="none">    <a shape="rect" href="https://mm.icann.org/mailman/listinfo/latingp" target="_blank">https://mm.icann.org/mailman/listinfo/latingp</a><br clear="none">    <br clear="none">    _______________________________________________<br clear="none">    By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a shape="rect" href="https://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a shape="rect" href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.<div class="yqt6510662102" id="yqtfd63799"><br clear="none"><br clear="none">_______________________________________________<br clear="none">Latingp mailing list<br clear="none"><a shape="rect" ymailto="mailto:Latingp@icann.org" href="mailto:Latingp@icann.org">Latingp@icann.org</a><br clear="none"><a shape="rect" href="https://mm.icann.org/mailman/listinfo/latingp" target="_blank">https://mm.icann.org/mailman/listinfo/latingp</a><br clear="none"><br clear="none">_______________________________________________<br clear="none">By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a shape="rect" href="https://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a shape="rect" href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div></div></div>
            </div>
        </div></body></html>