Netfront 3.2 Question

I've tested the trial version of 3.2; it works great. To find out the cause for the problem, I've written a small Java HTTP server (downloadable fromhttp://www.winmobiletech.com/sekalaiset/PageEncodingTester.java ) that makes it possible to modify the returned charset in both the "Content-Type" header and in the HTML header, in the meta tag, via the http-equiv parameter. It's a self-standing HTTP server to allow for free enabling/disabling/setting of the "Content-Type" header, which would be, otherwise, impossible with an already-deployed, non-personal Web server.

NF 3.2 (at least the trial version) works as expected, taking into account both the HTTP header and the http-equiv meta tag.

NF 3.1, on the other hand, simply ignores the "Content-Type" HTTP header and only sets the encoding based on the http-equiv meta tag. This is a bug in 3.1.

This means the pages you've visited may only have defined their content type in the "Content-Type" HTTP header and not in a http-equiv meta tag. In this case, NF 3.1 always defaults to ISO-8859-1, while NF 3.2 correctly sets the encoding of the document. That is, it's NF 3.2 that behaves correctly and it was by a mistake that 3.1 rendered those pages (more exactly, the parts that have Western-language characters) OK.

(Seehttp://www.w3.org/International/O-charset for more information on HTML character encoding.)

Incidentally, now that I've compared both versions so thoroughly, I've also found out another bug in NF 3.1, which has also been fixed in 3.2: 3.1 wasn't able to correctly use ­ (­ ­ Soft hyphen) entity (seehttp://penguin.dcs.bbk.ac.uk/academic/xml/dtd/index.php for more info). Pages using ­, therefore, are rendered under NF3.1 awfully, by using a real hyphen.

And, NF3.2 offers a lot of additional code pages in addition to the five in NF3.1. For example, in version 3.1, there is no Central-European (ISO-8859-2) support at all.

BTW, you may also want to readhttp://www.pocketpcthoughts.com/index.php?action=expand,41008&/netfront_3.2_english_finally_released.htm on other bugs I've found in 3.1 and that have been fixed in 3.2.

It seems NF3.2 indeed has problems with languages like Korean. I'm just trying to track down the error athttp://www.firstloox.org//forums/showthread.php?p=32610 .