Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: geronimo-dev@incubator.apache.org
Date: Tue, 19 Aug 2003 10:14:45 +0100
Subject: Re: [i18n] Hardcoded message strings
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Alex Blewitt <Alex.Blewitt@ioshq.com>
To: geronimo-dev@incubator.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <3F415CA4.4050904@tackline.demon.co.uk>
Message-Id: <9361E73C-D225-11D7-870E-0003934D3EA4@ioshq.com>

On Tuesday, Aug 19, 2003, at 00:09 Europe/London, Thomas Hawtin wrote:

> Jason Dillon wrote:
>> Yes we should, please submit a patch (someone).
>
> It appears that very few programs put there exception messages in 
> resource bundles. I guess we expect anyone who reads them to be a 
> programmer and be able to read English even if not quite like a 
> native. Also it's easier to edit the messages if they're inline. But I 
> won't let that stop me.

What's going to happen in the following situation:

o Server is running on server with default language French
o User running a web application is using German as a language

Which of the two will be used to dump exception messages? I can see two 
possibilities:

1) The administrator wants to see exceptions in their language in the 
logs (French)
2) The web user will be shown an error message based on an exception, 
and hopes that it would be in their language (German)

I think the only way of achieving this would be to have a 
formatExceptionInLocale(Locale) method which could choose the 
translation at print time, rather than at construction time.

Alex.