Internationalization with Play Framework(2.6.x)



In this blog, I will demonstrate how your application can support different languages using Play Framework 2.6.0 
 
What is Application/Website Internationalization ?
 
Application/Website Internationalization can be defined as a process of developing and designing an application that supports not only single language but also different languages so that it can be easily adapted by the users from any language, region, or geography. It ensures that the code base of your application is flexible enough to serve a new audience without rewriting the complete code or keeps text separate from the code base. 
 
Let us start the implementation step by step:
 
1. Specifying Languages for your application  
  
In order to specify Languages for your application, you need Language tags, which are specially formatted strings that indicate specific languages such as “en” for English, “fr” for French, a specific regional dialect of a language such as “en-AU” for English as used in Australia.
 
First, you need to specify the languages in the conf/application.conf file, Languages tags will be used to create play.api.i18n.Lang instances.
 
conf
                                            
         play.i18n.langs = [“en”, “fr”]
 

2. Externalizing Messages
 
Externalizing Messages in the conf/messages.xxx files. Here we have two language-specific message files messages.en for English and message.fr for French. If you don’t specify any message file for any specific language than the default conf/messages file matches all the languages.
 
you can provide messages in each language specific file like this, 
 

default.message = Play Framework Example

 

3.  Message with Controller
 
Created a controller MySupportController that extends I18nSupport trait. 
 
The I18nSupport trait adds following methods to a Request:
 
  • request.messages return the instance of Messages, using implicit MessagesApi.
  • request.lang returns the preferred Lang, using implicit MessagesApi
messagesApi.preferred method, by using this method the preferred language is extracted from the Accept-Language header and matching one of the MessageApi supported languages.
 
The i18nsupport trait also adds two language cookies supported methods to Result:
 
  • result.withLang(lang: Lang) is used to set the language for future request by storing it in the cookie.
  • result.clearingLang is used to discard the language cookie set by withLang.

4. Messages with Twirl Template

Here Twirl templates take MessageProvider, and it is assumed that a MessageProvider is passed into the template as an implicit parameter.

You can get the source code from here.

I hope this blog is helpful to you!

Thanks 

References:
 

KNOLDUS-advt-sticker

Advertisements

About Teena Vashist

Teena is a Software Consultant at Knoldus Software LLP having 2 year experience working in Scala. She is very enthusiastic towards her work and good at working in team. She is very much keen to learn new technologies. She is familiar with programming language's such as Scala, Play Framework, Akka, Javascript, HTML, Java.
This entry was posted in github, HTML, Internationalization, Play Framework, Scala and tagged , , , , . Bookmark the permalink.

2 Responses to Internationalization with Play Framework(2.6.x)

  1. anshulghogre says:

    Well explained

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s