RE: Bordering clearly between Mordern Mongolian and Ancient Mongolian solution.

Hi Liang Hai,

 

I am sorry, I did misunderstand your e-mail meaning.

I apologies for my last e-mail.

 

Thanks to declaration and hope the proposal get more Experts understandings

Let us work together to get the Mongolian Unicode Encoding improved and unified on the several arguing points.

 

Thanks and Best Regards,

 

Jirimutu

===============================================================

Almas Inc. 

101-0021 601 Nitto-Bldg, 6-15-11, Soto-Kanda, Chiyoda-ku, Tokyo

E-Mail: jrmt@almas.co.jp <mailto: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 <mailto:jirimutu@delehi.com>        Mobile:18647152148

Phone:  +86-471-6661969,      Ofiice： +86-471-6661995

http://www.delehi.com/

===============================================================

 

From: Liang Hai [mailto:lianghai@gmail.com] 
Sent: Thursday, January 26, 2017 10:48 AM
To: jrmt@almas.co.jp
Cc: Greg Eck <greck@postone.net>; r12a <ishida@w3.org>; public-i18n-mongolian@w3.org; foximoyi@icloud.com; csmhjy@126.com; siqin <siqin@almas.co.jp>
Subject: RE: Bordering clearly between Mordern Mongolian and Ancient Mongolian solution.

 

  <https://tr.cloudmagic.com/h/v6/emailtag/tag/1485395294/2b566f421423f5d0ca9f4185f69ad7cc/10a8f86eb471143d1a21b676521d3e60/ed059d35ffd374342358d38a3d5fdb9f/1a0a5ddb8ada1ff4c0d062e5a8719a01/newton.gif> Hi, Mr Jirimutu,

 

I think you might've misunderstood me a lot…

 

I'm basically on your side.

 

The 1st point in my last email was saying I'm against the mixing of modern and historical variants in the standard (L2/16-309 is mad). I think it's unwise to encode historical variants now when the Mongolian script's modern usage is still a mess to be resolved — exactly on your side I think, isn't it? Actually for now I don't even think those historical variants should be encoded ever because they seem to be fonts' responsibility.

 

The 2nd point was about that we need to be careful about mixing VS and FVS when we have to use them together some day. This point is not against your idea either. I don't even think we should introduce VS for Mongolian now, because modern variants won't need them and historical variants shouldn't be considered now — but just in case L2/16-309 gets favored by the China national body, we need to be prepared.

 

For now I just really want those modern variants to be settled down (preferably without historical variants' intervention), the NNBSP issue to be resolved — see my comments in L2/17-052: http://www.unicode.org/L2/L2017/17052-mongolian-cmt.pdf

 

No, I don't read Mongolian, but I'm a multilingual font technician who've started to work on Mongolian's Unicode and OpenType technologies with help from experts who know Mongolian (the script, and both the Mongolian and Manchu languages) very well (see L2/17-052).

 

I really hope this clears your misunderstanding. Maybe, please read my last email again along with this email's clarification.

 

Glad to talk to you.

 

梁海 Liang Hai