Bug#899979: keyboard-configuration: the caron dead-key of the czech keyboard on the console does not work as expected
- To: firstname.lastname@example.org
- Cc: Anton Zinoviev <email@example.com>, Samuel Thibault <firstname.lastname@example.org>
- Subject: Bug#899979: keyboard-configuration: the caron dead-key of the czech keyboard on the console does not work as expected
- From: Jan Rafaj <email@example.com>
- Date: Fri, 1 Jun 2018 16:06:34 +0200 (MEST)
- Message-id: <[🔎] alpine.LNX.firstname.lastname@example.org>
- Reply-to: Jan Rafaj <email@example.com>, firstname.lastname@example.org
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org> <email@example.com> <20180526092059.zpwnv3mmy4eywdbu@debian> <firstname.lastname@example.org> <email@example.com> <20180527170530.cysrqvwarvf46s46@debian> <firstname.lastname@example.org> <alpine.LNX.email@example.com> <20180531201243.63efdgu6kr2b4r3v@debian> <20180531214818.y24zgnol2ormbgu6@debian> <firstname.lastname@example.org> <email@example.com>
On Thu, 31 May 2018, Samuel Thibault wrote:
Anton Zinoviev, le ven. 01 juin 2018 00:48:18 +0300, a ecrit:
If a bug makes a package totally unusable, but otherwise harmless,
then this bug is (usually) not going to be fixed in the stable
Mmm, I believe that sentence enters the "important" area, or even more:
4 important a bug which has a major effect on the usability of a package,
without rendering it completely unusable to everyone.
For me, I took a liberty to mark it 'important' just becouse something,
that appeared to work in former Debian releases (console with ability to
write czech characters), has suddenly stopped working and I wasnt able to
obtain satisfactory results that would mitigate the problem - from that,
I thought it would somehow fall under the 'important' definition. But
feel free to change...
Now, to my latest post.
I did thorough checking of all the compose definitions I've suggested to
add, and have noticed that the following ones still do not produce the
corresponding caron-ified characters as they should - I have no idea why:
compose '^' 'S' to U+0160 # instead produces U+015A (0xC59A)
compose '^' 's' to U+0161 # instead produces U+00A8 (0xC2A8)
compose '^' 'Z' to U+017D # instead produces U+00B4 (0xC2B4)
compose '^' 'z' to U+017E # instead produces U+00B8 (0xC2B8)
All the other compose definitions produce correct results.
If you could also please look for the reason of this.