- General Information
- Connecting Third-party Systems
- crossConnect for content systems
- crossConnect for External Editing
- Purpose and usage
- Requirements
- Implementation
- 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
- APIs
- APIs - Technology
- crossTank API v1
- crossTank API v2
- crossTerm API v1
- crossTerm API v2
- crossAPI SI
- Requirements
- Function Return Types
- crossAPI SI and Java
- List of Objects in crossAPI SI
- Sample - transferring checkout files via FileManager
- Sample - VBS
- Text Preprocessing API
Solution approaches
Trial and error
One typical approach is to do the translation completely without any information on length restrictions. The test is done on a real device after the translation is finished. This trial and error approach is inefficient and expensive because several adjustment loops are necessary till a final result is available.
Special tools
Companies with corresponding development capacities sometimes implement special solutions which simulate the device where display texts are shown. Based on this simulation, translations are done.
The advantage of such an approach is clear: The adjustments loops mentioned in the trial and error approach are prevented.
- But there are several disadvantages to consider:
- The special tools usually don't offer translation memory or terminology support.
- There is no workflow support for notifications, review steps, and integration of external suppliers.
- The special tool has to be installed and distributed to all translators.
- Such tools are often restricted to internal use, whereas most translators are external users.
Across display text solution
Across discussed with many customers how a perfect display text solution should look like. The result is a crossWeb-based solution. Display text documents are checked in to the server where also the corporate fonts are available. The server performs length checks and generates previews in real time. The translator is using a browser which receives information from the crossWeb server and displays the results.
- The advantages are:
- No distribution of tools or fonts is necessary. The translator only needs a browser.
- The translator has a complete translation environment with all features translators need.
- The quality checks and preview are integrated.
- No downstream check and adjustment loops.
- Full workflow support.
- Seamless integration of the linguistic supply chain.
- Support of Asian and right-to-left languages.