Martin, I like the idea of using the OS local language as there are many many many users who are not native English speakers. That being said, its probably better to standardize on something and if English is the standard that is already being used, I say we stick to that.
Adam On Tue, Oct 23, 2012 at 7:05 AM, Martin Desruisseaux < [email protected]> wrote: > Hello all > > java.lang.Throwable has two methods for fetching the exception message: > getMessage() and getLocalizedMessage(). I realize that the later is very > rarely implemented. However I'm considering to use it for some (not > necessarily all) exceptions implemented in Apache SIS. The proposed policy > would be: > > * getMessage() returns the message in the system default locale. > * getLocalizedMessage() returns the message in the locale of the > object that produced it. > > > For example on a server machine configured for the English locale, if an > AngleFormat object has been created for parsing angles in the French locale > and if that AngleFormat throw a java.text.ParseException, then getMessage() > on that exception would return the parsing error message in English while > getLocalizedMessage() would return the message in French. > > In a client-server architecture, the intend is that getMessage() would use > the locale on the server side, while getLocalizedMessage() would use the > locale on the client side. This is based on the assumption that the > above-cited AngleFormat has been created for parsing client's input. > > Is there any opinion on that? > > Martin > >
