From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: bbdb and searching
Date: Mon, 20 May 2002 16:06:30 +0200 [thread overview]
Message-ID: <vafn0uuhq1l.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87n0uvt636.fsf@easynet.be>
remi.letot@easynet.be (Rémi Letot) writes:
> Now I don't understand the bits about 'using the X11 compose key
> (<compose> " a)'. Could you be more specific ? And is there a generic
> way to solve this problem ?
One of the keys on my kbd generates the Multi_key keysym. I'm used
to calling this the Compose key, because that's what's printed on it
on a Sun keyboard. X11R6 provides a general mechanism for typing
nonascii characters via the Multi_key. You type the Multi_key, then
a sequence of other keys, and the application sees some nonascii
character. For example, the Multi_key followed by " followed by a
inserts the ä character in my programs.
Some time ago, I was running in a Latin-1 environment, so the above
key sequence produced ä in Latin-1 encoding. Now I switched to
LC_CTYPE=de_DE@euro, so Emacs uses a Latin-9 environment, and hence
the same key sequence produces ä in Latin-9 encoding.
But actually it does not matter how the characters get into Emacs.
If you have the following line:
bäh bäh
and the two ä come from different charsets, then C-s C-w C-s when at
the beginning of the above line does NOT find the second word. Of
course, users would like C-s C-w C-s to find the second word.
In Emacs from CVS, you can turn on unify-8859-on-decoding-mode and
this will help somewhat because it reduces the number of times that ä
from different charsets appears in your file. (But it is also bad for
editing the file lisp/ChangeLog that comes with Emacs because it
changes the encoding of Pavel Janík's name -- the í should be from
Latin-2 but is reencoded into Latin-1 by unify-8859-on-decoding-mode.
Probably this special case is not very important for you.)
Work is currently in progress to change the internal encoding of
Emacs from Mule to something based on Unicode (ie, Unicode with some
extensions). When this happens, all ä characters will be the same
inside of Emacs. Then the searching problem will be gone. (It also
means that Pavel's name will be affected, one way or another.)
kai
--
Silence is foo!
next parent reply other threads:[~2002-05-20 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wutztdus.fsf@easynet.be>
[not found] ` <vafd6vrhzrh.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <87n0uvt636.fsf@easynet.be>
2002-05-20 14:06 ` Kai Großjohann [this message]
[not found] ` <1mlmaedfwx.fsf@Tempo.Update.UU.SE>
[not found] ` <vafy9ee96qj.fsf@lucy.cs.uni-dortmund.de>
2002-05-20 16:07 ` Fredrik Staxeng
[not found] ` <871yc6e62y.fsf@easynet.be>
2002-05-21 11:07 ` Kai Großjohann
2002-05-21 12:04 ` Rémi Letot
[not found] ` <vafelg5o9n0.fsf@lucy.cs.uni-dortmund.de>
2002-05-21 19:31 ` Rémi Letot
[not found] ` <vafelg4771p.fsf@lucy.cs.uni-dortmund.de>
2002-05-22 18:37 ` Robert Marshall
[not found] ` <87hel084uh.fsf@easynet.be>
[not found] ` <vaflmabdx8a.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <873cwj57c4.fsf@easynet.be>
2002-05-23 14:19 ` Kai Großjohann
[not found] ` <874rgy8sar.fsf@easynet.be>
2002-05-23 21:45 ` Josh Huber
2002-05-24 9:45 ` Kai Großjohann
2002-05-24 20:07 ` Rémi Letot
2002-05-24 20:25 ` Erwan David
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=vafn0uuhq1l.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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 NNTP newsgroup(s).