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
print does not respect "use encoding 'utf8'" #7967
Comments
From williams@tni.comCreated by williams@tni.com#!perl use utf8; # this simulates a utf8 string without the utf8 bit set, # prints 'hÿpër' correctly # prints doubly-encoded utf8: 'hÿpër' # prints 'hÿpër' correctly # The point is that C< use encoding 'utf8' > did not make C< print > Perl Info
|
From @jkeenanOn Sat Jun 11 11:12:41 2005, williams@tni.com wrote:
This appears to be the case with say() as well: ##### my $x = 'hÿpër'; print "$x\n"; Output: ##### hÿpër |
The RT System itself - Status changed from 'new' to 'open' |
From @jkeenanOn Sat Jun 11 11:12:41 2005, williams@tni.com wrote:
PATH=/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/lib/jre/bin:/home/williams/bin:/sbin/:/usr/sbin:/usr/lib/jre/bin
On the p5p list lately I believe there has been discussion of the Could someone familiar with those issues review this older ticket? Thank you very much. |
From @rjbsI have not reviewed this, but: 1. encoding is part of the Encode dist, which is upstream CPAN; this bug *probably* belongs 2. encoding is deprecated and will be removed, which means that it is unlikely that we'll see a -- |
From @cpansproutOn Fri Aug 30 19:10:28 2013, rjbs wrote:
encoding.pm is a small wrapper around core functionality.
I have not reviewed the bug itself, but generally it is not clear at all I suggest we collect these in a meta ticket so that we can reject them -- Father Chrysostomos |
From @HugmeirOn Sat, Aug 31, 2013 at 2:56 AM, Father Chrysostomos via RT <
+10 |
From @ap* Brian Fraser <fraserbn@gmail.com> [2013-08-31 15:10]:
One of those 10 is me. |
From @khwilliamsonSince the 'use encoding' feature is scheduled to be removed in v5.22, we likely won't fix this, but as per -- |
@khwilliamson - Status changed from 'open' to 'stalled' |
From @dcollinsnOn Mon Mar 10 14:05:55 2014, khw wrote:
That link is, sadly, now stale. As 5.22 has come and gone, and "encoding" is deprecated, what is the plan for tickets like this? -- |
The RT System itself - Status changed from 'stalled' to 'open' |
From @cpansproutOn Thu Jul 07 17:49:07 2016, dcollinsn@gmail.com wrote:
I am hoping to remove the functionality that encoding.pm wraps some time soon. At that point, the tickets related to it will be rejected. -- Father Chrysostomos |
From @cpansproutThe encoding.pm functionality was removed in the branch merged as a9cb10c. -- Father Chrysostomos |
@cpansprout - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#36248 (status was 'rejected')
Searchable as RT36248$
The text was updated successfully, but these errors were encountered: