all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16007@debbugs.gnu.org
Subject: bug#16007: admin/charsets/mule-charsets.el requires old Emacs version
Date: Thu, 02 Jan 2014 10:49:09 +0900	[thread overview]
Message-ID: <87wqijw3u2.fsf@gnu.org> (raw)
In-Reply-To: <83iou3zo1o.fsf@gnu.org> (message from Eli Zaretskii on Wed, 01 Jan 2014 18:04:19 +0200)

In article <83iou3zo1o.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

> > If you agree, I'll delete mule-charset.el and add proper
> > information to admin/charsets/mapfiles/README.

> I'm not sure we can distribute generated files without the programs
> that generated them.

They are not "generated files" in the same sence as, for
instance, PTCP154 is not a "generated file".

The files etc/charsets/MULE-*.map can not be generated
without an external source, and, in this case, that external
source is the ucs-tables.el in Emacs 22.  That situation is
the same as that etc/charsets/PTCP154.map can not be
generated without the external source
http://www.iana.org/assignments/charset-reg/PTCP154.

I don't know how
http://www.iana.org/assignments/charset-reg/PTCP154 is
generated and don't have a program to generate it.

Of course they both (and all othere charset maps) can be
generated if we have a running Emacs, but we don't have a
program to generate all of them.

> And even if we could, deleting a file because we
> don't want to maintain it sounds too drastic to me.

mule-charset.el is not what to be maintained.  It was once
used to generate MULE-*.map from Emacs 22.  It has already
finished the main role.  The only remaining role is to tell
peaple the origin of those map files as written in
admin/charsets/mapfiles/README:

------------------------------------------------------------
* MULE-*.map.gz

Created by using ../mule-charsets.el in Emacs 22 as this:
    % emacs-22 -batch -l ../mule-charsets.el
------------------------------------------------------------

> Why is it a problem to make changes in mule-charsets.el so that it
> could work both with Emacs 22 and with the latest versions of Emacs?

Because we don't have a reasonable explanation why we have
that file and keep it runnable with the latest Emacs.

> What do we lose if we make such a change in mule-charsets.el?

We will waste a time of future maintainers who must keep
that file runnable with the latest Emacs.  It's a waste
because such an effort yields nothing.

---
Kenichi Handa
handa@gnu.org





  reply	other threads:[~2014-01-02  1:49 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
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 [this message]
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=87wqijw3u2.fsf@gnu.org \
    --to=handa@gnu.org \
    --cc=16007@debbugs.gnu.org \
    --cc=eliz@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.