Comment 7 for bug 13938

Revision history for this message
Colin Watson (cjwatson) wrote :

The other non-ASCII characters you mention appear to produce valid UTF-8 when
typed at the terminal, but e-acute (and presumably the other characters produced
by composition) does not. I tried to track this down and ended up buried inside
a horrible pile of code in kbd-chooser that was cloned-and-hacked from an old
version of kbd. Cleaning up that mess would almost certainly help.