Tim McLaughlin writes:

OK, I used shane's tcpwatch to see why one page with Japanese characters (Unicode) rendered properly as kanji whereas the same property set when shown in the management screens (and therefore in a textarea) did not render as kanji, only to learn nothing :(

I expected to see the header content-type: text/html followed by charset=utf-8 in the one that worked, but this wasn't true in either... any ideas why one renders as unicode kanji, and the other as garbled junk? Did you see a

<meta http_equiv="Content-Type" content="text/html; charset=..."> in the header of your working page? Dieter