And after that, on step 6, after I run the KMSample1 app in the virtual device, there’s no Keyman keyboard installed in the virtual device. How can I arrive at the example in the picture with the Tamil keyboard shown?
But now it has a lot of warnings: “warning 209A: The rule will never be matched because its key code is never fired.” pops up 45 times (some duplicates), whereas previously (when I only intended for Windows) it didn’t. The rules in question all look OK, and when I compiled the kmn file for WIndows only they were working fine. Please advice how to debug this warnings.
Ok, you have now added in the Web and that doesn’t support nul, notany or if in conjunction with a context statement. I don’t know if you can think of another way to write the output you want without those statements? It may take more rules.
For now I have commented out the ‘nul + any(isNumbers)’ and ‘notany(isNumbers)’ rules to remove the errors
jawa.kmn: Error: line 244 error 4054: Statement nul is not currently supported in CODE_CONTEXT match
jawa.kmn: Error: line 245 error 4054: Statement notany is not currently supported in CODE_CONTEXT match
Good work on finding that solution. Just remember that the key part of the rule is matching a key on the keyboard – and the keys on the keyboard don’t have Unicode values :). It can be helpful to use virtual key identifiers for keys to help keep the distinction, e.g. + [K_A] > ... instead of + 'a' > ....
What trouble are you having with step 6? Can you elaborate?