starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Vietnamese IME word composition bug #15515

New Issue
Closed
opened 2026-01-31 04:40:53 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 04:40:53 +00:00
Owner
Copy Link

Originally created by @ducminh03 on GitHub (Oct 11, 2021).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version (or Windows build number)

Windows Terminal 1.10.2714.0

Other Software

  • Microsoft Windows [Version 10.0.22000.194] (though I believe this also occurs back to Windows 10 1903, which is the first version of Windows where Vietnamese Telex IME is first introduced)
  • Powershell 7.1.4 (x64)

Steps to reproduce

  1. Add the Vietnamese language and 'Vietnamese Telex' keyboard layout
  2. Open Windows Terminal, then switch to PowerShell
  3. Switch to Vietnamese Telex keyboard layout
  4. Type 'Xin chaof' (including the apostrophe) then press Enter

Expected Behavior

The sentence 'Xin chào' is written to the console, with normal word composition. (The screenshot is took in conhost)
conhost

(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 'Xin Xinchaof'.
wt

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

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.

Originally created by @ducminh03 on GitHub (Oct 11, 2021). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version (or Windows build number) Windows Terminal 1.10.2714.0 ### Other Software - Microsoft Windows [Version 10.0.22000.194] (though I believe this also occurs back to Windows 10 1903, which is the first version of Windows where Vietnamese Telex IME is first introduced) - Powershell 7.1.4 (x64) ### Steps to reproduce 1. Add the Vietnamese language and 'Vietnamese Telex' keyboard layout 2. Open Windows Terminal, then switch to PowerShell 3. Switch to Vietnamese Telex keyboard layout 4. Type `'Xin chaof'` (including the apostrophe) then press Enter ### Expected 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 `'Xin Xinchaof'`. ![wt](https://user-images.githubusercontent.com/17383640/136835614-330a88a2-f290-410e-b913-cb790239ee7e.gif) 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.
claunia commented 2026-01-31 04:40:55 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 18, 2022):

:tada:This issue was addressed in #13678, which has now been successfully released as Windows Terminal Preview v1.15.228.🎉

Handy links:

@ghost commented on GitHub (Aug 18, 2022): :tada:This issue was addressed in #13678, which has now been successfully released as `Windows Terminal Preview v1.15.228`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.15.228) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-i18n Area-Input Area-TerminalControl Issue-Bug Priority-1 Product-Terminal Resolution-Fix-Committed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15515
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?