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

RE: FVS Assignment for A

From: <jrmt@almas.co.jp>
Date: Mon, 10 Aug 2015 11:58:01 +0900
To: "'Richard Wordingham'" <richard.wordingham@ntlworld.com>, <public-i18n-mongolian@w3.org>
Message-ID: <000301d0d318$5ec66300$1c532900$@almas.co.jp>
Richard, 

> The purpose of free variation selectors is to overrule the decisions of
the basic context rules.
I did not see this explanation yet.
As my understanding is the MVS is prior than FVS.

> It's available at http://i.unu.edu/pub/techreports/report170a.tgz .
I got it from my colleague's hand. It is dated on 1999 and I saw this in
1998.
But I was not able to find that the ISO/IEC 10646/WG2 and Unicode Site
direct peoples to this document.
It is the valuable document for creating font in early time.
It is need to be updated on our discussion's conclusion.

> The second - fewer glyphs to write the hinting code for!
You misunderstanding me here.

> Additionally, in the OpenType scheme 'Replace the A with <Final_A> by
context' 
> would be part of a whole set of changes 'Replace X with <Final_X>' defined
as part of the "fina" feature.  
> The font does not need to define the context for this change; that is the
job of the OpenType layout engine.
Yes agree with you on this. Anyway, if you use medial BA_A + A/E to be the
glyph Final BA_A, you will cost more.

Jirimutu
==========================================================
Almas Inc.
101-0021 601 Nitto-Bldg, 6-15-11, Soto-Kanda, Chiyoda-ku, Tokyo
E-Mail: jrmt@almas.co.jp   Mobile : 090-6174-6115
Phone : 03-5688-2081,   Fax : 03-5688-2082
http://www.almas.co.jp/   http://www.compiere-japan.com/
==========================================================



-----Original Message-----
From: Richard Wordingham [mailto:richard.wordingham@ntlworld.com] 
Sent: Monday, August 10, 2015 3:01 AM
To: public-i18n-mongolian@w3.org
Subject: Re: FVS Assignment for A

On Mon, 10 Aug 2015 00:17:10 +0900
<jrmt@almas.co.jp> wrote:

> > We have a formal problem here.  How should <NA, A, NA, MVS, A,
> > FVS1> be rendered?  One might naively expect it to be rendered the 
> > FVS1> same as <NA, A, NA, MVS, A>.
> It should be same with <NA, A, NA, MVS, A>. 

> It is defined as "isol" in the MVS model ds00.pdf which we discussed 
> last month.

But <A-isolate, FVS1> is to be rendered as default isolated E!  That is
agreed by all fonts and definitions.  The purpose of free variation
selectors is to overrule the decisions of the basic context rules.

------------ 
> What I am talking is we need this kind on mapping separately in the 
> individual font or define it common to all font?

Each font has its own mappings.  For example, in one font identical glyphs
corresponding to different codepoints may have different PostScript names.
Another font might have no PostScript names.

-------------
> After this forum complete and getting conclusion, I think the glyph 
> set TR120 will be updated.

You're right in principle if you're talking about TR170.  Someone (you?)
posted a set of example words, and I can't find the link.  I want to check
the spelling of the name Ng.  I've a suspicion it's actually an isolated
ANG.

> Actually, I have not seen TR170 yet.
It's available at http://i.unu.edu/pub/techreports/report170a.tgz .

------------------

> The Variant Form mapping rule is the core.

I disagree.  The context rules are the core.  The job of the variant form
mappings is to overrule the results when they are inadequate.

------------------

> Just look one cooperation here:
> 1. Replacing final <BA, A> with < Final_BA_A glyph> one step
> 
> 2.  Replace BA before A with the <Medial_BA_A glyph>
>     Replace the A with the <Final_A> by context
>     Replace <Final_A> after <Medial_BA_A glyph> with 
> <Final_A_UNENCODED_2>
> 
> Which is simple and cheap?

The second - fewer glyphs to write the hinting code for!

Additionally, in the OpenType scheme 'Replace the A with <Final_A> by
context' would be part of a whole set of changes 'Replace X with <Final_X>'
defined as part of the "fina" feature.  The font does not need to define the
context for this change; that is the job of the OpenType layout engine.

Richard.
Received on Monday, 10 August 2015 02:58:20 UTC

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