Re: Enforcing Charset to UTF-32 in HTML using meta tags

There are better ways to do this. (Google still cannot read
UTF-16 and UTF-32.)

Where do you have that information from?
It is quite simple to convert from e.g. UTF-16 to UTF-8.
If a document can be recognized as being UTF-16 they
just need to convert the document.

However, it is annoying when people specify
different things in meta, BOM and server :-)


--
best regards
Thomas Schulz
:: A1 Sitemap Generator now ::
http://www.micro-sys.dk/products/sitemap-generator/

On Mon, 26 Nov 2007, dk_sz wrote:

(Google still cannot read UTF-16 and UTF-32.)

Where do you have that information from?

http://www.google.com/search?q=U.T.F.1-6

--
In memoriam Alan J. Flavell
http://groups.google.com/groups/sear...Alan.J.Flavell

Scripsit dk_sz:

There are better ways to do this. (Google still cannot read
UTF-16 and UTF-32.)

Where do you have that information from?

Would you believe that Andreas has actually done some tests?

It is quite simple to convert from e.g. UTF-16 to UTF-8.

For some values of "simple", but that does not force anyone to do such
conversions.

However, it is annoying when people specify
different things in meta, BOM and server :-)

I'd say it's just sloppyness. I've seen it happen rather often, and you
specify the actual encoding in the HTTP headers, the odds are that
you'll never notice that you meta tag is in violation of that.

--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/

On Mon, 26 Nov 2007, I wrote:

(Google still cannot read UTF-16 and UTF-32.)

Where do you have that information from?

http://www.google.com/search?q=U.T.F.1-6

I noticed that the number of pages found with this search
gets smaller. It seems that Google catches on with UTF-16.

This cached page
http://google.com/search?q=cache:www...e1-utf-16.html
looks OK now.

--
Bugs in Internet Explorer 7
http://www.unics.uni-hannover.de/nhtcapri/ie7-bugs