Vietnamese IME word composition bug #11479
Labels
Area-i18n
Internationalization issues (e.g.: non-US input handling doesn't work)
Area-Input
Related to input processing (key presses, mouse, etc.)
Area-TerminalControl
Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Priority-1
A description (P1)
Product-Terminal
The new Windows Terminal.
Resolution-Fix-Committed
Fix is checked in, but it might be 3-4 weeks until a release.
Milestone
Windows Terminal version (or Windows build number)
Windows Terminal 1.10.2714.0
Other Software
Steps to reproduce
'Xin chaof'
(including the apostrophe) then press EnterExpected Behavior
The sentence 'Xin chào' is written to the console, with normal word composition. (The screenshot is took in conhost)
![conhost](https://user-images.githubusercontent.com/17383640/136833540-4987f204-3a3b-41ba-ac14-1bc24462ccaf.gif)
(Note for non-Vietnamese: the 'f' denotes the grave on the main vowel, which, in this case, is the 'a')
Actual Behavior
The IME composition works normally for the first syllable Xin. However, after pressing the 'c', the IME suddenly sticks the previous syllable at the beginning when composing, which breaks normal Vietnamese syllable structure. Therefore, when pressing the letter 'f', the IME then decides to append an 'f' instead of putting a grave on the 'a'. All of these result in the output of
![wt](https://user-images.githubusercontent.com/17383640/136835614-330a88a2-f290-410e-b913-cb790239ee7e.gif)
'Xin Xinchaof'
.Somehow when composing the following words, the keystroke of the previous composition is retained. After typing Xin, then pressing Space and the 'f', the grave is put on the 'i' of the previous syllable 'Xin':
![wt](https://user-images.githubusercontent.com/17383640/136837065-d5d38d5c-6c3f-47aa-9b61-47224cd89479.gif)
The problem seems to come from the IME itself, since it is a relatively new piece of software. However, it would be nice to explain why the problem does not occur on conhost.
The text was updated successfully, but these errors were encountered: