[
http://jira.codehaus.org/browse/MSITE-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129810#action_129810
]
Petr Kozelka commented on MSITE-224:
------------------------------------
That's true for input encoding.
However, for output encoding, each xml file has its own XML declaration with
encoding optionally specified.
And when it is specified, it should be respected, otherwise it is a bug.
But respecting XML encoding is possible only if you can convert any text from
its content into the output encoding.
So in my opinion, the best solution is that the functionality fails when it
encounters any character that cannot be converted this way, but it might be
much harder to implement.
While switching (at least) the default output encoding to UTF8 is easy and
would be very helpful and produces no compatibility issues I believe.
> [PATCH] please make UTF-8 the default encoding
> ----------------------------------------------
>
> Key: MSITE-224
> URL: http://jira.codehaus.org/browse/MSITE-224
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Components: encoding
> Environment: Gentoo Linux, UTF-8 encoded pom files
> Reporter: Petr Kozelka
> Priority: Minor
> Attachments: site-plugin-UTF8-encoding.patch
>
>
> UTF-8 is already widely supported and used by tools, there is hardly a reason
> to keep with ISO-8859-1 found through the code.
> In my usecases, it typically makes troubles with developer names containing
> accented letters.
> Attached patch changes the default input and output encoding in
> maven-site-plugin which is the most important piece.
--
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
