unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@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: Tue, 10 Dec 2013 19:40:38 +0200	[thread overview]
Message-ID: <83d2l4y57t.fsf@gnu.org> (raw)
In-Reply-To: <87d2l56i6c.fsf@gnu.org>

> From: handa@gnu.org (K. Handa)
> Cc: rgm@gnu.org, 16007@debbugs.gnu.org
> Date: Tue, 10 Dec 2013 20:48:11 +0900
> 
> > > > Is the effort of making it work with MULE-is13194.map is
> > > > so significant?
> > > 
> > > ??? I'm saying that such an effort is useless.  If someone
> > > want to generate those maps, he/she should use Emacs 22.
> 
> > I don't understand: are you saying that these maps are not used at all
> > in Emacs 23 and later?  In that case, we should simply delete them
> > from the repository.
> 
> They are surely used as well as the other maps
> (e.g. Uni2JIS) which can never be re-generated if the source
> internet sites are gone.
> 
> > But if these files _are_ used by latest Emacsen, then having to look
> > for an old Emacs 22 binary in order to produce them is a nuisance.
> > E.g., imagine that the maps have been lost for some reason (like some
> > disaster on Savannah), and need to be regenerated.
> 
> I think it is a nuisance to prepare for such a disaster.
> But, if we are going to do that, as such a disaster will
> happen on any other internet sites, we should have a program
> to re-generate all charsets (and perhaps all uni-*.el).

I see.

What about the problem with indian-is13194 in list-charset-chars --
what is needed to fix that one?

Thanks.





  reply	other threads:[~2013-12-10 17:40 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 [this message]
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
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

  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=83d2l4y57t.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 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).