This article is about web application internationalisation (internationalization, I18N) and language localisation (localization, L10N). This article shows you how to localise a Play framework web application, with an example based on the 'Yet Another Blog Engine' example application, used in the Play tutorial.
Lunatech has built and continues to be responsible for maintaining several of Sdu's web-based law and jurisprudence document search applications. These applications divide the vast amount of Dutch law and related information into different areas of law, which provides added value to lawyers specialised in certain areas, eg. criminal law or labour law. Customers subscribe on-line to a number of different applications that give access to these different areas of law and different subsets of kinds of information (no jurisprudence, for instance) or access to the complete body of knowledge.
At Lunatech, we recently decided to build a small web application to implement one of our ideas for generating business plan summaries. We needed to get this running on-line as quickly as possible, with minimal time spent coding, so we chose to build it using the Play! framework. The result was fast development, clean code, easy deployment and an instantly popular web application - http://plancruncher.com/.
You have your Play! application deployed on production. It is a real success and you have loads of users. You are really happy, and because Play! is quite fast you do not have any performance issues yet :) However, you are receiving feature requests. Being agile developers, you implement them quickly, test them in acceptance and you are ready to let your users enjoy them. But, your web applications is so successful that you do not really want to plan any downtime…
Perhaps the most striking thing about about the Play! framework is that its biggest advantage over other Java web application development frameworks does not fit into a neat feature list, and is only apparent after you have used it to build something. That advantage is usability.
Copyright © 2005-2012, Lunatech Research B.V. All rights reserved.