On Mon, Jun 01, 2020 at 02:16:16PM +0200, Marc Espie wrote: > I occasionnally use setxkbmap 'us(intl)' in order to have diacritics > as dead keys. > > I have LC_CTYPE=en_US.UTF-8 > > If I type 'c > > I get a ç in programs like firefox or chrome, BUT I get > ć in xterm ? > > why are things different ?
Because firefox or chrome probably don't use /usr/X11R6/share/X11/locale/en_US.UTF-8/Compose (the rules used by Xlib) but their own Compose rules. I don't know if there is some other "standard" toolkit (gtk+3?) providing alternative rules or if they just hard-code their own rules somewhere. > which program is right ? There may be an international standard (ISO, XDG, ... ?) that controls those rules and what X.Org is shipping in /usr/X11R6/share/X11/locale/en_US.UTF-8/Compose But I can't find a reference. So I would say that xterm is right: the compose sequence for ç is ,c. And as you got it there is a ć character in some alphabets reachable with 'c or <Compose> ' c You have a <dead_cedilla> key in the default us(intl) XKB layout (it's on the the 4th group for the '5' key) but I don't remember how to reach that group :) > > (I have just tried with a test user with nothing configured besides > LC_CTYPE=en_US.UTF-8, without which xterm/vim doesn't show proper characters) I'm using a real US keyboard with AltGr or the Menu Key (depending on the actual keyboard) set as Compose and typing full compose sequences to get diacritics. ie <Compose> <comma> <c> and so on. -- Matthieu Herrb
