From: ulrich@mips.complang.tuwien.ac.at (Ulrich Neumerkel)
Subject: Re: German keyboard key bindings?
Date: Wed, 17 Dec 2003 21:24:50 GMT [thread overview]
Message-ID: <2003Dec17.222450@a0.complang.tuwien.ac.at> (raw)
In-Reply-To: 87wu8vywsh.fsf@emptyhost.emptydomain.de
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Kai Grossjohann <kai@emptydomain.de> writes:
>ulrich@mips.complang.tuwien.ac.at (Ulrich Neumerkel) writes:
>
>> To me this seems to be some kind of boot strap problem: In order to
>> mention ä one needs to be in a Latin-1 language environment etc.
>
>Well, C-x 8 " a seems easy enough to type if you need that character.
This is not about typing in other characters but referring
to them in .el-Files
>Since ä is a Latin-1 character, what's the point of making this "key"
>available to non-Latin-1 users?
This is more about particular keyboard layouts.
>;; -*- coding: latin-1; -*-
>(global-set-key (kbd "C-ä") 'dabbrev-expand)
>
>Does this work?
Yes, this is definitely better than what I had before,
but it is not what my post was about.
If latin-1 would be everything, then this would be perfect.
If I understand the situation correctly you need for any encoding
you care a separate file to define the appropriate bindings.
Right? The point would be to be able to refer to different
encodings in the same file.
--
Ulrich Neumerkel http://www.complang.tuwien.ac.at/ulrich/
next prev parent reply other threads:[~2003-12-17 21:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 20:24 German keyboard key bindings? Ulrich Neumerkel
2003-12-16 21:57 ` Edi Weitz
2003-12-17 0:03 ` Kai Grossjohann
2003-12-17 14:09 ` Ulrich Neumerkel
2003-12-17 17:58 ` Kai Grossjohann
2003-12-17 19:46 ` Ulrich Neumerkel
2003-12-17 14:10 ` Reiner Steib
2003-12-17 17:57 ` Kai Grossjohann
2003-12-17 21:11 ` Kai Grossjohann
2003-12-17 21:24 ` Ulrich Neumerkel [this message]
2003-12-18 9:10 ` Kai Grossjohann
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=2003Dec17.222450@a0.complang.tuwien.ac.at \
--to=ulrich@mips.complang.tuwien.ac.at \
/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).