From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: mail@axelsvensson.com, 37530@debbugs.gnu.org
Subject: bug#37530: 26.1; Tack characters translated incorrectly
Date: Fri, 27 Sep 2019 16:59:10 +0300 [thread overview]
Message-ID: <834l0xkfgx.fsf@gnu.org> (raw)
In-Reply-To: <878sq9q24o.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 27 Sep 2019 15:50:47 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: mail@axelsvensson.com, 37530@debbugs.gnu.org
> Date: Fri, 27 Sep 2019 15:50:47 +0200
>
> > I'd like someone to do the research and find out why Markus Kuhn's
> > suggestions were changed. I'd like also to state the source of the
> > data and the information about the change reason(s) in x-win.el, where
> > we have the mapping.
>
> If somebody wants to do that research, be my guest. I don't see the
> point -- this is the data the X server uses, so it's authoritative.
I'd like to hear more opinions, please.
> >> /* Keysyms directly mapped to Unicode characters. */
> >> if (keysym >= 0x01000000 && keysym <= 0x0110FFFF)
> >
> > To answer the question, one needs to compare the keysyms with the
> > corresponding codepoints. If they are identical, then the mapping is
> > trivial.
>
> I don't understand what you mean. The comment says that the keysyms in
> the 0x01000000 to 0x0110FFFF range map directly to code points. What is
> there to compare?
Perhaps I've misunderstood where the code was taken from. You didn't
say.
next prev parent reply other threads:[~2019-09-27 13:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 21:31 bug#37530: 26.1; Tack characters translated incorrectly Axel Svensson
2019-09-27 5:26 ` Eli Zaretskii
2019-09-27 10:37 ` Axel Svensson
2019-09-27 13:15 ` Eli Zaretskii
2019-09-27 13:17 ` Axel Svensson
2019-09-27 13:03 ` Lars Ingebrigtsen
2019-09-27 13:32 ` Lars Ingebrigtsen
2019-09-27 13:44 ` Eli Zaretskii
2019-09-27 13:50 ` Lars Ingebrigtsen
2019-09-27 13:59 ` Eli Zaretskii [this message]
2019-09-27 14:03 ` Lars Ingebrigtsen
2019-09-27 14:18 ` Axel Svensson
2019-09-27 14:10 ` Axel Svensson
2019-09-27 14:19 ` Lars Ingebrigtsen
2019-09-27 14:57 ` Axel Svensson
2019-09-27 14:25 ` Eli Zaretskii
2019-09-27 14:48 ` Axel Svensson
2019-09-27 15:30 ` Eli Zaretskii
2019-09-27 17:19 ` Axel Svensson
2019-09-27 18:35 ` Eli Zaretskii
2019-09-27 20:05 ` Axel Svensson
2019-09-28 6:18 ` Eli Zaretskii
2019-09-28 13:44 ` Axel Svensson
2019-09-28 14:12 ` Eli Zaretskii
2019-09-28 14:30 ` Axel Svensson
2019-09-28 14:48 ` Eli Zaretskii
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=834l0xkfgx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37530@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mail@axelsvensson.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 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).