/
How Globalese processes XLIFF files
How Globalese processes XLIFF files
- Greg Horváth (Unlicensed)
Owned by Greg Horváth (Unlicensed)
The following table describes what elements and attributes are required when Globalese parses an uploaded file, and what is changed by Globalese during pre-translation.
When preparing content for pre-translation using Globalese, it is important to let CAT tools do the preparations, or to follow the XLIFF 1.2 specifications otherwise.
XLIFF flavour / CAT tool | Input | Output |
|---|---|---|
memoQ | <trans-unit
mq:status="NotStarted"
<!-- translate="no" mq:locked="locked" attributes NOT present -->
>
<source>Source text</source>
</trans-unit> | <trans-unit
mq:status="MachineTranslated"
mq:lastchangedtimestamp="yyyy-mm-ddThh:mm:ssZ"
>
<source>Source text</source>
<target>Translation</target>
</trans-unit> |
Phrase This is only valid for files exported from Phrase in the | <trans-unit
m:confirmed="0"
m:locked="false"
>
<source>Source text</source>
<target></target>
</trans-unit> | |
SDL Trados Studio | ||
Smartcat | ||
translate5 | ||
Wordbee | ||
XLIFF 1.2 See official specification here. | or or | |
XTM |
, multiple selections available,
Related content
Uploading files
Uploading files
More like this
Text translation using deployed engines
Text translation using deployed engines
Read with this
Document translation
Document translation
More like this
Globalese API v3
Globalese API v3
Read with this
Integration
Integration
More like this
API keys for text translation
API keys for text translation
Read with this