Salesforce

WorldServer - how does the Language Weaver Cloud Machine Translation Adapter send content to Language Weaver Cloud?

« Go Back

Information

 
TitleWorldServer - how does the Language Weaver Cloud Machine Translation Adapter send content to Language Weaver Cloud?
URL Name000009534
SummaryWhen a Task/asset is sent to Language Weaver Cloud for Machine Translation - either through the Segment Asset step with option "Leverage Assigned MT: Yes" or through Apply Machine Translation, XLF files are created under the Tomcat Temp folder. This article explains more details.
Scope/EnvironmentWorldServer
Language Weaver
Question
What happens when a Task goes through Language Weaver Cloud for Machine Translation in WorldServer? How is the content sent to Language Weaver Cloud?
Answer

When a Task/asset is sent to Language Weaver Cloud for Machine Translation - either through the Segment Asset step with option "Leverage Assigned MT: Yes" or through Apply Machine Translation, XLF files are created under the Tomcat Temp folder, typically under this directory:

WS 11.6 and below: W:\WorldServer\tomcat\temp

WorldServer 11.7.0 and above: W:\WorldServer\temp

Note: the directory where the XLF are stored is hard coded and cannot be changed.

Two XLF files are created for each task/file that is processed by Language Weaver at Segment Asset or Apply Machine Translation:

xliff_run4048896661783689338.xlf :containing the source text only
target_xliff_run531607775633805076.xlf: containing the source and target

Note: in WS 11.7.3 and above, the xliff_run file is only temporary and is deleted when the target_xliff file is created

The digits in the file name are random and will vary.

Such an XLF file contains the segments to be pretranslated by Language Weaver Cloud for Machine Translation, along with segment ID (<trans-unit id="0"). This is how such an XLF file (source) could look like:

<?xml version="1.0" encoding="UTF-8"?>

<xliff encoding="UTF-8" version="1.1" xmlns="urn:oasis:names:tc:xliff:document:1.1">
<file datatype="text/xml" original="request.xml" source-language="en" target-language="de">
<body>
<trans-unit id="0">
<source>This is a house</source>
<target/>
</trans-unit>
<trans-unit id="1">
<source>This is a house</source>
<target/>
</trans-unit>
<trans-unit id="2">
<source>A cat in the tree</source>
<target/>
</trans-unit>
<trans-unit id="3">
<source>Lucy in the sky with diamonds</source>
<target/>
</trans-unit>
<trans-unit id="4">
<source>Lucy in the sky with pearls</source>
<target/>
</trans-unit>
<trans-unit id="5">
<source>repetition1</source>
<target/>
</trans-unit>
<trans-unit id="6">
<source>repetition1</source>
<target/>
</trans-unit>
<trans-unit id="7">
<source>another repetition</source>
<target/>
</trans-unit>
<trans-unit id="8">
<source>another repetition</source>
<target/>
</trans-unit>
<trans-unit id="9">
<source>a new word</source>
<target/>
</trans-unit>
  </body>
 </file>
</xliff>

The target XLF file will look the same while replacing the source text with the translated text from Language Weaver Cloud for Machine Translation.

Similar XLF files are created each time you test the functionality of the Language Weaver Cloud for Machine Translation Adapter by entering text in the source language and click Translate from

WS 11.6 and below: Tools > Machine Translations > Machine Translation Tool: SDL BeGlobal 4 Adapter, select MT Provider configuration in the dropdown.
WS 11.7.x and above: Tools > Machine Translations > Machine Translation Tool: Language Weaver Cloud, select MT Provider configuration in the dropdown.

**BeGlobal 4 was rebranded as Language Weaver Cloud and Language Weaver.
 
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by