[
https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562770#comment-15562770
]
Eldar Gabdullin commented on LOG4J2-1636:
-----------------------------------------
If only there was no distinction between Layouts and Appenders... They are just
sinks anyway.
Just dreaming...
{code}
interface LogEventSink<T> {
void write(LogEvent e, T data);
}
class PatterSink implements LogEventSink<LogEvent> {
private LogEventSink<String> target;
@Override
public void write(LogEvent e, LogEvent data) {
target.write(e, format(data));
}
private String format(LogEvent e) {
return e.toString();
}
}
class PrintStreamSink implements LogEventSink<String> {
private PrintStream out;
@Override
public void write(LogEvent e, String data) {
out.print(data);
}
}
{code}
> Bad console output encoding on windows
> --------------------------------------
>
> 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
>
> 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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
