United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-4661481 : REGRESSION: -encoding option is ignored for reading java sources

Details
Type:
Bug
Submit Date:
2002-04-02
Status:
Resolved
Updated Date:
2002-04-25
Project Name:
JDK
Resolved Date:
2002-04-25
Component:
docs
OS:
solaris_8
Sub-Component:
doclet
CPU:
sparc
Priority:
P3
Resolution:
Fixed
Affected Versions:
1.4.0
Fixed Versions:
1.4.1 (hopper)

Related Reports

Sub Tasks

Description

Name: nt126004			Date: 04/02/2002


FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)


FULL OPERATING SYSTEM VERSION :
SunOS java 5.8 Generic_108528-12 sun4u sparc SUNW,Ultra-2

ADDITIONAL OPERATING SYSTEMS :

Windows 2000, Windows 98 (Probably this bug is
platform-independent)

EXTRA RELEVANT SYSTEM CONFIGURATION :
Japanese language environments

A DESCRIPTION OF THE PROBLEM :
When -encoding option is specified to javadoc, Java source
codes can't be converted correctly. So Japanese characters
are converted to "???????".

For example, this problem occurs when you convert Java
source files encoded in Shift_JIS on Japanese Solairs EUC-JP
environment with "-encoding Shift_JIS".

Perhaps javadoc may convert Java sources in according to its
default character encoding, not an encoding specified by
"-encoding" option.

I guess this bug was included when you fixed Bug ID 4463408
from the following reasons:

1, In 1.4b, javadoc can convert java sources correctly, but
not package.html.
2, In 1.4b2, javadoc can convert package.html correctly, but
not java sources.
3, Bug ID 4463408 was fixed in 1.4b2.

REGRESSION.  Last worked in version 1.3.1

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1.Create a Java source file encoded in a character encoding
which isn't equal to javadoc's default character encoding.
For example, use EUC-JP on Japanese Windows platform and use
Shift_JIS on Japanese Solaris platform.
2.Run javadoc with "-encoding" and Java source's character
encoding.
3.Check the output.

EXPECTED VERSUS ACTUAL BEHAVIOR :
When "-encoding" option is specified, Javadoc should read
Java sources and package.html in according to it.

Now javadoc ignores "-encoding" option and reads Java
sources in according to its default character encoding and
produces currupted character sequences such as "??????".

ERROR MESSAGES/STACK TRACES THAT OCCUR :
No error message.

This bug can be reproduced always.

CUSTOMER WORKAROUND :
Convert Java sources to the default character encoding use
in your environment.

Release Regression From : merlin-beta
The above release value was the last known release where this 
bug was known to work. Since then there has been a regression.

(Review ID: 144520) 
======================================================================

                                    

Comments
EVALUATION

Would be important to fix for hopper
###@###.### 2002-04-02

This bug has been fixed.  Location of fix:

com.sun.tools.javadoc.Start

Regression test at:  test/com/sun/javadoc/testEncoding/testEncodingWrapper.sh
###@###.### 2002-04-22
                                     
2002-04-22
PUBLIC COMMENTS

This bug has been fixed.  Javadoc now correctly passes the encoding value to the source file parser.
###@###.### 2002-04-22
                                     
2002-04-22
CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
hopper

FIXED IN:
hopper

INTEGRATED IN:
hopper


                                     
2004-06-14



Hardware and Software, Engineered to Work Together