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] Cannot print chr(0x00F6) properly #16547
Comments
From @tisonkun* The Problem $ perl -e 'print chr(0x00F6)' Where chr(0x00F6) should be ö and it is printed properly by Python or Perl * Version Info $ perl -v This is perl 5, version 26, subversion 2 (v5.26.2) built for Copyright 1987-2018, Larry Wall Perl may be copied only under the terms of either the Artistic License or Complete documentation for Perl, including FAQ lists, should be found on - PS: Looking forward to your reply. At least let me know this e-mail has Alex. |
From @khwilliamsonOn Sat, 05 May 2018 01:14:34 -0700, wander4096@gmail.com wrote:
If you add the -C option, it works properly perl -C -e 'print chr(0x00F6)' What I suspect is happening is that your terminal is set up for UTF-8 text. Perl is printing the F6, but that is illegal UTF-8, and so your terminal doesn't handle it as one might expect. Perl doesn't know what your terminal is set up for. Specifying the -C tells it. With -C, perl converts the F6 to its UTF-8 representation before printing. The reason anything above 0xFF does print correctly is that it can't possibly be represented by a single byte, and so Perl converts it to UTF-8, and your terminal is happy. But you get the wide character warning indicating that Perl expects your terminal to not be able to handle UTF-8. I don't know why the other tools seem to work here. Can you detail what happened when your perlbug failed? |
The RT System itself - Status changed from 'new' to 'open' |
From @khwilliamsonNo response from OP. This ticket is not a perl issue. |
@khwilliamson - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#133177 (status was 'rejected')
Searchable as RT133177$
The text was updated successfully, but these errors were encountered: