From: "Globemaker" <firstname.lastname@example.org>
> Additional notes:
> I tried to fix the problem by posting UTF-32 codepoints directly into
> the blogspot. I verified that the values were near & # 73728. But the
> next day, they had all been changed to UTF-16. What next? Will those
> UTF-16 pairs of 16 bit integers be replaced by single & # 65533
> question marks again? I expect so. As a separate test, I have posted
> Cuneiform Unicode to Wordpress to see if it is uncensored there.
Besides setting up your OWN webv site, here is a simple solution.
Instead of posting the text in UTF-32 codepoints directly, post a graphic of the paragraph
of the text represented in UTF-32 codepoints.
BTW: I don't think the word "censorship" is apropos in this situation.
Multi-AV Scanning Tool - http://www.pctipp.ch/downloads/dl/35905.asp