From: Sebastian Tennant <sebyte@smolny.plus.com>
Subject: Re: Same non-ASCII characters not 'equal'
Date: Thu, 17 Aug 2006 10:23:42 +0300 [thread overview]
Message-ID: <87r6zfomf5.fsf@dellboy.org> (raw)
In-Reply-To: m3irkudcc1.fsf@lugabout.jhcloos.org
Quoth James Cloos <cloos@jhcloos.com>:
>>>>>> "Sebastian" == Sebastian Tennant <sebyte@smolny.plus.com> writes:
> Sebastian> Take 'child' and 'çocuk' for instance. Because the (turkish-postfix)
> Sebastian> input method is inherited in the minibuffer you have to type
> Sebastian> 'c h i 2 l d' to enter 'child' and a match is found, but when you
> Sebastian> enter 'çocuk' by typing 'c , o c u k', no match is found. Could this
> Sebastian> be a bug even?
>
> Emacs versions other than the emacs-unicode-2 branch store each of the
> iso-8859-x glyphsets separately. You are probably ending up with the
> 8859-1 (Latin 1) version of U+00E7 LATIN SMALL LETTER C WITH CEDILLA
> in the elisp; using the turkish-postfix input method most likely uses
> 8859-9 (Latin 5).
I don't think this is the problem as I'm working with a unicode
terminal, and the encodings used for read and write are mule-utf-8
> One way to make latin1’s ç and latin5’s ç match is to use one or both
> of unify-8859-on-decoding-mode and/or unify-8859-on-encoding-mode.
I've tried setting these variables in the temporary buffer, without
success.
> Or, make sure you use the same encoding to enter the elisp that your
> users will use. There are commands to convert the current buffer to
> a different encoding.
Everything is mule-utf-8.
> Since I’ve moved almost exclusively to the unicode-2 branch, I don’t
> remember the specifics of the unify-8859 modes, but they are documented
> in info.
I'm not sure what you mean by unicode-2 branch
(emacs-version)
"GNU Emacs 21.4.1 (i486-pc-linux-gnu)
of 2006-05-15 on trouble, modified by Debian"
> -JimC (who has been caught by this issue before)
Thanks for your help Jim, but I'm still stuck :-(
I've managed to establish that the problem is caused by either the
read or write to disk, or both. If the dictionary is defined in the
function, matches are found without a problem. It's only when the
dictionary is populated from disk when matches of non-ASCII characters
fail.
Can you think of anything else I can try?
Perhaps a few variable checks in the code, to help diagnose the
problem?
Sebastian
next prev parent reply other threads:[~2006-08-17 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 11:44 Same non-ASCII characters not 'equal' Sebastian Tennant
2006-08-15 1:20 ` James Cloos
2006-08-17 7:23 ` Sebastian Tennant [this message]
2006-08-17 16:49 ` James Cloos
2006-08-21 12:25 ` Sebastian Tennant
2006-08-21 13:15 ` James Cloos
[not found] <mailman.5138.1155469477.9609.help-gnu-emacs@gnu.org>
2006-08-13 16:56 ` Pascal Bourguignon
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=87r6zfomf5.fsf@dellboy.org \
--to=sebyte@smolny.plus.com \
/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.
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).