I ran into an issue where the parser was generating a "Wide character in print" warning. A Google search revealed that this is usually caused by unicode being handled improperly.

"Wide character in print" means you are trying to store a string of characters without converting them to bytes first. Files can only contain bytes.

Is the > prior to Item Summary no longer telling perl to create a new file to write too?

open(my $fh, "> $file") Old style open(my $fh, '>', $file) Better 5.6 style open(my $fh, '>:utf8', $file) Better 5.6 style with auto encoding

Always check the result of open for errors. You'll catch 99% of I/O errors.


In reply to Re: Solution to unicode issue creating more problems than it solves by ikegami
in thread Solution to unicode issue creating more problems than it solves by Mr.Churka

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.