The LILT + Smartling TMS connector enables companies to automatically push and pull web content between Smartling TMS and LILT. This saves you time by providing seamless localization while letting you continue to work in the systems you know.

​
Configuration

  1. Within Smartling, create a new user and provide its login credentials to your contact at LILT. For this example, we’ll call the user “Smartling User”.
  2. Create a workflow template that assigns this user as the linguist under the “translate” step. Share this with your LILT contact.
  3. Provide all languages and locales you’d like to have enabled as part of your workflow to your LILT contact
  4. Invite the LILT contact to your project needing translation

​
Workflow

Once the connector is configured, content is automatically moved between LILT and Smartling as outlined in the sections below.

​
Project creation

Create a translation project in Smartling under the LILT Smartling User. LILT periodically checks for new projects assigned to the LILT Smartling User. When found, new content is automatically pulled into LILT to create new LILT Projects where the content can be translated.

​
Project completion

When a project is “Delivered” in LILT, translations are sent back into Smartling and a workflow step is advanced for final review and approval in Smartling.

​
FAQ

Q: Why are some segments from Smartling not imported into Lilt? A: Segments that are “locked 100% matches” in Smartling are not included in the XLIFF file that Lilt receives. This is intended behavior from the Smartling side, and Lilt cannot change this as it’s a limitation of the Smartling API that Lilt uses. Q: Why doesn’t the Smartling connector show up in the new Connectors UI? A: The connector needs to have an liltOrganizationId associated with it to appear in the new UI. Connectors created through the older connectors-admin tool might not have this ID, but it can be added by a Customer Engineer. Q: What is the logic behind the . character being added to strings in the Smartling connector? A: The . was added to work around Smartling’s caching logic, forcing it to accept segments that were unchanged in Lilt. This is under active development and may change in the future. Q: Is it possible to show Lilt statuses in Smartling? A: It is not currently feasible to show Lilt statuses directly in Smartling due to limitations in Smartling’s API.