Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

Re^2: special characters in parsed json rendering badly in browser

by TheloniusMonk (Sexton)
on Sep 03, 2018 at 07:54 UTC ( [id://1221605]=note: print w/replies, xml ) Need Help??


in reply to Re: special characters in parsed json rendering badly in browser
in thread special characters in parsed json rendering badly in browser

This node falls below the community's threshold of quality. You may see it by logging in.
  • Comment on Re^2: special characters in parsed json rendering badly in browser

Replies are listed 'Best First'.
Re^3: special characters in parsed json rendering badly in browser
by haukex (Archbishop) on Sep 03, 2018 at 09:10 UTC
    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.

Re^3: special characters in parsed json rendering badly in browser
by Your Mother (Archbishop) on Sep 03, 2018 at 09:07 UTC

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1221605]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others surveying the Monastery: (9)
As of 2024-04-24 07:16 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found