Adding Lionbridge as a Provider
5 minute read
Before you can send content directly from Drupal TMGMT to Lionbridge, you must add the Lionbridge Connector for Drupal TMGMT as a provider in Drupal TMGMT.
You may want to add Lionbridge as multiple providers in Drupal TMGMT, for example, if you want to use multiple Content API credentials or different provider configurations.
Adding Lionbridge as a translator in Drupal TMGMT requires the following three general steps:
- Send an email to email@example.com requesting access to the Content API v2.
- The Lionbridge Connector Support team creates a Content API V2 account for you.
- In Drupal TMGMT, you configure the connection to your Content API V2 account.
Detailed instructions follow below.
Note: The default configuration settings are appropriate for most users.
To add Lionbridge as a provider in Drupal TMGMT:
Download the package for the latest version of the Lionbridge Connector using the link provided.
In Drupal, select Modules from the menu and then click Install new module to install the Lionbridge Connector package you downloaded in the previous step.
After you receive a notification from the Lionbridge Connector Support team that your Content API V2 account has been created, log in to Drupal to complete the process.
In Drupal, select Translation > Providers from the menu.
The Providers page opens.
Click Add provider.
The Add Provider page opens.
- Enter the following information:
Note: An asterisk (*) indicates a required field.
|Label||Your name for the Lionbridge Connector in Drupal TMGMT. This is what is displayed to users who select a translation provider (“provider”) when sending out content for translation.|
|Description||Your description of the provider.|
|Auto accept finished translations||Indicates whether to automatically accept all completed translations.
In the Provider plugin dropdown list, select Lionbridge Content API. This is the Drupal TMGMT plug-in for Lionbridge translation services.
In the Lionbridge Content API Settings section, enter the following information:
|Export to||Your content is always exported in XLIFF format, which is the standard XML-based format for exchanging localizable data between applications.|
|XLIFF CDATA||Select this check box to wrap the content in CData tags. This prevents the Connector from escaping special characters, and avoids the scenario of double-escaped characters.
Note: If you select this check box, the Connector ignores the Extended XLIFF processing setting, described next.
|Extended XLIFF processing||Select this check box to further process content semantics and mask HTML tags instead of escaping them:
|Allow export-format overrides||Select this check box to enable users to override the export-format settings when sending out content items for translation.|
|Use one export file for all items in job||Select this check box to export all content items to one file. Clear this check box to export content items to multiple files.|
|Download method||You can choose where to store exported files. Depending on your Drupal configuration, additional download methods and locations may be displayed in addition to Public local files served by the webserver.
Recommendation: Use a secure location to prevent unauthorized access.
|Lionbridge Content API
To obtain credentials for the Content API, you can contact
How to Contact Lionbridge Connector Support.
|PO Number||Optional. Enter a valid purchase order number that you set up in Lionbridge Freeway.|
|Client ID||The Lionbridge Client ID for accessing the Content API, which enables you to use the Connector to send Drupal content items to Lionbridge for translation.|
|Client Secret ID||The Lionbridge Client Secret ID for accessing the Content API, which enables you to use the Connector to send Drupal content items to Lionbridge for translation.|
|Username||The Lionbridge Zendesk username for accessing the Lionbridge Content API V1, which enables you to see the translation jobs sent to Lionbridge Content API V1.|
|Password||The Lionbridge Zendesk username for accessing the Lionbridge Content API V1, which enables you to see the translation jobs sent to Lionbridge Content API V1.|
- Click Connect. The Connector sends the credentials (Client ID and Client Secret ID) to the Content API. The Connector stores the returned token for future sessions.
Notes: The Connector does not save your Client ID or Client Secret ID. You must click Connect, at least once, to generate the access token required to use the Connector.
- Enter the following information in the bottom part of the page.
|Provider configuration||The default translation provider configuration. This translation provider will be displayed by default when users send content out for translation.|
|Allow provider overrides||Optional. This option determines whether users can change the translation provider when submitting jobs.
|Transfer all files as zip||Optional. Select this check box to instruct the Connector to deliver all files for translation in a single .zip file.|
|Auto Import Job||Optional. In the sub-section, select the check box. This instructs the Connector to deliver all translated content automatically, as soon as it is ready.|
- Optional. In the Remote Languages Mappings section, you can update the default mapping between each language in Drupal TMGMT and the corresponding Lionbridge Freeway language code.
Each text box in this section has a label with the language name and code of each language set up in the Drupal TMGMT Languages page. (To open this page, select Configuration > Regional and language > Languages from the menu.)
- Click Save.
The Providers page reopens, displaying the provider you just created.
If you want to add another provider to support different Content API credentials or different provider configurations, repeat the steps above.