- Release Notes v7.0
- Getting Started
- System Management
- General Information
- Users
- Groups & User Crowds
- Softkeys
- Reports for User and Group Information
- User Settings Templates
- Workflows
- Relations
- Languages
- Fonts
- User settings
- System settings
- Editing States
- User Dictionary
- crossGrid
- crossGrid Packaging Templates
- crossTank
- crossWAN Packaging Templates
- Subjects
- Information
- Machine Translation
- Project Settings Templates
- Quality Management v6.3
- Quality Management v7.0
- Reporting
- Segmentation
- Language Settings
- Structure Attributes
- System Attributes
- Search Center
- Concordance Search Results
- Stopwords
- Term Extraction
- Document Settings
- Document Associations
- Display Text
- .NET Resources
- Excel 2000-2003
- Excel 2007-2016
- IDML
- MIF 7
- MIF 8-2019
- PowerPoint 2000-2003
- PowerPoint 2007-2016
- QuickSilver
- Tagged HTML
- Tagged SGML
- Tagged XML
- Tagged XML v2
- Visual XML
- Windows Resources
- Word 2000-2003
- Word 2007-2016
- XLIFF
- Regular expressions
- System attributes
- Project Management
- Projects
- Project View
- Project settings
- Functions of the Module
- Project Search
- Project creation
- Adding attachements
- Releasing Projects
- Document and Project Updates
- Project status
- Exporting projects
- Importing projects
- Activating/Deactivating Projects
- Duplicating Projects
- Archiving Projects
- Change workflow
- Changing Workflows (Several Documents)
- Documents
- Reports
- Tasks
- Quality management
- Formats
- The Project Archive
- crossGrid
- Project Management Cockpit
- The Filter Editor
- crossAnalytics
- Linguistic Supply Chain Management (LSCM)
- crossWAN Project Management
- Partitioning
- Relay Translations
- Document preparation
- Term Extraction and Term Translation
- External Editing of Documents
- The EN 15038 Standard Workflow
- The ISO 17100 Standard Workflow
- crossConnect for External Editing
- Finishing pre-translated tasks automatically
- Projects
- Task Processing
- Working in crossDesk
- Paragraph States
- Empty Paragraphs
- Modes
- Customizing crossDesk
- Tasks in Across
- Comments
- Bookmarks
- Paragraph Numbering
- Sorting Paragraphs
- Context View/Source View
- crossTerm Window in crossDesk
- crossView
- Fuzzy search
- Concordance search
- crossSearch
- Spell-check and User Dictionary
- Pre-translations
- Store Translations Wizard
- The Target Editor
- Preview
- QM Check in crossDesk
- Search and Replace
- Correction
- Reviews
- Redelegation to the Translator
- Quick Translate
- Local Data in the Offline Client
- crossWAN
- TM Management
- Terminology Management
- Concept-Oriented Terminology System
- Definitions
- The crossTerm Manager
- crossTerm settings
- crossTerm Manager User Interface
- Searching for Entries/Terms
- 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
- crossMining
- crossSearch
- Browser-based Work
- Editing of Special Formats
- Menus, Icons, and Keyboard Shortcuts
Document Settings Templates
Processing and Display Types
The following processing and display types are available in document settings templates:
Type | Description |
Normal (or no display mode selected) | The text is visible to the translator and can be edited, i.e. translated. |
Locked | The text is visible to the translator but cannot be edited. |
Hidden | The text is not visible to the translator but can be viewed by the project manager. |
Ignored | The text is not taken into consideration when the document is checked in, e.g. in order to relieve system resources. The text is not visible to the translator and cannot be viewed or subsequently made visible by the project manager. |
For character styles (in Word) or for internal elements (e.g. Tagged XML), the following processing and display modes can be selected (in addition to Normal):
Type | Description |
Read-only and placeables | The text is displayed in the form of a placeable, i.e. a gray field that cannot be edited. The translator must copy the placeables to the target text. |
Read-write (Word only) | The text is displayed in the form of green fields that can be edited. These are inserted in the translation as fields and can be edited. |
Example: Excel
Using document settings templates, you can define that in Excel documents, for example, individual cells or entire columns exclusively containing numbers not to be changed by the translator are to be locked or hidden in crossDesk entirely. In this way, you can minimize the translation volume and avoid errors, e.g. due to accidental editing of numbers. Moreover, these contents can also be "ignored". This means that these contents will not be taken into consideration during check-in. In this way, the check-in and processing times can be reduced considerably.
Example: Word
For example, in Word documents, you can define spans to be hidden on the basis of styles used in the document.
Due to the new document formats of Office 2007, 2010, 2013, and 2016 (Word, Excel, and PowerPoint), there are two different areas in the system settings, respectively, with different document settings templates.
By default, Word templates are already prefilled with some elements. The prefilling consists of the elements images, objects, and document settings, which determine how these Word elements are to be processed. By default, these three element categories are ignored. This means that during check-in to Across, they are not taken into consideration and are therefore not available in Across as information. This reduced use of resources has a positive effect on the work with Across, as the documents are leaner and can be processed and edited faster.
Example: XML
In Across, XML documents can be edited in two different ways: as Tagged XML or Visual XML. For these two different types, there are also two different sections in the system settings with different document settings templates for processing XML documents.
When translating XML files, the document settings templates are particularly important: Unlike HTML, the tags available for XML is not predetermined, but can be freely defined on the basis of certain rules. Therefore, for the translation of XML documents, it is important to determine how Across is to treat the various tags at check-in. In particular, be sure to define inline tags as such prior to check-in in order to ensure correct display and translation of the source document.
You can load the XML document to be translated via Load. The elements contained in the document will automatically be listed in the document settings template. Subsequently, you can select the elements one by one and configure them as needed by means of the Edit button.
Normally, you should not customize these templates, as they have been optimized for processing the respective formats in Across. If you still want to customize the templates, be sure to make a backup copy of the original template (using the Export button). Consult a competence partner before you customize the templates.
External and Internal XML Elements
External elements are located outside the body text, never within a text line. Usually, they cause a line break. Inline elements are located within the body text; for example, they may cause a certain word within a string to be displayed in bold type. Usually, elements always consist of a start tag (e.g. <i>) and an end tag (e.g. </i>).
Example: <p>This is <b>boldface</b>.</p>
<p> (p for paragraph) and is an external element. <b> stands for bold and is an inline element.