AEM Classic Connector

AEM Classic Connector Request Translations

This article is for Account Owners and Project Managers

Once you have installed and configured the Smartling Adobe Experience Manager (AEM) Classic Connector, you can create and manage translation submissions to Smartling in the AEM Classic interface.

The Smartling AEM Classic Connector adds a Smartling-specific area to the Websites portal that allows you to manage components of AEM for translation.

Request Translations

Once the Smartling Connector is configured and target language branches have been created, translations of pages in the source or reference language can be requested from the Classic UI Editor.

Translate Pages

  1. Browse to the Websites portal and double-click to edit an existing page in the source language. In the Classic Editor Sidekick, open the Workflow tab and expand the Smartling Translations section. Click Translate.
  2. From the Send for Translation window, either enter a new Job Name and Due Date for this submission or choose the Add to Existing Job tab and select an existing job to which the page should be added. If you would like to authorize the job to be translated automatically, select Authorize Job.
  3. Select the language(s) into which you would like to translate the page and click Translate.

The sidekick will display the progress of the submission. The sidekick also indicates if a user has updated a page submitted for translation by marking the language with an asterisk (*).

Translate Content in Bulk

Check the Bulk Submit option from the Send for Translation window and use configure to select sub-pages to be included in the submission.

Include Visual Context with your Translation Request

A visual context capture tool is built into the Smartling AEM Classic connector, helping linguists get your translations right the first time - reducing translation cost and time to market.

If visual context is not displaying properly in Smartling, your AEM administrator should check the Smartling settings in AEM's Web Console Configuration page, or enable a proxy connection in Smartling - Network Settings

Mask a Variable in Content

If your content contains variables (such as the example below), you can protect variables from translation.

Contact Smartling {country} to see how we can help you grow your business and expand global reach.

The AEM Classic Connector already protects the standard Java placeholders which usually appears in i18n strings. It's done via Regex. You can extend it by adding a Regex pattern for your variable. For example, the variable "{country}" can be selected by using "\w+". You can add it into an existing configuration. 

  1. Open AEM web console (/system/console/configMgr).
  2. Find Smartling - Translatable Content Configuration.
  3. Update the value of the Custom Placeholder
  4. Resubmit your content to Smartling.

Check the Status of Translations

Once you have submitted the page(s) for translation, you can view and manage the submission on the Smartling Submissions page.

  1. Browse to the Websites portal and double-click Smartling > Submissions.
  2. Use the sidebar to search submissions by title, path, or status.
  3. Select one or more pages. (SHIFT + click to select multiple pages.)
  4. Choose an action:
    1. Re-send: Submit an updated version of the page to Smartling.
    2. Download: Manually download available translations from Smartling.
    3. Cancel: Cancels the submission. The download scheduler will no longer check for translations and the file will be unavailable for translation.

Preview Translations

Double-clicking any page will open a preview window showing the original page and the translated page side by side. Scroll and zoom is synced between the two windows.

Viewing Logs

If you encounter an error, you can access the Connector’s logs from within your AEM instance by clicking on the Websites Tab, then Smartling > Smartling Log Viewer.

Enter a number in the Line count box and click Refresh to display recent lines from the logs. 

Click Download to generate an archive containing the Smartling log file, and a snapshot of the connector's metadata for recently submitted pages. This information helps Smartling technical support to diagnose errors.

Troubleshooting Logs

If your ITOps has configured another location for log files then the Smartling log viewer should be configured additionally, otherwise you will see something like

File does not exist for 'logs/smartling.log', will try to find it in 'crx-quickstart/' folder.
  1. The actual smartling log path can be found on http://<aem_domain>/system/console/slinglog. You should copy this path and configure smartling log viewer with it.
  2. Open web console (http://<aem_domain>/system/console/configMgr)
  3. Find configuration Smartling - Log Viewerlog_viewer__1_.png
  4. Paste previously copied path here

Was this article helpful?