Hi Glen, Glen Daniels wrote:
1) Messages should be internationalized and accessed via resource APIs. Really. At some point we should all stop working on features and take a few days to hang out and make a serious push to do this across the board. After that's done we should implement a daily automated scan (like Axis1 does on each build) across the source to alert us of non-internationalized messages.
In my opinion, there are a some problems with internationalized exception messages:
- Confusion of tongues. While error notifications for end users certainly should be localized, exeption messages that normally appear in application logs and like that shouldn't, imo. If similar problems cannot neccessarily be identified by similar error messages, getting support for a specific problem becomes difficult.
- Error messages that are accessed via resource keys tend to become lies over time. Resource key reuse, copy&paste, non-adaption to modified code, or ambiguous resource key names do their corrosive work here;-)
- Error messages that are accessed via resource keys tend to be static. I absolutely agree with Sanjiva ("... give all the potentially useful info to the developer..."), so including information that's only available at runtime is often a good idea. Creating such dynamic error messages for different languages is difficult.
-- Just my 2 cents, Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
