From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Tor Kringeland <tor.a.s.kringeland@ntnu.no>, 52173@debbugs.gnu.org
Subject: bug#52173: `ś' character not available using `C-x 8'
Date: Mon, 29 Nov 2021 15:49:31 +0100 [thread overview]
Message-ID: <87a6hn585g.fsf@gmail.com> (raw)
In-Reply-To: <87o863xbs9.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 29 Nov 2021 15:43:34 +0100")
>>>>> On Mon, 29 Nov 2021 15:43:34 +0100, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> Robert Pluim <rpluim@gmail.com> writes:
>> Except C-x 8 is nominally based on ISO 10646, so thereʼs some kind of
>> underlying logic to the characters it supports.
Lars> In what way it it based on Unicode?
Sorry, ISO 8859-1, not 10646
Lars> Adding `C-x 8 ' s` for instance, wouldn't get in the way of anything
Lars> else, but would be helpful for those that have to write the
Lars> occasional... er... what is it? An s with a caron?
>>
>> s with acute. But there are input methods where 's => s with cedilla
>> (eg Romanian), so what's the logic for preferring Polish, especially
>> when we already have Polish/Czech/Romanian/latin-n methods etc for all
>> these characters?
Lars> I wasn't aware that there was any kind of logic to the `C-x 8' map
Lars> except "well, that's nice". 😀
:-)
Looking again at iso-transl.el, perhaps we could define a 'Polish' and
'Czech' language. But again this all duplicates existing
infrastructure in input methods.
Robert
--
next prev parent reply other threads:[~2021-11-29 14:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 3:08 bug#52173: `ś' character not available using `C-x 8' Tor Kringeland
2021-11-29 9:30 ` Robert Pluim
2021-11-29 13:55 ` Tor Kringeland
2021-11-29 14:06 ` Robert Pluim
2021-11-29 14:24 ` Lars Ingebrigtsen
2021-11-29 14:37 ` Robert Pluim
2021-11-29 14:43 ` Lars Ingebrigtsen
2021-11-29 14:49 ` Robert Pluim [this message]
2021-11-29 18:11 ` Tor Kringeland
2021-11-29 18:44 ` Lars Ingebrigtsen
2021-12-03 15:55 ` Tor Kringeland
2021-11-29 15:55 ` André A. Gomes
2021-11-29 16:52 ` Robert Pluim
2021-11-29 17:03 ` André A. Gomes
2021-11-29 17:19 ` Robert Pluim
2021-12-03 16:44 ` Lars Ingebrigtsen
2021-12-04 5:46 ` Richard Stallman
2021-12-04 5:56 ` bug#52173: `Å›' " Lars Ingebrigtsen
2021-12-05 5:07 ` Richard Stallman
2021-12-05 5:10 ` bug#52173: `Å›' " Lars Ingebrigtsen
2021-12-06 4:33 ` Richard Stallman
2021-12-06 5:04 ` bug#52173: `Å›' " Lars Ingebrigtsen
2021-12-06 17:38 ` Juri Linkov
2021-12-07 4:16 ` Richard Stallman
2021-11-29 17:09 ` bug#52173: `ś' " Juri Linkov
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=87a6hn585g.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=52173@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=tor.a.s.kringeland@ntnu.no \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).