- From: <jrmt@almas.co.jp>
- Date: Fri, 7 Aug 2015 10:06:46 +0900
- To: "'Greg Eck'" <greck@postone.net>, <public-i18n-mongolian@w3.org>
- Message-ID: <000801d0d0ad$556c60b0$00452210$@almas.co.jp>
Hi Greg, Here I continue my discussion around the FVS assignment for U1820-A. 1. I would like to amend one more glyph for f+FVS2. Please refer following picture. I saw you sugesstion image, it is not work on handwriting font. Please check the attached image which is zoomed to big enough to see clearly. 2. I can accept the I+FVS1 assignment, I do agree with Erdenchimeg's following comment. > Re point 3, the glyph at I+FVS1 (and M+FVS2 in NSM font) is only used after NNBSP, i.e. > it is always the first letter of a word suffix/case. > Teachers of Mongolian script always refer to this as initial form, which is the basis for the coding at I+FVS1. > However, in the Unicode standard the decision was made to code it as a middle form (basically because > it appears in the middle of the word), which is why it appears at M+FVS2 in some fonts. > I think the M+FVS2 combination could be omitted, as is done in BS. The M+FVS2 form of U1820_A should be omitted. We implemented our font as this. Just because our glyph rendering basic principle listed below, there are one M+FVS2 displaying on the <http://r12a.github.io/scripts/mongolian/variants> http://r12a.github.io/scripts/mongolian/variants If there are no different variant forms for FVS2 or FVS3, we implement it same with the default form or it means ignore the FVS2 or FVS3. It is not proper to become blank. The none in NP should give definition how to handle it, otherwise each implementation goes different direction. Thanks and Best Regards, Jirimutu ========================================================== Almas Inc. 101-0021 601 Nitto-Bldg, 6-15-11, Soto-Kanda, Chiyoda-ku, Tokyo E-Mail: <mailto:jrmt@almas.co.jp> jrmt@almas.co.jp Mobile : 090-6174-6115 Phone : 03-5688-2081, Fax : 03-5688-2082 <http://www.almas.co.jp/> http://www.almas.co.jp/ <http://www.compiere-japan.com/> http://www.compiere-japan.com/ ========================================================== From: Greg Eck [mailto:greck@postone.net] Sent: Friday, August 7, 2015 2:17 AM To: jrmt@almas.co.jp; public-i18n-mongolian@w3.org Subject: FW: New Thread - FVS Assignment MisMatch Hi Jirimutu, If we limit our comments to just the 6 FVS assignments, this is what I see . . You are in agreement with my suggestions for the suggestions being put before the UTC as outlined in my reponse to Erdenchimeg. . As to the new variant at U+1820/U+1821-Final swept left with no space - would it be something like the attached? This is the sequence < U+180A >< U+180A ><U+1820> with no MVS included. Would this not do? . You have further discussion on U+182D - let's wait until we find resolution on the 6 variant FVS assignments first. . You have further discussion on U+136 - let's wait until we find resolution on the 6 variant FVS assignments first. Greg From: jrmt@almas.co.jp [mailto:jrmt@almas.co.jp] Sent: Monday, August 3, 2015 7:01 AM To: Greg Eck <greck@postone.net>; public-i18n-mongolian@w3.org Subject: RE: New Thread - FVS Assignment MisMatch Hi Greg, I have some inputs in the FVS assignment MisMatch documents. Thanks and Regards, Jirimutu ========================================================== Almas Inc. 101-0021 601 Nitto-Bldg, 6-15-11, Soto-Kanda, Chiyoda-ku, Tokyo E-Mail: <mailto:jrmt@almas.co.jp> jrmt@almas.co.jp Mobile : 090-6174-6115 Phone : 03-5688-2081, Fax : 03-5688-2082 <http://www.almas.co.jp/> http://www.almas.co.jp/ <http://www.compiere-japan.com/> http://www.compiere-japan.com/ ========================================================== From: Greg Eck [ <mailto:greck@postone.net> mailto:greck@postone.net] Sent: Monday, August 3, 2015 12:14 AM To: <mailto:public-i18n-mongolian@w3.org> public-i18n-mongolian@w3.org Subject: New Thread - FVS Assignment MisMatch We are winding down on the NNBSP discussion. Let's go ahead with another topic as attached dealing with 6 FVS assignments. The basic issue is that the current specification says to make the assignment at one position whereas the glyph is processed by OT rulings at another position. Greg
Attachments
- image/png attachment: A_F_FVS2.png
Received on Friday, 7 August 2015 01:07:09 UTC