W3C mailing list search service

Search among 2,306,298 messages in the W3C mailing list archives:

This is page 1, displaying results 1-15 of 15

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

Date
Fri, 27 Jan 2017 19:10:09 +0800
Author
Liang Hai <lianghai@gmail.com>

Also — My group members support that we should name positional variants according to where they appear in writing instead of certain grammatical analysis. Eg, in a constructed word "á   á  Žá  " (N

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

Date
Fri, 27 Jan 2017 18:05:27 +0800
Author
Liang Hai <lianghai@gmail.com>

Just wanna mention here that — My group members (introduced in L2/17-052 http://www.unicode.org/L2/L2017/17052-mongolian-cmt.pdf) support the idea of introducing an explicit overriding mechanism (s

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

Date
Fri, 27 Jan 2017 16:51:51 +0900
Author
<jrmt@almas.co.jp>

Hi Greg, Yes. you are right. But in reality, the OE and UE is very hard to identify. We can see all of the overriding requirements on the UE (U1826). It is QUEUE, it means storehouse. Differentiate f

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

Date
Fri, 27 Jan 2017 04:04:32 +0000
Author
Greg Eck <greck@postone.net>

Hi Jirimutu, 1.) I am of the understanding and training that the 1825 will never occur in the context of the first example nor the 1823 – it will always be the 1826/1824 post initial syllable. Even

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

Date
Fri, 27 Jan 2017 12:16:08 +0900
Author
<jrmt@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 member

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

Date
Fri, 27 Jan 2017 01:56:34 +0000
Author
Greg Eck <greck@postone.net>

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? Regardi

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

Date
Fri, 27 Jan 2017 10:36:10 +0900
Author
<jrmt@almas.co.jp>

Hi Richard, I have not listed https://r12a.github.io/mongolian-variants/#char1887 in my last mail. Because, it is actually not modern character itself. All ALI GALI part we will not touch in modern u

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

Date
Fri, 27 Jan 2017 10:26:18 +0900
Author
<jrmt@almas.co.jp>

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 medial form, if we do not exclude (this

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

Date
Thu, 26 Jan 2017 09:16:04 +0000
Author
r12a <ishida@w3.org>

I suppose one thing to check is whether there are any characters that require more than 3 variant forms for the modern usage. (Should be easy to check quickly using the comparison chart.) For example

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

Date
Thu, 26 Jan 2017 17:10:07 +0900
Author
<jrmt@almas.co.jp>

Hi Greg, Thanks for sharing your work approach and related information to us. About the phase I approach, I am also strongly agree to clearly and without ambiguously define the StandardVaraint.txt. F

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

Date
Thu, 26 Jan 2017 11:42:27 +0900
Author
<jrmt@almas.co.jp>

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

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

Date
Thu, 26 Jan 2017 09:48:14 +0800
Author
Liang Hai <lianghai@gmail.com>

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 st

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

Date
Thu, 26 Jan 2017 10:30:21 +0900
Author
<jrmt@almas.co.jp>

Liang Hai, I am not sure you can read Mongolian or not ? But you are really not understanding current Unicode Mongolian Encoding standard is confusing users and the main reason is encoding a lot of A

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

Date
Wed, 25 Jan 2017 23:48:38 +0800
Author
Liang Hai <lianghai@gmail.com>

About variants, for now my major concerns are: 1. There is clear correspondence between modern variant forms and most (if not all) of those proposed historical ones. Isn't it a typical case that shou

Bordering clearly between Mordern Mongolian and Ancient Mongolian solution.

Date
Wed, 25 Jan 2017 19:19:31 +0900
Author
<jrmt@almas.co.jp>

(Resending by my registered mail address.) Hi Greg & Richard Ishida I am reading Mongolian Variant Form list on <https://r12a.github.io/mongolian-variants/> https://r12a.github.io/mongolian-variants/

Help and hints for using this service

W3C Member? Check the Member-only interface. W3C staff? Use the Team-only interface.