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

[PR #19274] docs: clarify color names and ECMA-48 mappingdocs: clarify color names and ECMA-48 mappingDocs/color names ecma48 explanation #31778

New Issue
Open
opened 2026-01-31 09:49:29 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:49:29 +00:00
Owner
Copy Link

Original Pull Request: https://github.com/microsoft/terminal/pull/19274

State: closed
Merged: No

Summary of the Pull Request

This PR adds a comprehensive documentation file doc/color-names-ecma48.md that clarifies confusing color terminology and provides practical ANSI/ECMA-48 mapping tables for Windows Terminal users.

References and Relevant Issues

Closes #2641 - Addresses the confusion around color names, ANSI vs ECMA-48 terminology, and provides clear mapping between different color naming conventions.

Detailed Description of the Pull Request / Additional comments

This documentation directly addresses the confusion highlighted in issue #2641 by providing:

🎯 For Beginners:

  • Clear explanations of why terminal colors are confusing (different naming conventions across systems)
  • Simple mapping tables showing ANSI codes, RGB values, Windows Terminal names, and plain language descriptions
  • Practical examples with copy-paste ready code for Bash, PowerShell, and Windows Terminal settings
  • Plain language clarifications like "Bright black = Gray" and "Purple vs Magenta"

📚 Comprehensive Coverage:

  • Standard 8 colors (3-bit) with complete mapping tables
  • Bright colors (4-bit) with beginner-friendly explanations
  • Extended color modes (256-color and true color) with examples
  • Background color codes and reset sequences
  • Accessibility considerations and best practices

🔗 Resource Links:

  • Links to official ECMA-48 and ISO/IEC 6429 standards
  • Windows Terminal documentation and color scheme references
  • Community tools and color testing scripts

🎯 Key Benefits:

  1. Eliminates confusion between ANSI, ECMA-48, VT100, and other color terminology
  2. Provides quick reference tables for developers and users
  3. Bridges the gap between technical standards and practical usage
  4. Supports both beginners and advanced users with appropriate examples
  5. Includes accessibility guidance for inclusive color usage

The document is structured to be both a learning resource for newcomers and a quick reference for experienced users, directly addressing the pain points mentioned in #2641.

Validation Steps Performed

  • ✅ All color codes and examples have been tested for accuracy
  • ✅ Links to official documentation and standards verified
  • ✅ Examples tested in Windows Terminal, PowerShell, and Bash
  • ✅ Markdown formatting validated for proper rendering
  • ✅ Content reviewed for beginner accessibility and technical accuracy

PR Checklist

References and Relevant Issues

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

PR Checklist

  • Closes #xxx
  • Tests added/passed
  • Documentation updated
    • If checked, please file a pull request on our docs repo and link it here: #xxx
  • Schema updated (if necessary)
**Original Pull Request:** https://github.com/microsoft/terminal/pull/19274 **State:** closed **Merged:** No --- ## Summary of the Pull Request This PR adds a comprehensive documentation file `doc/color-names-ecma48.md` that clarifies confusing color terminology and provides practical ANSI/ECMA-48 mapping tables for Windows Terminal users. ## References and Relevant Issues Closes #2641 - Addresses the confusion around color names, ANSI vs ECMA-48 terminology, and provides clear mapping between different color naming conventions. ## Detailed Description of the Pull Request / Additional comments This documentation directly addresses the confusion highlighted in issue #2641 by providing: ### 🎯 **For Beginners:** - **Clear explanations** of why terminal colors are confusing (different naming conventions across systems) - **Simple mapping tables** showing ANSI codes, RGB values, Windows Terminal names, and plain language descriptions - **Practical examples** with copy-paste ready code for Bash, PowerShell, and Windows Terminal settings - **Plain language clarifications** like "Bright black = Gray" and "Purple vs Magenta" ### 📚 **Comprehensive Coverage:** - Standard 8 colors (3-bit) with complete mapping tables - Bright colors (4-bit) with beginner-friendly explanations - Extended color modes (256-color and true color) with examples - Background color codes and reset sequences - Accessibility considerations and best practices ### 🔗 **Resource Links:** - Links to official ECMA-48 and ISO/IEC 6429 standards - Windows Terminal documentation and color scheme references - Community tools and color testing scripts ### 🎯 **Key Benefits:** 1. **Eliminates confusion** between ANSI, ECMA-48, VT100, and other color terminology 2. **Provides quick reference tables** for developers and users 3. **Bridges the gap** between technical standards and practical usage 4. **Supports both beginners and advanced users** with appropriate examples 5. **Includes accessibility guidance** for inclusive color usage The document is structured to be both a learning resource for newcomers and a quick reference for experienced users, directly addressing the pain points mentioned in #2641. ## Validation Steps Performed - ✅ All color codes and examples have been tested for accuracy - ✅ Links to official documentation and standards verified - ✅ Examples tested in Windows Terminal, PowerShell, and Bash - ✅ Markdown formatting validated for proper rendering - ✅ Content reviewed for beginner accessibility and technical accuracy ## PR Checklist - [x] Closes #2641 - [x] Tests added/passed (Examples verified in multiple terminals) - [x] Documentation updated (This IS a documentation addition) - [ ] Schema updated (not necessary for documentation)## Summary of the Pull Request ## References and Relevant Issues ## Detailed Description of the Pull Request / Additional comments ## Validation Steps Performed ## PR Checklist - [ ] Closes #xxx - [ ] Tests added/passed - [ ] Documentation updated - If checked, please file a pull request on [our docs repo](https://github.com/MicrosoftDocs/terminal) and link it here: #xxx - [ ] Schema updated (if necessary)
claunia added the pull-request label 2026-01-31 09:49:29 +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 pull-request
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#31778
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?