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

Width of kana are wrong and not uniform in Atlas #18583

New Issue
Open
opened 2026-01-31 06:18:26 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 06:18:26 +00:00
Owner
Copy Link

Originally created by @PhMajerus on GitHub (Oct 2, 2022).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.16.2642.0

Windows build number

10.0.22621.608

Other Software

No response

Steps to reproduce

Output Japanese hiragana and katakana using any CUI software.

Hiragana test string : *かきくけこ*がぎぐげご*さしすせそ*ざじずぜぞ*たちつてと*だぢづでど*はひふへほ*ばびぶべぼ*ぱぴぷぺぽ*
In JSON : "*\u304b\u304d\u304f\u3051\u3053*\u304c\u304e\u3050\u3052\u3054*\u3055\u3057\u3059\u305b\u305d*\u3056\u3058\u305a\u305c\u305e*\u305f\u3061\u3064\u3066\u3068*\u3060\u3062\u3065\u3067\u3069*\u306f\u3072\u3075\u3078\u307b*\u3070\u3073\u3076\u3079\u307c*\u3071\u3074\u3077\u307a\u307d*"

Katakana test string : *カキクケコ*ガギグゲゴ*サシスセソ*ザジズゼゾ*タチツテト*ダヂヅデド*ハヒフヘホ*バビブベボ*パピプペポ*
In JSON : "*\u30ab\u30ad\u30af\u30b1\u30b3*\u30ac\u30ae\u30b0\u30b2\u30b4*\u30b5\u30b7\u30b9\u30bb\u30bd*\u30b6\u30b8\u30ba\u30bc\u30be*\u30bf\u30c1\u30c4\u30c6\u30c8*\u30c0\u30c2\u30c5\u30c7\u30c9*\u30cf\u30d2\u30d5\u30d8\u30db*\u30d0\u30d3\u30d6\u30d9\u30dc*\u30d1\u30d4\u30d7\u30da\u30dd*"

(Note those test strings do not include all kanas, but only those that have common (han)dakuten variants)

Expected Behavior

These characters should render as double cells (except the separating *s), with their glyphs centered.

See the result in gnome-terminal:
image

Actual Behavior

Instead, all characters are left-aligned in their cells, and several (han)dakuten, but not all, are sized smaller than two cells, but still wider than a single cell... they look more like 1.5 cells but the length of the run of characters still accounts for double cells.

Here is the result of the same output in Windows Terminal 1.16.2642.0 using Atlas Engine
image

These are precomposed characters, their decomposed versions make the wrong spacing even more extreme.

Note that this is a bug introduced by the Atlas Engine, as in the same version of Windows Terminal but with Atlas Engine disabled, the result looks fine:
image

Originally created by @PhMajerus on GitHub (Oct 2, 2022). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.16.2642.0 ### Windows build number 10.0.22621.608 ### Other Software _No response_ ### Steps to reproduce Output Japanese hiragana and katakana using any CUI software. Hiragana test string : `*かきくけこ*がぎぐげご*さしすせそ*ざじずぜぞ*たちつてと*だぢづでど*はひふへほ*ばびぶべぼ*ぱぴぷぺぽ*` In JSON : `"*\u304b\u304d\u304f\u3051\u3053*\u304c\u304e\u3050\u3052\u3054*\u3055\u3057\u3059\u305b\u305d*\u3056\u3058\u305a\u305c\u305e*\u305f\u3061\u3064\u3066\u3068*\u3060\u3062\u3065\u3067\u3069*\u306f\u3072\u3075\u3078\u307b*\u3070\u3073\u3076\u3079\u307c*\u3071\u3074\u3077\u307a\u307d*"` Katakana test string : `*カキクケコ*ガギグゲゴ*サシスセソ*ザジズゼゾ*タチツテト*ダヂヅデド*ハヒフヘホ*バビブベボ*パピプペポ*` In JSON : `"*\u30ab\u30ad\u30af\u30b1\u30b3*\u30ac\u30ae\u30b0\u30b2\u30b4*\u30b5\u30b7\u30b9\u30bb\u30bd*\u30b6\u30b8\u30ba\u30bc\u30be*\u30bf\u30c1\u30c4\u30c6\u30c8*\u30c0\u30c2\u30c5\u30c7\u30c9*\u30cf\u30d2\u30d5\u30d8\u30db*\u30d0\u30d3\u30d6\u30d9\u30dc*\u30d1\u30d4\u30d7\u30da\u30dd*"` (Note those test strings do not include all kanas, but only those that have common (han)dakuten variants) ### Expected Behavior These characters should render as double cells (except the separating `*`s), with their glyphs centered. See the result in gnome-terminal: ![image](https://user-images.githubusercontent.com/25664275/193472152-c90ff783-f163-4b21-a06b-5556d874b1ad.png) ### Actual Behavior Instead, all characters are left-aligned in their cells, and several (han)dakuten, but not all, are sized smaller than two cells, but still wider than a single cell... they look more like 1.5 cells but the length of the run of characters still accounts for double cells. Here is the result of the same output in Windows Terminal 1.16.2642.0 using Atlas Engine ![image](https://user-images.githubusercontent.com/25664275/193472367-e291100e-ddb9-410e-9b75-c886d77ebc7b.png) These are precomposed characters, their decomposed versions make the wrong spacing even more extreme. Note that this is a bug introduced by the Atlas Engine, as in the same version of Windows Terminal but with Atlas Engine disabled, the result looks fine: ![image](https://user-images.githubusercontent.com/25664275/193472521-79c5b75b-c3e2-482a-a3e5-42adbee38444.png)
claunia added the Issue-BugIn-PRProduct-TerminalArea-AtlasEngine labels 2026-01-31 06:18:26 +00:00
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-AtlasEngine In-PR Issue-Bug 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#18583
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?