Hello all.
If any of you experience the same non-US keyboard layout problem I had, I believe
I have
figured it out,after much research and try-out of a number of keyboard-
related utilities.
I cannot say with absolute certainty that urxvt is the first upstream cause
-- maybe it is the way it was compiled?
-- Is it a glitch in version 9.22?
-- Is it the udev rules?
-- Is it some other language interface? ( E.g. i18n; MLterm comes with its own
i18n support. )
-- Is it the absence, in Puppy, of the traditional "kbd utils" found in other distros?
Whatever the ultimate cause may be, I now know that giving my CLI editors MLterm
support solved the problem.
The "ML" in MLterm stand for "multi-lingual". It was designed initially for Asian
languages, but if it can do that, it can accommodate "simpler" locales such as
fr_CA.UTF-8 and the ca keyboard layout.
MLterm has been around for a good while, but it is still maintained. As a matter of
fact, the devs have published a new version earlier this year.
MLterm lets me use the same ca keyboard layout in CLI as in GTK ( geany, for
ex., or any browser ), which urxvt seemed incapable of doing in the upupBB32's,
both jrb's and peebee's.
I will continue monitoring MLterm on my upupbb32-light for a day or two. If I get no
bugs, I'll make available a pet archive of the latest version, so other users of a
"latin" keyboard may benefit from this find.
BFN.