unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: tumashu  <tumashu@163.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re:Re: [ELPA] New package: pyim
Date: Mon, 22 Feb 2021 11:20:29 +0800 (CST)	[thread overview]
Message-ID: <1ec6a274.1f71.177c7c0ae20.Coremail.tumashu@163.com> (raw)
In-Reply-To: <jwvim6kstez.fsf-monnier+emacs@gnu.org>



>There's a fair bit of that discussion written in a language I sadly
>can't read.  What's still missing? 

Not missing  at the moment :-) I think.


>> * Need help
>>
>> pyim-pymap.el's  (https://github.com/tumashu/pyim/blob/master/pyim-pymap.el) 
>>
>>  Chinese char pinyin info come from rime's 
>> luna-pinyin-simple. (https://github.com/rime/rime-luna-pinyin)
>>
>> while lun-pinyin-simple's Chinese char pinyin come from android project
>>
>> http://android.git.kernel.org/?p=platform/packages/inputmethods/PinyinIME.git
>>
>> I do not know how to deal with this issue :-\
>
>This is quite outside of my area of expertise, so I don't really
>understand what this is about, but if the issue is to find a pinyin
>table, 

yes. 

then Emacs already comes with one, so we could both

yes, the problem is that the pinyin.map in emacs do not include many Chinese Char.
it is a *small* table :-)

pyim use it before.

>arrange for Emacs to make it available in a more convenient form
>(currently it's only available in the form of an input method, which may
>be somewhat inconvenient to work with), and we could create a GNU ELPA
>package containing it (or just add it to pyim) for use with older Emacsen.


>
>
>        Stefan
>

  reply	other threads:[~2021-02-22  3:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22  2:42 [ELPA] New package: pyim tumashu
2021-02-22  2:55 ` tumashu
2021-02-22  3:01 ` [ELPA] " Stefan Monnier
2021-02-22  3:20   ` tumashu [this message]
2021-02-22  4:42     ` Stefan Monnier
2021-02-22  4:56       ` tumashu
2021-02-22  6:31         ` Eric Abrahamsen
2021-02-22  6:49           ` tumashu
2021-02-22  8:19             ` Clément Pit-Claudel
2021-02-22  8:47               ` tumashu
2021-02-22 16:29     ` Zhu Zihao
2021-02-22 16:36       ` Zhu Zihao
2021-02-22 17:02         ` Clément Pit-Claudel
2021-02-23  6:11       ` tumashu
2021-02-22 15:09   ` Eli Zaretskii
2021-02-22 17:41     ` Robert Pluim
2021-02-22 18:28       ` Eli Zaretskii
2021-02-22 18:40         ` Robert Pluim
2021-02-22 18:51           ` Eli Zaretskii
2021-02-22 22:27             ` Stefan Monnier
2021-02-23  3:30               ` Eli Zaretskii
2021-02-23  5:07                 ` Stefan Monnier
2021-02-23  9:08                   ` tumashu
2021-02-23 15:18                   ` Eli Zaretskii
2021-02-23 16:17                     ` Stefan Monnier
2021-02-23 16:37                       ` Eli Zaretskii
2021-03-07  8:44                     ` William Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1ec6a274.1f71.177c7c0ae20.Coremail.tumashu@163.com \
    --to=tumashu@163.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).