From: Kenichi Handa <handa@m17n.org>
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: GNU Emacs 22.0.50 fails to find ä in different ISO Latin encodings
Date: Tue, 19 Sep 2006 12:58:31 +0900 [thread overview]
Message-ID: <E1GPWkh-0006ig-00@etlken> (raw)
In-Reply-To: <F021B5CA-A186-4AFB-B650-520DBB6261C4@Web.DE> (message from Peter Dyballa on Sun, 17 Sep 2006 15:42:59 +0200)
In article <F021B5CA-A186-4AFB-B650-520DBB6261C4@Web.DE>, Peter Dyballa <Peter_Dyballa@Web.DE> writes:
> Hello!
> Launched with -Q
> unify-8859-on-decoding-mode is nil
> unify-8859-on-encoding-mode is t
> I start i-search in an Unicode encoded buffer (*Help*). In an ISO
> 8859-1 encoded buffer ä and Ä are found, also in ISO 8859-10, ISO
> 8859-13 (except for Ä), ISO 8859-14, and ISO 8859-16 encoded buffers,
> but fails in ISO 8859-2, ISO 8859-3, ISO 8859-4, ISO 8859-9, and ISO
> 8859-15. It is similiar to ö and ü, accept that these are not found
> in the ISO 8859-14 encoded buffer. Changing unify-8859-on-decoding-
> mode's value makes no difference.
This is the story I remember.
A while ago, I proposed to change isearch so that it
translates characters by translation-table-for-input to
solve such a problem, but there raised an objection that
read-char should do that translation. RMS asked to check if
such a change to read-char is surely safe or not, but as
such a check is very difficult and time-consuiming, no one
took on the job.
So, this problem is still unfixed.
I again propose to change isearch. When we know that
changing read-char is safe in the future, we can cancel that
change in isearch.
---
Kenichi Handa
handa@m17n.org
next parent reply other threads:[~2006-09-19 3:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F021B5CA-A186-4AFB-B650-520DBB6261C4@Web.DE>
2006-09-19 3:58 ` Kenichi Handa [this message]
2006-09-19 6:43 ` GNU Emacs 22.0.50 fails to find ä in different ISO Latin encodings David Kastrup
2006-09-19 22:57 ` Richard Stallman
2006-09-20 7:10 ` Kenichi Handa
2006-09-20 7:43 ` Peter Dyballa
2006-09-20 8:05 ` Kenichi Handa
2006-09-20 11:17 ` Peter Dyballa
2006-09-21 2:13 ` Kenichi Handa
2006-09-21 8:09 ` Peter Dyballa
2006-09-21 23:22 ` Peter Dyballa
2006-09-22 0:44 ` Miles Bader
2006-09-22 9:06 ` Peter Dyballa
2006-09-22 10:31 ` Miles Bader
2006-09-22 10:55 ` Peter Dyballa
2006-09-22 11:27 ` Miles Bader
2006-09-22 22:54 ` Peter Dyballa
2006-09-22 23:25 ` Miles Bader
2006-09-23 8:45 ` Peter Dyballa
2006-09-24 1:51 ` Miles Bader
2006-09-23 3:34 ` Richard Stallman
2006-09-23 5:18 ` Miles Bader
2006-09-24 2:10 ` Richard Stallman
2006-09-22 1:06 ` Kenichi Handa
2006-09-22 9:32 ` Peter Dyballa
2006-09-21 17:20 ` Richard Stallman
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=E1GPWkh-0006ig-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@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).