> -----Original Message-----
> From: Dain Sundstrom [mailto:[EMAIL PROTECTED]
>
> Again we have the cart way ahead of the horse...
>
> We need to draw a line. What are we gong to make i18 and what are we
> going to leave in english. When are we going to add i18?
>
> I suggest we come up with a way for us to add i18 later without any
> pain now (see my previous message). Further, I suggest we make the
> rule that only user displayable messages and log messages > info
> support i18, but now Exceptions, debug, or trace.
>
> We have a huge project in front of us and we should do everything to
> make this a fast and enjoyable experience, and I find that editing
> messages bundles and working with message formatter to be neither. I
> think we should take a long breath and think about a way to make it
> easy add this later.
I have run into many, many, occasions where developers who have difficulty
with English appreciate i18n messages, I am certain that i18n exceptions
would be no exception. ;) Maybe we can be defiantly targeted at English
speaking developers. :p
I want a fast and enjoyable experience too, it does not stop me from writing
comments and javadocs or trying to format the code in a legible way.
One thing that I know for sure, either Geronimo puts it in early on or, let
us not kid ourselves, it will most likely never happen.
Regards,
Alan
----------------------------------------------------------------
Visit our Internet site at http://www.reuters.com
Get closer to the financial markets with Reuters Messaging - for more
information and to register, visit <http://www.reuters.com/messaging>
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of The
Reuters Group.
