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

Lucida Console can not fallback to display CJK characters after updating to 1803 #332

New Issue
Closed
opened 2026-01-30 21:49:17 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 21:49:17 +00:00
Owner
Copy Link

Originally created by @tojo17 on GitHub (Jul 22, 2018).

Originally assigned to: @miniksa on GitHub.

  • Windows build number: Version 10.0.17134.165

  • What you're doing and what's happening:
    Under chcp 65001 (UTF-8)
    the Lucida Console font in cmd is unable to display Chinese Japanese and Korean characters after updating to 1803 version in semi-year channel:
    image

  • What's wrong / what should be happening instead:
    Under MS-Mincho it works fine (but the font is ugly):
    image

and under version 1709 (build 10.0.16299.492) it also worked fine:
image

I have different computers set in English, Japanese and Chinese language, they all behaved the same. Maybe I'll have to change some setting in the registry?

Originally created by @tojo17 on GitHub (Jul 22, 2018). Originally assigned to: @miniksa on GitHub. * Windows build number: Version 10.0.17134.165 * What you're doing and what's happening: **Under chcp 65001 (UTF-8)** the Lucida Console font in cmd is unable to display Chinese Japanese and Korean characters after updating to 1803 version in semi-year channel: ![image](https://user-images.githubusercontent.com/5460009/43044988-95cd69f6-8de2-11e8-9d17-4fd0c1031ee0.png) * What's wrong / what should be happening instead: Under MS-Mincho it works fine (but the font is ugly): ![image](https://user-images.githubusercontent.com/5460009/43044984-8b47f280-8de2-11e8-948d-5eb4694ae35a.png) and under version 1709 (build 10.0.16299.492) it also worked fine: ![image](https://user-images.githubusercontent.com/5460009/43044993-aa3ce7cc-8de2-11e8-979e-a67347eeca13.png) I have different computers set in English, Japanese and Chinese language, they all behaved the same. Maybe I'll have to change some setting in the registry?
claunia added the Product-ConhostWork-ItemArea-RenderingIssue-BugNeeds-Tag-Fix labels 2026-01-30 21:49:17 +00:00
claunia commented 2026-01-30 21:49:18 +00:00
Author
Owner
Copy Link

@amasover commented on GitHub (Nov 14, 2018):

I am seeing the same behavior on Windows 1803. I'm using the NSimSun font for now, as it looks much better than MS-Mincho. My system locale and display language are both set to English (United States). In control panel -> region -> administrative -> change system locale I tried checking the box "Beta: Use Unicode UTF-8 for worldwide language support" but that did nothing.

@amasover commented on GitHub (Nov 14, 2018): I am seeing the same behavior on Windows 1803. I'm using the NSimSun font for now, as it looks much better than MS-Mincho. My system locale and display language are both set to English (United States). In control panel -> region -> administrative -> change system locale I tried checking the box "Beta: Use Unicode UTF-8 for worldwide language support" but that did nothing.
claunia commented 2026-01-30 21:49:18 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Aug 29, 2019):

This ask is specifically tagged against the Console and is largely resolved by @miniksa's new renderer, though that renderer won't be on by default in Console prior to 21H1 release (at the earliest).

Let's revisit for 21H1

@bitcrazed commented on GitHub (Aug 29, 2019): This ask is specifically tagged against the Console and is largely resolved by @miniksa's new renderer, though that renderer won't be on by default in Console prior to 21H1 release (at the earliest). Let's revisit for 21H1
claunia commented 2026-01-30 21:49:18 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 10, 2021):

I just found this issue by pure chance. This can be closed now that the duplicate issue #10472 has been fixed.

@lhecker commented on GitHub (Sep 10, 2021): I just found this issue by pure chance. This can be closed now that the duplicate issue #10472 has 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 Area-Rendering Issue-Bug Needs-Tag-Fix Product-Conhost Work-Item
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#332
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?