Auto-translation with MS Translator

Auto-translation with MS Translator
in Liferay 7.2  

Liferay 7.2 comes with auto-translation feature and uses MS Translator to translate language keys to supported locales.

Step 1 - Obtain subscription key

1) Create MS Azure account https://azure.microsoft.com (if not registered yet);

2) Create new “Translator Text”:


3) Copy the subscription key:

Step 2 - Prepare files to translate

Create module for resource bundle:
Make sure, you have Language.properties under /src/main/resources/content location with required keys to be translated.

Step 3 - Configure Gradle plugin

Include ‘buildLang’ plugin and specify subscription key (from step1)  in build.gradle:

dependencies {
  compileOnly group: "com.liferay.portal", name: "com.liferay.portal.kernel"
  compileOnly group: "org.osgi", name: "org.osgi.service.component.annotations"
  compileOnly group: "com.liferay.portal", name: "com.liferay.util.taglib"
  compileOnly group: "javax.portlet", name: "portlet-api"
  compileOnly group: "javax.servlet", name: "javax.servlet-api"
  compileOnly group: "jstl", name: "jstl"
  compileOnly group: "org.osgi", name: "osgi.cmpn"
}
buildscript {
  dependencies {
     classpath group: "com.liferay", name: "com.liferay.gradle.plugins.lang.builder", version: "3.0.12"
  }
  repositories {
     maven {
        url "https://repository-cdn.liferay.com/nexus/content/groups/public"
     }
  }
}
buildLang {
  translateSubscriptionKey = "<SUBSCRIPTION_KEY>"
}

Step 4 - running translator and checking results

Run ‘buildLang’ Gradle plugin:

Expected result:


Language files with translations should appear.
For translated keys “(Automatic Translation)” suffix will be added, for those, which were not translated - “(Automatic Copy)”.
Finally, you can verified translations manually (better with native-speaker), and then remove “(Automatic Translation)” suffix from language translations. 

Comments

Post a Comment

Popular posts from this blog

Liferay Search Container Example

Or how to implement a custom search container in Liferay Overview   Search Containers are used in Liferay to display the table data. This article shows a simple example of how to implement a custom search container.  Example < liferay-portlet :renderURL varImpl ="iteratorURL" /> < liferay-ui :search-container total =" <%= ProjectLocalServiceUtil. getProjectsCount (scopeGroupId) %> "                              delta ="10"                              emptyResultsMessage ="no-projects-found"                              iterato...
Read more

Installing Blade CLI from Command Line

Installing Blade CLI from Command Line Download JPM Jar file Download biz.aQute.jpm.run.jar file using link: https://raw.githubusercontent.com/jpm4j/jpm4j.installers/master/dist/biz.aQute.jpm.run.jar Initialize JPM Run command: java -jar biz.aQute.jpm.run.jar init Install Blade Run command: jpm install -f https://releases.liferay.com/tools/blade-cli/latest/blade.jar to install blade. Update blade to make sure you have the latest version, sample:  blade update Current blade version 3.3.0.201811151753 Updating from: https://repository-cdn.liferay.com/nexus/content/repositories/liferay-public-releases/com/liferay/blade/com.liferay.blade.cli//3.8.0/com.liferay.blade.cli-3.8.0.jar Update completed successfully. Congratulations! Now you have Blade CLI installed. Sample command for mvc-portlet: blade create -t mvc-portlet -p com.demo.portlet -c DemoPortlet demo-portlet Enjoy 😏
Read more

Liferay Keycloak integration

Image
Liferay Keycloak integration using OpenID Overview This tutorial explains how to configure OpenID SSO between Liferay 7.2 and Keycloak 7.0.1 Installation instructions KeyCloak Configuration 1. Install and startup Keycloak server Download latest Keycloak server:  https://www.keycloak.org/downloads.html Unzip keycloak-7.0.1.zip folder. Run  keycloak-7.0.1/bin/standalone.sh  (or  keycloak-7.0.1/bin/standalone.bat ) file. Keycloak should be started on 8080 port:  http://localhost:8080 2. Create default admin user: and sign in to Admin Console. 3. Check OpenID configuration Click on "OpenID Endpoint Configuration": JSON configuration should appear, like this: { "issuer": "http://localhost:8080/auth/realms/master", "authorization_endpoint": "http://localhost:8080/auth/realms/master/protocol/openid-connect/auth", "token_endpoint": "http://localhost:8080/auth/realms/master/protocol/openid-con...
Read more