One important strength of the Java Platform, Standard Edition (Java SE) has always been its internationalization and localization support. The platform continues to evolve, and Java SE 6 provides developers even more control over how they access and use locale-sensitive resources in their applications. Java SE 6 provides the following major enhancements to its internationalization support:
- Resource control and access
- Locale-sensitive service
- Text normalization
- International domain names
- Japanese calendars
- New supported locales
Read more about this in the article:
International Enhancements in Java SE 6
Language and geographic environment are two important influences on our culture. They create the system in which we interpret other people and events in our life. They also affect, even define, proper form for presenting ourselves and our thoughts to others. To communicate
effectively with another person, we must consider and use that person’s culture, language, and environment.
Similarly, a software system should respect its users’ language and geographic region to be effective. Language and region form a locale, which represents the target setting and context for localized software. The Java platform uses
java.util.Locale objects to represent locales. This article describes the
Locale object and its implications for programs written for the Java platform.
Have a look. It’s an older article, but still perfectly valid and useful: Understanding Locale in the Java Platform.
And sure to be someone’s favorite, submitted by Jon Hanna at IUC 33:
A harsh lonely night,
my Private Use Area
has no assignments
Submitted at the IUC #33 by Ken Lunde:
So many ideographs
So many Extensions
Submitted at the recent International Unicode Conference by Mark Crispin:
Unicode has planes
But not a power of two
After once declaring that NetBeans still coughs on spaces, I’m ready to declare that NetBeans has resolved this issue.
At my current day job, I’ve been using Eclipse almost exclusively. Not of my choice really. Sometimes while in Rome, you have to do as the Romans. These particular Romans like Eclipse, so I too must use it. And really I didn’t have a lot of choice because the Eclipse projects had spaces in their names…and NetBeans just pitched a fit over this, making an easy migration to NetBeans practically impossible without changing the projects. I don’t think NB really cared that spaces where in project names, but the Eclipse migration tool itself sputtered on it. Until now.