I asked a number of Japanese and Chinese colleagues, but nobody seemed to want the level names translated in the log output. They were all happy with the English names. About half advised against translating, half was indifferent, and one person said he wouldn't use it himself but he thought that other people might want it.
So maybe this is a "nice-to-have" rather than a "must-have" feature? On Friday, January 31, 2014, Remko Popma <remko.po...@gmail.com> wrote: > What does the localization do? > Is it for translating the built-in level names? > > > On Friday, January 31, 2014, Gary Gregory > <garydgreg...@gmail.com<javascript:_e(%7B%7D,'cvml','garydgreg...@gmail.com');>> > wrote: > >> In Log4j 1 we use: >> >> - org.apache.log4j.Category.setResourceBundle(ResourceBundle) >> - org.apache.log4j.Category.l7dlog(Priority, String, Object[], Throwable) >> >> It seems v2 makes sidesteps the whole localization/i18n issue. >> >> What's the migration path for that? >> >> So we'll never play nice with some projects that require playing with >> resource bundles. >> >> Should we recommend creating a Logger wrapper to hold a resource bundle? >> I'm not sure what else we can do... we could provide it... >> >> Thoughts? >> >> Gary >> -- >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >> Java Persistence with Hibernate, Second >> Edition<http://www.manning.com/bauer3/> >> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >> Spring Batch in Action <http://www.manning.com/templier/> >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory >> >
