Pushed as commit 121a1bad334459f66f78bfca6df53dc841cf97f8.
--
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/518056
Title:
cedilla appears as accented c (ć instead of ç) when typing 'c
To manage
A git patch would be welcome, but we at least need a signoff line for
the patch.
--
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/518056
Title:
cedilla appears as accented c (ć instead of ç) whe
> The desired behavior is that the key followed by the c key
> results in ccedilla, while keeping the original behavior for other letters.
It already does in the pt_BR.UTF-8 locale.
The compose file for pt_BR.UTF-8 includes the en_US.UTF-8 file and then
overrides some of the sequences, including
> Current kernels have KEY_MICMUTE==248, i. e. X.org should be
> perfectly able to recognize this. Apparently this was done in
> 2011 already.
248 is the first linux kernel value which X cannot handle.
The mapping is +8, so 248 ⟹ 256, which does not fix in 8 bits.
(The first 8 are reserved – fro
> If we look Unicode charts, they also plan these association (written
> under a character when there is one, for instance ⇱ is the "home" key)
> I don't know of any system actually supporting this.
rxvt-unicode does, using ctrl-shift as the introducer.
It also supports C-S + code point entry and
> Sure, my patch just follows the license of the original code. So it's
> in MIT/X11 license.
Cool. And to be clear, I only asked because of the license issue with
the first patch on this bug report.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribe
A non-working PgUp is a common result of an impedance mismatch between
the input driver and the configured xkb keycodes.
You should confirm that both are evdev or that you have keyboard and a
suitable keycodes for that.
Xorg.0.log will show which input driver is used. xkbcomp :0 - |grep keycod
Before the changes to the Compose files can be pushed, we need to
decide on what character to use for the apostrophe in the cʼh strings.
I spent some time before the holiday researching that.
The fdo bug reports and related posts in the list archives use U+2019
RIGHT SINGLE QUOTATION MARK.
Every
>> But there is no one reason to switch keyboard layouts in back order
>> in first place, isn't it?
As someone who loads extra layouts just in case, I find the reverse
order switching to be invaluable.
I use lctrl+rctlr; it may be easier to deal with the reverse order
in such cases than with the
9 matches
Mail list logo
