Matthieu Herrb writes:
> > cf becomes "variant fr-legacy" instead of "variant fr".
> >
> > cf.nodead becomes "variant fr-legacy" instead of "variant
> > fr_nodeadkeys".
>
> I don't know the subtilities of the canadian french keyboards, but
> that looks as a a behaviour change (even though it's mor
On Wed, Apr 03, 2019 at 10:01:03AM -0600, Anthony J. Bentley wrote:
> Diogo Galvao writes:
> > On Thu, Nov 1, 2018 at 10:15 PM Diogo Galvao wrote:
> > > So the condition ((wsenc & kbdvar[i].val) == kbdvar[i].val) ends up
> > > being true for KB_BR & KB_SF, therefore "fr" variant gets configured.
>
Diogo Galvao writes:
> On Thu, Nov 1, 2018 at 10:15 PM Diogo Galvao wrote:
> > So the condition ((wsenc & kbdvar[i].val) == kbdvar[i].val) ends up
> > being true for KB_BR & KB_SF, therefore "fr" variant gets configured.
> > That bitmasking was introduced in revision 1.15 along with a bitmask for
On Thu, Nov 1, 2018 at 10:15 PM Diogo Galvao wrote:
>
> When the "br" keyboard layout is chosen during install, keys like ç~"
> work correctly on the console but X tries to load the "fr" variant along
> with it, which is invalid for this layout, so it falls back to the
> default keymap. This can
When the "br" keyboard layout is chosen during install, keys like ç~"
work correctly on the console but X tries to load the "fr" variant along
with it, which is invalid for this layout, so it falls back to the
default keymap. This can be observed in the first Xorg.0.log below.
The variant seems to
