so \x{2018} is a two-byte encoding of chr(32) and chr(30)

Sorry, but no, this is incorrect. \x{2018} is not valid JavaScript, so I'm assuming it's Perl. In Perl, \x{2018} is interpreted as the Unicode character U+2018, LEFT SINGLE QUOTATION MARK, decimal 8216. Although one normally shouldn't have to worry about the internal encoding Perl uses, here it is anyway:

$ perl -CSD -MDevel::Peek -le 'my $x="\x{2018}"; Dump($x); print "<$x>"'
SV = PV(0x2147e80) at 0x21675b0
  REFCNT = 1
  FLAGS = (POK,IsCOW,pPOK,UTF8)
  PV = 0x21694e0 "\342\200\230"\0 [UTF8 "\x{2018}"]
  CUR = 3
  LEN = 10
  COW_REFCNT = 1
<‘>

Minor fixes.

In reply to Re^3: special characters in parsed json rendering badly in browser by haukex
in thread special characters in parsed json rendering badly in browser by slugger415

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.