From: Kenichi Handa <handa@gnu.org>
To: handa@gnu.org (K. Handa)
Cc: 16007@debbugs.gnu.org
Subject: bug#16007: admin/charsets/mule-charsets.el requires old Emacs version
Date: Wed, 01 Jan 2014 00:13:01 +0900 [thread overview]
Message-ID: <8738l9xddu.fsf@gnu.org> (raw)
In-Reply-To: <87k3eupa3s.fsf@gnu.org> (handa@gnu.org)
In article <87k3eupa3s.fsf@gnu.org>, handa@gnu.org (K. Handa) writes:
> I am still wondering how to solve this problem. At least,
> the docstring of indian-is13194 should state that the
> current implementation of that charset is for Devanagari
> users only if we suply the unify-map as your patch.
> The better will be to provide a different unify map for
> different lang. env. But, as IS13194 is used very rarely
> now, I'm not sure it's worth making such an effort.
> Please give me some more time to decide what to do for the
> next release.
I've just committed your changes plus the modification of
the docstring of the charset indian-is13194.
Happy new year (JST)!
---
Kenichi Handa
handa@gnu.org
next prev parent reply other threads:[~2013-12-31 15:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 1:54 bug#16007: admin/charsets/mule-charsets.el requires old Emacs version Glenn Morris
2013-11-30 10:48 ` Eli Zaretskii
2013-11-30 18:16 ` Glenn Morris
2013-11-30 18:38 ` Eli Zaretskii
2013-12-02 14:29 ` Kenichi Handa
2013-12-02 16:36 ` Eli Zaretskii
2013-12-03 14:50 ` Kenichi Handa
2013-12-03 15:59 ` Eli Zaretskii
2013-12-10 11:48 ` K. Handa
2013-12-10 17:40 ` Eli Zaretskii
2013-12-11 9:30 ` K. Handa
2013-12-11 16:16 ` Eli Zaretskii
2013-12-23 18:52 ` Eli Zaretskii
2013-12-24 15:00 ` K. Handa
2013-12-24 17:35 ` Eli Zaretskii
2013-12-31 15:13 ` Kenichi Handa [this message]
2013-12-31 15:18 ` Eli Zaretskii
2014-01-01 14:28 ` Kenichi Handa
2014-01-01 16:04 ` Eli Zaretskii
2014-01-02 1:49 ` Kenichi Handa
2014-01-02 3:40 ` Eli Zaretskii
2014-06-07 8:15 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738l9xddu.fsf@gnu.org \
--to=handa@gnu.org \
--cc=16007@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.