[Latingp] Sharp S variant set

[Tan Tanaka, Dennis]

Update: I’m trying to address the outstanding comment on page 65 regarding the additional variants because of overlapping variants (“ss” and “s”). However, the resulting variant table to make the set a well-behaved one is a 378-line table. Inserting the entire table will disrupt the flow of the document. I believe our best option is to make the commentary here (in page 65) and show the complete table in an appendix section. I will draft preliminary text for the chief editors to work with.

I will upload my copy with these edits, along with other commentary by end of today.

Dennis

From: Dennis Tan Tanaka <dtantanaka at verisign.com>
Date: Monday, January 6, 2020 at 11:09 AM
To: "Tan Tanaka, Dennis via Latingp" <latingp at icann.org>
Subject: Re: Sharp S variant set

I forgot to mention.

The variant relationships I considered were based on the current version of the proposal. If I missed any variant relationship please let me know and I can add it to the XML.

From: Dennis Tan Tanaka <dtantanaka at verisign.com>
Date: Monday, January 6, 2020 at 11:04 AM
To: "Tan Tanaka, Dennis via Latingp" <latingp at icann.org>
Subject: Sharp S variant set

Mirjana, et al

Enclosed the corresponding XML for the variant set for Sharp S and related code points. I added the range 0061-007a for convenience while doing label testing. Once merged with our main XML this should not be an issue.

While doing label testing I found (what I think) it is an odd behavior, from the tool part, regarding rule order application. Pitinan is helping sorting that part out. But this file should be good for submitting to IP.

Any questions, let me know.

Best,
Dennis




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/latingp/attachments/20200107/281877a7/attachment.html>