-
Notifications
You must be signed in to change notification settings - Fork 560
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
Text::CSV::Encoded is incorrectly forced to parse widechar #15739
Comments
From rafal@zorro.ztk-rp.euCreated by rafal@zorro.ztk-rp.euAfter upgrading from debian-wheezy to debian-jessie HTML::Mason started ========================
|
From @jkeenanOn Mon, 28 Nov 2016 12:34:02 GMT, rafal@zorro.ztk-rp.eu wrote:
It appears that the file does indeed contain characters which satisfy the condition required for the "Wide characters" warning. Here's what pod/perldiag.pod in perl-5.24.0 says: ##### (S utf8) Perl met a wide character (>255) when it wasn't expecting If I put your test data into a file and run it through 'od -c', I observe two characters in the >255 range. ##### Text::CSV::Encoded is not part of the Perl 5 core distribution, so I think including it in the test script muddies the waters. Here's a pure Perl reduction: ##### open(my $FH, '<', 'warsaw.txt') or die "open"; I think that warning is appropriate. However, I concede that I don't have much experience with 'cp1250' so I'm unclear what the expected behavior is. Other people on list should comment. Thank you very much. |
The RT System itself - Status changed from 'new' to 'open' |
From @jkeenanOn Mon, 28 Nov 2016 23:03:51 GMT, jkeenan wrote:
On #p5p khw has pointed out an error in my analysis. 'od -c' prints octal. So these characters are below \0377 equivalent to 255. Also, in my test program I should have applied binmode to STDOUT as well. ##### open(my $FH, '<', 'warsaw.txt') or die "open"; And once I 'binmode' STDOUT, the "Wide character" warning goes away. So, notwithstanding my errors, I still think this is not a bug -- at least not in perl-5.24.0. Thank you very much. -- |
From @eserteDana Mon, 28 Nov 2016 04:34:02 -0800, rafal@zorro.ztk-rp.eu reče:
As it seems to make a difference if the CSV file has DOS or UNIX newlines --- can you attach the sample file? (In any case, either with DOS or UNIX newlines I don't see different behavior between Debian's perl in wheezy and jessie) |
From cm.perl@abtela.comLe 28/11/2016 à 13:34, (via RT) a écrit :
Maybe a wild shot but isn't that combination asking for trouble ? FWIW, |
From @jkeenanOn Tue, 29 Nov 2016 08:24:13 GMT, slaven@rezic.de wrote:
[snip]
Rafal, can you please provide the sample file as an email attachment? We will need this for further diagnosis. Thank you very much. -- |
From @jkeenanOn Fri, 02 Dec 2016 21:55:42 GMT, jkeenan wrote:
If there's no response from the original poster within a week, I will close this ticket. Thank you very much. -- |
From @jkeenanOn Sun, 25 Dec 2016 02:12:24 GMT, jkeenan wrote:
Closing as per schedule. Thank you very much. -- |
@jkeenan - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#130199 (status was 'rejected')
Searchable as RT130199$
The text was updated successfully, but these errors were encountered: