[
https://issues.apache.org/jira/browse/LOGCXX-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397832#comment-15397832
]
Giora Guttsait commented on LOGCXX-483:
---------------------------------------
Hi, currently I cannot check most of these out, I'll only be able to do so this
sunday, but I do have some questions.
How do I find the version of log4cxx I'm using? it's not stated in the header
files.
The locale is normal English. Regarding the build, I think I saw the
configuration today during my research, I'll be able to tell you that in Sunday
also.
Regarding UTF and wchar_t, the only thing I know to tell you right now is that
when I look at logger.h, the parts that use #define LOG4CXX_UNICHAR_API are
disables (marked out when looking at them in eclipse).
I might try and get a new version of Log4cxx, problem is that the code is in a
separate network and it takes time to move files from WWW to our network, but
it is something I should probably do at some point, as the current version is
probably there for several years. I know for sure that my team leader was
working on out logger wrapper class approx 3 years ago, and considering what
parts of code use it, if I use git blame and check, it'll probably even be more
then that.
Have there been any changes in the library regarding encoding issues or just
general encoding changes in the recent years?
> Not able to see hebrew values when logging in log4cxx
> -----------------------------------------------------
>
> Key: LOGCXX-483
> URL: https://issues.apache.org/jira/browse/LOGCXX-483
> Project: Log4cxx
> Issue Type: Bug
> Environment: Linux Debian 8 32bit
> Reporter: Giora Guttsait
>
> When logging messages with a console appender (whose output is directed to a
> file), hebrew text is shown as weird symbols.
> It really affects out ability to debug and analyze the program output at
> specific points, so a quick fix(if possible) would be great
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
