On Aug 21, 2009, at 4:32 AM, shadow king wrote:
thanks for your reply.
BTW, Is there a convinent way to swtich off all the "decoding &
encoding" thing completely? Because I don't want the performance
penalty imposed by the related function.
For me, I cound not see the benefit of using u
thanks for your reply.
BTW, Is there a convinent way to swtich off all the "decoding & encoding"
thing completely? Because I don't want the performance penalty imposed by
the related function.
For me, I cound not see the benefit of using unicode as the internal
charset in log4cxx and I just want
I'm thinking the constant should be 0x20, not 0x30. The code was an
attempt to be able to handle non-ASCII platforms like EBCDIC but looks
like it was mangled and was done without access to a non-ASCII
platform. Was just trying to do enough decoding to get the encoding
name to load a full
HI,
I am a chinese and I am using log4cxx as a logging facility in my
project(the locale in my linux server has been set to "zh_CN.GBK").
when I switch to the 0.10.0 release(I used version 0.97 beta before), I came
cross a problem: all the chinese logging message produced by my program
could not
