From: Eli Zaretskii <eliz@gnu.org>
To: handa@gnu.org
Cc: 16007@debbugs.gnu.org
Subject: bug#16007: admin/charsets/mule-charsets.el requires old Emacs version
Date: Mon, 23 Dec 2013 20:52:09 +0200 [thread overview]
Message-ID: <83r493763q.fsf@gnu.org> (raw)
In-Reply-To: <83ppp3wefv.fsf@gnu.org>
Ping!
Is the patch suggested below correct, please?
> Date: Wed, 11 Dec 2013 18:16:36 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 16007@debbugs.gnu.org
>
> > From: handa@gnu.org (K. Handa)
> > Cc: rgm@gnu.org, 16007@debbugs.gnu.org
> > Date: Wed, 11 Dec 2013 18:30:35 +0900
> >
> > Does your change break mule-charsets.el working with Emacs
> > 22? If not, it's ok to keep it as is now, but if it breaks,
> > please revert your change.
>
> It is unusual to keep code in Emacs that specifically targets older
> versions. So no, I didn't keep the v22 code. But I could easily
> reinstate it, if that's a requirement, conditioned by the Emacs
> version.
>
> > > What about the problem with indian-is13194 in list-charset-chars --
> > > what is needed to fix that one?
> >
> > I'm sorry that I don't have a time to fix it yet.
>
> I think I know the reason: we didn't specify the mapping file for that
> charset, and didn't make that charset unified. Do you agree with the
> following patch? It makes list-charset-chars work again for this
> charset.
>
> --- lisp/international/mule-conf.el~ 2013-06-30 07:20:59.000000000 +0300
> +++ lisp/international/mule-conf.el 2013-12-11 16:13:53.778785000 +0200
> @@ -895,7 +895,8 @@
> :emacs-mule-id 225
> :supplementary-p t
> :code-space [33 126]
> - :code-offset #x180000)
> + :code-offset #x180000
> + :unify-map "MULE-is13194")
>
> (let ((code-offset #x180100))
> (dolist (script '(devanagari sanskrit bengali tamil telugu assamese
> @@ -1197,6 +1198,7 @@
> (unify-charset 'japanese-jisx0212)
> (unify-charset 'japanese-jisx0213-1)
> (unify-charset 'japanese-jisx0213-2)
> +(unify-charset 'indian-is13194)
>
> \f
> ;; These are tables for translating characters on decoding and
>
>
>
>
next prev parent reply other threads:[~2013-12-23 18:52 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 [this message]
2013-12-24 15:00 ` K. Handa
2013-12-24 17:35 ` Eli Zaretskii
2013-12-31 15:13 ` Kenichi Handa
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=83r493763q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16007@debbugs.gnu.org \
--cc=handa@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.