You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-dev@logging.apache.org by "Thorsten Schöning (JIRA)" <lo...@logging.apache.org> on 2016/07/28 18:36:20 UTC
[jira] [Comment Edited] (LOGCXX-483) Not able to see hebrew values
when logging in log4cxx
[ https://issues.apache.org/jira/browse/LOGCXX-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397979#comment-15397979 ]
Thorsten Schöning edited comment on LOGCXX-483 at 7/28/16 6:35 PM:
-------------------------------------------------------------------
{QUOTE}
How do I find the version of log4cxx I'm using? it's not stated in the header files.
{QUOTE}
That heavily depends on what you are actually using: If it's some package form the package manager of your distro, that should have some version number. If your are using some checkout from the VCS, you need to know the exact revision used yourself and if you are using an official release from the website you should have some pom.xml containing a "version" node.
{QUOTE}
The locale is normal English.
{QUOTE}
The codepage of your shell is important to as well as where your hebrew chars are coming from and and which encoding is used to print them to STDOUT.
{QUOTE}
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).
{QUOTE}
The more important headers are log4cxx.h regarding LOGCHAR, CHAR_API and such and logstring.h regarding LOG4CXX_STR.
{QUOTE}
Have there been any changes in the library regarding encoding issues or just general encoding changes in the recent years?
{QUOTE}
Both and encoding issues are somewhat complex and not necessarily only a problem in log4cxx, but requirements like APR may be the problem as well. Some examples:
https://issues.apache.org/jira/browse/LOGCXX-167
https://issues.apache.org/jira/browse/LOGCXX-371
https://issues.apache.org/jira/browse/LOGCXX-340
https://issues.apache.org/jira/browse/LOGCXX-241
https://issues.apache.org/jira/browse/LOGCXX-84
was (Author: tschoening):
> How do I find the version of log4cxx I'm using? it's not stated in the header files.
That heavily depends on what you are actually using: If it's some package form the package manager of your distro, that should have some version number. If your are using some checkout from the VCS, you need to know the exact revision used yourself and if you are using an official release from the website you should have some pom.xml containing a "version" node.
>The locale is normal English.
The codepage of your shell is important to as well as where your hebrew chars are coming from and and which encoding is used to print them to STDOUT.
> 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).
The more important headers are log4cxx.h regarding LOGCHAR, CHAR_API and such and logstring.h regarding LOG4CXX_STR.
> Have there been any changes in the library regarding encoding issues or just general encoding changes in the recent years?
Both and encoding issues are somewhat complex and not necessarily only a problem in log4cxx, but requirements like APR may be the problem as well. Some examples:
https://issues.apache.org/jira/browse/LOGCXX-167
https://issues.apache.org/jira/browse/LOGCXX-371
https://issues.apache.org/jira/browse/LOGCXX-340
https://issues.apache.org/jira/browse/LOGCXX-241
https://issues.apache.org/jira/browse/LOGCXX-84
> 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)