From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 9653@debbugs.gnu.org
Subject: bug#9653: 24.0.50; `ucs-names' - Why all of the ("" . XXX) entries?
Date: Mon, 20 Feb 2012 09:39:55 +0900 [thread overview]
Message-ID: <tl7fwe65odg.fsf@m17n.org> (raw)
In-Reply-To: <jwvzkch5w1i.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 17 Feb 2012 10:25:21 -0500)
In article <jwvzkch5w1i.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> Could you take a look at this problem and replace the "" with nil for
>>> the name of unassigned chars?
> > Done.
> Thank you,
No, the original bug is not yet fixed. Perhaps I
misunderstood what you wanted me. I've done this part only
"replace the "" with nil for the name of unassigned chars".
If what you wanted me includes fixing this problem, please
ask the author of ucs-names. He should be able to work on
it much faster/easier than me. I've never read the code of
ucs-names.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2012-02-20 0:39 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tl74nupdi7g.fsf@m17n.org>
2012-02-17 15:25 ` bug#9653: 24.0.50; `ucs-names' - Why all of the ("" . XXX) entries? Stefan Monnier
[not found] ` <7CCDEE21B0ED42B097600BB24692952A@us.oracle.com>
2012-02-17 23:42 ` Stefan Monnier
2012-02-18 0:05 ` Drew Adams
[not found] ` <8339a8wp2m.fsf@gnu.org>
2012-02-18 19:08 ` Drew Adams
2012-02-20 0:39 ` Kenichi Handa [this message]
[not found] <<74B14D2A03144E798C9415172D5FE01A@us.oracle.com>
[not found] ` <<tl7fwe65odg.fsf@m17n.org>
2011-10-02 16:36 ` Drew Adams
2011-10-02 17:38 ` Drew Adams
2011-10-02 22:31 ` Juanma Barranquero
2011-10-02 22:51 ` Drew Adams
2011-10-02 22:55 ` Juanma Barranquero
2011-10-03 13:20 ` Jason Rumney
2011-10-03 13:56 ` Drew Adams
2011-10-03 14:00 ` Juanma Barranquero
2011-10-02 18:09 ` Thierry Volpiatto
2011-10-03 1:28 ` Stefan Monnier
2011-10-03 4:23 ` Kenichi Handa
2011-10-03 8:22 ` Andreas Schwab
2011-10-04 1:14 ` Kenichi Handa
2011-10-03 13:31 ` Stefan Monnier
2011-10-04 1:59 ` Kenichi Handa
2011-10-04 12:56 ` Stefan Monnier
2011-10-06 3:53 ` Kevin Rodgers
2011-10-06 12:19 ` Juanma Barranquero
2011-10-06 13:02 ` Andreas Schwab
2011-10-06 13:47 ` Juanma Barranquero
2011-10-06 14:01 ` Andreas Schwab
2011-10-06 14:02 ` Juanma Barranquero
2011-10-04 2:19 ` Drew Adams
2011-10-04 4:02 ` Kenichi Handa
2011-10-04 13:43 ` Drew Adams
2011-10-04 17:34 ` Drew Adams
2011-10-04 18:19 ` Eli Zaretskii
2011-10-04 18:30 ` Drew Adams
2011-10-04 20:55 ` Eli Zaretskii
2011-10-04 21:39 ` Stefan Monnier
2011-10-04 22:03 ` Drew Adams
2011-10-05 4:11 ` Eli Zaretskii
2011-10-05 13:20 ` Drew Adams
2011-10-05 17:24 ` Eli Zaretskii
2011-10-05 8:59 ` Kenichi Handa
2011-10-05 10:20 ` Eli Zaretskii
2011-10-05 12:40 ` Stefan Monnier
2011-10-06 18:02 ` Eli Zaretskii
2011-10-06 20:56 ` Stefan Monnier
2012-01-14 18:35 ` Drew Adams
2012-02-17 15:55 ` Drew Adams
2018-02-13 23:35 ` Drew Adams
2018-02-15 1:11 ` Noam Postavsky
2018-02-15 3:17 ` Drew Adams
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=tl7fwe65odg.fsf@m17n.org \
--to=handa@m17n.org \
--cc=9653@debbugs.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).