I looked at the material and then I wondered why U+045F CYRILLIC SMALL LETTER DZHE is matched to U+1EF1 LATIN SMALL LETTER U WITH HORN AND DOT BELOW and not to U+1EE5 LATIN SMALL LETTER U WITH DOT BELOW (which is also in our repertoire). I think that U+045F and U+1EE5 are more similar than U+045F and U+1EF1.First displayed as text in the mail:1EF1 045F 1EE5Times: ự џ ụHelvetica: ự џ ụCourier new: ự џ ụHere as a picture:Yours,Mats---Mats DufbergDNS Specialist, IISMobile: +46 73 065 3899-----Original Message-----From: Latingp <latingp-bounces@icann.org> on behalf of ICANN Latin GP <latingp@icann.org>Reply-To: "Tan Tanaka, Dennis" <dtantanaka@verisign.com>Date: Monday, 30 July 2018 at 04:57Subject: Re: [Latingp] Latin-Cyrillic cross-script analysisLatin GP,Based on Michael's and Bill's input I have resolved all the pending cases. These are highlighted as <green>include</green> or <red>excluded</red> in each of the sets. Review the comments for context as well.Please review the revised doc and provide any other comments you may have.Thanks,DennisOn 7/27/18, 11:30 AM, "Latingp on behalf of Michael Bauland" <latingp-bounces@icann.org on behalf of Michael.Bauland@knipp.de> wrote:Hi all,On 26.07.2018 21:12, Bill Jouris wrote:> I have reviewed these. In several cases, I believe it is possible to> resolve the issue using the same principle:> When both inspectors have the same rating for the highest ranked font,> and the only difference is between fonts, there seems no reason to look> further. Just take the agreed highest rating (for example 2) and move on.I agree with Bill. We decided to look at several fonts in order to findmore cases for possible variants (not to find less cases). Therefore itmakes sense to always take the rating from the highest ranked font. Incase both inspectors agree, there is nothing more to do.> I also noticed a couple of cases where the first inspector had a rating> of 5 (i.e. no candidate found) while the second inspector had something> else. Perhaps the first inspector could go back and consider the> candidate which, apparently, arose after his initial inspection. Even> if that results in a rating of 4 (different), it would at least give us> someplace to start discussion.Done. Those were my cases and I changed my original 5 to the ratingreferring to the newly found candidate.Furthermore I added my vote to the occasions were first and secondinspector disagreed (and Bill's suggestion from above does not work). Ifthe others could do the same, we could probably apply some majority vote.Have a nice weekendMichael--______________________ ______________________________ ________________| || knipp | Knipp Medien und Kommunikation GmbH------- TechnologieparkMartin-Schmeisser-Weg 944227 DortmundGermanyDipl.- Informatiker Fon: +49 231 9703-0Fax: +49 231 9703-200Dr. Michael Bauland SIP: Michael.Bauland@knipp.deSoftware Development E-mail: Michael.Bauland@knipp.deRegister Court:Amtsgericht Dortmund, HRB 13728Chief Executive Officers:Dietmar Knipp, Elmar Knipp_______________________ ________________________Latingp mailing list__________________________ _____________________Latingp mailing list
______________________________ _________________
Latingp mailing list
Latingp@icann.org
https://mm.icann.org/mailman/ listinfo/latingp