W3C home > Mailing lists > Public > www-international@w3.org > October to December 2000

NS4.5, GB2312 and Tildes

From: Etienne Kroger <etienne99@nettaxi.com>
Date: Mon, 04 Dec 2000 10:53:56 +0900
Message-Id: <4.2.0.58.J.20001204105350.0311ae20@sh.w3.mag.keio.ac.jp>
To: www-international@w3.org
Hi,

I am running into a an issue with Netscape 4.5, the charset meta tag and
tildes (gb2312 encoded file).

It appears that certain characters are not being rendered correctly when
using
Netscape (4.5) AND the META tag specifying the charset gb2312. Under these
circumstances, when two or more tildes (~) are adjacent to each other one or
more of them are not rendered in a form.

When the charset tag is removed from the page, Netscape processes the file
properly (accurate number of tildes).

IE handles the file properly in either cases.

Thank you for your help!

Etienne Kroger
etienne.kroger@welocalize.com

---------------------
Detailed Explanation
---------------------

This is the meta tag we are including:

<meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=gb2312">

We use the tilde character (~) as our delimiter.

<input type="Hidden" name="TextField0" value="Qaa~1~~~">

When using Netscape as the browser and the meta tag defining the charset is
included, the hidden field is rendered as:

<input type="Hidden" name="TextField0" value="Qaa~1~">

Notice the two ending tildes are not rendered. This causes an error in our
processor because the program is looking for a specific number of fields.
Sometimes the tildes are not rendered when they are in the middle of the
string:

<INPUT TYPE=RADIO NAME="1-1" value="2~21 - 50~Q2~2~~~~Q1-1-2">

Is rendered as (notice the missing 2 delimiter before the word "Answer")

<INPUT TYPE=RADIO NAME="1-1" value="2~21 - 50~Q2~2~~Q1-1-2">
Received on Sunday, 3 December 2000 21:09:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:16:55 GMT