Skip to content

Comments

Fix ASCII fallback for box-drawing chars when alt charset unsupported#1638

Merged
gnodet merged 1 commit intomasterfrom
fix/ascii-fallback-line-drawing
Feb 23, 2026
Merged

Fix ASCII fallback for box-drawing chars when alt charset unsupported#1638
gnodet merged 1 commit intomasterfrom
fix/ascii-fallback-line-drawing

Conversation

@gnodet
Copy link
Member

@gnodet gnodet commented Feb 19, 2026

Summary

  • When a terminal does not support alternate charset mode (smacs/rmacs), box-drawing Unicode characters were passed through as-is
  • Terminals that can't render these (e.g., TERM=screen-256color) displayed garbled output like qqqqqq instead of horizontal lines
  • Added ASCII fallback: -, |, corners/intersections → +

Fixes #1259

Test plan

  • ./mvx mvn -pl terminal -am test passes
  • Manual: verify with TERM=screen-256color that TailTipWidgets separator renders as ------ instead of qqqqqq

…s unsupported

When a terminal does not support alternate charset mode (enter_alt_charset_mode /
exit_alt_charset_mode capabilities), box-drawing Unicode characters like '─' were
passed through as-is. Terminals that cannot render these characters would display
garbled output (e.g., 'qqqqqq' instead of '------' for horizontal lines).

Add an else branch that converts box-drawing characters to ASCII equivalents:
  ─ → -    │ → |    corners/intersections → +

Fixes #1259
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TailTipWidgets prints qqqqqq instead of ---- as separator when TERM is screen-256color instead of xterm-256color

1 participant