This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Localization == internationalization, right? Personally, I'm not planning on doing it. My assignment didn't say anything about it. Remember that you get no extra point for doing anything outside of requirements. I'm happy that for once I don't have to do it -- sick of having to do it at work all the time.
Basically I have the same opinion about i18n. But I think it is not good style when the texts for display are hard coded. Especially when the texts are spread all over the gui view code (depends on over how much compile units the gui views are spread). For maintainability it is important to easily locate the text definitions. If the texts are hardcoded it would be harder to find them. Maintainability (=quality) is desirable (in any software ). For my assignment I don't plan to use the jdk's resource bundle mechanism but I plan to externalize my display texts in some way. I have yet no concrete concept how I'll realize it. Maybe it would be a good idea to define constants for all display texts of a view and concentrate them at one point in the code. However, the best way is to keep it as simple as possible. Do you know what I mean?