I found the source of my problem. I was adding the serialized data to a tar file via Archive::Tar->add_data. But I had missed the documentation in Archive::Tar that says:

Unicode strings need to be converted to UTF-8-encoded bytestrings before they are handed off to "add_data()":

So this change on the serializer

- $tar->add_data($filename, $serialized_context, { type => Archive: +:Tar::FILE }); + $tar->add_data($filename, encode_utf8($serialized_context), { typ +e => Archive::Tar::FILE });

and this change on the de-serializer

- $self->serialized_blob($serialized_context); + $self->serialized_blob(decode_utf8($serialized_context));

make it all work as expected, and my original problem makes more sense now, though it's not much more than GIGO.


In reply to Re: storable and utf8 by kgoess
in thread storable and utf8 by kgoess

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.