ubuntu-x-swat team mailing list archive

[Bryce Harrington <408651@xxxxxxxxxxxxxxxxxx>]

Thanks commenters in #7 and #8, that is a very good analysis of the
problems.  On my fairly pedestrian USA layout I'm able to reproduce the
set of keys in 2a.

I'm not sure why 2b is different; possibly there are locale settings or
console-setup settings at play?  Check /etc/default/console-setup and
setxkbmap -print.  `xkbcomp :0 -w0 -` might be worth comparing between
the two setups.  I haven't been able to reproduce that case, although I
do notice that under one font, ẽ (e with tilde) looks identical to ē (e
with bar); could a font issue be at play?  Maybe we should focus this
bug report on the irregularity of 2a, and if you still can reproduce 2b,
open a new bug report.

I'm also able to confirm that <Compose>+"e"+<tilde> produces nothing for
me, although <Compose>+<tilde>+"e" does.  I don't hear sound, but that's
probably the system bell, which I have turned off.  Looking through the
Compose file I see there are some discrepencies in how ã and ẽ are
defined.

** Package changed: xkeyboard-config (Ubuntu) => libx11 (Ubuntu)

** Changed in: libx11 (Ubuntu)
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in ubuntu.
https://bugs.launchpad.net/bugs/408651

Title:
  contains conflicting compose definitions