Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The cursor position looks to be incorrect after output IVS ( Ideographic Variation Sequence : U+E0100 to U+E01EF) #8731

Closed
hymkor opened this issue Jan 10, 2021 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@hymkor
Copy link

hymkor commented Jan 10, 2021

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
  • Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Windows Terminal version (if applicable):
  • 1.4.3243.0
Any other software?
  • go1.15.6 windows/amd64 OR node.js v15.5.1

( I consider that any programming language program that supports Unicode(UTF8) can reproduce the behaviour. )

Steps to reproduce

By Golang, execute go run sample.go

// sample.go
package main

import (
	"fmt"
)

func main() {
	fmt.Print("[\u908A\U000E0104]\n")
	fmt.Print("[\u908A\U000E0104")
	fmt.Print("]\n")
	fmt.Print("[ABCD")
	fmt.Print("]\n")
}

Or, on node.js 's command line , execute as below

process.stdout.write("[\u908A\u{E0104}]\n")
process.stdout.write("[\u908A\u{E0104}") ; process.stdout.write("]\n")
process.stdout.write("[ABCD") ; process.stdout.write("]\n")

Expected behavior

I expect that these text are output as below.

[邊󠄄]
[邊󠄄]
[ABCD]

The first line and the second line are same and no blank(space) exist anywhere.
The third line exists to show that the print/write function does not insert any blank.

Actual behavior

The cursor position after output IVS( Ideographic Variation Sequence : U+E0100 to U+E01EF) seems to be incorrect

[邊󠄄]
[邊󠄄 ]
[ABCD]

image

image

Would you please confirm the behaviour above ?

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jan 10, 2021
@skyline75489
Copy link
Collaborator

I think this is covered in #3546. The Unicode support is not complete yet.

@zadjii-msft
Copy link
Member

I'm inclined to agree. Thanks @skyline75489!

/dup #3546

@ghost
Copy link

ghost commented Jan 11, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jan 11, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jan 11, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants