all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: 8859 unification and Emacs' ChangeLog files
Date: Mon, 31 Mar 2003 09:45:48 +0900 (JST)	[thread overview]
Message-ID: <200303310045.JAA14857@etlken.m17n.org> (raw)
In-Reply-To: <848yuy3xab.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@gmx.net)

In article <848yuy3xab.fsf@lucy.is.informatik.uni-duisburg.de>, kai.grossjohann@gmx.net (Kai Großjohann) writes:
> I've learned the hard way that unify-8859-on-decoding-mode mangles
> Emacs' ChangeLog files.  Now Simon (see Cc) has shown me that it is
> possible to turn unification off for certain encodings.

> Do you think it might be good to turn it off for iso-2022-7bit?
[...]
> Simon's Lisp was: (coding-system-put 'iso-2022-7bit
> 'translation-table-for-decode (make-translation-table))

Yes, it works because it overrides the translation table
created by unify-8859-on-decoding-mode.

But, it results in that a Latin-2 char read by iso-2022-7bit
is different from what read by iso-latin-2.  I don't think
such a change is a good idea.

> Maybe that would make it possible to turn unify-8859-on-decoding-mode
> on by default?

It will stop unibyte<->multibyte automatic conversion in any
single byte lang. env. (e.g. Latin-X, Greek) except for
Latin-1.

I think unify-8859-on-decoding-mode is still only for those
people who knows the consequence of the command well.

---
Ken'ichi HANDA
handa@m17n.org

  reply	other threads:[~2003-03-31  0:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-29 17:19 8859 unification and Emacs' ChangeLog files Kai Großjohann
2003-03-31  0:45 ` Kenichi Handa [this message]
2003-04-03 16:50   ` Kai Großjohann
2003-04-03 18:38     ` Stefan Monnier
2003-04-03 20:38     ` Jason Rumney
2003-04-03 20:52       ` Jason Rumney
2003-04-04 12:58       ` Kai Großjohann

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=200303310045.JAA14857@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=emacs-devel@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.