unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Axel Svensson <mail@axelsvensson.com>
Cc: 37530@debbugs.gnu.org
Subject: bug#37530: 26.1; Tack characters translated incorrectly
Date: Fri, 27 Sep 2019 08:26:59 +0300	[thread overview]
Message-ID: <83zhiqjom4.fsf@gnu.org> (raw)
In-Reply-To: <CAJ40yayVXzDjgptThaVZNijFOxK_h8f_QvL6E0JGJzZRq_HuRA@mail.gmail.com> (message from Axel Svensson on Thu, 26 Sep 2019 23:31:34 +0200)

> From: Axel Svensson <mail@axelsvensson.com>
> Date: Thu, 26 Sep 2019 23:31:34 +0200
> 
> Press C-h l to run view-lossage.
> The last lines display the erroneous characters that were inserted,
> rather than the expected characters.
>  ⊣ [self-insert-command]
>  ⊢ [self-insert-command]
>  ⊥ [self-insert-command]
>  ⊤ [self-insert-command]
>  C-h l [view-lossage]
> 
> In order to confirm that the behavior I have stated as expected is the
> correct one, look to the XKB keysym definitions:
> > #define XKB_KEY_downtack                      0x0bc2  /* U+22A4 DOWN TACK */
> > #define XKB_KEY_uptack                        0x0bce  /* U+22A5 UP TACK */
> > #define XKB_KEY_lefttack                      0x0bdc  /* U+22A3 LEFT TACK */
> > #define XKB_KEY_righttack                     0x0bfc  /* U+22A2 RIGHT TACK */
> These can be found at:
> https://github.com/xkbcommon/libxkbcommon/blob/master/xkbcommon/xkbcommon-keysyms.h
> 
> It is understandable that bugs like these can go unnoticed seeing that
> these characters probably aren't part of any widely used keyboard
> layout. If this bug can be confirmed, and depending on what caused it,
> it might be beneficial to add the complete mapping from X11 keysyms to
> Unicode codepoints as automated tests. I'm willing to provide this
> mapping, including source references.

Isn't the output of "C-h l" evidence that Emacs actually received the
codepoints it displayed?  IOW, how do we know this is a problem in
Emacs and not in the keyboard configuration and/or driver software?

Thanks.





  reply	other threads:[~2019-09-27  5:26 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 [this message]
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
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=83zhiqjom4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37530@debbugs.gnu.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).