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 handling on Windows command line #5244
Comments
From joerg.thomas.de@googlemail.comI hope Unicode passes through via e-mail, if not please refer to the Unicode handling on the Windows command line fails: C:\Windows\System32>perl6 -e "'Я'.say" Interestingly, this works: C:\Windows\System32>perl6 -e "Buf.new(0xD0, 0xAF).decode('UTF-8').say" Seen on Rakudo version 2016.01.1 built on MoarVM version 2016.01 |
From @zoffixznetOn Mon Apr 18 13:51:31 2016, joerg.thomas.de@googlemail.com wrote:
Does it still fail if you change cmd.exe to use unicode code page? Run chcp 65001 in the terminal first. |
The RT System itself - Status changed from 'new' to 'open' |
From @zoffixznetOn Tue Apr 19 11:00:00 2016, cpan@zoffix.com wrote:
To answer my own question: yes, it still fails. It also fails if you spurt it into a file. Looking around, I found this StackOverflow answer with one of the commenters claiming there are bugs with cmd.exe and programs that use IO from C standard lib: http://stackoverflow.com/questions/388490/unicode-characters-in-windows-command-line-how/388500#​388500 |
From @zoffixznetAnother report in NQP repo: Raku/nqp#346 ------------->8---------------------- It is entirely possible that I am missing something obvious, but while trying to figure out what happens between typing C:\> perl6 -e "say 'yağmur'" and getting the output yagmur |
From @zoffixznetFWIW, nqp -e "say('yağmur')" and perl -C -wlE "use utf8; say('yağmur')" have the same issue (the output comes out as `yagmur`, without the thingie on `g`). So, perhaps this is a Windows command prompt issue? |
From 1parrota@gmail.comA quick look at Stackoverflow suggests that Windows isn't being On 2/7/17, Zoffix Znet via RT <perl6-bugs-followup@perl.org> wrote:
|
From @nanisThe problem is caused by the fact that moar.exe uses main rather than However, I wrote a wrapper around moar.exe which basically does what In that case, I get incorrectly encoded output as in: C:\> p6run -e "say 'yağmur'" and C:\> p6run yağmur.pl6 perl and a bunch of other programs also use main instead of wmain, so I would like to know what encoding is assumed for command line Thank you. -- Sinan |
From @nanisI created this report by mistake when I was hastily trying to follow-up on https://rt.perl.org/Public/Bug/Display.html?id=127925 The reply belongs there. I would appreciate it if you could merge this Apologies and thank you. |
From @nanis@Parrot Raiser, please see -- Sinan |
From @nanisSee also MoarVM/MoarVM#527 |
From @nanisI think my pull request has reached the point where it should work on Please try it out: |
From @nanishttps://github.com/MoarVM/MoarVM/pull/528/files?diff=split was merged so this ticket can be closed. Thank you. -- Sinan |
From @zoffixznetMarking as testsneeded. |
From @zoffixznetTests added Raku/roast@5eb61ccaf2 |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#127925 (status was 'resolved')
Searchable as RT127925$
The text was updated successfully, but these errors were encountered: