feat(developer): support for U_xxxx_yyyy#5894
Merged
Conversation
User Test Results
|
Contributor
|
TEST_U_xxxx_yyyy: PASSED |
Collaborator
|
Changes in this pull request will be available for download in Keyman version 15.0.146-alpha |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2858.
This feature requires KeymanWeb 15.0.
Adds support for
U_xxxx_yyyy_....identifiers so that you can emit more than a single Unicode character with touch keys without needing kmn code. For example, to emit U+1000 U+1001 with a single keystroke, you'd need to call the key, e.g.T_1000_1001and include a rule+ [T_1000_1001] > U+1000 U+1001. Now you can do the same thing without a rule for it.See keymanapp/help.keyman.com#487 for documentation.
User Testing
Test in Keyman Developer, KeymanWeb test, for iPhone or iPad.