- 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
- Rights System: Default Settings
- System Management
- User settings
- System settings
- System attributes
- Project Management
- Quality management
- QM Criteria
- SGML, XML, and XLIFF (QM v6.3)
- Windows Resources (QM v6.3)
- .NET Resources (QM v6.3)
- Display Text (QM v6.3)
- QM Templates (v7.0)
- Date/Time/Numbers (QM v7.0)
- Display Text (QM v7.0)
- Formatting (QM v7.0)
- Spacing and Whitespaces (QM v7.0)
- Placeables (QM v7.0)
- Private Use Area Characters (QM v7.0)
- Spell-Check (QM v7.0)
- Punctuation (QM v7.0)
- Use of Terminology (QM v7.0)
- Use of TM (QM v7.0)
- Translation Consistency (QM v7.0)
- XML (QM v7.0)
- QM criterion for .NET resources (QM v7.0)
- QM criterion for Windows resources (QM v7.0)
- QM Criteria
- 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
- 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
Customizing and adding crossSearch resources
Before you customize an existing resource or create a new one, you should carry out a brief analysis to find out in which URLs it is possible to carry out a search (see example below).
A new resource can only be queried by crossSearch if the search query appears in the URL and can be transformed into a universally valid URL pattern rendering all possible search queries. (The URLs of some pages never change. In these cases, using this resource in crossSearch is not possible.)
Please note that the configuration and setting up of crossSearch resources requires basic knowledge of HTTP and HTML.
You can carry out the following settings for crossSearch resources:
General Settings Tab
The General Settings tab is used to configure general details and the URL syntax of the respective source.
The Name input field contains the name under which the resource appears, e.g. in crossDesk. Under Description you can enter additional information.
The URL pattern field contains the universally valid URL for each resource.
The URL has to be customized in order to use it in the different languages and search queries. For each separate search, Across replaces the inserted tags with the concrete values.
In IATE, the search query for "Search for translations for the word 'Schatz’ from German into English" is translated in the background into the following URL:
In the URL, the search word "Schatz", the source language "DE" and the target language "EN" are recognizable. These concrete values that are only valid for the search, have to be replaced by universally valid tags. For every single search with crossSearch, Across subsequently replaces these tags with the concrete values.
The universally valid URL pattern for IATE is:
The search word "Schatz" has been replaced by the tag <word>, the source language by <srclang> and the target language by <trglang>.
You can use the following tags to formulate the URL pattern:
The language of the page on which the query is supposed to take place
Name of a project (in particular for special search queries in Intranet resources)
If an Internet resource is, for any reason, temporarily not available or is unable to deliver a match for the search term, you can enter the text that in this case appears as a message (e.g. "Connection no longer available"). Across will not enter this Internet resource in the crossSearch results list.
Click Resources icon to select which icon should appear to signify that particular resource in the crossDesk results list. You can select whether it should be automatically found, whether the standard icon for that particular application should be used (e.g. for the Internet Explorer) or whether a user-defined icon should be used. For this, a corresponding URL address or a local path to a local icon (JPG, ICO, etc.) must be entered.
Language Settings Tab
The language settings for each resource are configured in the Language settings tab.
To begin with, the codepage (UTF-8 or language default) and the type of resource can be selected. Here you can select whether the resource is a bilingual resource (e.g. dictionaries) or a monolingual resource (e.g. a glossary).
The languages and corresponding codes to be used in search queries are entered in the Language coding section. The code used for the language in the search query has to be specified for each language consulted. The best method is to carry out test searches outside of Across to ascertain the codes for the various languages. Click Add, select the language and, if necessary, a country and enter the code for each language. Click OK to save these settings.
Hit List Settings Tab
You can use the Hit List Settings tab to configure which section of the page should be displayed in crossDesk.
The following options are available:
Hit list only (without page text)
In this case, only the link is displayed that must be clicked in order to see the result of the search.
Hit list with complete page text
The entire page with the results of the search query will be displayed in crossSearch. This option should only be selected for pages with a very simple structure and limited size.
Only show the text between the first occurrence of ... and the first occurrence of ...
Only the text will be shown that is located between the two defined tags. (You have to look at the source code of the results display of each resource in order to make the settings.)
Page Language Tab
The Page Language tab is used to define the language in which the page with the hit display should be shown.
For each language the respective code has to be entered, with which the page language is translated into the search query. The best method is to carry out test searches outside of Across to ascertain the codes for the various languages. Click Add, select the language and, if necessary, a country and enter the code for each language. Click OK to save these settings.