-
Notifications
You must be signed in to change notification settings - Fork 20
C2LC-539: Platform detection and platform-specific wording for key bindings. #296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
the-t-in-rtf
wants to merge
4
commits into
codelearncreate:develop-1.2
Choose a base branch
from
the-t-in-rtf:C2LC-539
base: develop-1.2
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
0c03d93
C2LC-539: Platform detection and platform-specific wording for key bi…
the-t-in-rtf f7dba7c
C2LC-539: Converted 'option' icon to use unicode character.
the-t-in-rtf 4079136
C2LC-539: Fixed key binding descriptions to match Figma wording.
the-t-in-rtf ca65391
Merge remote-tracking branch 'upstream/develop-1.0' into C2LC-539
the-t-in-rtf File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I started to wonder do we really need to use intl to get the KeyIcons as they all seem to be international?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's potentially useful for countries that tend to use local abbreviations for the common modifier keys. I couldn't find any French Canadian keyboards that went so far as to translate "control", et cetera, but I did find German layouts that were translated. However, even in that case, it varies by keyboard, the Apple keyboard for the German market still uses the English terms. You'd really have to assume that modern computer users would be used to the English terms for their platform, so probably we could just use that. For the letter keys, internationalisation seems less useful and potentially dangerous, as you never want to get in a situation where the key code doesn't match the label.
I could see moving these to a constant array in
KeyboardInputSchemes, and it wouldn't take long. I'll wait to get Simon's input first.