Child pages
  • Content Translator Liferay 7.2

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


When the application is installed a new button "Automatic Translation" will appear next to Liferay's "Add Translation"

Image Modified

When you click on the button "Automatic Translation" a new dialog will be displayed where you can select one or more languages. This dialog will show only the languages that are supported by both the azure translate API and the current Liferay configuration.

Image RemovedImage Added

After selecting the desired languages and click on the "Continue" button, the new translation(s) should be listed as regular Liferay's translations:

Image RemovedImage Added

This feature will work exactly the same in complex Web Content that uses Liferay's structures and templates, in this case only the fields with text content will be translated.



Click in the Plus icon "create a resource"

Search and select the translator resource

Click in the create button 


Fill out the form

Important values 

  • Region = Global
  • Pricing tier = Free F0

Click in the Next Identity button 

Click in the Next Tags button 

Click on the Next Review button 


Finally, create the resource

Click in the create button 

Click Go to Resource button 

Click in the Keys and Endpoint option 

Copy the key


After obtaining the credentials configure them in the Control Panel:

Under Control Panel, under Configuration, select "System Settings"

Image Modified

Go to the Other section and click on the other icon 

Image Modified

  1. Select the "Automatic Translator Configuration"
  2. Provide the API key, and then click Save

Image Modified

Additional Considerations

There are some languages that may generate characters not supported by some databases using certain configuration, for example the default configuration that Liferay uses to connect to MySQL forces UTF-8 encoding that may lead to Exceptions when trying to add a translation in languages such as Japanese, in the case of MySQL this can be solved changing the connection string in the file like this:

Locate the JDBC connection string:


Remove the characterEncoding\=UTF-8 parameter:


The server needs to be restarted after the change.

Code repository

The latest source code is located at the following location:

Contact Us

We welcome feature/bug reports concerning the Content translator app. Discussion helps clarify the ways the app can be used and also helps define directions for future development. Please post your concerns at

Change Log

Liferay 7.2 version