ó
is the UTF-8 encoded version of ó
My guess is your JSON serializer is converting to UTF-8. Maybe that can output ISO-8859-1 instead? (see What is the difference between UTF-8 and ISO-8859-1?)
If you are setting the cookie via a Set-Cookie
HTTP Header (vs. in JavaScript), IE probably handles this different that Chrome. (see HTTP header should use what character encoding?)
Update: EricLaw's comment is correct about using US-ASCII. I think RFC 2047 is the best reference on this, where it introduces "encoded word" for character sets other than US-ASCII.
However, in this particular example, instead of using encoded word or %XX URL encoding, this cookie value is JSON, so I would use the JavaScript string escape sequence (see Special Characters (JavaScript) and Converting Unicode strings to escaped ascii string). ó
is character 0xF3 so use the string '\u00F3'
in your JSON formatted cookie value. This allows any client side cookie reads, to just JSON.parse() the value.
document.cookie
"ProcessArray=[{"ProcessID":1,"Description":"Adquisici\u00F3n de
Articulos","Path":"internalprocess.aspx?process=1"}]"