JDK-6343111 : some text format issues in Japanese API doc
  • Type: Bug
  • Component: globalization
  • Sub-Component: translation
  • Affected Version: 5.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2005-10-28
  • Updated: 2005-11-16
  • Resolved: 2005-11-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0u6 b05Fixed
Description
Japanese API doc is using an intermediate file 'cmnt' (comment) file to
translate the contents of API doc.  In this case, there are some content
format problem in the cmnt files.

ex) java.awt.image.ComponentSampleModel
http://java.sun.com/j2se/1.5.0/ja/docs/ja/api/index.html

In the overview, there are some non-processed '@see' tags at the bottom.
In the method details, the following methods have the same issue.
  getSampleSize
  getBankIndices
  getBandOffsets
  getScanlineStride
  getPixelStride

In the cmnt file, these tags do not have the proper line break.
And the other issues in the cmnt file are attached.
Comments
EVALUATION For targetting 5.0u6, we have fixed the generated htmls only, not for cmnt files. Fixing cmnt files will be completed in next major release Mustang.
16-11-2005
EVALUATION All the cmnt files should be rechecked and fixed in the next Japanese API doc update process.
28-10-2005