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

Telnet to mapscii.me doesn't work (not enough xterm features) #104

Closed
bitcrazed opened this issue Feb 16, 2018 · 4 comments
Closed

Telnet to mapscii.me doesn't work (not enough xterm features) #104

bitcrazed opened this issue Feb 16, 2018 · 4 comments
Labels
Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Area-VT Virtual Terminal sequence support Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Conhost For issues in the Console codebase Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@bitcrazed
Copy link
Contributor

From @timfel on May 30, 2017 9:44

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    10.0.15063

  • What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)
    Type telnet mapscii.me. This will connect to the server of this project: https://github.com/rastapasta/mapscii. The expectation is to see an ASCII map of the world.

  • What's wrong / what should be happening instead:
    Expected:
    image

Got:
image

Copied from original issue: microsoft/WSL#2173

@bitcrazed
Copy link
Contributor Author

From @sunjoong on May 30, 2017 13:38

@timfel - It looks like to be able to draw shape of land but not to print names in my case on unbuntu and gentoo on WSL;
map

@bitcrazed
Copy link
Contributor Author

From @zadjii-msft on July 13, 2017 22:29

@timfel what font & size are you using? I believe that on Insider's builds, it works fine

image

Albeit, I couldn't find a font with the right characters

@bitcrazed
Copy link
Contributor Author

From @shanselman on January 19, 2018 22:49

@tara-raj good test case for font fallback.

@zadjii-msft zadjii-msft added Product-Conhost For issues in the Console codebase and removed console labels May 21, 2018
ellemenno added a commit to ellemenno/programming-pages that referenced this issue Jan 27, 2019
vanilla windows terminal (cmd.exe) does not have robust unicode support
beyond the old ibm codepage 437.

the console team is aware and working on it..

- microsoft/WSL#75
- microsoft/terminal#104
- microsoft/terminal#190
- microsoft/terminal#226
- microsoft/terminal#306
@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label May 17, 2019
@miniksa miniksa added Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Area-VT Virtual Terminal sequence support Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. labels May 29, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label May 29, 2019
@miniksa
Copy link
Member

miniksa commented May 29, 2019

This is exactly #94

@miniksa miniksa closed this as completed May 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Area-VT Virtual Terminal sequence support Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Conhost For issues in the Console codebase 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