Use case - Machine translation

In case of machine translation, the process is as follows:

Step	Tool	Description
1	Across Language Server	A finished pre-translation process triggers a corresponding event.
2	crossAutomate	crossAutomate triggers all workflows which listen to the "pre-translation finished" event. For the MT systems integrated via crossConnect for External Editing, corresponding standard workflows exist. These workflows can be configured by the user (e. g. filters that define which tasks to process and which not). The crossAutomate workflow creates an External Editing Work Unit (EWU) for the configured MT system and puts the EWU file in the exchange folder FromAcross on the file system. EWU files are encrypted XLIFF files. Each vendor receives a vendor library from Across which allows to read/decrypt EWU files.
3	Across Trusted Integration Solution	The Trusted Integration Solution watches for new files in the exchange folder and triggers the integration process.
4		The Across Trusted Integration Solution uses the provided vendor library to read the plain XLIFF from the encrypted EWU file. For adding machine translations, the provided XLIFF files have to be parsed. A paragraph should be skipped by the machine translation in case: its state differs from the state Untouched (state-id="1") it has the attribute translate="no" it has the state-flag Keep Source (0x00000400) set For the paragraphs processed by the machine translation, the machine translated text should be inserted into the <target> tags. For machine translated segments, these across-specific attributes of <trans-unit> elements should be set (see Paragraph states and flags): state-name="Touched" state-id="2" state-flags: apply the Pretranslated External flag (0x01000000) Tip The Across Trusted Integration Solution must ensure that the decrypted XLIFF file can only be processed in the Trusted Integration Solution. Exports must not be possible.
5		When machine translated strings are added to the XLIFF file, the vendor library comes into play again. The changed XLIFF content is written via the security functions to a so-called External Editing Response Unit (ERU) and stored in the exchange folder ToAcross.
6	crossAutomate	crossAutomate watches for new files in the ToAcross folder and triggers the import process.
7	crossAutomate	The import process imports the data in Across.