W3C home > Mailing lists > Public > public-i18n-mongolian@w3.org > January to March 2017

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

From: <jrmt@almas.co.jp>
Date: Fri, 27 Jan 2017 12:16:08 +0900
To: "'Greg Eck'" <greck@postone.net>, "'r12a'" <ishida@w3.org>, <public-i18n-mongolian@w3.org>
Cc: <foximoyi@icloud.com>, <csmhjy@126.com>, "'siqin'" <siqin@almas.co.jp>
Message-ID: <003201d2784b$b489b650$1d9d22f0$@almas.co.jp>
Hi Greg,

 

Please find attached override examples for the three characters.

 

*  Regarding 1836 over-ride, I can delete the override comment in the DS01 if you think that is better.

All of our team members and most of the end users in Inner Mongolia expecting to delete the “contents-driven and override” logic for U1836 and U1838 medial form.

 

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/

 <http://www.mongolfont.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:   <mailto:jirimutu@delehi.com> jirimutu@delehi.com       Mobile:18647152148

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

 <http://www.delehi.com/> http://www.delehi.com/

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

 

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

 

Hi Jirimutu,

 

I can understand most of your comments.

 

Can you help me with an example for medial FVS3 1825 override?

Also for medial 1831 medial override?

Also for medial 1833 medial override?

Regarding 1836 over-ride, I can delete the override comment in the DS01 if you think that is better.

 

Greg

 

>>>>> 

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

 

 

Hi Richard,

 

Yes. currently, in our DS01 or WG2, we have following characters need more than 4 variants.

1.  <https://r12a.github.io/mongolian-variants/#char182C> https://r12a.github.io/mongolian-variants/#char182C medial form, if we do not exclude  << OLE Object: Picture (Device Independent Bitmap) >> (this is not modern) or move  << OLE Object: Picture (Device Independent Bitmap) >>  and  << OLE Object: Picture (Device Independent Bitmap) >> (it is actually final) to final form, there is shortage.

2.  <https://r12a.github.io/mongolian-variants/#char182D> https://r12a.github.io/mongolian-variants/#char182D medial form, if we do not exclude  << OLE Object: Picture (Device Independent Bitmap) >> (this is not modern) or move  << OLE Object: Picture (Device Independent Bitmap) >> (it is actually final) to final form, there is shortage.

 

For several characters we need OVERWRITE TO DEFAULT FORM logic for modern Mongolian, we need to use extra one FVS for these characters. 

Currently we are using FVS3 sometimes, but using FVS1 alternatively in DS01. Actually, it is not the proper method for using FVS1 in the encoding principle, because FVS1 already have one encoding glyph. 

These characters are 

1.        <https://r12a.github.io/mongolian-variants/#char1822> https://r12a.github.io/mongolian-variants/#char1822     We are using FVS3 for medial U1822_I OVERRIDE (DS01). 

2.        <https://r12a.github.io/mongolian-variants/#char1825> https://r12a.github.io/mongolian-variants/#char1825 We have OVERRIDE requirement for medial form. But DS01 have not listed yet. We are using FVS3 by default in our font MWc.

3.        <https://r12a.github.io/mongolian-variants/#char1826> https://r12a.github.io/mongolian-variants/#char1826 We have OVERRIDE requirement for medial form. But DS01 have not listed yet. We are using FVS3 by default in our font MWc.

4.        <https://r12a.github.io/mongolian-variants/#char1828> https://r12a.github.io/mongolian-variants/#char1828 We have OVERRIDE requirement for medial form. But DS01 have not listed yet. We are using FVS3 or FVS2 by default in our font MWc.

5.        <https://r12a.github.io/mongolian-variants/#char182C> https://r12a.github.io/mongolian-variants/#char182C We have OVERRIDE requirement for medial form. But DS01 have no extra FVS to list it. If we remain  << OLE Object: Picture (Device Independent Bitmap) >> ,  << OLE Object: Picture (Device Independent Bitmap) >> ,  << OLE Object: Picture (Device Independent Bitmap) >>  as the Modern Mongolian and classify  << OLE Object: Picture (Device Independent Bitmap) >>  as ancient Mongolian, we have FVS3 left for OVERWRITE, otherwise, we will have FVS shortage on this character. Of cause, we cannot encode  << OLE Object: Picture (Device Independent Bitmap) >> and  << OLE Object: Picture (Device Independent Bitmap) >> as medial form.

6.        <https://r12a.github.io/mongolian-variants/#char182D> https://r12a.github.io/mongolian-variants/#char182D We have OVERRIDE requirement for medial form. But DS01 have no extra FVS to list it. If we remain  << OLE Object: Picture (Device Independent Bitmap) >> ,  << OLE Object: Picture (Device Independent Bitmap) >> ,  << OLE Object: Picture (Device Independent Bitmap) >>  as the Modern Mongolian and classify  << OLE Object: Picture (Device Independent Bitmap) >>  as ancient Mongolian, we have FVS3 or FVS2 left for OVERWRITE, otherwise, we will have FVS shortage on this character. Of cause, we cannot encode  << OLE Object: Picture (Device Independent Bitmap) >> as medial form.

7.        <https://r12a.github.io/mongolian-variants/#char1831> https://r12a.github.io/mongolian-variants/#char1831 We have OVERRIDE requirement for medial form. But DS01 have not listed yet. We are using FVS3 or FVS2 by default in our font MWc.

8.        <https://r12a.github.io/mongolian-variants/#char1833> https://r12a.github.io/mongolian-variants/#char1833 We may have OVERRIDE requirement for medial form. But DS01 have not listed yet. We are using FVS3 or FVS2 by default in our font MWc.

9.        <https://r12a.github.io/mongolian-variants/#char1836> https://r12a.github.io/mongolian-variants/#char1836 We do not allow OVERRIDE or TOGGLE for this character medial form. DS01 comments contents-driven and OVERRIDE default form in PDF. 

10.    <https://r12a.github.io/mongolian-variants/#char1838> https://r12a.github.io/mongolian-variants/#char1838 We do not allow OVERRIDE or TOGGLE for this character medial form. DS01 comments contents-driven in PDF.

 

OVERWRITE TO DEFAULT FORM is mean that if 

When we using content-driven logic to selected the character’s second or third or fourth form, but for irregular writing case, we need to change the writing form to default variant form.

 

>>>>> 

 

 


Received on Friday, 27 January 2017 03:16:45 UTC

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