> no, kid encodes this correctly in utf-8 as two-byte-sequence: C2 A9. ... > this happens if your browser decodes these two bytes according to > ISO-8859-1 as two characters. ...
Hi Martina, Thank you very much for your advices. Yes, you guys all right. It was an untidiness in template which didn't tell the browser of UTF-8 content type. Returning of <meta http-equiv="content-type" content="text/html; charset=UTF-8" /> back fixed it.
