** Changed in: gtk
Importance: Unknown = Medium
--
Several compose key combinations don't work
https://bugs.launchpad.net/bugs/74360
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
you can read the upstream bug for details
--
Several compose key combinations don't work
https://bugs.launchpad.net/bugs/74360
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
upstream considers this issue fixed, if you still have things not
working in lucid open a new bug
** Changed in: gtk+2.0 (Ubuntu)
Status: Triaged = Fix Released
--
Several compose key combinations don't work
https://bugs.launchpad.net/bugs/74360
You received this bug notification because
Why is this bug set as Fix Released?
I'm using version 2.21.2-0ubuntu3 of gtk+2.0 (from maverick), and the
Compose-O-- sequence still gives an Õ instead of an Ō, as Eiríkr Útlendi posted
above, so apparently this bug is still present.
--
Several compose key combinations don't work
** Changed in: gtk
Status: Confirmed = Fix Released
--
Several compose key combinations don't work
https://bugs.launchpad.net/bugs/74360
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: gtk
Status: Unknown = Confirmed
--
Several compose key combinations don't work
https://bugs.launchpad.net/bugs/74360
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: gtk via
http://bugzilla.gnome.org/show_bug.cgi?id=557420
Importance: Unknown
Status: Unknown
** Changed in: gtk+2.0 (Ubuntu)
Status: Confirmed = Triaged
--
Several compose key combinations don't work
https://bugs.launchpad.net/bugs/74360
You received this
Running Jaunty 9.04, fully updated as of Monday 18 May 2009.
The Gnome project's decision to implement an unannounced (to the end
user) separate compose key list shows mind-bogglingly poor judgment.
As Jan Minář notes, compose is a powerful mechanism, and quite simple
and easy to use as well.
Did my best to report on this issue. It sounds like Gnome is struggling
to integrate older compose key sequences with the X11 lists, and these
bugs are cropping up due to list disagreement. Judging from the bug
report discussion, hopefully these issues will be shaken out before too
much longer.
could somebody try on jaunty and send it to bugzilla.gnome.org?
** Changed in: gtk+2.0 (Ubuntu)
Importance: Undecided = Low
** Changed in: gtk+2.0 (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
--
Several compose key combinations don't work
The compose tables should be unified, also with the Linux virtual
console compose tables. The compose mechanism is a very powerful one,
and this schism is contra-productive.
I should not have to think carefully before I can type my own surname.
--
Several compose key combinations don't work
Setting GTK_IM_MODULE=xim worked well on Ubuntu 8.04. Wish it was the
default setting, to make the GTK applications consistent with everything
else.
--
Several compose key combinations don't work
https://bugs.launchpad.net/bugs/74360
You received this bug notification because you are a member of
Appears for me on Intrepid, GTK_IM_MODULE is scim-bridge. Setting it to
xim removes compose key support completely. However, the bug wasn't
present on this system when using Ubuntu Hardy, and is hence a
regression.
--
Several compose key combinations don't work
Also bitten by this one. GTK_IM_MODULE=xim fixes the problem.
--
Several compose key combinations don't work
https://bugs.launchpad.net/bugs/74360
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I had some troubles with c cedilla (like Ç, instead Ć). In Brazil we type ' + c
(acute plus c) to do ć. But when running Firefox32 with Kubuntu 64 bits, GTK
fails to load the 32 bit cedilla IM module. GTK always load the 64 bit module
version.
I workaround it changing the internal references to
If there is a need to standardise Compose key sequences, perhaps this
could be forwarded to or taken up by freesdesktop.org?
--
Several compose key combinations don't work
https://bugs.launchpad.net/bugs/74360
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Not with Firefox, but with other applications such as gedit and
gnome-terminal, there *is* a graphical way to change your input method
temporarily to the X input method. Right-click (if your pointing device is
set for right-handedness :^]) in the text input field, and choose Input
Methods and
Though someone metioned that this didn't work for him, it did for me.
Thank you for the hint.
--
Several compose key combinations don't work
https://bugs.launchpad.net/bugs/74360
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
So, is there any official decision made about which system Ubuntu should
adhere to? The X11 compose sequences, or the Gnome/GtkComposeTable. Or
is GTK just being followed, because Ubuntu uses Gnome per default...
Choosing GtkComposeTable obviously confuses some users. It also seems
less complete,
Using GtkComposeTable in GTK applications confuses some users, because
compose sequences then work differently depending on the application's
GUI framework. A kind of low-level distinction of applications, that I
believe the general user not should need to make. Shouldn't it work the
same way
Daniel, I agree with you that it should work the same for the user on
all applications, but I'm not sure who is responsible for making this
sort of decision. This is, in my opinion, against the Ubuntu design
principle of There should be exactly one recommended way to accomplish
a task.
** Changed
Using GtkComposeTable would be fine with me, if the missing characters
were included (I'm missing lower opening and upper closing double quotes
most desperately). In the current state I would consider this a bug, and
I would appreciate any suggestions for disabling this behaviour.
--
Several
mkluwe:
A quick fix for that seems to be to put the following into ~/.gnomerc:
export GTK_IM_MODULE=xim
GTK will then use the X11 compose sequences, which has less , and
greater , that you want.
See: https://help.ubuntu.com/community/ComposeKey
--
Several compose key combinations
Seems to be a wishlist item rather than a bug.
** Changed in: gtk+2.0 (Ubuntu)
Sourcepackagename: None = gtk+2.0
--
Several compose key combinations don't work
https://bugs.launchpad.net/bugs/74360
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I'd also like to note that the GNOME compose table appears to lack a
mapping to give open and close double quotes, though it does have open
and close single quotes.
--
Several compose key combinations don't work
https://bugs.launchpad.net/bugs/74360
You received this bug notification because you
I just used the method described in
https://help.ubuntu.com/community/ComposeKey on my Gutsy system, and it
does appear to work. GTK applications now use the same Compose map as
non-GTK applications. Is there any reason not to make the xim input
module not the default?
--
Several compose key
I have just discovered that there are two problems here.
One is that compose key combinations are not what they were. For
instance I used to use [ gu ] for a g-breve (as per
http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWdev/I18NDG/p25.html
etc.), but now it is [ Ug ].
The other problem
I have just discovered that there are gnome compose key sequences for
probably all the characters the normal compose key sequences cover. They
are listed at https://help.ubuntu.com/community/GtkComposeTable.
The trouble has been that it has taken me many many hours to discover
this. And even then
This bug is still present in Feisty. Please give it a high priority!
It's very frustrating having to learn a Turkish keyboard layout simply
to enter a g-breve. The problem is a regression because the sequences
used to work in xfree86/x.org (for instance they were working in the
Gentoo installation
29 matches
Mail list logo
