Dear colleagues, I have added my assigned stacking cases to my existing stacking diacritics document (attached). Happily, none of them appear to be problematic. Bill Jouris Inside Products bill.jouris@insidethestack.com 831-659-8360 925-855-9512 (direct) On Monday, July 8, 2019, 11:16:14 AM PDT, Mirjana Tasić <Mirjana.Tasic@rnids.rs> wrote: <!--#yiv8704368535 _filtered #yiv8704368535 {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv8704368535 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv8704368535 {font-family:"Calibri Light";panose-1:2 15 3 2 2 2 4 3 2 4;}#yiv8704368535 #yiv8704368535 p.yiv8704368535MsoNormal, #yiv8704368535 li.yiv8704368535MsoNormal, #yiv8704368535 div.yiv8704368535MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", sans-serif;}#yiv8704368535 h2 {margin-top:2.0pt;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;margin-bottom:.0001pt;font-size:13.0pt;font-family:"Calibri Light", sans-serif;color:#2F5496;font-weight:normal;}#yiv8704368535 a:link, #yiv8704368535 span.yiv8704368535MsoHyperlink {color:#0563C1;text-decoration:underline;}#yiv8704368535 a:visited, #yiv8704368535 span.yiv8704368535MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv8704368535 p.yiv8704368535MsoListParagraph, #yiv8704368535 li.yiv8704368535MsoListParagraph, #yiv8704368535 div.yiv8704368535MsoListParagraph {margin-right:0cm;margin-left:0cm;font-size:12.0pt;font-family:"Times New Roman", serif;}#yiv8704368535 span.yiv8704368535EmailStyle17 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv8704368535 span.yiv8704368535Heading2Char {font-family:"Calibri Light", sans-serif;color:#2F5496;}#yiv8704368535 .yiv8704368535MsoChpDefault {font-family:"Calibri", sans-serif;} _filtered #yiv8704368535 {margin:72.0pt 72.0pt 72.0pt 72.0pt;}#yiv8704368535 div.yiv8704368535WordSection1 {}#yiv8704368535 _filtered #yiv8704368535 {} _filtered #yiv8704368535 {margin-left:54.0pt;font-family:"Calibri", sans-serif;color:black;} _filtered #yiv8704368535 {margin-left:90.0pt;} _filtered #yiv8704368535 {margin-left:126.0pt;} _filtered #yiv8704368535 {margin-left:162.0pt;} _filtered #yiv8704368535 {margin-left:198.0pt;} _filtered #yiv8704368535 {margin-left:234.0pt;} _filtered #yiv8704368535 {margin-left:270.0pt;} _filtered #yiv8704368535 {margin-left:306.0pt;} _filtered #yiv8704368535 {margin-left:342.0pt;} _filtered #yiv8704368535 {} _filtered #yiv8704368535 {margin-left:54.0pt;font-family:"Calibri", sans-serif;color:black;} _filtered #yiv8704368535 {} _filtered #yiv8704368535 {} _filtered #yiv8704368535 {} _filtered #yiv8704368535 {} _filtered #yiv8704368535 {} _filtered #yiv8704368535 {} _filtered #yiv8704368535 {} _filtered #yiv8704368535 {}#yiv8704368535 ol {margin-bottom:0cm;}#yiv8704368535 ul {margin-bottom:0cm;}--> Dear GP members, Please find included some notes from our last call. Every comment, suggestion or update are appreciated. Regards Mirjana Notes from the call on 4th of July, 2019 1. URL Underlining analysis completed 2. Appendix D merger – Meikal made an oversight using Trello tool for keeping track what is missing in Appendix D. There are 14 items more which should be analyzed, beside some other items which are not finished by GP members from previous assignment. All assigned and not completed items has in the title of item the code(1 to 7) which marks to whom the item was assigned. The assignment of new 14 new items is proposed as follows: | No | Item | GP member | | 1. | Shape: Ring above vs Hook Above | 1 | | 2. | Shape: Ring above vs Dot Above | 2 | | 3. | Shape: Caron vs Horn above | 3 | | 4. | Stacking: Circumflex (above) and dot below | 4 | | 5. | Stacking: Breve above and dot below | 5 | | 6. | Stacking: Grave and dot below | 6 | | 7. | Stacking: Acute and dot below | 7 | | 8. | Stacking: Horn and Acute above | 1 | | 9. | Stacking: Horn and Tilde above | 3 | | 10. | Stacking: Horn and Dot below | 4 | | 11. | Stacking: Acute vs non acute | 5 | | 12. | IDNA Compatibility: i vs dotless i (overlaps with base character analysis) | 6 | | 13. | IDNA Compatibility: Sharp s vs sequence ss | 2 | | 14. | Visual analysis : turned e vs schwa | 7 | Finished analysis could be inserted inAppendix D merger, or sent to the list in an e-mail. - Seven members of the GP will get accounts with wordmark.it. Pitinan will inform GP when accounts will be ready for use. - GP decided to use rest of the time in the call to look at Michaels contribution in the report about sharp s vs ss and his consultations with German, Austrian and Swiss ccTLD. This part of the report is cleaned of some remarks, but it should be discussed again with other GP members which were not present on this call. - Visual Analysis of in-script variants was also added to the agenda. Meikal said that in this topic all homoglyphs in the script should be analyzed. Up to now he has proposed only one “turned e vs schwa” It was proposed that all members of the panel should pass through the defined Repertoire and propose any other code points for Visual analysis. _______________________________________________ Latingp mailing list Latingp@icann.org https://mm.icann.org/mailman/listinfo/latingp _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). 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.