Ah, thanks for the clarification. I think that we assume that the numbers are always the base keys on a keyboard, and I'm not sure we have a way of declaring the opposite case at the moment.
My suggestion for a workaround would be to instead create a keyboard layout for French Canadian, and set the system to use this setting. If the example I saw is correct, the keyboard layout for French Canadian has the numbers as base keys:
Yes, you're right. The problem is that you set numbers as base keys and it's not always the case for all keyboards.
I think it should be possible to change this because If I check the keyboardmapping_de.DE, there are changes (like the z key position) that is not in the properties file. So I suppose you can adapt the change you made to reflect a French (Belgium or France) keyboard layout.
The big problem is when you automate test (after a nightly build for example) you will not be sure that the keyboard is defined as English (US) or something else if it's a normal workstation used during the day...
I have the same problem as Michel. I dont succeed to create a mapping for the ; char. So, the documentation is not so easy to understand and the product limited. If I can't say that 1 is shift+& this is a problem.
May be a solution si to use the keycode, but is not so easy.