If you show a little more code, esp. how your perl script opens the output file, that may help. Your perl upgrade might be interacting with your current shell environment regarding "locale", What version were you using the last time it worked? What version did you upgrade to? In what OS?
Then, maybe a sample of the output you expect (e.g. as a snippet hex dump from a good file), along with a sample of what your upgraded perl is producing (also as a hex dump snippet).
Till then, there's nothing much we can do...
Update: BTW,the way to avoid unicode "interpretation" on output is to open the output file like this:
open( my $outfh, '>:raw', $filename ) or die "$filename: $!\n";
(but if the data you print to the output file handle has somehow been flagged as utf8 text, you might get a warning about that)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.