[
https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659211#comment-13659211
]
Nick Williams commented on LOG4J2-255:
--------------------------------------
Yes, Gary is completely right about Java's strings always being unicode.
I'm a bit confused here. My (admittedly limited) understanding of character
sets was that UTF-8 takes care of *everything*. English, Cyrillic, Korean,
Japanese, etc. should all be able to be properly represented using UTF-8.
That's why I'm a bit uncertain about why we can't always use UTF-8 for
*everything*. The only exception I can think of is /reading/ files, which would
have been created by something else (text editor, other program) and need to
have their encoding detected/specified. But why wouldn't UTF-8 work for
everything that Log4j writes/transmits?
> Multi-byte character strings are scrambled in log output
> --------------------------------------------------------
>
> Key: LOG4J2-255
> URL: https://issues.apache.org/jira/browse/LOG4J2-255
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders, Core
> Affects Versions: 2.0-beta6
> Reporter: Remko Popma
> Assignee: Remko Popma
> Priority: Blocker
> Fix For: 2.0-beta7
>
>
> When I tried to log a Japanese string the output was scrambled in both the
> Console and a log file.
> For example,
> logger.warn("日本語テスト"); // (Japanese test)
> came out as
> 15:07:00.184 [main] WARN test.JapaneseTest - 譌･譛ｬ隱槭ユ繧ｹ繝?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
