From xemacs-m  Wed Sep  3 06:25:19 1997
Received: from Flux.tokai.jaeri.go.jp (root@flux.tokai.jaeri.go.jp [133.53.13.28])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id GAA01580
	for <xemacs-beta@xemacs.org>; Wed, 3 Sep 1997 06:25:18 -0500 (CDT)
Received: from localhost (localhost [127.0.0.1])
	by Flux.tokai.jaeri.go.jp (8.8.5/8.8.5) with ESMTP id UAA14105;
	Wed, 3 Sep 1997 20:25:17 +0900
To: xemacs-beta@xemacs.org
Cc: furutaka@Flux.tokai.jaeri.go.jp
Subject: Re: [Success] XEmacs 20.3-beta19 "Kyiv" on Linux-2.0.30, but...
In-Reply-To: Your message of "03 Sep 1997 00:44:22 -0700"
	<m2n2lukfjd.fsf@altair.xemacs.org>
References: <m2n2lukfjd.fsf@altair.xemacs.org>
X-Mailer: Mew version 1.90 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
X-Pgp-Fingerprint: 14 2B DA A1 31 70 7E A6  18 24 7E 03 EB 4D B3 64
X-Pgp-Public-Key: mailto:pgp-public-keys@icat.or.jp / Subject: GET 0x4734C8B5
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <19970903202516H.furutaka@Flux.tokai.jaeri.go.jp>
Date: Wed, 03 Sep 1997 20:25:16 +0900
From: Kazuyoshi Furutaka <furutaka@Flux.tokai.jaeri.go.jp>
X-Dispatcher: imput version 970830
Lines: 22

In <m2n2lukfjd.fsf@altair.xemacs.org>
at 03 Sep 1997 00:44:22 -0700
SL Baur <steve@xemacs.org> wrote
on "Re: [Success] XEmacs 20.3-beta19 "Kyiv" on Linux-2.0.30, but..."...

> > Signaling: (error "No such coding system" iso-2022-ss2-7)
> 
> This coding-system is now named iso-2022-7bit-ss2 (to synch with Emacs 
> 20 :-( ).  Sorry for the confusion.

Is there any GOOD AND SIMPLE way for an application to determine
whether the new coding system should be used or not (for compatibility
of an elisp package with older [X]Emacs/Mule)?

Yes, we can use emacs-{major,minor,beta}-version, but the code will be UGLY.

Kazuyoshi
--
Kazuyoshi Furutaka
furutaka@Flux.tokai.jaeri.go.jp


