[slf4j-dev] slf4j i8ln

[Ralph Goers]

Interesting, but I personally would not be happy with that interface.
1. It relies on resource bundles.
2. None of the methods accept a Locale so the framework has to rely on  
the default locale. Without this it means that while the app can  
support any language a particular instance can only support one. That  
is fine in some use cases but not all.

I actually dealt with this kind of stuff years ago. Consider a use  
case where you have call centers in Japan, France and the U.S. each  
handling customers in their native country and the application is  
running in a single data center. a) either all your customer service  
reps have to understand a single language or b) the log records need  
to be written to a file using the message key and the substitution  
parameters. The message should not be localized until it is going to  
appear on the customer service reps console so they can read it in  
whatever language they are configured for.

To truly internationalize properly the translation needs to happen as  
late as possible. In that case the logging framework doesn't even  
really need to support resource bundles.

But, assuming you still want to have the framework "do" I18N, as I  
said in my earlier message, it can still be handled in the appender,  
not in the API layer.

Ralph

On Aug 18, 2009, at 6:38 AM, Pete Muir wrote:

> To follow up on this, Mark Little pointed me at the Common Logging  
> Framework developed by Arjuna as another way this problem has been  
> addressed in the past.
>
> See http://docs.jboss.org/process-guide/en/html/internationalization.html#d0e4183
>
> On 17 Aug 2009, at 18:05, Pete Muir wrote:
>
>> Hi,
>>
>> As discussed here https://jira.jboss.org/jira/browse/WBRI-290, we  
>> would like to switch to slf4j as our logger (it offers a logging  
>> facade, supports MDC/NDC and parameter replacement).
>>
>> However, as Takeshi highlights here https://jira.jboss.org/jira/browse/WBRI-214 
>> , a needed feature is explicit i8n support, and it sounds like Ceki  
>> would be happy to accept a contribution for this directly to the  
>> slf4j.
>>
>> Perhaps, to get started, we should discuss the overall design and  
>> aims. In the linked issue, Takeshi adds three features in the patch:
>>
>> - ability to localize a message by providing a resource bundle,  
>> which has the same name as the class using the logger (the  
>> declaring class)
>> - the ability to log an enum value (rather than using a static to  
>> hold the message/key)
>> - the ability to associate the level at which to log with the  
>> message with the enum (via an annotation) rather than in the call  
>> from the declaring class
>>
>> (Takeshi, correct me if this is incorrect). I think we can probably  
>> separate these features out when discussing.
>>
>> I think we would also need:
>>
>> - ability to specify the resource bundle to use when getting the  
>> logger
>> - ability to use statics fields or just a string id embedded in  
>> call to logger
>>
>> But I'm sure others have given this more thought than me!
>>
>> Pete
>> _______________________________________________
>> dev mailing list
>> dev at slf4j.org
>> http://www.slf4j.org/mailman/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev at slf4j.org
> http://www.slf4j.org/mailman/listinfo/dev