bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: address@hidden: Chinese big5: hanyu pinyin tone marks]


From: Kenichi Handa
Subject: Re: address@hidden: Chinese big5: hanyu pinyin tone marks]
Date: Mon, 7 Jan 2002 13:03:45 +0900 (JST)
User-agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.1.30 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI)

Richard Stallman <address@hidden> writes:

> Can you handle this?

Ok.

> ------- Start of forwarded message -------
> To: address@hidden
> From: Dan Jacobson <address@hidden>
> Subject: Chinese big5: hanyu pinyin tone marks
[...]
> For Hanyu pinyin Big5 input, please put these tone symbols on
> v1 v2 v3 v4 v5
[...]

As I wrote before, translation rules of some input methods
are generated from *.tit file, and it is better to avoid
modifying that file because we may get a newer version from
the other source (e.g. from the distribution of CXTERM).
So, I'm going to make a general mechanism to add Emacs' own
translation rules to the existing rules.  I'll design an API
that is also usable by users.  Then, a user doesn't have to
copy the whole *.el (of input-method) and modify it.

By the way...
> actually for v1 one really should have a high bar... so maybe find one
> from the symbol set and use it instead.  For the 5th [light] tone also
> add a hollow circle too.

It seems that A3BB..A3BF of Big5 are for tone marks.

---- extracted from BIG5.TXT found under www.unicode.org -------------
0xA3BB  0x02D9  # DOT ABOVE (Mandarin Chinese light tone)
0xA3BC  0x02C9  # MODIFIER LETTER MACRON (Mandarin Chinese first tone)
0xA3BD  0x02CA  # MODIFIER LETTER ACUTE ACCENT (Mandarin Chinese second tone)
0xA3BE  0x02C7  # CARON (Mandarin Chinese third tone)
0xA3BF  0x02CB  # MODIFIER LETTER GRAVE ACCENT (Mandarin Chinese fourth tone)
----------------------------------------------------------------------

So, even if my Big5 font (and it seems that yours too)
doesn't have correct glyphs for A3BB and A3BC, I think we
should use those characters.

---
Ken'ichi HANDA
address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]