[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Prevent iso-8859 unification for some files?
From: |
Kenichi Handa |
Subject: |
Re: Prevent iso-8859 unification for some files? |
Date: |
Mon, 4 Feb 2002 14:26:15 +0900 (JST) |
User-agent: |
SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.1.30 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) |
Andreas Schwab <address@hidden> writes:
> Kenichi Handa <address@hidden> writes:
> |> Andreas Schwab <address@hidden> writes:
> |> > IMHO the right way to fix the ucs-table breakage is to use hex escapes
> |> > instead of literal characters, since the file depends on exact codes. If
> |> > you agree I'll do the necessary changes.
> |>
> |> There's an easier solution. We can make a new coding system
> |> that is same as iso-2022-7bit except for that it explicitly
> |> has a empty translation table.
> I don't think this is necessary, since using emacs-mule is already enough
> to prevent unification. But I still think that using hex escapes is
> better for future compatibility.
Why? Using hex escapes means that we embed internal
character codes. They will be changed in the future
(i.e. in unicode-base Emacs). But, emacs-mule and
iso-2022-7bit-no-trans are decoded correctly even in the
future.
And, it seems that it's a bug rather than a feature that
emacs-mule ignore translation table (I didn't notice it
until now :-().
By the way, as unicode-base Emacs won't need ucs-table.el,
we don't have to care for future compatibility.
---
Ken'ichi HANDA
address@hidden