In these cases wouldn't you want to log the raw data (message id and
parameters) and then localize when displaying? That way anyone could
view the logs.
-dain
On Apr 9, 2006, at 1:33 PM, Lars Kühne wrote:
Hi Edell,
Nolan, Edell wrote:
[...] As regards getting the wrong language - this won't happen
because this is actually based on the locale - The Logic ensures
it picks the most specific one to the more generic one.
So in the case if you are in germany you will never get thai etc.
you got me wrong: We are in developing in germany, our customers
are running our software in Thailand (or wherever). Hence we will
get error messages that are not helpful at all for our engineers.
Note from the Class ResourceBundle API:
Resource bundles contain locale-specific objects. When your
program needs a locale-specific resource, a String for example,
your program can load it from the resource bundle that is
appropriate for the current user's locale.
That is the point. For GUIs the current user's locale ist exactly
what you want. For logfiles, it's exactly *not* what you want,
unless your developer/support team speaks each customer's language.
For us (and I assume most globally active software vendors?) this
is not the case.
Regards,
Lars
