You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by Michael Dick <mi...@gmail.com> on 2009/06/05 22:32:32 UTC

Localized trace messages

Does anyone have strong feelings regarding localization of trace messages?

Currently nearly every message we log is externalized for future
localization. For warning, log etc. messages this makes sense, but I'm not
sure there's a compelling need for localization of trace messages.

Is there a compelling reason that I've missed?

-mike

Re: Localized trace messages

Posted by Rick Curtis <cu...@gmail.com>.
I can't come up with any good reasons to localize trace messages. Requiring
such may hinder *some* developers from actually putting trace in there code.


-Rick

On Fri, Jun 5, 2009 at 3:32 PM, Michael Dick <mi...@gmail.com>wrote:

> Does anyone have strong feelings regarding localization of trace messages?
>
> Currently nearly every message we log is externalized for future
> localization. For warning, log etc. messages this makes sense, but I'm not
> sure there's a compelling need for localization of trace messages.
>
> Is there a compelling reason that I've missed?
>
> -mike
>

Re: Localized trace messages

Posted by Donald Woods <dw...@apache.org>.
Agree, that trace messages don't need to be translated, but would like 
to hear some or lack of feedback from users before deciding.


-Donald


Michael Dick wrote:
> Does anyone have strong feelings regarding localization of trace messages?
> 
> Currently nearly every message we log is externalized for future
> localization. For warning, log etc. messages this makes sense, but I'm not
> sure there's a compelling need for localization of trace messages.
> 
> Is there a compelling reason that I've missed?
> 
> -mike
>