Some remarks:
my $ok = utf8::decode($json);
is not the best way to validate utf8. Because:
-
It only validates Perl's notion of utf-8. Which is not exactly what the Unicode Consortium says.
use feature 'say';
binmode STDOUT, 'encoding(utf-8)';
my $str = "\xFC\x90\x80\x80\x80\x80";
my $ok = utf8::decode( $str );
say $ok ? 'ok' : 'not ok';
say $str;
output:
ok
Code point 0x10000000 is not Unicode, may not be portable at demo.pl l
+ine 8.
"\x{10000000}" does not map to utf8 at demo.pl line 8.
\x{10000000}
-
It always decodes a string in place. So doing
my $ok = utf8::decode($json);
Dump( $json );
is not super useful
Second, according to JSON's docs,
encode_json is equivalent to
JSON->new->utf8->encode($perl_scalar), while
to_json is
JSON->new->encode($perl_scalar). I don't know how these modules work, but the presence/absence of
->utf8 probably makes some difference?
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.