Name: nl37777 Date: 06/23/2004

The native2ascii tool documentation has several problems:

- The "\udddd" notation seems to indicate a decimal format. In fact,
the digits are assumed to be hexadecimal, so "\uxxxx" would be more
appropriate.

- The terms "Unicode" or "Unicode encoded" are used to describe this
notation. This is wrong - it is not a standard Unicode encoding scheme.
The JLS describes it more appropriate as "Unicode escape".

- The documentation states that "the Java compiler and other Java tools
can only process files which contain Latin-1 and/or Unicode-encoded
(\udddd notation) characters." At least for javac this statement is
wrong - javac can handle the same set of encodings as native2ascii. The
main use for native2ascii is for properties files for the
java.util.Properties class.

- The documentation refers to the file.encoding property. This property
is not part of the platform specification, may not have the effect
that's implied here, and should not be mentioned.

- The documentation states that "The encoding_name string must be taken
from the first column of the table of supported encodings in the
Supported Encodings document." This is not correct for 1.5.0; names
taken from either the first or the second column are accepted.

- The documentation uses the term "native encoding" while in fact any
character encoding supported by the JRE can be used.

Some affected pages:
http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/native2ascii.html
http://java.sun.com/j2se/1.5.0/docs/tooldocs/solaris/native2ascii.html

======================================================================