On Oct 27, 2004, at 1:52 PM, Curt Arnold wrote:
I'm currently writing test cases for log4j's date formatting to determine what it actually supports. I'm finding some strange behavior and will probably raise that on the log4j dev mailing list tomorrow. After I figure out what log4j does then I'll port those tests over to log4cxx and see what is missing.
I got side-tracked today and won't be able to get back to it till tomorrow. However, from the limited amount of code review of and test writing for log4j, it appears to be very difficult to configure log4j to format times for an arbitrary timezone and, if attempted, one would run into bugs that have yet to be reported
It should be fairly simple to support formatting dates for current local time and/or UTC without involving ICU or the TZ environment variable. The problem with the TZ variable comes from trying to emulate java.util.TimeZone which is used in the log4j implementation. The same goals can be achieved by having a more limited TimeZone class that only identifies a TimeZone as local or UTC which eliminate any motivation to use ICU4C or tweak with TZ.
APR on the other hand still looks very handy for threads, date formatting and character encoding.
