[
http://jira.codehaus.org/browse/MPLUGIN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MPLUGIN-95.
--------------------------------
Assignee: Herve Boutemy
Resolution: Fixed
Fix Version/s: 2.4.2
applied in r643342
thanks
> Output proper charset name in XDoc report for mojos
> ---------------------------------------------------
>
> Key: MPLUGIN-95
> URL: http://jira.codehaus.org/browse/MPLUGIN-95
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.4
> Reporter: Benjamin Bentmann
> Assignee: Herve Boutemy
> Priority: Minor
> Fix For: 2.4.2
>
> Attachments: registered-charset-name.patch
>
>
> My original patch for MPLUGIN-76 has an unintended side effect:
> {{OutputStreamWriter.getEncoding()}} does not exactly report back the
> encoding supplied in the constructor. On a Sun JDK 1.6.0_04 for Windows, I
> observed that {{getEncoding()}} returnes "UTF8" instead of "UTF-8" as
> supplied in the constructor.
> This might not be an issue as long as the XML file is only processed by
> Java-based code, but
> # the [XML spec|http://www.w3.org/TR/2006/REC-xml11-20060816/#charencoding]
> suggests to use the string "UTF-8" to indicate that encoding
> # the [IANA charset database|http://www.iana.org/assignments/character-sets]
> does not mention "UTF8" as a valid alias for "UTF-8"
> # some non-Java programs really fail on parsing such a XML due to
> "unsupported 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
