On Thu 12. January 2006 07:15, David Martínez Moreno wrote:
> en_US.UTF-8/Compose: ca_ES.UTF-8
> +en_US.UTF-8/Compose: cs_CZ.UTF-8 <<<<----- additional
> en_US.UTF-8/Compose: cy_GB.UTF-8
> en_US.UTF-8/Compose: cz_CZ.UTF-8
> en_US.UTF-8/Compose: da_DK.UTF-8
I don't have colons after Compose, but otherwise I have added
cs_CZ.UTF-8 line there (see attached). However, I still get ˇS
when trying to write Scaron (see attached xev.log). What's even
more strange that apparently X are able to decipher that Scaron
is (c5 a0) "Š":
KeyPress event, serial 31, synthetic NO, window 0x2000001,
root 0x4c, subw 0x0, time 162804, (508,357), root:(512,384),
state 0x1, keycode 0 (keysym 0x1000160, U0160), same_screen
YES,
XLookupString gives 0 bytes:
XmbLookupString gives 2 bytes: (c5 a0) "Š"
XFilterEvent returns: False
but still I get ˇS. Is it problem of Qt-based applications or
some other technology, which is not used by Gnome and other
non-KDE applications (firefox has no problems with it)?
Actually, it is not that simple OOo (albeit with KDE skin)
reacts even more strange -- just writes plain S and caron is
silently omitted.
Any ideas?
Matej
Attachment:
compose.dir.bz2
Description: BZip2 compressed data
Attachment:
pgpG6LeTMKy_4.pgp
Description: PGP signature