[
https://issues.apache.org/jira/browse/MNG-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979823#comment-15979823
]
Hervé Boutemy commented on MNG-6205:
------------------------------------
uh :(
I really don't understand how the System.out encoding is chosen by the JVM on
WIndows for every JVM vendor, based on the mess Windows does between GUI
encoding (for example Windows-1252 in french) and CLI encoding (for example
CP850, see {{chcp}} command)
Perhaps the solution will be to change the whole JAnsi logic regarding
AnsiConsole class: avoid creating a PrintWriter that does the encoding
conversion (see
https://github.com/fusesource/jansi/blob/master/jansi/src/main/java/org/fusesource/jansi/AnsiConsole.java#L45
), then has to do it with the same voodoo than System.out, but delegate the
conversion to System.out: whatever the voodoo is, it will use it.
I'll try this
> Non-ascii chars in name element are displayed as question marks in Win CLI
> output (regression)
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-6205
> URL: https://issues.apache.org/jira/browse/MNG-6205
> Project: Maven
> Issue Type: Bug
> Components: Logging
> Affects Versions: 3.5.0
> Environment: Windows 7, IBM JDK 7.1, Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426)
> Reporter: Anders Hammar
> Fix For: 3.5.1-candidate
>
> Attachments: jansi-1.16-SNAPSHOT.jar, pom.xml
>
>
> If non-ascii characters (such as Swedish chars å, ä, ö) are used in the pom
> name element, they are displayed as question mark ('?') in the CLI output
> when building on Windows. This can been seen e.g. in the Reactor Summary in
> the end.
> See attached pom for an example.
> This was not an issue in Maven 3.3.9.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
