{"id":36825,"date":"2016-06-28T09:21:44","date_gmt":"2016-06-28T03:51:44","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=36825"},"modified":"2016-06-28T10:46:53","modified_gmt":"2016-06-28T05:16:53","slug":"javascript-based-internationalization-in-grails","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/javascript-based-internationalization-in-grails\/","title":{"rendered":"JavaScript based internationalization in Grails"},"content":{"rendered":"

Generally Internationalization is used for displaying HTML text \u00a0based on user\u2019s locale or\u00a0region. This is often done on server side of the application.<\/p>\n

Of late a lot of applications do the HTML generation on the client side, rather than on the server side. And to support the internationalization on client side is a common problem in this scenario.<\/p>\n

Currently there are 2 ways to achieve internationalisation on client side:<\/p>\n

1.Pass the i18n messages from controller<\/a> to client side in response<\/p>\n

2.Internationalize the required messages on the client side instead of server side<\/p>\n

Both of them are not easy. But, out of the two, I would personally recommend the second option as passing the i18n messages every time in the response is not a good practice.<\/p>\n

However, if we are working on Grails<\/span><\/strong>\u00a0framework<\/a>, the second option is fairly easy to achieve due to its i18n-asset-pipeline plugin.<\/p>\n

i18n-asset-pipeline plugin is an asset pipeline plugin, that generates a JavaScript file with internationalized texts, which can be used for client side i18n.<\/p>\n

To use this plugin, add the following code to your BuildConfig-<\/p>\n

[java]<\/p>\n

plugins {<\/p>\n

compile ":i18n-asset-pipeline:1.0.6"<\/p>\n

}<\/p>\n

[\/java]<\/p>\n

For defining internationalised messages we have to create a special file (per locale) with ‘i18n’ extension, eg. messages_fr.i18n, where ‘_fr’ represents french locale and ‘messages’ is the base name of the file that is common amongst all files. These files contains list of local messages keys you would like to use on the client-side.<\/p>\n

Now, to load the messages file for specific locale, all you have to do is use the following tag in your code:<\/p>\n

[java]<\/p>\n

<asset:i18n locale="en_UK" \/>
\nOR
\n<asset:i18n locale="${locale}" name=\u201dtext\u201d\/>
\n[\/java]<\/p>\n

where locale is a string or locale object and name is the base name of the file you want to load. In first case the \u201cmessages_uk.i18n\u201d file will be loaded and in second case, if the locale object is of France then \u201ctext_fr.i18n\u201d file will be loaded.<\/p>\n

After the file is loaded you can show the locale specific message by using following code:<\/p>\n

[java]$L("user.name.label")[\/java]<\/p>\n

assuming, user.name.label is one of the keys defined in your locale file.<\/p>\n

The beauty of this plugin is that it creates a JS file similar to messages.properties and places all the keys and their values, that it had pick from correspoding message.properties file, in it. And since the output file is .js type, therefore now you can use the locale specific messages in your javascript code without worrying about where to get them from.<\/span><\/p>\n

\u00a0<\/strong><\/strong>For further details you can use my sample project<\/a><\/span>.<\/span><\/p>\n

Hoping this information was helpful. Happy Internationalisation!<\/span><\/strong><\/p>\n

Cheers!<\/p>\n","protected":false},"excerpt":{"rendered":"

Generally Internationalization is used for displaying HTML text \u00a0based on user\u2019s locale or\u00a0region. This is often done on server side of the application. Of late a lot of applications do the HTML generation on the client side, rather than on the server side. And to support the internationalization on client side is a common problem […]<\/p>\n","protected":false},"author":256,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":3},"categories":[7],"tags":[4840,3640,3636,3638,3639,3637,3631,3630],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/36825"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/256"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=36825"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/36825\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=36825"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=36825"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=36825"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}