W3C home > Mailing lists > Public > public-i18n-mongolian@w3.org > July to September 2015

Re: New Thread - FVS Assignment MisMatch

From: Richard Wordingham <richard.wordingham@ntlworld.com>
Date: Thu, 6 Aug 2015 03:22:34 +0100
To: Greg Eck <greck@postone.net>
Cc: "jrmt@almas.co.jp" <jrmt@almas.co.jp>, "public-i18n-mongolian@w3.org" <public-i18n-mongolian@w3.org>
Message-ID: <20150806032234.63006603@JRWUBU2>
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:23:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:07:04 UTC