Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.0, 2.0.1, 2.0.2, 2.0.3
-
Fix Version/s: None
-
Component/s: POM::Encoding
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
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.
Issue Links
- relates to
-
MNG-2254
the encoding parameter in xml declaration of POM is ignored
-
Activity
| Assignee | Carlos Sanchez [ carlos ] | |
| Resolution | Won't Fix [ 2 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Component/s | POM::Encoding [ 12860 ] | |
| Component/s | General [ 12033 ] |
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