GNU bug report logs -
#37530
26.1; Tack characters translated incorrectly
Previous Next
Reported by: Axel Svensson <mail <at> axelsvensson.com>
Date: Thu, 26 Sep 2019 21:33:02 UTC
Severity: normal
Merged with 40240
Found in versions 26.1, 26.3
Fixed in version 27.1
Done: Robert Pluim <rpluim <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
Message #32 received at 37530 <at> debbugs.gnu.org (full text, mbox):
> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: mail <at> axelsvensson.com, 37530 <at> 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.
This bug report was last modified 5 years and 141 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.