/
How Globalese processes XLIFF files

How Globalese processes XLIFF files

Owned by Greg Horváth (Unlicensed)
Last updated: Nov 24, 2022
2 min read

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

XLIFF flavour / CAT tool

Input

Output

memoQ
.mqxliff

<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
.mxliff

This is only valid for files exported from Phrase in the .mxliff format. The Phrase plugin sends standard XLIFF files to Globalese.

<trans-unit m:confirmed="0" m:locked="false" > <source>Source text</source> <target></target> </trans-unit>
<trans-unit m:trans-origin="mt" m:created-by="Globalese" m:modified-by="Globalese" > <source>Source text</source> <target>Translation</target> </trans-unit>

SDL Trados Studio
.sdlxliff

<trans-unit> <seg-source>Source text</seg-source> <sdl:seg-defs> <sdl:seg <!-- conf attribute NOT present --> <!-- locked attribute NOT equal to "true" --> /> </sdl:seg-defs> </trans-unit>
<trans-unit> <seg-source>Source text</seg-source> <target>Translation</target> <sdl:seg-defs> <sdl:seg conf="Draft" origin="mt" origin-system="Globalese" /> </sdl:seg-defs> </trans-unit>

Smartcat
.xliff

<trans-unit> <source>Source text</source> <target state="needs-translation"></target> </trans-unit>
<trans-unit> <source>Source text</source> <target state="needs-review-translation" state-qualifier="leveraged-mt" >Translation</target> </trans-unit>

translate5
.xliff

<trans-unit <!-- translate="no" attribute NOT present --> > <source>Source text</source> <target state="needs-translation"></target> </trans-unit>
<trans-unit> <source>Source text</source> <target state="needs-review-translation" state-qualifier="leveraged-mt" translate5:origin="Globalese" >Translation</target> </trans-unit>

Wordbee
.xlf

<trans-unit> <source>Source text</source> <target /> </trans-unit>
<trans-unit> <source>Source text</source> <target state="needs-review-translation" state-qualifier="leveraged-mt" >Translation</target> </trans-unit>

XLIFF 1.2
.xliff or .xlf

See official specification here.

<trans-unit> <source>Source text</source> <target state="needs-translation"></target> </trans-unit>

or

<trans-unit> <source>Source text</source> <target state="new"></target> </trans-unit>

or

<trans-unit> <source>Source text</source> </trans-unit>
<trans-unit> <source>Source text</source> <target state="needs-review-translation" state-qualifier="leveraged-mt" >Translation</target> </trans-unit>

XTM
.xlf

<trans-unit translate="yes"> <source>Source text</source> <target></target> </trans-unit>
<trans-unit translate="yes"> <source>Source text</source> <target state-qualifier="mt-suggestion" >Translation</target> <alt-trans origin="Globalese"> <source>Source text</source> <target>Translation</target> </alt-trans> </trans-unit>

 

Related content