TMX Import and Server Context

The server context designates the data pool of a Master Server or Trusted Server. The server context ensures that data sets from two different Master Servers are not mixed on the Trusted Server side but always remain separated. TMX files contain information about the server context they originate from.

  • With respect to the server context, the import of a TMX file takes place according to the following rules:
  • If the TMX file contains a server context that exists on the side of the Across Language Server on which the TMX import is performed, the translation units will be imported to this server context.
  • If the TMX file contains a server context that does not exist on the side of the Across Language Server on which the TMX import is performed, the translation units will be imported to the current server context. Normally, the current server context is the local server context, i.e. the server context of the Across Language Server on which the TMX import is performed. If, however, a task of another server context is currently opened in crossDesk (e.g. a task delegated by a Master Server), this server context is the current server context.
  • If the TMX file does not contain any server context or if it contains translation units without any server context, these translation units will also be imported to the current server context.
Attention

In particular, TMX files do not contain any server context if the TMX file originates from a non-Across TM system.

Tip

The permission to import TMX files to a Master Server can be controlled via the crossGrid Server rights.