In today’s post i’ll share with you the way we’re handling Internationalization (i18n) and Localization (L10n) in our REST API which is based on Spring MVC (3.2.3.RELEASE).
Our front-end web client is an SPA (Single Page Application) built using AngularJS framework and occasionally it needs to handle Java exceptions messages thrown by the back-end. The way it has been implemented is that it intercepts JSON error responses, wraps them in a pre-defined web page template and displays to the user in a unified and nice way.
“Localization” of back-end related error messages happens …at the back-end level.
After this quick intro let’s get familiar with following two definitions:
- Internationalization – process of designing software applications so that they can be adapted to various languages and regions without engineering changes.
- Localization – process of adapting internationalized applications for a specific region or language by adding locale-specific components and translating text.
View original post 492 more words