Hmmm. For one thing, your ISO_1 key shouldn't be a CapsStat 5 but 0 key (i.e., it's like the number/symbols keys not the letter keys) – but that shouldn't be enough to throw the layout and just means that your Caps states will be wonky. It's 1 to make the key affected by Caps state, 5 if the AltGr mapping is affected too. Amusingly enough, going through my own PKL layout files I just found a slew of Caps errors. I don't use the Caps state much...
Possibly you may have to use another ISO_# for that key. On my keyboard there's OEM_1 (;:), 2 (/?), 3 (`~), 4 ([{), 5 (\|), 6 (]}) and 7 ('") but yours may be different. You could check out which keys do what. Bit of a long shot though.
Try this:
SC027 = OEM_1 VirtualKey ; QWERTY semicolon
(I actually had OEM_3 there – QWERTY-NO 'Ø'. You might try that too then since the Norwegian Ø is on the semicolon key.)
You'd lose the óÓ since that's not defined in the base system layout, but that may be acceptable and at any rate help you determine the problem better. I use dead keys for accents since I need many of them and like this solution – keep in mind that if your system layout has dead keys then pkl.ini needs to be told which ones they are.
Tip for your Github script: You should state "If your Windows system keyboard layout is anything other than QWERTY UK" instead of "If your Windows keyboard layout is Colemak UK"! The script is just as useful for a Dvorak or what-have-you user. You might add that the AltGr mappings are your own though (or even mention Colemak-eD).
Last edited by DreymaR (07-Oct-2013 12:24:58)