From: tumashu <tumashu@163.com>
To: "Eric Abrahamsen" <eric@ericabrahamsen.net>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re:Re: [ELPA] New package: pyim
Date: Mon, 22 Feb 2021 14:49:10 +0800 (CST) [thread overview]
Message-ID: <2ed6a51a.3542.177c87fbd73.Coremail.tumashu@163.com> (raw)
In-Reply-To: <87y2fgbokl.fsf@ericabrahamsen.net>
At 2021-02-22 14:31:54, "Eric Abrahamsen" <eric@ericabrahamsen.net> wrote:
>tumashu <tumashu@163.com> writes:
>
>> At 2021-02-22 12:42:59, "Stefan Monnier" <monnier@iro.umontreal.ca> wrote:
>>>>>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.
>>>
>>>Even better.
>>>
>>>> yes, the problem is that the pinyin.map in Emacs do not include many Chinese Char.
>>>> it is a *small* table :-)
>>>
>>>Then we should improve it within Emacs, not just within pyim.
>>>
>>>Presumably there's an appropriately licensed pinyin map somewhere that's
>>>more complete, like maybe one used by some part of Gnome, or something?
>>>
>>>
>>> Stefan
>>>
>>
>> should We find a GPL license pinyin map?
>>
>> ibus-libpinyin's tabe come from android im too, it is Apache License Version 2.0
>> https://github.com/libpinyin/libpinyin/blob/master/data/opengram.license
>
>I went a little ways towards this in #34862, but it fizzled out:
>
>https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34862
>
>I'd be happy to help pitch in here.
the real quesiton for me, is that is it acceptable for GNU elpa by import and convert libpinyin's table to pyim.
If acceptable, no other things need to do, If not acceptable, I have replace the current pymap.el to other.
Chinese Char and Pinyin is the core basic of Chinese Language, really have **Copyright issues**? I doubt it.
next prev parent reply other threads:[~2021-02-22 6:49 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
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 [this message]
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=2ed6a51a.3542.177c87fbd73.Coremail.tumashu@163.com \
--to=tumashu@163.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--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).