Open SeerLite opened 9 months ago
Hi @SeerLite I have assigned this to you.
Thank you. But which of the two proposed solutions do you think I should go for?
@SeerLite This one is probably the most novel. Since grave is intentionally broken for Windows and Mac this would follow the pattern:
Make it act as dead acute accent and a non-dead ~ when shift is held. ñ can only be typed with AltGr.
Also, é and í come up a lot in ES200 anyway, I would think that would alleviate more of the AltGr strain even if ñ can't be a part of it.
@SeerLite Do you think you have something workable you might want to pull in or are you still trying out adaptations?
Please assign to me.
I have a working XKB file based off of the one in the Canary repo, AltGr works for ñáéíóú too (in fact I made that modification before even finding Canaria). However there's an issue: It's not possible to give the acute accent dead key multiple meanings depending on which key is pressed next, as far as I know. The keysym typically used for the acute accent dead key is
dead_acute
, and it only applies the acute accent. (Makes you áblé tó týṕé fúńńý). The Canaria layout, as specified in the README (and as I've understood without being able to try the layout on Windows), requires the following rules for the dead key:~
(doable)n
:ñ
(the same for uppercase)aeiou
:áéíóú
(the same for uppercase)The last 3 are not possible in XKB.
I have two solutions:
~
with shift), like in standard US QWERTY.ñáéíóú
can only be typed with AltGr.~
when shift is held.ñ
can only be typed with AltGr.Personal opinion: I hate dead keys, and the moment I switched to Colemak-DH and discovered there was a way to accent vowels with AltGr I was relieved I'd never have to use one again. I'd apply the first solution.
And thank you for Canaria!