But in your world view, [unpack "H*", pack "U", $codepoint] should return some variable number of hex digits that has no clear definition already laid out for it.

pack producing something that isn't bytes? Unpacking something that (potentially) isn't bytes? In my world view, the construct doesn't make much sense.

I don't have any experience will "U" which is why I didn't comment on it initially. I'm not in a good position to judge what the problem with the new or old method are since I don't even know what kind of problems it solves. I'll read your post when I have more time to absorb it.

In reply to Re^10: Parsing UTF-16LE CSV Records Using Text::CSV* (5.10) by ikegami
in thread Parsing UTF-16LE CSV Records Using Text::CSV* by Jim

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.