BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:UTC BEGIN:STANDARD DTSTART:16010101T000000 TZOFFSETFROM:+0000 TZOFFSETTO:+0000 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T000000 TZOFFSETFROM:+0000 TZOFFSETTO:+0000 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ORGANIZER;CN=Pitinan Kooarmornpatana:MAILTO:pitinan.koo@icann.org ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Latin GP:M AILTO:latingp@icann.org ATTACH:CID:image001.png@01D6B2D4.782D1680 DESCRIPTION;LANGUAGE=en-US:Dear Latin GP members\,\n\n\n\nThis is a placeho lder for the meeting this week\, 5 Nov 2020\, 17:00 UTC.\n\n\n\nPlease joi n the meeting at https://icann.zoom.us/j/98435828760\n\nPasscode: 1F$^iEkt $#\n\n\n\nAgenda for Latin GP call on \; November  \;the 5th \ ;\, 2020 17:00UTC\n\n \;\n\n 1. \; \; \; \; \; New time for GP calls\, Pitinan has \; \; \;conflict at 16.00 UTC Thursdays for next six months starting this week.\n\n a.& nbsp\; \; \; \; \; \; ether we move our call to 17:00 UTC on Thursday\n\n b. \; \; \; \; \; or Pitinan could make a doodle poll for 16:00 UTC on Monday\, Tuesday and Fri day\n\n c. \; \; \; \; \; \; or any o ther proposal\n\n 2. \; \; \; \; \; During test da ta production Bill found the following:\n „In the course of this\, I came across the Serer language (ISO 639-3 \;srr). \; It isn't in our list of languages included\, but it is EGIDS 5 and has roughly 1.2 mil lion native speakers so it would appear to fit our criteria. \; \; Also the Kpelle language (ISO 639-3 \;kpe)\, which is also EGIDS 5 and has about 1.4 million native speakers. \;\n\n\n  \;\n\n Adding Serer would entail adding 3 code points for Serer to the reper toire: \;\n\n U 0188 \; Small Letter C with Hook \;&nbs p\;ƈ \;\n\n U 01A5 \; Small Letter P with Hook \;  \;ƥ \; \;\n\n U 01AD \; Small Letter T with Hook \ ; \;ƭ \;\n\n  \;\n\n For Kpelle we would also n eed to add: \;\n\n U 0260 \; Small Letter G with Hook \ ; \;ɠ \;\n\n \;\n\n We might pick up a couple of Varia nts as well. \; For example\, a P with Hook (ƥ) \;resembles a Tho rn (þ) far more than a P alone does. \;“\n\n 3. \; \;&n bsp\; \; \; Code points like “s” and “ട” (U+0D1F) \; Malayalam letter. On August 22nd \; Bill wrote\n\n “Dear coll eagues\, \;\n\n  \;\n\n I was reading the latest ver sion of the LRG (https://www.icann.org/sites/default/files/lgr/lgr-4-overv iew-29jun20-en.pdf [icann.org])& nbsp\;and noticed this in the discussion of variants.\n\n  \;\n \n In typical user interface fonts\, even code points like “s” and “ട” (U+0D1F) may look indistinguishable.\n\n  \;\n\n It occurs to me\, if the IP is going to use this pair as an example of code points that are potentially indistinguishable\, might we not want to at least evaluate it\, to see if we think it should be a variant?  \; We may not\, but I think we should at least be able to say we looked at it. \;\n\n  \;\n\n Bill”\n\n  \;\n\n 4. \; \; \; \; \; Test data production\n My pro posal with \; test data provided by Bill are here \;\n https:/ /1drv.ms/t/s!AoE6DtesaqpIhCxEk8eVroNWMgZg?e=ttsQrn[1drv.ms]\n\n\n 5. \; \; \; \; \; Appendix C reord ering of letters\, Bill’s proposal e-mail \; on 23.7 2020:\n\n\n “I had a couple of thought on cosmetic changes to this Appendix\, to improve usability.\n\n · \; \; \; \; \;&nb sp\; \; \; \;I think the entry for Latin Small Letter Ae shoul d come after all of the entries for Letter A\n\n · \; \ ; \; \; \; \; \; \; \;I think the entry for La tin Small Letter Eth should come after all of the entries for Letter D&nbs p\;\n\n · \; \; \; \; \; \; \;  \; \;I think the entries for Latin Small Letter Open E should follow a ll of the entries for Letter E \;\n\n · \; \; \ ; \; \; \; \; \; \;I think the entries for Latin S mall Letter Open O should follow all of the entries for Letter O. \;\n \n · \; \; \; \; \; \; \; \;&nb sp\;I think the entry for Ligature Oe should follow the entries for Open O \n\n These are\, I would say\, cosmetic. \; We certainly can se nd the document to the IP for review without doing them. \; But I woul d like to see them happen before we go to public comment. \;“\n\n  \;\n\n  \;\n\n\n 6. \; \; \;&nb sp\; \; Capital Letters Discussion\, Mats sent an e-mail on 23.7 2020\ n\n\n At the start of our work it was forbidden to talk about c apital letters. Now we have had a long discussion about capital I with and without dot\, so I think it is time that we look at another phenomenon in our data.\n\n  \;\n\n Note that I do not argue that we should create new variant sets\, just that we should look at it be fore we send the report out for comment.\n\n  \;\n\n In our repertoire we have U+00F0\, U+0111 and U+0256. Those lower cas e letters are distinct so that is not the problem. The potential issue is that the capital letters of those three are homoglyphs\, not just similar. You can see below how they look like. I have enclosed them below \;in different typefaces.\n\n  \;\n\n U+00F0 LATIN S MALL LETTER ETH\n\n U+00D0 LATIN CAPITAL LETTER ETH\n\n  \;\n\n U+0111 LATIN SMALL LETTER D WITH STROKE\n\n U+0110 LATIN CAPITAL LETTER D WITH STROKE\n\n  \;\n \n U+0256 LATIN SMALL LETTER D WITH TAIL\n\n U+0189 LATIN CAPITAL LETTER AFRICAN D\n\n  \;\n\n   \;\n\n I think this should be mentioned in the text and the rea son why we do not think it is a problem (if that is the conclusion).\n\n  \;\n\n Pasted in the same order as above with sm all letter a in between\, in in Helvetica\, Times New Roman and New Courie r:\n\n  \;\n\n aÐaĐaƉa\n\n\n aÐa ĐaƉa\n\n\n aÐaĐaƉa\n\n  \;\n\n T he same as picture:\n\n  \;\n\n\n\n 7. \; \;&nb sp\; \; \; Review of the Appendix E: Confusable.\n\n\n 8.  \; \; \; \; \; Next \;call \; \;to be decided during this call\n\n\n 9. \; \; \; \; \; AOB\n\n\n Regards\,\n\nPitinan\n UID:95464BAB-3019-402D-8143-636C73B1846B SUMMARY;LANGUAGE=en-US:Latin GP meeting DTSTART;TZID=UTC:20201105T170000 DTEND;TZID=UTC:20201105T180000 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20201104T110109Z TRANSP:OPAQUE STATUS:CONFIRMED SEQUENCE:1 LOCATION;LANGUAGE=en-US:https://icann.zoom.us/j/98435828760 X-MICROSOFT-CDO-APPT-SEQUENCE:1 X-MICROSOFT-CDO-OWNERAPPTID:2118854316 X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-CDO-ALLDAYEVENT:FALSE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INSTTYPE:0 X-MICROSOFT-DONOTFORWARDMEETING:FALSE X-MICROSOFT-DISALLOW-COUNTER:FALSE BEGIN:VALARM DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT15M ACTION:DISPLAY END:VALARM END:VEVENT END:VCALENDAR