[
https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563182#comment-15563182
]
Eldar Gabdullin commented on LOG4J2-1636:
-----------------------------------------
No need to say, that relying on {{sun.stdout.encoding}} is a very weak point.
Can we instead consider the following:
Tweak {{ConsoleAppender}} in such a way, that if it's layout is an instance of
{{AbstractStringLayout}}, then do the following for writing
1) decode bytes back to string,
2) call {{.print()}} method
Now, this is backwards incompatible. Add an option to disable this behavior.
> Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and
> sun.stderr.encoding
> ----------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1636
> URL: https://issues.apache.org/jira/browse/LOG4J2-1636
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders, Layouts
> Environment: Windows
> Reporter: Eldar Gabdullin
> Assignee: Gary Gregory
>
> The Oracle Java 8 platform supports two system properties to configure the
> System console: sun.stdout.encoding and sun.stderr.encoding.
> ----
> Default log4j configuration prints to console using platform's default
> encoding, however that's not what standard windows console expects.
> I.e.
> {code}
> System.out.println("Поехали"); // works just fine
> System.out.write("Поехали!\n".getBytes(Charset.defaultCharset())); //
> characters are messed up
> log.info("Поехали"); // messed up in the same way
> {code}
> This happens not just on one machine, but on all Windows desktops and servers
> in our organization.
> Can we have out of the box Layout/Appender which prints directly to
> System.out/err?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
