Integration

There are three different ways how display texts can be integrated into the ALS:
Integration with crossTransform
Cold integration
Hot integration

Integration with crossTransform

If you would like your project managers to check in display text documents manually with the Across client, then you will find instructions in the crossTransform section of the SDK.

Cold integration

Cold integrations are services that watch a so-called "hot folder" and trigger actions such as project creation, check-in, etc. when a new file is added by a content management system to this hot folder.

crossConnect

With crossConnect, Across offers a standard solution for cold integrations. crossConnect can save a lot of efforts, but it is also limited by its standard functionality.

crossAPI SI

If the standard functionality of crossConnect is not sufficient for your cold integration, you can implement your own connector service and use crossAPI SI for the interaction with the Across Language Server.

Hot integration

In some cases, a deeper integration is wished in order to fulfill e. g. the following requirements:
No intermediate software/hot folder
Offer in the CMS (pre-translation results, progress information, intermediate results, ...)

For such requirements, a hot integration is necessary where the content management system makes use of crossAPI SI.

Document format GUIDs

Some integration approaches require a specification of the right document format GUID. For display texts, it is "26C0812C-5C2B-442E-911C-989340FFDA12"

Display text file extensions

The display text XML file extension is .dtxml.

The display text package extension is .dtx.