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

Unicode: shells print garbage instead of "「」" #6639

Open
p6rt opened this issue Nov 16, 2017 · 3 comments
Open

Unicode: shells print garbage instead of "「」" #6639

p6rt opened this issue Nov 16, 2017 · 3 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Nov 16, 2017

Migrated from rt.perl.org#132452 (status was 'open')

Searchable as RT132452$

@p6rt
Copy link
Author

p6rt commented Nov 16, 2017

From @lefth

The Windows command shells I've used (CMD and Cmder) fail to print the "「」"
that are part of stringified matches. This is a significant issue, since
new users use regular expressions when working through tutorials.

Since pasting these characters into the console will also yield garbage, I
suggest we pick different symbols, like "��", instead. (IMO, it's important
to choose two symbols that will not blend together when showing an empty
match.)

The current output​:

say 'a' ~~ /./
��óa��ú

Note​: I'm using the October 2017 Rakudo release.

@p6rt
Copy link
Author

p6rt commented Nov 16, 2017

From @zoffixznet

On Thu, 16 Nov 2017 02​:28​:11 -0800, dan@​zwell.net wrote​:

The Windows command shells I've used (CMD and Cmder) fail to print the "「」"
that are part of stringified matches. This is a significant issue, since
new users use regular expressions when working through tutorials.

Since pasting these characters into the console will also yield garbage, I
suggest we pick different symbols, like "��", instead. (IMO, it's important
to choose two symbols that will not blend together when showing an empty
match.)

The current output​:

say 'a' ~~ /./
��óa��ú

Note​: I'm using the October 2017 Rakudo release.

That's because Windows cmd.exe isn't using UTF-8 by default. You need to run `chcp 65001` to switch to the proper code page.

-1 on trying to cater to cmd.exe's featureset or using mismatched brackets.

@p6rt
Copy link
Author

p6rt commented Nov 16, 2017

The RT System itself - Status changed from 'new' to 'open'

@p6rt p6rt added the Windows label Jan 5, 2020
codesections referenced this issue in rakudo/rakudo Oct 28, 2020
- to be shown when starting the REPL
- to be shown when doing `raku -v`

As part of the effort of trademarking Rakudo and Raku.  codesections++
for working with The Perl Foundation on this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant