The customer is developing a PlugIn for Java WorkShop 2.0,
including a Japanese on-line doc for the PlugIn.
The customer complains that javadoc-generated document cannot be viewed
using JWS 2.0 on-line viewer. This is because the customer
writes the Java code on PC in Shift-JIS encoding, ran javadoc
on PC, and the generated .html file does not have an encoding
announcement embedded, and JWS's help browser defaults to EUC (because
the help files supplied by Sun is in EUC, the Solaris's standard).
This weren't be a problem if javadoc generates an encoding announcement, i.e.,
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;charset=Shift_JIS">
or
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;charset=EUC-JP">
depending on the encoding of the platform where javadoc is run,
in between <HEAD> and </HEAD>. The charset name to be used must
be taken from the IANA registry, not those of Java encoding names
(I.e., use EUC-JP instad of EUCJIS).
Japan Software Center would also like this feature. Not having this feature,
we had to write a script to insert the META tag to the generated files,
complicating the build process.
including a Japanese on-line doc for the PlugIn.
The customer complains that javadoc-generated document cannot be viewed
using JWS 2.0 on-line viewer. This is because the customer
writes the Java code on PC in Shift-JIS encoding, ran javadoc
on PC, and the generated .html file does not have an encoding
announcement embedded, and JWS's help browser defaults to EUC (because
the help files supplied by Sun is in EUC, the Solaris's standard).
This weren't be a problem if javadoc generates an encoding announcement, i.e.,
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;charset=Shift_JIS">
or
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;charset=EUC-JP">
depending on the encoding of the platform where javadoc is run,
in between <HEAD> and </HEAD>. The charset name to be used must
be taken from the IANA registry, not those of Java encoding names
(I.e., use EUC-JP instad of EUCJIS).
Japan Software Center would also like this feature. Not having this feature,
we had to write a script to insert the META tag to the generated files,
complicating the build process.
- relates to
-
JDK-4210341 Javadoc -charset, default charset should not be iso-8859-1
-
- Resolved
-
-
JDK-4034096 stddoclet: Add support for HTML keywords via META tag for class names
-
- Resolved
-