From: James Cloos <cloos@jhcloos.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Same non-ASCII characters not 'equal'
Date: Mon, 14 Aug 2006 21:20:14 -0400 [thread overview]
Message-ID: <m3irkudcc1.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <87wt9cj1ww.fsf@dellboy.org> (Sebastian Tennant's message of "Sun, 13 Aug 2006 14:44:15 +0300")
>>>>> "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).
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.
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.
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.
-JimC (who has been caught by this issue before)
--
James Cloos <cloos@jhcloos.com>
next prev parent reply other threads:[~2006-08-15 1:20 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 [this message]
2006-08-17 7:23 ` Sebastian Tennant
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3irkudcc1.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=help-gnu-emacs@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.