Converting to Base64 would be massive overkill, surely.


There's no reason you can't include strings containing HTML in JSON
data.  You just have to make sure your strings are valid string
literals, like this:

    message: "<p>This is HTML.</p>"

There's nothing special other than making sure the HTML is correctly
escaped -- e.g., if you're putting the JSON string in double quotes,
naturally any double quotes in the HTML will need a backslash in front
of them -- as, for that matter, will any backslashes!

T.J. Crowder
tj / crowder software / com

On Apr 24, 5:05 pm, Ananth Raghuraman <araghuram...@gmail.com> wrote:
> JSON should not contain HTML for tactical/ease of programming purposes
> unless the HTML is there as part of a larger design, but there may or may
> not be implementation restrictions.
> If you are facing problems, can you try encoding the HTML string (Base64)
> and decoding back (using Javascript Base64 code ) before display on the
> browser?
> On Fri, Apr 24, 2009 at 11:30 AM, Matt <guitarroman...@gmail.com> wrote:
> > Hi there,
> > I'm using PHP to output some JSON through AJAX to my page. It breaks
> > whenever I use a backslash or quote mark.
> > I've tried using php's json_encode function which doesn't seem to
> > help, just breaks it further. I've also tried php's addslashes() to
> > the output, again, same problem.
> > Am I approaching this correctly, fundamentally? Is JSON supposed to
> > contain HTML?
> > Thanks,
> > Matt
You received this message because you are subscribed to the Google Groups 
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptaculous@googlegroups.com
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to