From: Tor Kringeland <tor.a.s.kringeland@ntnu.no>
To: Stefan Kangas <stefankangas@gmail.com>, Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Any use cases of `iso-transl-language-list'?
Date: Thu, 02 Dec 2021 16:57:26 +0100 [thread overview]
Message-ID: <m2pmqf9ezd.fsf@ntnu.no> (raw)
In-Reply-To: <CADwFkmnZAVJTZ17yEZwJeOomRTPbsM7P=awFGXYivS2YG94p+Q@mail.gmail.com>
Stefan Kangas <stefankangas@gmail.com> writes:
> When typing Spanish, the characters I have trouble inputting are exactly
> ¡, ¿, ñ and Ñ, but not the accented vowels (I use a prefix character ´
> for them). So it seems "complete" in the sense that it covers exactly
> the characters I'd use. Maybe your experience is different.
I see your point. I use an US keyboard layout which doesn't have
modifiers for accents, so I've just gotten used to using `C-x 8' or
inputs methods, where producing "ñ" or "é" require the same amount of
key-strokes. Though /e.g./ Norwegian keyboards have modifiers "´" and
"`" which one could also use for /e.g./ writing Italian. There's also a
"^" modifier. So this is more complete than I had thought, in that it
covers these more tricky characters.
I still think using the default `C-x 8' or input methods is a better
method in general, but in its current state this seems to have a use
case for said languages, so leaving it as is and documenting is better.
> Documenting this sounds like a good idea. Could you write up a patch?
Yes
next prev parent reply other threads:[~2021-12-02 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 20:40 Any use cases of `iso-transl-language-list'? Tor Kringeland
2021-12-02 6:33 ` Eli Zaretskii
2021-12-02 11:17 ` Stefan Kangas
2021-12-02 6:40 ` Po Lu
2021-12-02 15:14 ` Tor Kringeland
2021-12-02 15:35 ` Stefan Kangas
2021-12-02 15:57 ` Tor Kringeland [this message]
2021-12-02 15:36 ` Robert Pluim
2021-12-03 4:26 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2pmqf9ezd.fsf@ntnu.no \
--to=tor.a.s.kringeland@ntnu.no \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.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.
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.