You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not valid .kmn syntax. [...] is treated as a virtual key, so this will not be doing what you expect. In Keyman Developer 18, these are detected as invalid, because they are not valid key codes:
slp1_roman.kpj - info KM05002: Building release/s/slp1_roman/slp1_roman.kpj
slp1_roman.kmn - info KM05002: Building release/s/slp1_roman/source/slp1_roman.kmn
slp1_roman.kmn:76 - error KM0200A: Invalid token found
slp1_roman.kmn - info KM05007: release/s/slp1_roman/source/slp1_roman.kmn failed to build.
slp1_roman.kpj - info KM0500C: Project release/s/slp1_roman/slp1_roman.kpj failed to build.
@Harshavardhan-Pandurangan Please note the issue above for the slp_roman` keyboard. When I approved your keyboard I only checked that your keyboard would build, and it did build in Keyman Developer 17.0 but I think Keyman Developer 18.0 is being more rigorous in checking.
So, these two store don't actually function as you are hoping:
You would need to remove all the "grouped" ones like [U+0061 U+0304] because Keyman stores won't treat those as a unit. I can't see that removing those "grouped" ones would be detrimental to how your keyboard works, because you've written extensive rules below that seem to already produce the behavior you want.
This is not valid .kmn syntax.
[...]
is treated as a virtual key, so this will not be doing what you expect. In Keyman Developer 18, these are detected as invalid, because they are not valid key codes:Originally posted by @mcdurdin in #3298 (comment)
The text was updated successfully, but these errors were encountered: