7 Aug
2001
7 Aug
'01
8:08 p.m.
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? Tim McLaughlin