--- Begin Message ---
Package: console-setup
Dear Sirs,
I am experimenting with Debian on a Nokia N900 (RX-51). I debootstrapped a Jessie file system. When configuring the keyboard, I found an issue. Namely, the symbols file uses a custom type called PC_FN_LEVEL2; however, when setupcon is called, and from there ckbcomp is invoked, this type is not recognised.
There is a fix on the version of console-setup which is available in the Sid repository. The bug report is found at:
1. The type is already defined in /usr/share/X11/xkb/types/nokia
2. This type file is correctly referenced in /usr/share/X11/xkb/rules/xorg (line 1018/1225) (although I found no trace of Nokia models in xorg.lst and xorg.xml)
3. Based on my investigations, I believe the rules file is read by cbkcomp, but the types file is not
My conclusion is that the problem is ckbcomp not reading the type file indicated in the rule file, and that should be fixed, instead of hardcoding the custom type into ckbcomp.
Best regards,
Enrico Menotti
--- End Message ---
--- Begin Message ---
On Wed, Apr 19, 2017 at 06:20:30PM +0200, Enrico Menotti wrote:
>
> >Can you send:
> >1. A sample command line for ckbcomp.
> >2. The output ckbcomp generates.
I asked for this information because I thought ckbcomp (version 1.164)
didn't work properly with the PC_FN_LEVEL2 type. I didn't realise that
your bug report is only about ckbcomp not reading the type files and
relying on hardcoded info instead.
> But in this way it is impossible to define custom types. But yes, if
> it is impossible to let ckbcomp behave accordingly to what is stated
> in the type file, then this workaround is the only possible solution.
> And I admit that probably there is no practical need for the types to
> be customisable, so doing a huge work to modify ckbcomp would be not
> worth it. In conclusion, based on your reply, I think it be better to
> close this bug report without doing anything.
Thank you.
Anton Zinoviev
--- End Message ---