[
http://jira.codehaus.org/browse/MPLUGIN-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MPLUGIN-96:
-------------------------------------
Description:
The current usage of JTidy has some bugs:
- Non-ASCII characters are translated into HTML entities, making an ordinary
XML parser (like the Plexus' MXParser) fail to parse the XDoc (see
exception.txt)
- Non-Latin1 characters won't make it through the
StringInput-/StringOutputStream (two further classes an international app
should avoid...)
was:
The current usage of JTidy has some bugs:
- Non-ASCII characters are translated into HTML entities, making an ordinary
XML parser (like the Plexus' MXParser) fail to parse the XDoc (see
exception.txt)
- Non-Latin1 characters won't make it through the
StringInput-/StringOutputStream (two further classes an internal app should
avoid...)
> Handle character encoding properly in makeHtmlValid()
> -----------------------------------------------------
>
> Key: MPLUGIN-96
> URL: http://jira.codehaus.org/browse/MPLUGIN-96
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: API
> Affects Versions: 2.4
> Reporter: Benjamin Bentmann
> Attachments: exception.txt, jtidy-character-encoding.patch
>
>
> The current usage of JTidy has some bugs:
> - Non-ASCII characters are translated into HTML entities, making an ordinary
> XML parser (like the Plexus' MXParser) fail to parse the XDoc (see
> exception.txt)
> - Non-Latin1 characters won't make it through the
> StringInput-/StringOutputStream (two further classes an international app
> should avoid...)
--
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
