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

RE: Reference Scheme for Mongolian Rendering

From: <jrmt@almas.co.jp>
Date: Tue, 25 Aug 2015 16:50:30 +0900
To: "'Greg Eck'" <greck@postone.net>, "'Richard Wordingham'" <richard.wordingham@ntlworld.com>, <public-i18n-mongolian@w3.org>
Message-ID: <000001d0df0a$b76aef50$2640cdf0$@co.jp>
The file attachment was not succeeded in the last mail. 
resending the  mail with attached file.


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/
http://www.mongolfont.com/
---------------------------------------------------------------
Inner Mongolia Delehi Information Technology Co. Ltd.
010010 13th floor of Uiles Hotel, No 89 XinHua east street 
XinCheng District, Hohhot, Inner Mongolia
Mail:  jirimutu@delehi.com       Mobile:18647152148
Phone:  +86-471-6661969,      Ofiice: +86-471-6661995
http://www.delehi.com/
===============================================================

-----Original Message-----
From: jrmt@almas.co.jp [mailto:jrmt@almas.co.jp] 
Sent: Tuesday, August 25, 2015 4:44 PM
To: 'Greg Eck'; 'Richard Wordingham'; public-i18n-mongolian@w3.org
Subject: RE: Reference Scheme for Mongolian Rendering

Hi Greg and Richard,

I have commented to your OverRides2.pdf with Red lines.
Please check if it is ok to modify the rule like this ?
I fell the original one could not cover all of the cases, And comment on it
with my suggestion.

Thanks and Best Regards,

PS. All of the glyph selection is based on current NP column definition in
the attached file.

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/
http://www.mongolfont.com/
---------------------------------------------------------------
Inner Mongolia Delehi Information Technology Co. Ltd.
010010 13th floor of Uiles Hotel, No 89 XinHua east street XinCheng
District, Hohhot, Inner Mongolia
Mail:  jirimutu@delehi.com       Mobile:18647152148
Phone:  +86-471-6661969,      Ofiice: +86-471-6661995
http://www.delehi.com/
===============================================================



-----Original Message-----
From: Greg Eck [mailto:greck@postone.net] 
Sent: Friday, August 14, 2015 7:14 PM
To: Richard Wordingham; public-i18n-mongolian@w3.org
Subject: RE: Reference Scheme for Mongolian Rendering

Hi Richard, 

Attached please find the rules for the four over-rides.
I did this a bit fast, everyone please look over carefully to see if I made
a mistake.

Thanks,
Greg


-----Original Message-----
From: Richard Wordingham [mailto:richard.wordingham@ntlworld.com] 
Sent: Friday, August 14, 2015 8:56 AM
To: public-i18n-mongolian@w3.org
Subject: Reference Scheme for Mongolian Rendering

Looking at Greg's list of data sets (DS...) in his post of Saturday 8th
August ('Mongolian Variation Sequences Missing from Unicode 8.00 Code
Chart',
http://lists.w3.org/Archives/Public/public-i18n-mongolian/2015JulSep/0248.ht
ml
), we are missing two important items:

1) A reference scheme for rendering.  I offer one in the attachment
rendering_framework.odt.

2) The rules for contextual forms that may be overridden by variation
selectors.  Without these rules, we do not know whether we have an adequate
set of variation selectors for rendering connected text.

I am trying to identify the contextual rules, though I am not the best
person for the job.  NNBSP has me worried.  Do we need to identify suffix
rules for every language that might conceivably be written in the Mongolian
script with separated suffixes?

Richard.



Received on Tuesday, 25 August 2015 07:51:06 UTC

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