Google censors Unicode 0x12000

My two blogspot websites were censored by google where I posted
Unicode for Cuneiform above hex 0x12000 as code points. Here is where
it is done :
The Cuneiform Club
http://cuneiformclub.blogspot.com/p/...-failures.html
Greek Alphabet
http://greekalphabet.blogspot.com/
The code points above 0x12000 were replaced by question marks below
0xFFFF
That is decimal 73728 replaced by 65533 automatically by google on my
blogspots.
What's up?

From: "Globemaker" <alanfolmsbee@cabanova.com>

> My two blogspot websites were censored by google where I posted
> Unicode for Cuneiform above hex 0x12000 as code points. Here is where
> it is done :
> The Cuneiform Club
> http://cuneiformclub.blogspot.com/p/...-failures.html
> Greek Alphabet
> http://greekalphabet.blogspot.com/
> The code points above 0x12000 were replaced by question marks below
> 0xFFFF
> That is decimal 73728 replaced by 65533 automatically by google on my
> blogspots.
> What's up?

Its a free service and they don't like the char set as maybe it it could be used in a
malicious way.

I suggest your OWN web site and then you can do what you bloody like .


--
Dave
Multi-AV Scanning Tool - http://www.pctipp.ch/downloads/dl/35905.asp

On May 25, 12:13*pm, "David H. Lipman" <DLipman~nosp...@Verizon.Net>
wrote:
> From: "Globemaker" <alanfolms...@cabanova.com>
>
> > My two blogspot websites were censored by google where I posted
> > Unicode for Cuneiform above hex 0x12000 as code points. Here is where
> > it is done :
> > The Cuneiform Club
> >http://cuneiformclub.blogspot.com/p/...-failures.html
> > Greek Alphabet
> >http://greekalphabet.blogspot.com/
> > The code points above 0x12000 were replaced by question marks below
> > 0xFFFF
> > That is decimal 73728 replaced by 65533 automatically by google on my
> > blogspots.
> > What's up?
>
> Its a free service and they don't like the char set as maybe it it could be used in a
> malicious way.
>
> I suggest your OWN web site and then you can do what you bloody like .
>
> --
> Dave
> Multi-AV Scanning Tool -http://www.pctipp.ch/downloads/dl/35905.asp


More details, and correction:

The problem has been traced to a UTF-16 issue, not a 0x12000 range
issue for UTF-32 to UTF-8 encoding translation. When Cuneiform is in
Wordpad, and then copied to blogspot, it looks like the 0x12000
codepoint is then encoded into pairs of unicode high surrogate and low
surrogate 16 bit versions as so as UTF-16 decimal:
& # 55304 ; & # 56320
& # 55304 ; & # 56384

When Blogspot overlords at google spot that, they change it to a
UTF-32 question mark glyph at 65533 decimal
So the censorship is not for 12000 codepoints in UTF-32 it is for
UTF-16 pairs of numbers as hi surrogate and low surrogate.

Those encodings were all useable by some browsers, but not all.
Internet Explorer 8 was able to display the UTF-16 pairs but not
Chrome or Firefox.

Conclusion: the automatic censorship is taking place for the UTF-16
encodings of Cuneiform glyphs in Unicode, but not for UTF-32
encodings.

On May 25, 12:27*pm, Globemaker <alanfolms...@cabanova.com> wrote:
> On May 25, 12:13*pm, "David H. Lipman" <DLipman~nosp...@Verizon.Net>
> wrote:
>
>
>
>
>
>
>
>
>
> > From: "Globemaker" <alanfolms...@cabanova.com>
>
> > > My two blogspot websites were censored by google where I posted
> > > Unicode for Cuneiform above hex 0x12000 as code points. Here is where
> > > it is done :
> > > The Cuneiform Club
> > >http://cuneiformclub.blogspot.com/p/...-failures.html
> > > Greek Alphabet
> > >http://greekalphabet.blogspot.com/
> > > The code points above 0x12000 were replaced by question marks below
> > > 0xFFFF
> > > That is decimal 73728 replaced by 65533 automatically by google on my
> > > blogspots.
> > > What's up?
>
> > Its a free service and they don't like the char set as maybe it it could be used in a
> > malicious way.
>
> > I suggest your OWN web site and then you can do what you bloody like .
>
> > --
> > Dave
> > Multi-AV Scanning Tool -http://www.pctipp.ch/downloads/dl/35905.asp
>
> More details, and correction:
>
> The problem has been traced to a UTF-16 issue, not a 0x12000 range
> issue for UTF-32 to UTF-8 encoding translation. When Cuneiform is in
> Wordpad, and then copied to blogspot, it looks like the 0x12000
> codepoint is then encoded into pairs of unicode high surrogate and low
> surrogate 16 bit versions as so as UTF-16 decimal:
> *& # 55304 ; & # 56320
> & # 55304 ; & # 56384
>
> When Blogspot overlords at google spot that, they change it to a
> UTF-32 question mark glyph at 65533 decimal
> *So the censorship is not for 12000 codepoints in UTF-32 it is for
> UTF-16 pairs of numbers as hi surrogate and low surrogate.
>
> Those encodings were all useable by some browsers, but not all.
> Internet Explorer 8 was able to display the UTF-16 pairs but not
> Chrome or Firefox.
>
> Conclusion: the automatic censorship is taking place for the UTF-16
> encodings of Cuneiform glyphs in Unicode, but not for UTF-32
> encodings.

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.
http://popcry.wordpress.com/abecedary/

From: "Globemaker" <alanfolmsbee@cabanova.com>

> 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.
> http://popcry.wordpress.com/abecedary/

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.


--
Dave
Multi-AV Scanning Tool - http://www.pctipp.ch/downloads/dl/35905.asp

On May 25, 5:19*pm, "David H. Lipman" <DLipman~nosp...@Verizon.Net>
wrote:
> From: "Globemaker" <alanfolms...@cabanova.com>
>
> > 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.
> >http://popcry.wordpress.com/abecedary/
>
> Besides setting up your OWN webv site, here is a simple solution.
>
> Instead of posting the text in UTF-32 codepoints directly, post a graphicof the paragraph
> of the text represented in UTF-32 codepoints.
>
> BTW: *I don't think the word "censorship" is apropos in this situation.
>
> --
> Dave
> Multi-AV Scanning Tool -http://www.pctipp.ch/downloads/dl/35905.asp

Unicode 6.0 is intended to let all character sets from many cultures
be displayed on most computers. I am working to confirm that for
Cuneiform, the original alphabet of Iraq. As an alternative to
Unicode, I could make a jpeg image of clay tablets I prepare with a
stylus.

This may not be appropriate to call this Censorship, when an American
superpower corporation destroys the writings of Iraq. A better
description instead of censorship might be patriotism. Or maybe this
is a heroic effort to make the world safe for Anglophiles by deleting
Cuneiform Iraqi files. Imagine how this deletion of my Unicode code
points for Cuneiform may have occurred: Bush is sitting in his bunker
in Crawford Texas glued to his plasma monitor, scouring the websites
of the world with robotic killer code, unleashing programmatic ethnic
cleansing to provide a Uniform character set instead of Unicode
varieties for which there may be a 1% chance of malicious intent.

Yes, you are right, an image of Cuneiform may be more secure from such
deletions.

Thank you