Re: NS4.5, GB2312 and Tildes

This is probably a bug in Netscape 4.X. I believe that the GB2312
converter routines were merged with the HZ routines, and these use the
tilde as the "escape" (quote) character.

How about changing the Web site to use something other than tilde for
that purpose?

Erik

"Etienne Kroger (by way of Martin J. Duerst )" wrote:
> 
> 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 Tuesday, 5 December 2000 02:54:42 UTC