The Lilt + XTM Cloud connector enables companies to automatically push and pull web content between XTM and Lilt. This saves you time by providing seamless localization while letting you continue to work in the systems you know.
At a high-level, Lilt's XTM LSP connector handles:
Submission via XTM: Create new projects in Lilt by creating a project in XTM using a project template assigned to the Lilt LSP.
Project Progress: Using XTM, check on the status of the content you sent to Lilt for localization.
Delivery to XTM: Lilt to deliver localized content to XTM for approval.
TM Creation: Use XTM to select a TM you want uploaded to Lilt.
TM Write-back: Update XTM translation memories with Lilt changes.
Send TB: Export XTM termbase to Lilt.
Add Lilt as an LSP within their instance of XTM.
Go to the
Fill in the fields marked with a red asterisk and click the
For additional information, reference XTM's documentation on How to set up subcontracting in XTM.
Adding Lilt as an LSP within your XTM instance will trigger XTM to send an email to the address specified in the previous step. Once Lilt has added the customer's credentials (specified in the email) to Lilt's XTM instance, XTM will send an email back to the customer with instructions for how to complete the handshake process.
Complete the process by heading to the
LSPsand click the
Lilt LSPoption to open the LSP editor. Navigate to
Connectionand fill in
Connection information from the LSPfields using the information provided to the customer (via email) by XTM.
Now you will have the ability to assign Lilt as the LSP for a particular project.
Building a workflow with Lilt
You will need to create a workflow in XTM that assigns the Lilt LSP to the translate step of the workflow. This will allow content to be transferred between XTM and Lilt.
Create one or many XTM project templates which you can use to send content to Lilt for localization. Having more than one Lilt-specific project template is useful for accommodating different localization workflows.
Navigate to the Projects tab and click
Define the following attributes for your template (* starred fields are required):
Source language (one)*
Target languages (many)*
For additional information, reference XTM's documentation on How to create a project template.
Once you have specified your desired template properties and workflow, click
Save a templateto create the template.
Head to the template and navigate to the workflow subpage. Here will see the workflow you assigned to the project template.
Assign the Lilt LSP to the
translateworkflow step in order to ensure projects created using this template are sent to Lilt for localization.
Define any additional workflow steps for XTM to carryout once Lilt has returned the localized content.
For additional information, reference XTM's documentation on Setting up and monitoring project workflows in XTM.
savebutton to finalize your template.
Once the connector is configured, content is automatically moved between Lilt and XTM as outlined in the sections below.
Creating a project in XTM (using the project template assigned to the Lilt LSP) will automatically create new Lilt Projects for the content to be localized. The following properties defined during project creation will be carried over to Lilt:
Using XTM, you can check on the status of the content you sent to Lilt for localization.
When a Lilt Project is marked as
done, the Project's contents are automatically sent back to XTM and the workflow step is advanced.
XTM batch delivery
By default, files submitted in a batch to Lilt via XTM get added under one Lilt Project. Project files are only returned to XTM when all the files have been localized and the Project has been marked as done.
If you want to circumvent this, you could submit smaller batches to Lilt, but this reduced the efficiency of batch uploads. Luckily, there is a better solution! You can configure the maximum number of files allowed per Lilt Project when submitting via XTM. When the file count exceeds this number, separate projects are created to house the files.
The example image below shows what would happen if nine files were submitted and each Lilt Project was limited to three files. In this case, the files would appear in three separate Lilt projects. When all three files in any Project are translated, the Project could be marked as done to send those files back to XTM without having to wait on any of the other Projects.
Smaller maximum file counts accelerates the average speed at which individual files are delivered back through XTM. However, smaller maximum file counts can make things more challenging to manage. Experiment with different maximum file counts to find what works best for you.
Lilt has a demo system and test configurations set up. Access can be provided upon request.