[
http://jira.codehaus.org/browse/MJAVADOC-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96856
]
Steven Coco commented on MJAVADOC-123:
--------------------------------------
This Web app is broken. I wrote a lengthy comment and apparently my session
timed out. When I submitted I got an error message saying I was not alows to
post. And I can't go "back" and get the text that I entered into the form. I
have to start now from scratch and that's totally unacceptable.
[This version shorter because I'm out of time.]
I tried both options.
I made 2 new projects: version 3 and 4. They contain the plugin snapshot
repository declaration.
Version 3 POM has been switched to ISO-8859-1: declared in the XML declaration,
and correctly saved.
Building with this command:
mvn -U -X -e -Ddebug=true -Dfile.encoding=UTF-8 clean javadoc:javadoc
Verify that maven is using the JavaDoc snapshot plugin.
In each case the options file is in UTF-8 encoding. However, in the version 3
file, the (R) has been inserted as the Unicode replacement character (correctly
encoded in UTF-8). This should never happen since that character exists in both
charsets.
Tried switching to -Dfile.encoding=ISO-8859-1 and building both again -- both
builds would still be valid builds this way.
Similar problem, only seemingly worse: options file is again in UTF-8 encoding
(with the replacement character).
Something is using the wrong encoding.
I'm not sure when I'll get to look at the sources. I'll keep trying.
Ciao.
> Encoding Error When Getting project.name For JavaDoc -doctitle
> --------------------------------------------------------------
>
> Key: MJAVADOC-123
> URL: http://jira.codehaus.org/browse/MJAVADOC-123
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Environment: Linux coco-laptop 2.6.20-15-generic #2 SMP Sun Apr 15
> 07:36:31 UTC 2007 i686 GNU/Linux
> Maven version: 2.0.6
> Reporter: Steven Coco
> Assignee: Vincent Siveton
> Fix For: 2.3
>
> Attachments: javadoc-encoding-2.tar.gz, javadoc-encoding-3-4.tar.gz,
> javadoc-encoding.tar.gz
>
>
> I have found an encoding handling error in JavaDoc generation.
> The POM for this project is in UTF-8 encoding. the project.name element
> contains the trade mark character, U+2122.
> When the JavaDoc plugin builds the documentation, the default HTML charset is
> used: ISO-8859-1.
> When viewing the JavaDoc pages, the trade mark character in the title has
> been munged: "â¢".
> At some location, the project name's text is being copied and ported to the
> JavaDoc tool in the wrong encoding.
> The attachment has a test case. Since it's very small, the javadoc has
> already been built there to prevent any unwanted encoding mismatches during
> transmission of the attachment. View the POM to see the trade mark character
> in the name. View target/site/apidocs/index.html to see the munged trade mark
> character. View the src/main/java/overview.html file to see the other content
> used for the API overview page.
> N.B.: In the attachment, all files are in UTF-8 encoding.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
