{"id":8624,"date":"2016-05-23T09:54:37","date_gmt":"2016-05-23T07:54:37","guid":{"rendered":"http:\/\/phraseapp.com\/blog\/?p=211"},"modified":"2024-02-15T15:47:33","modified_gmt":"2024-02-15T14:47:33","slug":"i18n-3-easy-steps-to-localize-java-play-applications","status":"publish","type":"post","link":"https:\/\/phrase.com\/blog\/posts\/i18n-3-easy-steps-to-localize-java-play-applications\/","title":{"rendered":"3 Easy Steps to Localize Java Play Framework Projects"},"content":{"rendered":"

Localizing Java Play Framework apps can be quite tedious. In this tutorial, we’ll show you how Phrase can aid the translation of your Play Framework projects.<\/p>\n

Your Basic Setup for Localizing Java Play Framework Apps<\/h2>\n

The steps to internationalization are quite easy and can be followed by the i18n guide from Typesafe<\/a>.<\/p>\n

First, add the desired languages you would want to accept to your conf\/application.conf<\/code> with priority from important to a less important locale:<\/p>\n

application.langs=\"en,de,fr\"<\/pre>\n
Add the files messages.en<\/code>, messages.de<\/code>, and messages.fr<\/code> to your \/conf folder.
\nNow you can start translating\/localizing by consulting the official Play Documentation.<\/a><\/p>\n
Integrate with Phrase<\/h2>\n
Using the proper format for your localization files is important. Phrase supports the Play Properties format with UTF-8 encoding and without content escaping.<\/p>\n
Other than that it is based on the Java Properties format.<\/p>\n
Phrase renders all downloaded files with the file extension of the locale name you use within your project (like en_US, en-GB or de). See our Format Guide<\/span><\/a>.<\/p>\n
A sample valid Play Properties file:<\/p>\n
# My Software Project (description)\nproject.name=Some Name\ntitle1=AwesomeApp\n# You can never have enough titles!\nmore_titles Another Title<\/pre>\n
You can now easily upload the locale file to Translation Center:<\/p>\n
\"Uploading<\/p>\n
\u2026 or through our phrase gem<\/a>\u2026<\/p>\n
phrase push conf\/messages.en --format=play_properties --locale=en --tag=version_1<\/pre>\n
Along the lines with \u201cpush\u201d the usage of phrase pull is straightforward. Simply type:<\/p>\n
phrase pull en --format=play_properties --target=conf\/ --tag=version_1<\/pre>\n
The tag option is optional but always nice. With this, you have a labeling system to manage your translations in manageable chunks (like Gmail).<\/p>\n
In this example we explicitly deal with the en locale, you can also push directories or pull all locales and their translations by not typing a locale at all.<\/p>\n
If Ruby does not suit your needs, just use our REST-based API directly<\/a>.<\/p>\n
Next Steps<\/h2>\n
Now that your application is up to speed with your latest translations you can start collaborating with your team members to edit your translations from within the Phrase Translation Center.<\/p>\n
To invite your team members, go to our web frontend known as the \u201cTranslation Center\u201d click on \u201cAccount\u201d and go to your user management. Invite translators, developers or managers to your team all with their own permissions.<\/p>\n
Your translators can work from within the Translation Center. Your developers might do some more background work with the API to regularly update translations by pushing first. Through pushing, the local translations added by your developers are transmitted to the Translation Center. By pulling the new content – created by your translators – it is updated in your local application, too. This needs to be done continuously especially when you ship often.<\/p>\n
Further Reading<\/h2>\n