microsoft / microsoft/terminal
Error render Regional Indicator flags
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
### Windows Terminal version
latest
### Windows build number
Win 10 22H2
### Other Software
font - JetBrainsMonoNL Nerd Font
### Steps to reproduce
a.go
```
package main
import (
"fmt"
)
func main() {
// flag - 🏳️🌈
fmt.Println(string([]byte{0xf0, 0x9f, 0x8f, 0xb3, 0xef,
0xb8, 0x8f, 0xe2, 0x80, 0x8d, 0xf0, 0x9f, 0x8c, 0x88}))
// DE - 🇩🇪
fmt.Println(string([]byte{0xf0, 0x9f, 0x87, 0xa9, 0xf0, 0x9f, 0x87, 0xaa}))
}
```
### Expected Behavior
first emoji (rainbow flag) - show right because its a true ZWJ emoji
but second - it two Regional Indicator flags and show as error glyph.
But VSCode with same font show this two Regional Indicator flags properly as `DE` in editor and in own's debug console/terminal.
### Actual Behavior
-
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the provided a.go reproduction in Windows Terminal on Windows 10 22H2 with JetBrainsMonoNL Nerd Font, then compare the Regional Indicator output with VSCode. Done means the DE flag renders correctly while the rainbow flag continues to render correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100