Exporting/Importing Content for Offline Translation
This feature is available for all Account Owners and Project Managers via the Jobs Dashboard (Enterprise only).
Occasionally, you may want to send a Job that's in progress in Smartling to a translator for offline translation. This feature allows you to export content with linguistic assets and easily import the completed translations back into your Smartling account.
- This feature is for Account Owner and Project Manager users only
- Offline Translation must be enabled for the translation step the job is in. Go to the Project settings > Workflows > Manage Step > Allow offline work.
- The Job must be authorized and in progress - not awaiting authorization or published.
How to Export Content
- From the Jobs Dashboard (account-level or project-level), locate the Job that's in progress and click the ellipses (3 dots).
- Select “Export Content” for a job that is in progress.
- Choose from all languages and workflow steps that are available for offline translation
- Select which files;
- Glossary files (TBX)
- Translation Memory files (TMX)
- You can select any combination of files for export. Exporting multiple files with multiple Translation Memory Files might take up to 2 minutes to export.
- Click Export.
- For larger files, a notifier will inform you that you will receive an email to your username email address, with a download link for the exported file.
- Exported content will be found in your local drive under Downloads.
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2"
<file original="smartling_offline_cat_data.xliff" source-language="en-US" target-language="de-DE" datatype="plaintext">
<trans-unit id="cf2c8a76485f273cbc59b2c9b73d9522" resname="">
<source>Job for Documentation</source>
<seg-source><mrk mtype="seg" mid="1">Job for Documentation</mrk></seg-source>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE tmx SYSTEM "tmx14.dtd">
<header creationtool="Smartling" creationtoolversion="1.1" srclang="en-US" datatype="xml" segtype="block" adminlang="en-US" o-tmf="Smartling" />
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE martif SYSTEM "TBXcoreStructV02.dtd">
<martif type="TBX" xml:lang="en"><martifHeader><fileDesc><sourceDesc><p>Smartling's TBX glossary export for Example Glossary</p></sourceDesc></fileDesc><encodingDesc><p type="XCSURI">http://www.ttt.org/oscarstandards/tbx/TBXXCS.xcs</p></encodingDesc></martifHeader><text><body><termEntry><langSet xml:lang="en"><tig><term>Example Term</term><termNote type="createdBy">Rachel Carey</termNote><termNote type="lastModifiedBy">Rachel Carey</termNote><termNote type="Example Custom Field">Custom Field for Source metadata</termNote><descrip type="Definition">This is an example glossary term definition</descrip></tig></langSet></termEntry><termEntry><langSet xml:lang="en"><tig><term>Test string</term><termNote type="createdBy">Rachel Carey</termNote><termNote type="lastModifiedBy">Rachel Carey</termNote><descrip type="Definition">Glossary definition of test string</descrip></tig></langSet></termEntry></body></text></martif>
How to Import Content
- From the project-level Jobs Dashboard, locate the Job that's in progress and click the ellipses (3 dots).
- Select “Import Content” for a job that is in progress.
- Select or drag and drop the .xliff files that you want to import into Smarting. Only .xliff files are supported for content import.
- Choose from one of the import options:
- Save and remain in the current step: keeps the content you are importing in the current workflow step.
- Save and submit to next step: automatically pushes all content you are importing to the next workflow step.
- Click Import
When import commences, you will see which files have imported successfully (green checkmarks), and which files have failed to upload (listed in red).
From the Strings View, you can view imported content. If any individual strings have failed to import, the target translation will be blank. The most common reasons for a failed string import are that tags used in the offline translation are not supported in Smartling for the specific file type.
Important Considerations for Exporting/Importing Content
The following are important considerations when using exporting and importing content off the Smartling platform:
Loss of context
Translators lose the ability to get the contextual view which is key for ensuring they are translating the content under the right context, and for your to minimize questions around what the content is about, issues with bad translations, and time spent in QA once the content is published from your side.
Loss of transparency
As a customer, you no longer can track the progress of where the content is in the translation workflow, and do not know how many resources are being used to translate your content. In addition, all available reports to track translation velocity, and changes will not have the data needed to evaluate how long is taking for the content to get translated, edited, and how many changes are being done by editors as an example.
Markup/code integrity risks
When working online in Smartling, we ensure that all your underlying code and markup is protected. Translators are not able to alter it since we protect it by masking it. When you export the content under a flat file (.xliff) all code is visible, and can potentially be altered which could result in broken functionality, or more time spent on QA and fixing any issues that might come up because of changed code.