[ http://jira.codehaus.org/browse/MNG-2215?page=all ]
Carlos Sanchez closed MNG-2215:
-------------------------------
Assign To: Carlos Sanchez
Resolution: Won't Fix
It's not a matter of changing the default but spporting different encodings.
And no, iso-8859-1 chars don't map directly to UTF-8, eg acentuated chars are
diferent
> Change the default input/output encoding to UTF-8 instead of ISO-8859-1
> -----------------------------------------------------------------------
>
> Key: MNG-2215
> URL: http://jira.codehaus.org/browse/MNG-2215
> Project: Maven 2
> Type: Improvement
> Components: General
> Versions: 2.0.1, 2.0.3, 2.0, 2.0.2
> Reporter: Trustin Lee
> Assignee: Carlos Sanchez
>
>
> Currently, all input and output encodings of source code and site are
> ISO-8859-1 by default. UTF-8 covers all characters in ISO-8859-1 without any
> migration, and moreover, it supports other characters which ISO-8859-1 cannot
> cover such as Korean and Japanese. Changing the default encodings to UTF-8
> will be great because some plugins might not provide any configuration
> properties for encodings but uses some default values. For example, maven
> site plugin didn't have an input encoding property. If the default encoding
> is ISO-8859-1, people doesn't have any chance to express their native
> language at all (e.g. source code comments, site documentation, ...). If the
> default encoding is UTF-8 at least, they could use their native language at
> least.
> To do this,
> 1) Change all default values which are ISO-8859-1 to UTF-8
> 2) Set VM system property: -Dfile.encoding=UTF-8 for the plugins which
> doesn't consider encodings at all.
--
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
