Add key mappings for Kana
, Eisu_toggle
and Muhenkan
#832
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.
This request is a continuation of #818 to share Japanese keyboards with Windows and mac computers while keeping Japanese input functionalities.
Windows and mac provide similar but different keys to enable and disable Japanese input methods:
Muhenkan
(Windows) <->Eisu_toggle
(mac)Henkan
(Windows) <->Kana
(mac)Making a mapping of these keys is important to share the Japanese keyboards but unfortunately some of these keys are not recognized by barrier.
The request #818 added key entries for
Eisu_toggle
andMuhenkan
to the barrier internal key representation.This request adds a mapping between the internal representation with OS-specific key representation.
I confirmed that this request makes barrier aware of
Kana
,Eisu_toggle
,Henkan
andMuhenkan
keys in thesection: options
section in the setting file.After merging this request, we can smoothly share Japanese keyboards between Windows and mac computers by adding the following settings (in the case of Windows server):
Note that GUI hotkey editor does not recognize these Japanese IME keys and therefore we have to edit the configuration file directly. Fixing it is out of scope of this request.