starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Rapid Cyrillic keyboard input renders characters as questions marks #14840

New Issue
Closed
opened 2026-01-31 04:20:58 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 04:20:58 +00:00
Owner
Copy Link

Originally created by @synner88 on GitHub (Aug 11, 2021).

Windows Terminal version (or Windows build number)

10.0.19042.0, 1.9.1942.0

Other Software

Cygwin 3.2.0
GNU bash, version 4.4.12(3)-release (x86_64-unknown-cygwin)

settings.json snippet:

            {
                "acrylicOpacity": 0.90000000000000002,
                "antialiasingMode": "cleartype",
                "bellStyle": 
                [
                    "window",
                    "taskbar"
                ],
                "closeOnExit": "always",
                "commandline": "C:/cygwin64/bin/bash.exe -i -l",
                "cursorShape": "filledBox",
                "experimental.retroTerminalEffect": false,
                "fontFace": "Cascadia Code",
                "fontSize": 12,
                "fontWeight": "normal",
                "guid": "{ff3d2c15-5fce-4569-bc80-b635ba6fd059}",
                "hidden": false,
                "icon": "D:\\Dropbox\\Icons\\Dakirby309-Simply-Styled-OS-Linux.ico",
                "name": "Cygwin Bash",
                "padding": "10",
                "useAcrylic": true
            },

Steps to reproduce

  1. Add "Bulgarian (Phonetic Traditional)" keyboard layout from Windows 10 Language options.
  2. Setup Cygwin bash inside Windows Terminal via above JSON config.
  3. Open Windows Terminal
  4. Alt+Shift to select "Bulgarian (Phonetic Traditional)" keyboard layout.
  5. Rapidly type on the keyboard.

Issue occurs even inside vim!
Saved files even contain the "?" instead of the typed Cyrillic chars, so it's not just a rendering issue, but an input one!
Can it be font-related? But slow typing renders/inputs correct chars!

Expected Behavior

Cyrillic letters are properly rendered at the command prompt.

Actual Behavior

Some characters are rendered as questions marks "?".
Refer to screenshot.
Cygwin bash

Originally created by @synner88 on GitHub (Aug 11, 2021). ### Windows Terminal version (or Windows build number) 10.0.19042.0, 1.9.1942.0 ### Other Software Cygwin 3.2.0 GNU bash, version 4.4.12(3)-release (x86_64-unknown-cygwin) settings.json snippet: ``` { "acrylicOpacity": 0.90000000000000002, "antialiasingMode": "cleartype", "bellStyle": [ "window", "taskbar" ], "closeOnExit": "always", "commandline": "C:/cygwin64/bin/bash.exe -i -l", "cursorShape": "filledBox", "experimental.retroTerminalEffect": false, "fontFace": "Cascadia Code", "fontSize": 12, "fontWeight": "normal", "guid": "{ff3d2c15-5fce-4569-bc80-b635ba6fd059}", "hidden": false, "icon": "D:\\Dropbox\\Icons\\Dakirby309-Simply-Styled-OS-Linux.ico", "name": "Cygwin Bash", "padding": "10", "useAcrylic": true }, ``` ### Steps to reproduce 1. Add "Bulgarian (Phonetic Traditional)" keyboard layout from Windows 10 Language options. 2. Setup Cygwin bash inside Windows Terminal via above JSON config. 3. Open Windows Terminal 4. Alt+Shift to select "Bulgarian (Phonetic Traditional)" keyboard layout. 5. **Rapidly** type on the keyboard. Issue occurs even inside vim! Saved files even contain the "?" instead of the typed Cyrillic chars, so it's not just a rendering issue, but an input one! Can it be font-related? But slow typing renders/inputs correct chars! ### Expected Behavior Cyrillic letters are properly rendered at the command prompt. ### Actual Behavior Some characters are rendered as questions marks "?". Refer to screenshot. ![Cygwin bash](https://user-images.githubusercontent.com/29090601/129000396-eef9fcd2-ad1e-4610-8a9f-53b3551879b1.png)
claunia added the Needs-TriageNeeds-Tag-FixNeeds-AttentionProduct-Terminal labels 2026-01-31 04:20:59 +00:00
claunia commented 2026-01-31 04:21:00 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Mar 16, 2023):

Hi @synner88. Sorry for the radio silence here. It's been quite some time. Is this still happening? If so, does it happen with shells that do not use the cygwin runtime at all?

@carlos-zamora commented on GitHub (Mar 16, 2023): Hi @synner88. Sorry for the radio silence here. It's been quite some time. Is this still happening? If so, does it happen with shells that do not use the cygwin runtime at all?
claunia commented 2026-01-31 04:21:00 +00:00
Author
Owner
Copy Link

@synner88 commented on GitHub (Mar 17, 2023):

Hello, @carlos-zamora, thank you for your concern!
Issue disappeared long time ago but I don't know at what release version.
I am always using the latest stable release.
Cheers!

@synner88 commented on GitHub (Mar 17, 2023): Hello, @carlos-zamora, thank you for your concern! Issue disappeared long time ago but I don't know at what release version. I am always using the latest stable release. Cheers!
claunia commented 2026-01-31 04:21:00 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 17, 2023):

Thank you for following up! Glad it's been fixed!

@DHowett commented on GitHub (Mar 17, 2023): Thank you for following up! Glad it's been fixed!
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 Needs-Attention Needs-Tag-Fix Needs-Triage Product-Terminal
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#14840
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?