ansaurus

Question

Javascript parse error on '\u2028' unicode character

Answer 1

A:

Well, that makes sense, since you are telling the browser that the HTML and script are both using UTF-8, but then you specify a character that is not UTF-8 encoded. When you specify "charset=UTF-8", you are respoonsible for making sure the bytes transmitted to the browser are actually UTF-8. The web server and and browser will not do it for you in this situation.

Remy Lebeau - TeamB 2010-06-03 20:07:43

So, how to solve it? The character was entered by a user of the website. His data is stored in JSON. Every time I request the JSON I get a parse error, because the character is in there. I cannot just delete the character, because it's likely that the client will enter it again.

klaaspieter 2010-06-04 04:45:06

According to the comments for [this](http://stackoverflow.com/questions/1811505/with-jquery-access-json-from-cross-domain-url-where-json-may-be-poorly-formed#1811737) answer, this is a valid UTF-8 character which should be correctly parsed.

klaaspieter 2010-06-04 07:50:35

Answer 2

+1 A:

Could you just use \u2028, instead of real character?, because U+2028 is unicode line seperator, browsers would think that as real line break character like \n.

We cannot do like

x = "

"

Right? but we do x = "\n", so might be same concept.

S.Mark 2010-06-04 08:08:04

Douglas Crockford's JSON implementation does escape the string, but still throws the parse error. In Safari the native JSON implementation is used, which also throws the parse error.We're loading jsonp so the browser will attempt to parse it before any other javascript has a chance to strip out any invalid characters. I will probably have to solve this server side.

klaaspieter 2010-06-04 08:16:57

Yeah @klaaspieter, probably on server side, and If you got to do that, also escape `\u2029` too

S.Mark 2010-06-04 08:20:24

By the way, I've tested it some more, Douglas Crockford's implementation is *not* throwing the parse error.

klaaspieter 2010-06-04 09:05:10

Answer 3

+1 A:

Alright,to answer my own question.

Normally a JSON parser strips out these problem characters, because I was retrieving JSONP I wasn't using a JSON parser, in stead the browser tried to parse the JSON itself as soon as the callback was called.

The only way to fix it was to make sure the server never returns these characters when requesting a JSONP resource.

p.s. My question was about u2028, according to Douglas Crockford all of the following characters can cause these problems:

\u0000\u00ad\u0600\u0604\u070f\u17b4\u17b5\u200c\u200f\u2028\u202f\u2060\u206f\ufeff\ufff0-\uffff

klaaspieter 2010-06-04 11:06:09

ansaurus

tags:

views:

answers:

Javascript parse error on '\u2028' unicode character

related questions