unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 34862@debbugs.gnu.org
Subject: bug#34862: 27.0.50; Trying to update pinyin.map
Date: Fri, 15 Mar 2019 09:04:54 +0200	[thread overview]
Message-ID: <83ef781uuh.fsf@gnu.org> (raw)
In-Reply-To: <87o96cbrwp.fsf@ericabrahamsen.net> (message from Eric Abrahamsen on Thu, 14 Mar 2019 22:58:14 -0700)

> From: Eric Abrahamsen <eric@ericabrahamsen.net>
> Cc: 34862@debbugs.gnu.org
> Date: Thu, 14 Mar 2019 22:58:14 -0700
> 
> > I'm not sure I understand the encoding of which file would you like to
> > change?  Could you please clarify?
> 
> Sorry, I'm trying to add more characters to ./leim/MISC-DIC/pinyin.map,
> which is encoded as chinese-iso-8bit-dos, and it can't accept the new
> characters with that current encoding. That's the file I'd like to
> change.

That file is imported from an external source, isn't it?  Are you
saying we should stop synchronizing it with that source, and instead
fork it, maintain our own separate copy, and never resync with that
source again?  If so, then I see no reason not to recode it in UTF-8.

Btw, I understand that the Google pinyin method is Apache licensed,
but does this mean we can freely use its data for updating pinyin.map?
IANAL.  Could you perhaps describe how you intend to extract the data
from the Google input method for the purpose of updating our file?  I
think someone will have to audit that process for being legal and
compatible with both the Apache license and the GPL.

(Also, I'm somewhat surprised that gbk isn't capable of covering the
characters you want to add.  Or did you not try using it?)

Thanks.





  reply	other threads:[~2019-03-15  7:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 21:49 bug#34862: 27.0.50; Trying to update pinyin.map Eric Abrahamsen
2019-03-15  5:03 ` Eli Zaretskii
2019-03-15  5:58   ` Eric Abrahamsen
2019-03-15  7:04     ` Eli Zaretskii [this message]
2019-03-15 18:31       ` Eric Abrahamsen
2019-03-20  9:45         ` Eli Zaretskii
2019-03-20 19:30           ` Eric Abrahamsen
2019-03-20 19:39             ` Eli Zaretskii
2019-03-20 19:41               ` Eric Abrahamsen
2022-02-02 18:59             ` Lars Ingebrigtsen
2022-02-08  0:26               ` Eric Abrahamsen
2022-02-08  6:12                 ` Lars Ingebrigtsen

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=83ef781uuh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34862@debbugs.gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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).