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

Does not handle ansi-bbs line drawing characters correctly #20858

New Issue
Closed
opened 2026-01-31 07:26:03 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:26:03 +00:00
Owner
Copy Link

Originally created by @kalleswe on GitHub (Nov 21, 2023).

Windows Terminal version

1.18.2822.0

Windows build number

10.0.19045.3693

Other Software

No response

Steps to reproduce

Connect to any ansi bbs and you will see that line drawing characters/ansi is not properly displayed.

Expected Behavior

Correct rendering of line drawing charachters/ansi

Actual Behavior

blocky and round characheters and misalined gfx.

Originally created by @kalleswe on GitHub (Nov 21, 2023). ### Windows Terminal version 1.18.2822.0 ### Windows build number 10.0.19045.3693 ### Other Software _No response_ ### Steps to reproduce Connect to any ansi bbs and you will see that line drawing characters/ansi is not properly displayed. ### Expected Behavior Correct rendering of line drawing charachters/ansi ### Actual Behavior blocky and round characheters and misalined gfx.
claunia added the Needs-TriageIssue-BugNeeds-Author-FeedbackNo-Recent-Activity labels 2026-01-31 07:26:04 +00:00
claunia commented 2026-01-31 07:26:05 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 21, 2023):

Can you please enable "AtlasEngine" in the "Rendering" section of the settings and try it again?

@lhecker commented on GitHub (Nov 21, 2023): Can you please enable "AtlasEngine" in the "Rendering" section of the settings and try it again?
claunia commented 2026-01-31 07:26:05 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 21, 2023):

Also, sharing the specific font you're using would be helpful too (if atlas engine doesn't fix it)

@zadjii-msft commented on GitHub (Nov 21, 2023): Also, sharing the specific font you're using would be helpful too (if atlas engine doesn't fix it)
claunia commented 2026-01-31 07:26:05 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Nov 25, 2023):

I suspect the issue is the character set. ANSI-BBS is typically going to expect you to be using code page 437 (or at least one of the other DOS code pages), and if you're connecting via a WSL telnet you're going to have UTF-8. That's the difference between something like this (using UTF-8):

image

and this (using code page 437):

image

You may still encounter other issues, because the ANSI-BBS protocol is not fully compatible with VT terminals, but the character set will be the most obvious problem.

In terms of font choice, I find Consolas works better than Cascadia, and the new Atlas engine is better than the DX engine, but those differences aren't hugely significant.

@j4james commented on GitHub (Nov 25, 2023): I suspect the issue is the character set. ANSI-BBS is typically going to expect you to be using code page 437 (or at least one of the other DOS code pages), and if you're connecting via a WSL telnet you're going to have UTF-8. That's the difference between something like this (using UTF-8): ![image](https://github.com/microsoft/terminal/assets/4181424/722018e3-c7c9-4325-a37d-1e86cdd84896) and this (using code page 437): ![image](https://github.com/microsoft/terminal/assets/4181424/5f481f58-d37b-49b2-9830-50d222225260) You may still encounter other issues, because the ANSI-BBS protocol is not fully compatible with VT terminals, but the character set will be the most obvious problem. In terms of font choice, I find Consolas works better than Cascadia, and the new Atlas engine is better than the DX engine, but those differences aren't hugely significant.
claunia commented 2026-01-31 07:26:06 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Nov 29, 2023):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Nov 29, 2023): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 Issue-Bug Needs-Author-Feedback Needs-Triage No-Recent-Activity
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#20858
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?