Internationalization (i18n). A vital aspect to development of enterprise applications in today's world. Without i18n at the core of development activity, product globalization would be impossible, feature localization a nightmare, and UI translation turned into a twisted joke on the eventual end user. True, thanks to the baked-in world-ready goodness of Unicode and Java itself, much of the pain we've endured in the past when it came to internationalization is gone. But...
It's still good to know the basics, and... there's still a lot of legacy stuff out there that needs to be integrated with, or needs to be rebuilt to work in, the cloud.
So, here's a great little blog post from John O'Conner (@joconner) on the absolute minimum you should know about internationalization.
John's an experienced Java and Android head, and an i18n veteran too. Yes, he really was doing i18n before it was cool!
Let's keep the following kinds of experiences behind us forever:
A real-world example from ye olde days of #i18nfail. Character encoding failure, hard-coded line-breaks, no expansion space, no externalization from the SQL, it's a classic! Circa 1998 I think. The content has been reworked to protect the näive at the time.
To explore more about Oracle ADF internationalization, then head on over to the ADF Architecture TV YouTube channel and check out what our own Frédéric Desbiens (@blueberrycoder) has to say in his awesome series of recordings.