- Release Notes v7.0
- Installation and Administration
- About Across Translator Edition
- Installation of the Across Translator Edition
- Connection to Across Account
- Activation of the Across Translator Edition
- Functions of the Across Translator Edition
- Data Synchronization/Migration of the Across Translator Edition
- Backing up Data of the Translator Edition
- Restoring Translator Edition Backups
- Uninstalling the Across Translator Edition
- Getting Started
- Structure and Architecture
- Basic Decisions
- Logging in
- Change username/password
- Confirming and Opening Tasks
- Internal Communication
- System Management
- User settings
- System settings
- Quality Management v6.3
- Quality Management v7.0
- System Attributes
- Tagged HTML
- Tagged SGML
- Tagged XML
- Tagged XML v2
- Visual XML
- Word 2000-2003
- Word 2007-2016
- System attributes
- Project Management
- Adding a document
- Adding a target language
- Aligning Existing Translations
- Document Formats and Programs
- Locking and Hiding Text
- Redoing Document Versions
- Deleting a Document Version
- Machine Translation
- Document Settings Templates
- Checking out Documents
- Quality management
- The Filter Editor
- Relay Translations
- Document preparation
- Term Extraction and Term Translation
- External Editing of Documents
- The EN 15038 Standard Workflow
- The ISO 17100 Standard Workflow
- Cost Estimates
- Task Processing
- Working in crossDesk
- Paragraph States
- Empty Paragraphs
- Customizing crossDesk
- Tasks in Across
- Paragraph Numbering
- Sorting Paragraphs
- Context View/Source View
- crossTerm Window in crossDesk
- Fuzzy search
- Concordance search
- Spell-check and User Dictionary
- Store Translations Wizard
- The Target Editor
- QM Check in crossDesk
- Search and Replace
- Redelegation to the Translator
- Quick Translate
- Local Data in the Offline Client
- TM Management
- The crossTank Manager
- Adding Translations
- Editing Translations
- Changing the Status of Translations
- Merging Translations
- Deleting Translations
- Protecting Translations
- Searching for Translations
- Generating a crossTank Summary
- crossTank Import
- crossTank Export
- crossTank Maintenance
- Terminology Management
- Concept-Oriented Terminology System
- The crossTerm Manager
- crossTerm settings
- crossTerm Manager User Interface
- Searching for Entries/Terms
- Search Types
- Display of Search Suggestions
- Filters and Filter Sets
- Entry and term elements
- Editing Entries/Terms
- Delete Entries/Term(s)
- Merging Entries
- Duplicating Entries
- Manual correction
- crossTerm Reports
- crossTerm Import
- crossTerm Export
- crossTerm Data Maintenance
- crossTerm Web
- Browser-based Work
- Editing of Special Formats
- HTML Documents
- XML Documents
- SGML Documents
- FrameMaker Documents
- Word Documents
- TXT Documents
- Excel Documents
- PowerPoint documents
- InDesign and InCopy Documents
- QuickSilver documents
- PO Documents
- MC Documents
- XLIFF Documents
- Software Localization
- Localization of mobile apps
- Localizing Display Texts
- Menus, Icons, and Keyboard Shortcuts
Tagged ML Formats – Configuration
Using the Splitting Settings entry, you can select the splitting of paragraphs in crossDesk. In this way, the texts in crossDesk will be displayed sentence-wise, not paragraph-wise. In addition, you can determine that paragraphs with more than a certain number of characters are to be split. This might be useful with very long paragraphs.
Using the Preview entry, you can generate previews of ML files on the basis of the settings of the current document settings template. In this way, you can see how the differently defined contents of the file will be processed during check-in to Across and subsequently displayed in crossDesk.
Various colors can be selected to display the different contents.
To generate a preview, click Browse and select the respective XML file. Then click OK. The preview will be created and displayed in a preview window.
The Advanced entry enables you to configure additional settings.
First, you can determine how scripts contained in XML documents are to be handled. Normally, scripts are not translated. Nevertheless, the script may contain certain passages that need to be translated. Thus, you can enable the translation of all strings, L_ strings only, or no strings at all.
Usually, variable names with contents that need to be translated are marked with an L_ prefix.
Handling of META charsets
For tags for META charsets, i.e. meta information that determines the character encoding, you can determine that a missing <META> tag may be inserted, the value of the <META> tag may be modified, or the value may not be modified.
Target text encoding
If XML files are not encoded in UTF-8 or UTF-16, it may be necessary to change the encoding of the target documents in order to ensure correct display of all characters. For such cases, you can determine the encoding to be used for the target documents.
- You can determine:
- that the correct encoding is to be auto-detected by Across;
- that the encoding of the source document is to be used in the target document; or
- that a particular encoding is to be used (via a drop-down list).
Processing of undefined tags
For tags not defined in the respective document processing templates, you can define whether these undefined tags are to be treated as inline tags or as external tags.
Especially if the ML structure of the file to be translated is so dynamic that you do not always know in advance which external tags may occur, this setting can be very useful.
Furthermore, you can determine whether and which character entities are to be converted automatically. The entities are consolidated to sets. For a conversion to be performed, you must activate the respective checkbox. The contents of the corresponding set will be displayed in the lower window pane.
Click Add to create a new entity set. Subsequently, you can define new entities by clicking Add in the pane below or import an entity set as a file (in the *.ent format).
Treatment of white spaces
ML editors often insert special white spaces (e.g. soft line breaks and tabs) in the documents in order to present a more "plastic" structure, thereby improving the visual makeup of the documents. However, these white spaces are not relevant to the translation and merely generate unnecessary processing overhead. You can now determine that these special white spaces are to be kept or "normalized". The option Treat boundary space as parts of a paragraph allows you to keep white spaces at the beginning and end of paragraphs. On the other hand, the option Normalize white spaces allows you to convert both external and internal white spaces to normal spaces in the first step, i.e. to normalize them, and then to combine multiple spaces to a single space.
Treatment of invalid tags
In case the ML document contains invalid tags, the new option Treat invalid tags as text can be activated in order for these tags to be interpreted as plain text, thus enabling the ML document to be checked in and processed. For example, the invalid tags may be unmasked XML characters. In the following example, the < ("less than") is mistakenly not masked as <: <p>if x < 1 then write ('test')</p>
If the option Treat invalid tags as text is deactivated, a parsing error will occur when the respective document is checked in. In contrast, the document can be checked in if the option is activated.
Treatment of paragraphs without text
For paragraphs that do not contain any translatable text but only placeables or internal tags, a corresponding option can be activated to determine whether or not these paragraphs are to be extracted at check-in and thus displayed in crossDesk.
DTD Settings (XML only)
Using the DTD Settings entry, you can import document type definitions. In this way, the imported DTD will automatically be taken into consideration if the corresponding template is used during project creation and will be used for the XML files to be processed. The QM criterion for the validity check checks the target text based on the imported Master DTD for its validity.
Click the Load DTD button to import the desired DTD. Any dependencies referred to in the DTD will also be taken into consideration.
The imported DTD serves as master DTD. This means that this DTD will be used even if an XML file that is checked in to Across makes reference to another external DTD or contains another internal DTD.
If the master DTD is updated (by importing a new DTD in the document settings template), this new DTD will automatically be taken into consideration for XML files that have already been checked in. Thus, these XML files do not need to be checked in anew.
XSD Settings (XML Only)
Click XSD Settings to import XML schema definitions (XSD). In this way, the imported XSDs will automatically be taken into consideration when using the respective document settings template during project creation. Moreover, the QM criterion for the validity check will check the validity of the target text on the basis of the imported XSD.
In addition to XSD files, XML files in which the XML schema is integrated (XML MetaData; XMD) are also supported.
Click Add XSD to import the desired XSD. Click Add from XML to load an XML schema from an XML file.
The imported XSD serves as master XSD. This means that this XSD will be used even if an XML file that is checked in to Across makes reference to another external XSD or contains another internal XSD.
If the master XSD is updated (by importing a new XSD in the document settings template), this new XSD will automatically be taken into consideration for XML files that have already been checked in. Thus, these XML files do not need to be checked in anew.