[
https://issues.apache.org/jira/browse/MRESOURCES-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081867#comment-15081867
]
Aaron Digulla commented on MRESOURCES-171:
------------------------------------------
[~afloom] Well, he can't use Maven and expect properties files to work, then.
It's as simple as that: You have place A where you can't change anything and
place B, where you can, so B has to give. That means if you load all your
resources via {{ResourceBundles}} and you don't use any libraries, this might
work. Or maybe the code above is a workaround for the broken Maven resource
plugin - which would give this bug even more priority.
[~khmarbaise] Please reopen the bug. As you quoted: *Characters not in Latin1
... are represented ... using Unicode escapes* That means you can never use
anything but Latin 1 in plain properties files and expect them to work. Which
is why Java comes with
[native2ascii|http://docs.oracle.com/javase/7/docs/technotes/tools/windows/native2ascii.html]
> ISO8859-1 properties files get changed into UTF-8 when filtered
> ---------------------------------------------------------------
>
> Key: MRESOURCES-171
> URL: https://issues.apache.org/jira/browse/MRESOURCES-171
> Project: Maven Resources Plugin
> Issue Type: Bug
> Components: filtering
> Reporter: Alex Collins
> Priority: Minor
> Attachments: filtering-bug.zip
>
>
> Create:
> src/main/resources/test.properties
> And add a ISO8859-1 character that is not ASCII or UTF-8, do not use \uXXXX
> formatting.
> When adding this line:
> <resource><directory>src/main/resources</directory><filtering>true</filtering></resource>
> Expected:
> ISO8859-1 encoded file in jar.
> Actual:
> UTF-8 encoded file in jar.
> ---
> If there are any property files (which can only be ISO8859-1) they appear to
> be converted into UTF-8 in the jar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
