unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Van Ly <van.ly@sdf.org>
Cc: 52918@debbugs.gnu.org
Subject: bug#52918: 29.0.50; to make use of ucd/Unihan_Readings.txt for kDefinition entry
Date: Sun, 23 Jan 2022 08:00:01 +0200	[thread overview]
Message-ID: <83v8ybkn4u.fsf@gnu.org> (raw)
In-Reply-To: <Pine.NEB.4.64.2201230208400.10119@faeroes.freeshell.org> (message from Van Ly on Sun, 23 Jan 2022 02:15:06 +0000 (UTC))

> Date: Sun, 23 Jan 2022 02:15:06 +0000 (UTC)
> From: Van Ly <van.ly@sdf.org>
> cc: 52918@debbugs.gnu.org
> 
> On Mon, 3 Jan 2022, Eli Zaretskii wrote:
> 
> >>    . Unihan_Readings.txt
> >>
> >> Like how quail-show-key helps by showing in the minibuffer the input
> >> sequence needed to type a character for a specific input method, can
> >> there be a function called quail-show-unihan that exposes in the
> >> minibuffer the kDefinition entry associated with the East Asian
> >> character from ucd/Unihan_Readings.txt?
> >
> > Yes, this could be added to Emacs, and IMO would be a useful feature.
> >
> > Suggested implementation:
> >
> >  . import the Unihan_Readings.txt file into Emacs
> >  . add Makefile rules to produce a uni-unihan-readings.el file from
> >    Unihan_Readings.txt, which defines a char-table where each
> >    character has its kDefinition property value
> >  . code a minor mode which will show in the echo area the value of
> >    the kDefinition property, if any, of the character at point
> >
> > Patches welcome.
> >
> 
> See patch attached.
> 
> Two of the three implementation steps suggested are done.

Thanks.

You don't seem to have copyright assignment on file, and without that
we cannot accept such large contributions.  Would you like to start
your legal paperwork now?  If so, I will send you the form and the
instructions.





  parent reply	other threads:[~2022-01-23  6:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31 17:55 bug#52918: 29.0.50; to make use of ucd/Unihan_Readings.txt for kDefinition entry Van Ly
2022-01-03 13:54 ` Eli Zaretskii
2022-01-04 15:13   ` Van Ly
2022-01-17 18:25   ` Van Ly
2022-01-18 11:30     ` Van Ly
     [not found]   ` <Pine.NEB.4.64.2201230208400.10119@faeroes.freeshell.org>
2022-01-23  6:00     ` Eli Zaretskii [this message]
2022-01-23 11:22       ` Van Ly
2022-01-23 11:40         ` Eli Zaretskii
2023-07-25 15:44           ` Eli Zaretskii
2023-07-25 18:18             ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=83v8ybkn4u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52918@debbugs.gnu.org \
    --cc=van.ly@sdf.org \
    /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).