Ubuntu
gtk+2.0 package

Unicode keyboard entry does not work in multiple applications

Bug #59543 reported by Michael B. Trausch
2
Affects Status Importance Assigned to Milestone
gtk+2.0 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

(Rewritten to be more accurate)

In Edgy, it seems that entering Unicode characters directly using their code points (e.g., Control+Shift+uXXXX) does not work for xterm or emacs-snapshot-gtk. I can almost see it for xterm, because that is not a GNOME application, but emacs-snapshot-gtk integrates pretty well and it would seem that I should be able to insert characters like “ and ” into it without issue.

In either application, when I press Control+Shift+u, I get a system beep, and future numeric keypresses are registered as Shift+number. For example, when I type the sequence to get — (the em dash) in xterm or emacs, I get instead “)!$”.

See original description
Revision history for this message
Michael B. Trausch (mtrausch) wrote :

Oops. Okay. A user of my local lug pointed out that it is now Control+Shift+uXXXX, where XXXX is the character code point.

However, this does not work in some applications (notably, emacs-snapshot-gtk and xterm). IIRC, the old system worked before with those; so the real issue more likely than not that it just does not work in those applications. I will change the report itself to reflect that.

description: updated
Revision history for this message
Michael B. Trausch (mtrausch) wrote :

This is not, in fact, a bug in the system; the method of inputting Unicode character points has changed. Emacs needs a bug reported towards it, though, for its failure to accept input in this fashion.

Changed in gtk+2.0:
status: Unconfirmed → Rejected
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for updating the bug and closing it with an explanation

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.