- General Information
- Connecting Third-party Systems
- crossConnect for content systems
- crossConnect for External Editing
- Purpose and usage
- Across XLIFF format
- Across-specific Extensions
- <xliff> Element Attributes
- <file> Element Extensions
- <trans-unit> Element Extension
- Paragraph States
- Paragraph State Flags
- <source> and <target> Element Content
- <bpt> Element Attributes
- <ph> Element Attributes
- <x> Element Attributes
- Across-specific Properties
- Analysis Results
- Sample Files
- Across XLIFF - import, export and segmentation
- Context information
- Exporting best matches in Across XLIFF
- Hyperlinks to XLIFF
- Secure file handling with C#
- Secure file handling with JAVA
- Workflow and vendor configuration
- Sample code - Integrated solution
- Across XLIFF format
- Generic File Connector
- Display Texts
- Solution approaches
- The Across solution in detail
- The display text format
- The display text package
- APIs - Technology
- crossTank API v1
- crossTank API v2
- crossTerm API v1
- crossTerm API v2
- crossAPI SI
- Function Return Types
- crossAPI SI and Java
- List of Objects in crossAPI SI
- ObjectManager - Overview
- ProjectManager - Overview
- WanGridManager - Overview
- Sample - transferring checkout files via FileManager
- Sample - VBS
- Text Preprocessing API
There are some controllers in the crossTerm ASP .Net Web API which are not strictly crossTerm-specific. In fact, they represent general objects used in the Across Language Server, which also comprise translation project management, user management, translation memory functions, etc.
It is planned to move these controllers to a different area of the Across Language Server API(s) in a later version.
- For this reason, the controllers are currently found in a special location within the crossTerm API, marked as "deprecated":
GET http://<API-base-URI>/deprecated/api/v1/Languages returns a list of all languages activated in the Across Language Server along with their LCIDs.
Note than only one language code per "main language" is returned, as opposed to all sub-language variants. So, for example, the list may include:
to represent that the main language English is activated in the server. The Lcid:1033 for US English is used in this case. The list will not contain all additional possible language codes for English, such as Lcid:2057 for British (UK) English.
This list is interesting because the language of a term in crossTerm must be one that is activated in the Across Language Server. So, the information could be used to design a language selection control.
System attributes are special data categories which can be used anywhere in the Across Language Server. They describe general properties such as subject (domain) or relation (typically department, customer, or similar entities), which are not specific to terminology (as opposed to linguistic entities such as part of speech or example sentence, for example).
Default system attributes and their identifiers
Some mandatory system attributes exist in every Across Language Server. These are:
Subjects (domains, typically "knowledge areas", such as Biology, Chemistry)
Relations (typically department, customer, or similar entities)
Users of the Across Language Server
Translation Projects that were/are processed by the Across Language Server
Across Language Servers may be connected into a grid by the crossGrid technology. Due to this, there can be default system attributes with different values (as defined by different server owners) known to one server. To differentiate between these system attributes and their values, the ServerId information should be evaluated. It is provided for each system attribute, as follows:
where 61faf985-... is some GUID that identifies the Across Server.
User defined system attributes
In addition to the default system attributes, user-defined system attributes may exist on each Across Server and in each server context (identified by its ServerId). Their names and Ids (GUIDs) cannot be predicted. These can be used, for example, to represent publication types, production sites, or anything that a company considers important for managing their translation projects.
System attribute values
This controller allows to retrieve, for example, a collection of all system attribute values. The information returned contains, among other things, the ID and the name (label) of the value as well as the ID of the system attribute that this value belongs to.
For example, the following shows that there is a value "Display Texts" (which is shown as the label or name of this value in crossTerm and in other areas of the Across Language Server), and that this value belongs to the system attribute with ID 3d7a90c2-7604-4d71-99ed-a44e813d8909. As we have seen above, this ID belongs to the default system atribute "Projects". So, "Display Texts" is the name of a project.