RE: [WDSCI-L] Non-traditional encodings

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: eiichi.yoshihira@xxxxxxxxxxxxx
> 
> Joe,
> Do you have the folllowing page directives written within your JSP?
> 
> JSP1.2:
> <%@ page language="java" contentType="text/html; charset=SHIFT_JIS"
> pageEncoding="SHIFT_JIS" %>
> JSP1.1:
> <%@ page language="java" contentType="text/html; charset=SHIFT_JIS" %>
> 
> It seems to be that if either of these are not specified, WDSC assumes
> they are in US-ASCII.

Thank you, Eiichi-san!

As far as I can tell, it looks as though the "encoding" value is set when you 
create the JSP.  There is a place where you can identify the encoding in the 
JSP creation wizard.  This determines whether you get the popup that says 
"invalid data found".  Interestingly enough, even if it does find invalid data, 
it seems to write it to the file just fine.

The metatags (the <%@ page %> statement or the content-type metatag) determine 
what is shown in the browser.  However, even if the correct glyphs show up in 
the browser, all I see in design and source mode is square boxes, one for each 
kana.  This is annoying.

If I create the very same JSP, but with the encoding set to ISO8859, then at 
least I see some data, although it looks very strange:

ÅÅâÃâââÂâÃâPâÃâIâÃâÃâÂâÂâÂ

This is the ISO8859-1 representation of Shift-JIS data.  I don't like it much, 
but it's better than the square boxes, because at least I can tell one literal 
from another. 

Joe