[
https://issues.apache.org/jira/browse/MJAVADOC-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957525#comment-17957525
]
Olivier Lamy commented on MJAVADOC-123:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#570|https://github.com/apache/maven-javadoc-plugin/issues/570].
> Encoding Error When Getting project.name For JavaDoc -doctitle
> --------------------------------------------------------------
>
> Key: MJAVADOC-123
> URL: https://issues.apache.org/jira/browse/MJAVADOC-123
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> 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: Siveton Vincent
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
