Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
4.2.3
Issue ID
1269900
Regression
No
HoloLens2 - Using TouchScreenKeyboardType.EmailAddress to bring up the HoloLens system keyboard prevents JP IME from working
1. What happened
Follow the documentation here to bring up the system keyboard on HoloLens 2:
https://docs.microsoft.com/en-us/windows/mixed-reality/keyboard-input-in-unity
However, instead of using TouchScreenKeyboardType.Default, configure it to be TouchScreenKeyboardType.EmailAddress. On Japanese (language/keyboard, etc), even after switching input mode, the Japanese IME is still not showing up.
2. How we can reproduce it using the example you attached
a. Configure the device to use Japanese:
- Windows Display Language – Japanese
- App Preferred Language – Japanese
- Keyboard – Japanese Microsoft IME
b. Launch the app and then navigate to the "Unity UI Examples" and tap on the "UGUI Input Field (experimental)" to bring up the system keyboard.
c. Make sure the Japanese keyboard is selected and switch the system keyboard input mode to enter japanese char (2nd key on the bottom row of the keyboard from the left), e.g. it should read "abc".
d. Type 'ab' - the 'auto complete' of the keyboard only shows 'ab' and that's wha
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note:
Investigation into issues has revealed this is most likely an MS issue. We have communicate the details to the MS WinMR team.