- From: Greg Eck <greck@postone.net>
- Date: Thu, 6 Aug 2015 02:37:06 +0000
- To: Richard Wordingham <richard.wordingham@ntlworld.com>
- CC: "jrmt@almas.co.jp" <jrmt@almas.co.jp>, "public-i18n-mongolian@w3.org" <public-i18n-mongolian@w3.org>
Hi Richard, I am not quite clear on your reply. If we deal only with the textual specification, are you saying that the actual current spec for U+1820 should look like this with the "NotUsed" lines actually in the spec? I am not talking about the implementation at this point. ISOLATE 1820+NoFVS SpecificationDescription 1820+FVS1 SpecificationDescription 1820+FVS2 NotUsed 1820+FVS3 NotUsed INITIAL 1820+NoFVS SpecificationDescription 1820+FVS1 NotUsed 1820+FVS2 NotUsed 1820+FVS3 NotUsed MEDIAL 1820+NoFVS SpecificationDescription 1820+FVS1 SpecificationDescription 1820+FVS2 SpecificationDescription 1820+FVS3 NotUsed FINAL 1820+NoFVS SpecificationDescription 1820+FVS1 SpecificationDescription 1820+FVS2 NotUsed 1820+FVS3 NotUsed Greg -----Original Message----- From: Richard Wordingham [mailto:richard.wordingham@ntlworld.com] Sent: Thursday, August 6, 2015 10:23 AM To: Greg Eck <greck@postone.net> Cc: jrmt@almas.co.jp; public-i18n-mongolian@w3.org Subject: Re: New Thread - FVS Assignment MisMatch On Thu, 6 Aug 2015 01:56:08 +0000 Greg Eck <greck@postone.net> wrote: > If we take one example from the font comparator site > (http://r12a.github.io/scripts/mongolian/variants ) and look at > U+1820. We see that Isolate+FVS1 is specified. Isolate+FVS2 AND > Isolate+FVS3 are not specified as they are "don't care conditions". > These two sequences are left to the judgment of the font designer to > handle. No. <U+1820, FVS3> must be treated the same as U+1820, for the variation sequence is not defined. Once <U+1820, FVS2> ceases to be specified for any position, then the same will apply to <U+1820, FVS2>. It is not clear what should happen if only some positional variants are defined for a variation sequence. Richard.
Received on Thursday, 6 August 2015 02:37:41 UTC