Transit/TermStar NXT

Transit/TermStar NXT Reference Guide 2015-01

Valid from Service Pack 8 Version 2015-01. This document is valid as of Transit NXT Service Pack 8. Transit is being continuously further developed. You can find current Service Packs, installation instructions, user documentation and accessories on our website in the following area: "Downloads Transit & TermStar NXT" Contact STAR Group Headquarters: STAR AG Wiesholz 35 8262 Ramsen Switzerland www.star-group.net info@star-group.net Telephone +41 (0) 52 742 92 00 Fax +41 52 742 92 92 STAR Language Technology & Solutions GmbH Umberto-Nobile-Str. 19 71063 Sindelfingen Germany You can find your local STAR subsidiary on our website under "STAR Group worldwide". Copyright, liability and trademarks 2015 STAR AG. All rights reserved. All wording and images contained in this document are protected by copyright and may only in whole or in part be reproduced, processed, passed on to third parties or published with written permission from STAR AG. If you would like to use the content of this document, please contact info@star-group.net. The content of this document has been carefully checked. STAR AG cannot be held liable for any consequences arising from the use of this documentation. The trademarks used within this document are the property of their respective rights holders.

Contents Contents 1 Using startup parameters for Transit/ TermStar NXT 1.1 -DialogLanguage (Set up dialog language)... 9 1.2 -U (Start with a specific user)... 10 1.3 -H (Start with a specific user role)... 10 1.4 -P (Open project)... 11 1.5 -O (Open the language pairs of the open project)... 13 2 Exchanging reference material via TMX 2.1 Overview... 14 2.2 Exporting language pairs to TMX file... 15 2.2.1 Exporting files to a TMX file... 15 2.2.2 Exporting the current project to a TMX file... 17 2.3 Importing TMX files in Transit NXT... 18 2.3.1 Naming and saving of language pairs... 18 2.3.2 Performing a TMX import... 20 2.3.3 Using segments from TMX import as reference material... 21 2.4 Compatibility of the language and country codes of TMX files... 22 2.4.1 Overview... 22 2.4.2 Differences in the usage of language and country codes... 22 2.4.3 Importing TMX files from Transit into Trados... 23 2.4.4 Importing TMX files from Trados into Transit... 24 3 Managing roles 3.1 Overview... 25 3.2 Opening a role... 25 3.3 Creating a new role... 28 3.3.1 Creating completely new roles... 28 3.3.2 Editing an existing role... 29 3.3.3 Allocating passwords to user roles... 30 Transit/TermStar NXT Reference Guide 3

Contents 3.4 Overview of standard roles... 32 3.4.1 Overview... 32 3.4.2 Ribbon bar, general functions... 33 3.4.3 Ribbon bar, Transit-specific functions... 35 3.4.4 Ribbon bar, TermStar-specific functions... 38 3.4.5 Transit/TermStar button... 39 3.4.6 Resource bar... 40 4 Customising Transit/TermStar NXT 4.1 Overview... 43 4.2 Automating tasks using macros... 43 4.2.1 Overview... 43 4.2.2 Tips for creating macros... 44 4.2.3 Recording a new macro... 45 4.2.4 Running the macro... 46 4.2.5 Editing the macro... 47 4.2.6 Example macro: Inserting Unicode characters... 49 4.3 Customising the system environment... 51 4.3.1 Overview... 51 4.3.2 Multithreading for multilingual projects... 51 4.3.3 Restricting a background search with shared dictionaries... 53 4.3.4 Updating common dictionaries... 54 4.3.5 Specifying dialogue box fonts... 55 4.4 Spellchecking: list of unknown words... 56 4.4.1 Opening and editing the list of unknown words... 57 4.5 Customising index buttons for TermStar NXT... 58 4.5.1 Overview... 58 4.5.2 Configuration file for index buttons... 58 4.5.3 Changing index buttons... 58 4.6 Checking and changing abbreviation list... 59 5 Print definition set-up 5.1 Overview... 61 5.2 Opening a print definition... 61 5.2.1 Saving the print definition... 62 5.2.2 Setting page margins... 64 5.2.3 Defining separators for dictionaries... 65 5.2.4 Specifying headers and footers... 68 5.2.5 Specifying the page layout... 71 4 Transit/TermStar NXT Reference Guide

Contents 6 Customising projects 6.1 Overview... 73 6.2 Compressing files with formatting information (cod files)... 74 6.3 Excluding hidden or locked text from translation in Excel... 74 6.4 Optimising the pretranslation time... 76 6.4.1 Overview... 76 6.4.2 The MaxPreTransHits parameter... 76 6.4.3 Customising the MaxPreTransHits parameter... 77 7 Fields in the TermStar dictionary 7.1 Overview... 78 7.2 Field types... 78 7.2.1 Header fields... 79 7.2.2 Language fields... 81 7.2.3 Entry fields and subentry fields... 82 7.2.4 Subentry types... 85 8 Customising layouts 8.1 Overview... 86 8.2 Managing layouts... 86 8.2.1 Overview... 86 8.2.2 Creating a new layout... 87 8.2.3 Opening existing layouts... 87 8.2.4 Saving the layout and closing the layout editor... 89 8.3 Working with the layout editor... 91 8.3.1 Areas of a layout... 91 8.3.2 Layout editor interface... 92 8.3.3 Available Fields... 93 8.3.4 Structure of the language units... 94 8.4 Editing the layout... 96 8.4.1 Selecting and removing fields for the layout... 96 8.4.2 Inserting and deleting static text unit... 97 8.4.3 Specifying the order of fields... 98 8.5 Specifying field properties... 99 8.5.1 Overview... 99 8.5.2 Formatting units... 100 8.5.3 Formatting entries and subentries... 101 8.5.4 Formatting the fields... 103 8.5.5 Entering and formatting static text units... 104 8.5.6 Variables... 105 Transit/TermStar NXT Reference Guide 5

Contents 8.5.7 Formatting automatic cross-references... 105 8.5.8 General layout settings... 108 9 Customising dictionaries 9.1 Overview... 111 9.2 Modifying field names... 111 9.2.1 Overview... 111 9.2.2 Changing field names for all languages... 112 9.2.3 Changing field names for specific languages... 113 9.2.4 Resetting changed field names... 114 9.2.5 Transferring field names from other dictionaries... 115 9.3 Setting graphics file access... 116 9.4 Specifying cross-reference separators... 117 9.5 Specify additional sort field... 118 10 Spellcheck dictionaries 10.1 Installing a spellcheck dictionary... 125 10.1.1 Uninstalling spellcheck dictionaries... 126 11 Managing database links 11.1 Overview... 127 11.2 Creating a database link... 127 11.2.1 Overview... 127 11.2.2 Connecting an MS Access database... 128 11.2.3 Connecting an MS SQL database... 133 11.3 Deleting a database link... 137 11.4 Transferring database connections to other computers... 138 11.5 Deleting incorrect database links... 141 11.6 Compressing databases and dictionaries... 142 11.7 Database driver information... 142 6 Transit/TermStar NXT Reference Guide

Contents 12 Compacting Microsoft Access database or transferring it to SQL server 12.1 Overview... 144 12.2 Transferring TermStar databases from Microsoft Access to an SQL server... 148 12.2.1 Renaming an ODBC connection in Windows... 149 12.2.2 Creating a database in Transit/TermStar NXT... 151 12.2.3 Transferring a database from Access to an SQL server... 155 13 Regular expressions 13.1 Overview... 159 13.1.1 What are regular expressions?... 159 13.1.2 Basic settings for searches in Transit NXT... 159 13.1.3 What can you use regular expressions for?... 160 13.2 Defining regular expressions... 161 13.3 Control characters... 162 13.4 Overview of meta characters... 163 13.5 Wildcards:. [ ] &... 164 13.5.1 Wildcard for any single character:. (dot)...164 13.5.2 Wildcard for any of a specified group or class: square brackets ([])... 165 13.5.3 Wildcard for any sequence of characters: ampersand (&)... 167 13.6 Quantifiers: +*?... 169 13.7 Escapement: \... 172 13.8 Applying meta characters to character strings: ( )... 174 13.9 Placement: ^ $... 176 13.10 Negation:!... 178 13.10.1 Negation of a character or character string... 179 13.10.2 Negation of a character group... 180 13.10.3 Negation of beginning/end of line... 181 13.11 Alternatives:... 183 13.11.1 What does Transit NXT interpret as an alternative?... 183 13.11.2 Alternatives and character groups/classes... 184 13.11.3 Alternatives and negated character strings... 185 13.12 Variables: #... 186 13.12.1 Why use variables?... 186 13.12.2 How are variables used?... 187 13.12.3 Changing the case when replacing... 189 13.12.4 Changing number formats when replacing... 190 13.12.5 Performing mathematical calculations when replacing... 191 Transit/TermStar NXT Reference Guide 7

Contents 13.12.6 Rounding figures when replacing... 193 13.13 Invalid regular expressions... 195 13.13.1 Ambiguous regular expressions... 195 13.13.2 Syntax errors... 195 13.14 Appendix overview of meta and control characters... 197 14 Keyboard shortcuts 14.1 Overview... 200 14.2 Keyboard shortcuts for Transit NXT... 200 14.2.1 General functions... 200 14.2.2 Moving between windows... 201 14.2.3 Translating in the Transit editor... 201 14.2.4 Working with terminology... 202 14.2.5 Moving the cursor... 203 14.2.6 Formatting text manually... 204 14.2.7 Selecting and editing text blocks... 204 14.2.8 Searching for notes... 205 14.3 Keyboard shortcuts for TermStar NXT... 206 14.3.1 General functions... 206 14.3.2 Navigating within a dictionary... 206 14.3.3 Editing data records... 207 14.3.4 Edit mode... 207 14.4 Keyboard shortcuts for Alignment... 208 15 Codes and extensions 15.1 Files in Transit/TermStar NXT... 209 15.2 3-letter language code... 212 15.3 Microsoft language code... 227 8 Transit/TermStar NXT Reference Guide

1 Using startup parameters for Transit/TermStar NXT 1 Latest manuals on our website The latest version of this manual and other documentation is available from the Downloads Transit & TermStar NXT User Documentation section on our website www.star-group.net. 1 Using startup parameters for Transit/TermStar NXT As an experienced user, you can use startup parameters so that Transit/TermStar will automatically start with a specific Transit user and/or automatically use a specific standard user role or open a specific project and/or a specified language pair on startup. In doing so, you use a desktop shortcut, the command prompt or a batch file for starting Transit/TermStar NXT and defining the startup parameters. The following startup parameters, which you can combine in any way, are available: 1.1 -DialogLanguage (Set up dialog language) This parameter starts Transit/TermStar NXT with a specific dialog language. Without this parameter, Transit/TermStar NXT starts with the dialog language that has been used when Transit/TermStar NXT was last called. Syntax of the startup parameter Attribute Sample call DialogLanguage=[<LanguageCode>] Attribute <LanguageCode> (optional): 3-letter language code of the dialog language. Possible values: Section 15.2 "3-letter language code" on page 212 -DialogLanguage=ENG Transit/TermStar NXT starts with English (UK) as dialog language. Transit/TermStar NXT Reference Guide 9

1 Using startup parameters for Transit/TermStar NXT 1.2 -U (Start with a specific user) This parameter starts Transit/TermStar NXT automatically with a specific user. Without this parameter, Transit/TermStar NXT starts with the user whose short name matches the Windows logon name. Transit/TermStar NXT uses the user for the following functions among others: Selection of the folder in which Transit/TermStar NXT saves settings for the User scope Identification of the author of changes to the dictionary Identification of the author of changes to segments Syntax of the startup parameter Attribute Sample call -U[<UserShortName>] Attribute <UserShortName> (optional): Short name of user with which Transit/TermStar NXT is to start. Please note that this is not the full name that is used as the folder name and displayed in Transit/ TermStar NXT. The attribute value ignores case. In other words, the parameter does not distinguish between user names that differ only in terms of use of lower/upper case. Default: Without specifying an attribute, Transit/ TermStar NXT displays the Select user window containing a list of the existing users and waits for input from the user (not suitable for automatic startup). "d:\transit_nxt\bin\transitnxt.exe" -Ucon Transit/TermStar NXT starts with the user with the short name con. 1.3 -H (Start with a specific user role) This parameter starts Transit/TermStar NXT automatically with a specific user role. Without this parameter, Transit/TermStar either starts with the user role last selected or with the Select user role window if the option Don't ask again at startup has not been selected in this window (not suitable for automatic startup). 10 Transit/TermStar NXT Reference Guide

1.4 -P (Open project) 1 This parameter does not alter the user role saved, i.e. the next time the program is started without the parameter, Transit/TermStar NXT again uses the user role last selected in the Select user role window. Syntax of the startup parameter Attribute -H[<n>] Attribute <n> (optional): User role with which Transit/TermStar NXT should start. Possible values: 1 Project Manager user role (Transit only) 2 Project Calculation Manager user role (Transit only) 3 Translator user role (Transit only) 4 Reviewer user role (Transit only) 5 Markup Specialist user role (Transit only) 6 Reference Material Manager user role (Transit only) 7 Alignment Specialist user role (Transit only) 8 Terminology Manager user role (Transit/ TermStar) 9 Terminologist user role (Transit/TermStar) 10 Terminology Translator user role (Transit/TermStar) 11 Localisation Specialist user role (Transit only) 12 Super User user role (Transit/TermStar) Sample calls "d:\transit_nxt\bin\transitnxt.exe" -H4 Transit NXT starts with the Reviewer user role. "d:\transit_nxt\bin\transitnxt.exe" -H12 Transit NXT starts with the Super User user role. 1.4 -P (Open project) This parameter automatically opens a project and thus prevents displaying the Open project window, which requires interactive user input. Syntax of the startup parameter -P[<ProjectName>] Transit/TermStar NXT Reference Guide 11

1 Using startup parameters for Transit/TermStar NXT Attribute Attribute <ProjectName> (optional): Path and name of the project that Transit/TermStar NXT should open. The attribute value ignores case. In other words, the parameter does not distinguish between project names that differ only in terms of use of lower/upper case. Default: The project last opened by the current user. Please note that Transit/TermStar NXT saves the project last opened separately for each user. This is particularly significant if you start Transit/TermStar NXT with different users (parameter -U, see page 10). Sample calls "d:\transit_nxt\bin\transitnxt.exe" - P"d:\Transit_NXT\config\global\Nxt_Word.PRJ" Transit/TermStar NXT opens the project NXT_Word. "d:\transit_nxt\bin\transitnxt.exe" -P Transit/TermStar NXT opens the project last opened by the current user. "d:\transit_nxt\bin\transitnxt.exe" - P"d:\Transit_NXT\config\customers\Terminus \Brochure.PRJ" Transit/TermStar NXT opens the project Brochure which is stored in the scope Customer for the customer with the short name Terminus. 12 Transit/TermStar NXT Reference Guide

1.5 -O (Open the language pairs of the open project) 1 1.5 -O (Open the language pairs of the open project) This parameter opens language pairs in the currently open project without interactive input from the user. Transit NXT opens the language pair or language pairs for the source and current target language specified in the project settings. Condition Project must have been opened (parameter -P) Syntax of the startup parameter Attribute -O[<n>] Attribute <n> (optional): Language pairs to be opened Possible values: no value The last language pair opened by the current user in the current project. * All language pairs in the project (except translation extract). Sample calls "d:\transit_nxt\bin\transitnxt.exe" - P"d:\Transit_NXT\config\global\Nxt_Word.PRJ" -O Transit NXT opens the language pair last opened by the current user in the current project. "d:\transit_nxt\bin\transitnxt.exe" - P"d:\Transit_NXT\config\global\Nxt_Word.PRJ" -O* Transit NXT opens all language pairs in the current project in a single window (globally). Sample call combining all startup parameters: "d:\transit_nxt\bin\transitnxt.exe" -Ucon -H12 - P"d:\Transit_NXT\config\global\Brochure.PRJ" -O* Transit/TermStar NXT automatically starts with the user with the short name con using the Super User user role, opening the project Brochure which is stored in the scope Global and opening all language pairs in this project in a single window (globally). Transit/TermStar NXT Reference Guide 13

2 Exchanging reference material via TMX 2 Exchanging reference material via TMX 2.1 Overview TMX (Translation Memory exchange) is a data format based on XML for exchanging data between different translation memory systems. You have the following options for exchanging reference material via TMX: Exporting Transit language pairs into a TMX file, importing this file into another translation memory systems and using it there as reference material For instructions on this refer to section 2.2 Exporting language pairs to TMX file on page 15. Importing TMX files into Transit, creating language pairs from them and using them as reference material For instructions on this refer to section 2.3 Importing TMX files in Transit NXT on page 18. Compatibility of the language and country codes of TMX files To identify a language Transit NXT uses a combination of language and country codes in accordance with the TMX standard. A code of this type consists of a 4-digit combination of language and country codes. Transit NXT essentially uses the codes in accordance with the ISO 639-1 and ISO 3166 standards. There can be differences between the identifiers for certain languages (Afrikaans, Basque, Catalan, Farsi, Hebrew and Serbian) if exchanging with programs which only partly follow this standard. Please refer to section 2.4 Compatibility of the language and country codes of TMX files on page 22 for detailed information. TMX versions supported by Transit NXT Transit NXT uses TMX version 1.4 for the TMX export. For imports of TMX files, Transit NXT supports TMX versions 1.1 to 1.4. 14 Transit/TermStar NXT Reference Guide

2.2 Exporting language pairs to TMX file 2 2.2 Exporting language pairs to TMX file Transit offers the following options for exporting language pairs to a TMX file: Exporting files to a TMX file on page 15 Exporting the current project to a TMX file on page 17 2.2.1 Exporting files to a TMX file Using the following function you can export any number of projects, reference folders, reference files and languages to the TMX format. How do I export files to a TMX file? 1 Select Reference material TMX interface Export TMX from the resource bar. Transit NXT displays the Create TMX file window: Fig. 2-1: Create TMX file window Transit/TermStar NXT Reference Guide 15

2 Exchanging reference material via TMX 2 Specify which files you want to export into the TMX format. Select Add project to export the files of a project. Select Add folder to export the files of a folder. Select Add files to export individual files. Click on Remove reference to undo your selection. 3 In the Export languages section, select the languages which you want to export to TMX format. If you selected several target languages for the project in the project settings, you can select one, several or all languages. Languages which you are not exporting now can be exported at a later stage. Activate Select all if you want to export the files for all languages. Transit NXT selects all languages. 4 Specify the TMX file to which the data should be exported. Click on the button to the right of the TMX file field. Transit NXT displays the Create TMX file window. Enter a file name in the File name field and the file name extension.tmx for the file to which the data are to be exported. Click Save to confirm the information specified. Transit NXT exports the files of the selected languages to a single TMX file. 5 Specify the following options, if required. Via the Also export protected segments option you can specify if segments that consist exclusively of markup information are exported in addition to the text segments. Selecting this option is necessary only if you want Transit NXT to correctly export the files at a later point in time (not necessary for exchanging reference material). NOTE: This option works only if you have also selected the Also export unaltered segments option. Via the Also export unaltered segments option you can specify if segments with an identical content (including markups) in source and target language are exported (selected by default). Via the Minimum segment status option you can specify that only segments with the selected minimum status are to be exported. Under File format you can specify how the TMX file is to be encoded (UTF-8 or UTF-16). 6 Create the TMX files by clicking Start. 7 Transit NXT displays the Export progress window during the export. Once Transit NXT has completed the export, it displays the following message in the Export progress window: Completed successfully. Transit has saved the TMX file to the folder you selected. 8 Click OK to close the Export progress window. 16 Transit/TermStar NXT Reference Guide

2.2 Exporting language pairs to TMX file 2 Transit NXT now displays the TMX export window again in the foreground. If you want to carry out another export, you can change the settings accordingly and carry out another export. If you do not want to carry out another export, simply click on Close. 2.2.2 Exporting the current project to a TMX file Using the following function you can export the language pairs of the currently opened project to an TMX file. Transit automatically uses basic settings of the current project: Data to be exported: All language pairs of the current project Source language: Source language of the current project Export languages: Source language and all target languages of the current project This function is a simplified alternative to the more complex function for the TMX export with which you can export any number of projects, reference folders, reference files and languages (see section Exporting files to a TMX file on page 15). How do I export a project to a TMX file? 1 Select Reference material TMX interface Export current project as TMX from the resource bar. Transit NXT displays the Create TMX file window: Fig. 2-2: Create TMX file window 2 Specify the TMX file to which the data should be exported. Click on the button to the right of the TMX file field. Transit NXT displays the Create TMX file window. Navigate to the desired folder and enter a file name in the File name field and the file name extension.tmx. Click Save to confirm the information specified. Transit/TermStar NXT Reference Guide 17

2 Exchanging reference material via TMX 3 Specify the following options, if required. Via the Also export protected segments option you can specify if segments that consist exclusively of markup information are exported in addition to the text segments. Selecting this option is necessary only if you want Transit NXT to correctly export the files at a later point in time (not necessary for exchanging reference material). NOTE: This option works only if you have also selected the Also export unaltered segments option. Via the Also export unaltered segments option you can specify if segments with an identical content (including markups) in source and target language are exported (selected by default). Via the Minimum segment status option you can specify that only segments with the selected minimum status are to be exported. Under File format you can specify how the TMX file is to be encoded (UTF-8 or UTF-16). 4 Create the TMX files by clicking Start. 5 Transit NXT displays the Export progress window during the export. Once Transit NXT has completed the export, it displays the following message in the Export progress window: Completed successfully. Transit has saved the TMX file to the folder you selected. 6 Click OK to close the Export progress window. 2.3 Importing TMX files in Transit NXT 2.3.1 Naming and saving of language pairs If you import TMX files to Transit, Transit generates language files. How Transit names the language files generated depends on the following factors: Were the TMX files generated by Transit or another Translation Memory System? In TMX files from Transit NXT, the file names of the original language pairs are saved in the TMX files which means that Transit NXT can restore the file name during import. For this reason, you do not have to specify files names for TMX files from Transit NXT. Transit may therefore generate several language pairs if your TMX material was generated from several reference files. You can therefore work as usual with single files and select them individually as reference material. 18 Transit/TermStar NXT Reference Guide

2.3 Importing TMX files in Transit NXT 2 In the TMX files from other Translation Memory Systems (e.g. Trados), no file names are saved. When you are working with such TMX files, you always need to specify the file name for the file to be created. Since a TMX file from other Translation Memory Systems does not contain any information on the origin of the references, a single language pair is generated from it which contains the entire data. In this respect, please note that other Translation Memory Systems use unusual language and country codes for some languages (see section 2.4 Compatibility of the language and country codes of TMX files on page 22.) Should Transit create the language files in the working folder of the current project, or in another location? If Transit NXT is not to create the language files in the working folder of the current project, please specify another folder for the files. In this case, it is necessary to specify a file name - even if the TMX file was originally created from Transit language pairs. When you select a different folder, Windows requires a file name to be entered. However, on creating the language pairs Transit NXT uses the names of the original language pairs and not the name you have entered. Specifying file name extension.txt for the language pairs to be created In the case of TMX files created from other translation memory systems, you have to specify a name for the language files to be created. In these cases, use.txt as the file name extension. During the TMX import, Transit NXT then creates language files with the file names you specified and the file name extension corresponding to the 3-letter language code. Example: For the import of an English-Swedish TMX file, you specify the file name manual_scan.txt. Transit NXT then creates the language files manual_scan.eng and manual_scan.sve. Transit/TermStar NXT Reference Guide 19

2 Exchanging reference material via TMX 2.3.2 Performing a TMX import How do I import TMX files into Transit NXT? 1 Select Reference material TMX interface Import TMX from the resource bar. Transit NXT displays the TMX import window: Fig. 2-3: TMX import window 2 Click. to the right of the TMX import file field to select the TMX file you want to import. Transit NXT displays the Open TMX file window. 3 Select the TMX file you wish to import. Confirm your choice by clicking Open. 4 Specify the file names and folder for the language files which Transit NXT should generate from the TMX file. How you specify this depends on the following factors: Were the TMX files generated by Transit NXT or another Translation Memory System? Should Transit NXT create the language files in the working folder of the currently opened project, or in another location? Importing a TMX file created by Transit in the current working folder: You do not have to specify file name for a TMX file that was originally created from Transit language files. Importing a TMX file created by Transit in another folder: Click on right from the field Resulting language pair. Transit NXT displays the Create language pairs from TMX file window. Select the desired folder in the Create language pairs from TMX file window. Enter any file name in the File name field and the file name extension.txt. During import, Transit NXT saves the language pairs under their original file names. Click Save to confirm the information specified. 20 Transit/TermStar NXT Reference Guide

2.3 Importing TMX files in Transit NXT 2 Importing a TMX file created by another translation memory system into the current working folder: Enter the file name for the language pair to be created in the Resulting language pair field of the TMX import window. Use the file name extension.txt. During the import, Transit NXT creates a language pair with the name you have entered. If the file size exceeds 15,000 segments, Transit NXT creates another language pair. Importing a TMX file created by another translation memory system into another folder: To the right of the Resulting language pair field, click on. Transit NXT displays the Create language pairs from TMX file window. Select the desired folder in the Create language pairs from TMX file window. Enter the file name for the language pair to be created in the Files names field. Use the file name extension.txt. During the import, Transit NXT creates a language pair with the name you have entered. Click Save to confirm the information specified. 5 Once you have checked the options and made any necessary changes, start the import by clicking Start import. Transit imports the selected TMX file and generates the language files from it. Transit NXT displays the Import progress window during the import. Once Transit NXT has completed the import, it displays the following message in the Import progress window: Completed successfully. Transit NXT has imported the TMX files and saved them to the language files in the folder you selected. 6 Click OK to close the Import progress window. Transit NXT now displays the TMX Import window again in the foreground. If you want to carry out another import, you can change the options accordingly and carry out another import. If you do not want to carry out another import, simply click on Close. 2.3.3 Using segments from TMX import as reference material TMX files do not contain any information about the status of the segments they contain. During the TMX import, Transit NXT automatically assigns the segment status Translated to the source and target languages of the language pairs created. Under certain circumstances, it might still be required to check the newly created language pairs and to assign them a different segment status before they are used in translation projects as reference material. You can do so either by checking each segment and assigning it a status individually or by changing the status globally for the entire language file. Please refer to section 6.8 Proofreading mode of the Transit NXT User's Guide for more detailed information. Transit/TermStar NXT Reference Guide 21

2 Exchanging reference material via TMX 2.4 Compatibility of the language and country codes of TMX files 2.4.1 Overview To identify a language Transit NXT uses a combination of language and country codes in accordance with the TMX standard. A code of this type consists of a 4-digit combination of language and country codes. Transit NXT essentially uses the codes in accordance with the ISO 639-1 and ISO 3166 standards. Example: zh-cn In compliance with ISO 639-1, zh is the language code for Chinese; In compliance with ISO 3166, CN is the country code for China. The 4-digit code thus designates the language Chinese for the People's Republic of China. 2.4.2 Differences in the usage of language and country codes If you compare the standard for the import and export of TMX files in Transit with that of SDL/Trados, you will determine certain differences with regard to the language codes (Table 2-1 on page 22) or country codes (Table 2-2 on page 23) that are used. These differences are listed below. Language Language code according to ISO 639-1 Language code used in Transit NXT Language code used in SDL Trados Afrikaans af af af Basque eu eu eu Catalan ca ca ca Persian fa fa fa Hebrew (Israel) he iw iw Norwegian (Nynorsk) Norwegian (Bokmål) nn no no nb no no Serbian sr sr sh Tab. 2-1: Language codes according to ISO 639-1 in Transit NXT and in SDL Trados 22 Transit/TermStar NXT Reference Guide

2.4 Compatibility of the language and country codes of TMX files 2 Country Country code according to ISO 3166 Country code used in Transit NXT Country code used in SDL Trados Afrikaans - - 01 Basque - - 01 Catalan - - 01 Persian - - 01 Hebrew (Israel) il il 01 Norwegian (Nynorsk) no ny ny Serbian yu yu yu Tab. 2-2: Language codes according to ISO 3166 in Transit NXT and in SDL Trados 2.4.3 Importing TMX files from Transit into Trados Essentially, Transit NXT uses codes that match the pattern described in section 2.4.2 for the TMX export. In a few cases (see Table 2-3), however, the codes used in Transit deviate from this pattern. TMX files that contain such languages cannot be imported into Trados, because Trados uses other country or language codes in these cases. Language Identifier as per ISO and in Transit NXT Afrikaans af Basque eu Catalan ca Persian fa Hebrew iw-il Serbian sr-yu Tab. 2-3: Identifier from Transit NXT as per standard Transit/TermStar NXT Reference Guide 23

2 Exchanging reference material via TMX 2.4.4 Importing TMX files from Trados into Transit Transit NXT, on the other hand, can also handle the following identifiers which are created during a TMX import/export in SDL Trados: Language Identifier in Trados Afrikaans af-01 Basque eu-01 Catalan ca-01 Persian fa-01 Hebrew iw-01 Tab. 2-4: Identifiers from SDL Trados which do not follow the standard The following identifier generated by Trados cannot be imported as the language code does not comply with the standard: Language Identifier in Trados Serbian sh-yu Tab. 2-5: Identifiers from SDL Trados which do not follow the standard 24 Transit/TermStar NXT Reference Guide

3 Managing roles 3 3 Managing roles 3.1 Overview The role administration of Transit/TermStar NXT enables you to view the definitions of the 12 standard roles that are supplied (see section 3.2 Opening a role on page 25) as well as to create your own roles (see section 3.3 Creating a new role on page 28). At the end of the section, you will see in tabular overviews what effects the choice of each individual standard role has on the functions that Transit/TermStar NXT provides in the user interface (see section 3.4 Overview of standard roles on page 32). 3.2 Opening a role In the role administration of Transit/TermStar NXT, the functional elements whose provision is affected by your role selection are displayed hierarchically in the form of a tree. These five function levels are under the top level Transit NXT: General: General areas of the ribbon bar Transit: Transit-specific areas of the ribbon bar TermStar: TermStar-specific areas of the ribbon bar Arranged below each of these three areas of the ribbon bar are the groups of these areas under these the individual functional elements subfunctions below these etc. File menu: Menu of the Transit/TermStar button below these submenus (if applicable) Resource bar below these the buttons of the resource bar below these submenus (if applicable) Other elements of a role definition are the windows and views linked to the role. Transit/TermStar NXT Reference Guide 25

3 Managing roles How do I open a user role? 1 Select User roles Manage user roles from the resource bar. Transit/TermStar NXT opens the Manage user roles window: Fig. 3-1: Manage user roles window 2 Select Open. 26 Transit/TermStar NXT Reference Guide

3.2 Opening a role 3 Transit/TermStar NXT opens the Open user role window: Fig. 3-2: Open user role window 3 Select the user role you want to open and confirm your choice by clicking Open. Transit/TermStar NXT closes the Open user role window. In the Manage user roles window, you can now see the definition of the role you have selected. The tree structure of the function levels is displayed in the upper section of the window. Initially, you only see the top level with the name Transit NXT. Navigation through the tree structure works in the same way as navigation through a file structure using the Windows Explorer: Click on the plus sign in front of the name to get to the next-lowest levels. The sub-levels fold out; the plus sign becomes a minus sign. To close the sub-levels of a level, click on the minus sign. To see the entire structure with all sub-levels, select Details. To reverse the view of all sub-levels, click once again on Details. If a function element is available in the selected role, there is a check mark in the box in front of the name of that element. If this mark is absent, the element is not available to the user in the selected role. You will find the set of windows assigned to the role in the Windows section. You will find the view in Transit/TermStar NXT assigned to the role in the View section. Transit/TermStar NXT Reference Guide 27

3 Managing roles 3.3 Creating a new role Using an existing role as the basis You can create a completely new role. However, it is generally easier to open an existing role (see section 3.2 Opening a role on page 25), save it under a different name and then edit it. This makes the process of creating a new role quicker. 3.3.1 Creating completely new roles How to create a completely new role: 1 Select User roles Manage user roles from the resource bar. Transit/TermStar NXT opens the Manage user roles window. 2 Click Create. A new role is displayed in a tree structure function in the upper section of the window. In this tree, all the functions are enabled, i.e. the names of all functional elements are marked with check marks. Information on the tree structuring and how to navigate within it can be found in section 3.2 Opening a role on page 25. 3 You can now define your new role by clicking away check marks and by selecting sets of windows and views in the Windows and View sections. If you do not want the ribbon bar to display groups that are completely inactive or the resource bar to display greyed-out buttons, activate the Hide greyed-out groups on the ribbon bar and greyed-out buttons on the resource bar option. 4 Click Save to save the information entered. 28 Transit/TermStar NXT Reference Guide

3.3 Creating a new role 3 Transit/TermStar NXT displays the Save user role window with the existing roles: Fig. 3-3: Save role window with existing roles 5 Enter a name for the new role in the Filename field. 6 Select a scope of validity for your new role at Scope. 7 Click Save to confirm the information entered. Transit/TermStar NXT saves the role under the selected name. 8 As an option, a password can be allocated for the role. 3.3.2 Editing an existing role How to edit an existing role: 1 Open the role as described in section 3.2 Opening a role on page 25. To reduce editing work to a minimum, it is recommended that a role is selected which is as similar as possible to your expected role. 2 Click Save As. Transit/TermStar NXT displays the Save user role window with the existing roles (Fig. 3-3). 3 Enter a name for the new role in the Filename field. 4 Select a scope of validity for your new role at Scope. 5 Click Save to save the information entered. Transit/TermStar NXT saves the role under the selected name. Transit/TermStar NXT Reference Guide 29

3 Managing roles 6 In the Manage user roles window, edit the structure tree for the functions by adding or removing check marks and selecting windows and views in the Windows and Views sections. Information on the tree structuring and how to navigate within it can be found in section 3.2 Opening a role on page 25. If you do not want the ribbon bar to display groups that are completely inactive or the resource bar to display greyed-out buttons, activate the Hide greyed-out groups on the ribbon bar and greyed-out buttons on the resource bar option. 7 As an option, a password can be allocated for the role 8 Click Save to save the information entered. 9 Click OK to start using the new role directly or Cancel to go back to the user role currently loaded. 3.3.3 Allocating passwords to user roles You have the option to protect user roles with passwords. This option is mainly intended for when you want a particular user, e.g. a translator or proofreader, to only be able to work with the password-protected role you have created and to also ensure this role cannot be changed. Ensuring that a user can only select the password-protected role you have created: 1 Create an individual new role which meets your needs; either by creating a completely new role or by editing an existing role (see section 3.3.1 Creating completely new roles on page 28 or 3.3.2 Editing an existing role on page 29). To ensure that the user cannot change the role, when it is created, you must deactivate the Managing roles option in the tree structure with the functional elements: Fig. 3-4: Manage user roles window, tree structure 30 Transit/TermStar NXT Reference Guide

3.3 Creating a new role 3 The password can be specified by clicking the Password option in the Manage user roles window and entering a password in the Assign new password window and confirming this: Fig. 3-5: Assign new password window The password is saved under the attribute name URPWD in the ACT file for each role in the subfolders for each of the selected areas in the \config folder. It will be displayed in the ACT file in encoded form. 2 Ensure that the standard roles for all users cannot be selected and are displayed as greyed out. The user's administrator can make this setting at the same time for all standard roles via the starte.ini file only, in which the following parameter and value have been inserted in the [Options]section: StdActorsDisabled=1 To ensure this setting cannot be changed, the user must not have access to the \bin folder of his or her Transit/TermStar NXT installation. If the user has already set up individual roles, these must be deleted by the administrator. 3 Send each user the ACT file for the role and the relevant password, so that he or she can open the role. The ACT file for the role is found in the subfolder for each selected section in the \config folder. To allow a user to use the password-protected role that was sent: 1 Place the ACT file for the role in the subfolder for the desired section in the \config folder. 2 If Transit/TermStar NXT is already open, the role can be opened as described in section 3.2 Opening a role on page 25. If you are restarting Transit/TermStar NXT, you can open the role quicker by selecting it directly in the Role overview window or via the resource bar (Roles My roles). Transit/TermStar NXT Reference Guide 31

3 Managing roles Transit/TermStar NXT opens the Enter password window: Fig. 3-6: Enter password window 3 Enter the password you have been given. 3.4 Overview of standard roles 3.4.1 Overview The following tables provide a complete overview of the effect of the selected standard role on the functions available in Transit/TermStar NXT: Tab. 3-1: Roles and general functions of the ribbon bar on page 33. Tab. 3-2: Roles and Transit-specific functions of the ribbon bar on page 35. Tab. 3-3: Roles and TermStar-specific functions of the ribbon bar on page 38. Tab. 3-4: Roles and the Transit/TermStar button on page 39. Tab. 3-5: Roles and the resource bar on page 40. 32 Transit/TermStar NXT Reference Guide

3.4 Overview of standard roles 3 3.4.2 Ribbon bar, general functions Table 3-1 shows the effect of the selected role on the available general groups in the ribbon bar: Tab Group Project Manager Project Calculation Manager Translator Reviewer Project Markup Specialist Reference Material Manager Alignment Specialist Terminology manager Terminologist Terminology Translator Localisation Specialist Super User Administration Create x - x x x x x - x x x x Open x x x x x x x - x x x x Open language pair x x x x x x x - x x x x Settings x x x x x x x - x x x x Save x x x x x x x - x x x x Save as x - x x x x x - x x x x Delete x - - - - x x - x x x x Workflow Import x - - - x x x - - - x x Export x - - - - x x - - - x x Merge extract x - - - x x x - - - x x Exchange Pack x - - x x - x - x x x x Forward project x - x x x x x - x x x x Unpack x x x x x x x - x x x x Tab. 3-1: Roles and general functions of the ribbon bar Transit/TermStar NXT Reference Guide 33

3 Managing roles Tab Group Project Manager Project Calculation Manager Translator Reviewer Markup Specialist Reference Material Manager Alignment Specialist Terminology manager Terminologist Terminology Translator Localisation Specialist Super User Pack translation x - x x x x x - x x x x Unpack translation x x x x x x x - x x x x Project Statistics Template x - - - - - x - - - x x Customer x x x x x x x - x x x x Language pairs x x x x x x x x x x x x Terminology x x x - - - - x x x x x Clipboard - - x x x x x x x x x x Format - - x x x x x x x x x x Macros - - x - - x x x x x x x Text Character table - - x x x x x x x x x x Bookmark - - x x - - x x x x x x Set flag - - x x x x x x x x x x Go to flag - - x x x x x x x x x x AutoText - - x x - - x x x x x x Read only - - x x - x x x x x x x Change case - - x x - x x x x x x x Edit Miscellaneous - - x x x x x x x x x x Administration x x x x x x x x x x x x Window Activate x x x x x x x x x x x x TermStar x x x x x x x x x x x x Tab. 3-1: Roles and general functions of the ribbon bar (cont.) 34 Transit/TermStar NXT Reference Guide

3.4 Overview of standard roles 3 3.4.3 Ribbon bar, Transit-specific functions Table 3-2 shows the effect of the selected role on the available Transit-specific groups in the ribbon bar: Tab Group Project Manager Project Calculation Manager Translator Reviewer Markup Specialist Reference Material Manager Alignment Specialist Terminology manager Terminologist Terminology Translator Localisation Specialist Super User Find Find x x x x x x x - - - x x Replace x x x x - x x - - - x x Go to x x x x x x x - - - x x Number x x x x x x x - - - x x Translate Confirm - x x x x x - - - - x x Next - x x x x x - - - - x x Navigate - x x x x x x - - - x x Segment status - x x x - x x - - - x x Join - x x x - x x - - - x x Undo join - x x x - x x - - - x x Internal Repetitions On/Off x x x x - x - - - - x x Next x x x x - x - - - - x x Translate group - x x x - x - - - - x x Editing Navigate x x x x - x - - - - x x Markups - x x x x x x - - - x x Tab. 3-2: Roles and Transit-specific functions of the ribbon bar Transit/TermStar NXT Reference Guide 35

3 Managing roles Tab Group Project Manager Project Calculation Manager Translator Reviewer Markup Specialist Reference Material Manager Alignment Specialist Terminology manager Terminologist Terminology Translator Localisation Specialist Super User Proofread - x x x - x x - - - x x Spellcheck - x x x - x x - - - x x Check Terminology - x x x - x x - - - x x Format check - x - x x x x - - - x x Dual Concordance search x x x x - x - - - - x x Matches Fuzzy search (source) Fuzzy search (target) x x x x - x - - - - x x x x x x - x - - - - x x Creation - x x - - - x - x x x x Use Find x x x - x - - - x x x x Options - x x - x - - - x x x x Terminology Automatic insert Segment Automatic insert File x x x x x x x - x x x x - x x - - - - - x x x x Dynamic Linking x x x x x x x - x x x x Alignment - x - - - - x - - - x x Alignment Confirm proposal - x - - - - x - - - x x Segments - x - - - - x - - - x x Confirm man. align. - x - - - - x - - - x x Tab. 3-2: Roles and Transit-specific functions of the ribbon bar (cont.) 36 Transit/TermStar NXT Reference Guide

3.4 Overview of standard roles 3 Tab Group Project Manager Project Calculation Manager Translator Reviewer Markup Specialist Reference Material Manager Alignment Specialist Terminology manager Terminologist Terminology Translator Localisation Specialist Super User Segment Filter x x x x x x x - x x x x Language pair x x x x x x x - x x x x Segments x x x x x x x - x x x x Display text x x x x x x x - x x x x Terminology layout x x x - - - - - x x x x Administration Save x x x x x x x - x x x x Save as x x x x x x x - x x x x Delete x x x x x x x - x x x x Reset x x x x x x x - x x x x View View for Transit editor x x x x x - x - x x x x Tab. 3-2: Roles and Transit-specific functions of the ribbon bar (cont.) Transit/TermStar NXT Reference Guide 37

3 Managing roles 3.4.4 Ribbon bar, TermStar-specific functions Table 3-3 shows the effect of the selected role on the available TermStar-specific groups in the ribbon bar: Tab Group Project Manager Project Calculation Manager Translator Reviewer Editing Markup Specialist Reference Material Manager Alignment Specialist Terminology manager Terminologist Terminology Translator Localisation Specialist Super User Data record - - x x - - x x x x x x Find Language entry - - x x - - x x x x x x Global changes - - - x - - x x x x x x In the dictionary x - x x x x x x x x x x Dynamic Linking x - x x - - - x x x x x Languages x x x x x x x x x x x x Data record filter Create x x x x x - x x x x x x Change x x x x x - x x x x x x Delete x x x x x x x x x x x x Data record filter x x x x x x x x x x x x On/Off x x x x x x x x x x x x Default data record filter x x x x x x x x x x x x View Terminology display x x x x x x x x x x x x Administration x x x x x x x x x x x x Tab. 3-3: Roles and TermStar-specific functions of the ribbon bar 38 Transit/TermStar NXT Reference Guide

3.4 Overview of standard roles 3 3.4.5 Transit/TermStar button Table 3-4 shows the effect of the selected role on the available functions in the menu of the Transit/TermStar button (counterpart to the File menu in version XV): Menu item Project Manager Project Calculation Manager Translator Reviewer Markup Specialist Reference Material Manager Alignment Specialist Terminology manager Terminologist Terminology Translator Localisation Specialist Super User Open dictionaries x x x x x x x - x x x x Open language pair x x x x x x x - x x x x Save language pair x x x x x x x x x x x x Save all language pairs x x x x x x x - x x x x Save as x x x x x x x - x x x x Printing x x x x x x x x x x x x Close language pair x x x x x x x - x x x x Close all language pairs x x x x x x x - x x x x Tab. 3-4: Roles and the Transit/TermStar button Transit/TermStar NXT Reference Guide 39

3 Managing roles 3.4.6 Resource bar Table 3-5 shows the effect of the selected role on the available functions in the resource bar: Button Menu item Project Manager Project Calculation Manager Translator Roles Reviewer Markup Specialist Reference Material Manager Alignment Specialist Terminology manager Terminologist Terminology Translator Localisation Specialist Super User Standard roles x x x x x x x x x x x x My roles x x x x x x x x x x x x Manage roles x x x x x x x x x x x x Role overview x x x x x x x x x x x x MS Office x - - - - x x - - - x x CAD x - - - - x x - - - x x DTP x - - - - x x - - - x x Graphics x - - - - x x - - - x x HTML x - - - - x x - - - x x SGML x - - - - x x - - - x x XML x - - - - x x - - - x x Localisation files x - - - - x x - - - x x Interfaces Dual fuzzy Text files x - - - - x x - - - x x RTF x - - - - x x - - - x x Trados (TTX) x - - - - x x - - - x x - x - x x - x - - - - x x Tab. 3-5: Roles and the resource bar 40 Transit/TermStar NXT Reference Guide

3.4 Overview of standard roles 3 Button Menu item Project Manager Project Calculation Manager Translator Reviewer Markup Specialist Reference Material Manager Alignment Specialist Terminology manager Terminologist Terminology Translator Localisation Specialist Super User Manage reference material Maintain reference material Create reference extract Exchange reference material (TMX) - - x x - x - - - - - x - - x x - x - - - - - x - - x - - x - - - - - x - - x - - x - - - - - x Alignment - - x - - x x - - - - x Reference material Convert reference material XV --> NXT Convert reference material NXT --> XV - - x - - x - - - - - x - - x x - x x - - - - x Open dictionary - - x - x x - x x x - x Dictionaries / databases - - x - - - - x x - - x Dictionaries Localisation WebTerm interface - - x - - - - x x - - x Import terminology - - - - - - - x x - - x Export terminology - - - - - - - x x - - x Localisation files x - - - - x x - - - x x Tab. 3-5: Roles and the resource bar (cont.) Transit/TermStar NXT Reference Guide 41

3 Managing roles STAR James Button Menu item Project Manager Project Calculation Manager Translator Reviewer Markup Specialist Reference Material Manager Alignment Specialist Terminology manager Terminologist Terminology Translator Localisation Specialist Super User Mach. trans. Synchron. Preview - x x x - - - - - - - - x Lögos x - - - - - - - - - x x Reverso x - - - - - - - - - x x Systran x - - - - - - - - - x x - x - x x x - - - - - x x Tab. 3-5: Roles and the resource bar (cont.) 42 Transit/TermStar NXT Reference Guide

4 Customising Transit/TermStar NXT 4 4 Customising Transit/ TermStar NXT 4.1 Overview You can customise Transit NXT and TermStar NXT to achieve optimum results for the tasks you perform. Automating tasks using macros section 4.2 on page 43 You can use a macro to automate a task you want to perform repeatedly in Transit/TermStar NXT. Customising the system environment section 4.3 on page 51 The starte.ini file contains a wide range of settings for running Transit NXT or TermStar NXT. Please refer to section 4.3 Customising the system environment for information on these settings and how you can change them. Spellchecking: list of unknown words section 4.4 on page 56 When performing a spellcheck, you can record unknown words in a list. If this term occurs in another part of your text, Transit NXT will not display it again as unknown because the term is now treated as a known term. Customising index buttons for TermStar NXT section 4.5 on page 58 The letters and letter groups of the TermStar NXT index buttons are specified in a configuration file. You can create an individual configuration file for each source language to generate language-specific index buttons (e.g. St and Sch for German). Checking and changing abbreviation list section 4.6 on page 59 When segmenting by sentences, Transit NXT works in each language with two files to determine whether a string is an abbreviation or not. 4.2 Automating tasks using macros 4.2.1 Overview You can use a macro to automate a task you want to perform repeatedly in Transit/ TermStar NXT. A macro comprises a number of commands and instructions which are automatically carried out when the macro is run. When creating a macro, you must assign it a shortcut which you select. Transit/TermStar NXT Reference Guide 43

4 Customising Transit/TermStar NXT A macro is more or less a user-defined sequence of commands: You no longer need to manually carry out a sequence of individual actions in Transit/TermStar NXT - now all you have to do is execute the macro using one shortcut. Typical uses for macros are: To speed up editing and formatting tasks To combine several commands To improve accessibility of an option in a window Before creating a new macro, please pay special attention to our recommendations in section 4.2.2 Tips for creating macros on page 44. To use a macro, you must first record it. Transit/TermStar NXT saves all the commands and instructions you give when recording the macro. Please refer to section 4.2.3 Recording a new macro on page 45 for more detailed information. You can run the macro once you have recorded it. In this way, Transit/TermStar NXT automatically carries out all the commands and instructions contained in the macro. Please refer to section 4.2.4 Running the macro on page 46 for information on how to run a macro. You also have the option of altering, correcting or deleting an existing macro. Please refer to section 4.2.5 Editing the macro on page 47 for more detailed information. 4.2.2 Tips for creating macros Before recording a macro, plan out the steps and the commands which you want the macro to perform. If you make an error while recording a macro, Transit/ TermStar NXT will also record the corrections made. You can edit the macro later and remove any unnecessary steps. Try and think one step ahead to avoid unnecessary queries and messages. For example, if you want to close a modified language file with a macro, Transit NXT may display a message telling you that you have not yet saved the file. To avoid Transit NXT displaying the message in the middle of a macro, save the language file first and then close it. If a macro contains the Search or Replace command, click on Processing Find/ Replace Find and select Entire document from the Search direction list. If you do not do this, Transit NXT will stop the macro when it reaches the start or end of the language file and will display a message as to whether the search should be continued. If you wish to use the macro recorded for other language files, ensure that the macro is not dependent upon the contents of the current language file. For each macro, you must specify a keyboard shortcut which you can use to start the macro. Please ensure that you do not use standard Transit/ TermStar NXT keyboard shortcuts with which you normally work. Transit/TermStar NXT does not record any mouse movements in macros. For this reason, only use keyboard shortcuts for actions which the macro should carry out. Note down keyboard shortcuts you are not familiar with before recording a macro. 44 Transit/TermStar NXT Reference Guide

4.2 Automating tasks using macros 4 4.2.3 Recording a new macro Transit/TermStar NXT saves all the commands and instructions you give when recording a new macro. Recording macros without mouse movements Only use keyboard shortcuts or keyboard input for macros. Transit/TermStar NXT does not record any mouse movements. This means that commands you carry out using the mouse cannot be saved. How do I record a macro? 1 Select Edit Macros Record. Transit/TermStar NXT displays the Record macro window (Fig. 4-1). Fig. 4-1: Record macro window 2 In the Macro name field, enter a name for the macro. 3 In the Hotkey section, specify the hotkey with which you want to run the macro. Select SHIFT+ for a keyboard shortcut using the Shift key. Select CTRL+ for a keyboard shortcut using the Control key. From the Key list, select the key if necessary in conjunction with the SHIFT and/or CTRL key with which you want to run the macro. 4 To have Transit/TermStar NXT display the commands recorded after recording the macro, select Show macro definition after recording. Transit/TermStar NXT can also display the macro definition any time at a later date (see section 4.2.5 Editing the macro on page 47). 5 Confirm your entry with OK. Transit/TermStar NXT displays the following message if you have entered a name which is already used for another macro: Macro name already exists. Transit/TermStar NXT Reference Guide 45

4 Customising Transit/TermStar NXT Confirm the message by clicking OK and in the Macro name field, enter another name which is not already in use (Step 2). If you have not selected anything from the Key list, Transit/TermStar NXT displays the following message: No hotkey selected. Confirm the message by clicking OK and select a key in the Macro name field (Step 3). From this point, Transit/TermStar NXT records all the keyboard input and commands you execute using keyboard shortcuts. 6 Carry out all the commands and keyboard inputs which you want to record in the macro. 7 To stop recording the macro, use the mouse to select Edit Macros Stop. Make sure you select this option using the mouse. Do not use a keyboard shortcut as this would be recorded with the macro. Transit/TermStar NXT stops recording the macro. If you selected the Show macro definition after recording option in the Record macro window (Step 4 on page 45), Transit/TermStar NXT displays the Edit macro window with the recorded macro. You can edit the macro as described in section 4.2.5 Editing the macro on page 47. Saving macros Transit NXT saves macros on a user-related basis at \config\users\<user name>\ in the file default.prf. A macro definition then appears under [Macros], as soon as you open the User preferences window after recording the macro and click on Save. 4.2.4 Running the macro You can run the macro once you have recorded it. Transit/TermStar NXT then automatically carries out all the commands contained in the macro. Please refer to section 4.2.3 Recording a new macro on page 45 for information on how to run a macro. There are two ways of running a macro: Using a hotkey Using Edit Macros Play. How do I run a macro using a hotkey? 1 Press the hotkey which you specified for the macro. You specified this hotkey while recording the macro (see Step 3 on page 45). You can view or alter this hotkey at a later stage (see section 4.2.5 Editing the macro on page 47). Transit/TermStar NXT runs the macro selected. 46 Transit/TermStar NXT Reference Guide

4.2 Automating tasks using macros 4 How do I run a macro using the ribbon bar? 1 Select Edit Macros Play. Transit/TermStar NXT displays the Edit macro window. 2 From the Macro name list, select the name of the macro which you want to run. 3 Click on Run. Transit/TermStar NXT runs the macro selected. 4.2.5 Editing the macro You can edit existing macros. You have the following options: Display the contents of a macro Change a macro Delete a macro Change the hotkey for a macro Re-recording an existing macro If you want to re-record an existing macro, delete the macro and then record it under the same name. Transit/TermStar NXT displays the contents of a macro: 1 Select Edit Macros Play. Transit/TermStar NXT displays the Edit macro window (Fig. 4-2). Fig. 4-2: Edit macro window Transit/TermStar NXT Reference Guide 47

4 Customising Transit/TermStar NXT 2 From the Macro name list, select the name of the macro which Transit/TermStar NXT should display. In the Shortcut and Macro definition sections, Transit/TermStar NXT displays the shortcut or the contents of the macro. 3 Click OK to close the window without changing the macro. How do I change a macro? 1 Select Edit Macros Play. Transit/TermStar NXT displays the Edit macro window (Fig. 4-2 on page 47). 2 From the Macro name list, select the name of the macro which you want to change. Transit/TermStar NXT displays the commands which are saved in the macro in the Macro Definition field. 3 Change the commands to suit your requirements. 4 To confirm the changes, click Apply and close the window by clicking OK. How do I delete a macro? 1 Select Edit Macros Play. Transit/TermStar NXT displays the Edit macro window (Fig. 4-2 on page 47). 2 From the Macro name list, select the name of the macro which you want to delete. 3 To delete the macro, click Delete and close the window by clicking OK. Transit/TermStar NXT deletes the macro. How do I change the hotkey for a macro? 1 Select Edit Macros Play. Transit/TermStar NXT displays the Edit macro window (Fig. 4-2 on page 47). 2 From the Macro name list, select the name of the macro whose hotkey you want to change. Transit/TermStar NXT displays the hotkey of the macro in the Hotkey section. 3 In the Hotkey section, specify the keyboard shortcut with which you want to run the macro (see Step 3 on page 45). 4 To confirm the changes, click Apply and close the window by clicking OK. 48 Transit/TermStar NXT Reference Guide

4.2 Automating tasks using macros 4 4.2.6 Example macro: Inserting Unicode characters To insert Unicode characters, click Edit Text Character map to open the Character map window. However, if you need a Unicode character very often, e. g. a nonbreaking space, we recommend a better option: Specify a macro. How do I record a macro used for inserting a Unicode character? 1 Select Edit Macros Record. Transit/TermStar NXT displays the Record macro window. In the Macro name field, enter a name for the macro. Example: Non-breaking space In the Hotkey section, specify the hotkey with which you want to run the macro. Example for non-breaking space: Ctrl + SPACE Select Show macro definition after recording. Confirm your entry with OK. From this point, Transit NXT records all the keyboard input and commands you execute using keyboard shortcuts. 2 Finish recording of the macro immediately afterwards. To do so, select Edit Macros Stop using the mouse. Make sure you select this option using the mouse. Do not use a keyboard shortcut as this would be recorded with the macro. Transit NXT displays the empty macro in the Edit macro window. 3 In the large empty field, enter the command that Transit NXT uses for inserting the Unicode character in text. Example for non-breaking space: 4 To confirm the changes, click Apply and close the window by clicking OK. Now, you can simply insert the Unicode character in Transit NXT with the defined shortcut, i. e. a non-breaking space using the shortcut Ctrl + Space. Displaying special characters For inserted unicode characters to be displayed, the Special characters option under View Text/Markups must be selected. Transit/TermStar NXT Reference Guide 49

4 Customising Transit/TermStar NXT Fig. 4-3: Macro for Unicode characters 50 Transit/TermStar NXT Reference Guide

4.3 Customising the system environment 4 4.3 Customising the system environment 4.3.1 Overview The starte.ini file contains a wide range of settings for running Transit/ TermStar NXT. The file starte.ini is located in the \bin folder of your Transit/TermStar NXT installation. This section describes the following system modifications: Restricting a background search with shared dictionaries (section 4.3.3 on page 53) Updating common dictionaries (section 4.3.4 on page 54) Specifying dialogue box fonts (section 4.3.5 on page 55) Changes to the file starte.ini only take effect after Transit/TermStar NXT is restarted Use a text editor to open and edit the file. Please note that the changes only come into effect if you restart Transit/TermStar NXT after saving the starte.ini file. 4.3.2 Multithreading for multilingual projects To speed up the pretranslation process for multilingual projects in Transit NXT, you can use what is known as Multithreading. This is used for multilingual projects to import and pretranslate the corresponding number of languages at the same time, depending on the number of CPUs. For instance, if a computer has four CPUs, then four languages can be pretranslated at the same time. This allows NXT to carry out the pretranslation four times as fast. Transit/TermStar NXT Reference Guide 51

4 Customising Transit/TermStar NXT For bilingual projects, a further improvement can be made, as the fuzzy index can be created during filtering rather than these processes having to be carried out in turn. This means that the creation of the fuzzy index starts in parallel to filtering. So, if filtering takes 5 minutes to complete, for example, then the creation of the fuzzy index will take 5 minutes less. File Range Parameter Possible values starte.ini [Options] MaxPretranThreads <XX> Instead of <XX> (including the characters < and >), enter the maximum number of CPUs or threads. Tab. 4-1: MaxPretranThreads parameter Multithreading is set up as follows: 1 In the area [Options], add the following line and enter the desired value: MaxPretranThreads=<XX> Instead of <XX>, including the characters < and >, use the maximum number of CPUs or threads. You can enter either positive or negative values. Example: If your high-performance computer has 8 CPUs and you have a maximum of 8 languages to pretranslate, enter the following lines: MaxPretranThreads=8 One thread will be opened per CPU. If your high-performance computer has 8 CPUs and you have a maximum of 16 languages to pretranslate at the same time, enter the following lines: MaxPretranThreads=-16 Two threads will be opened per CPU. 2 Save and close the file and restart Transit NXT. If you do not specify this option, Transit NXT will automatically use the maximum available number of CPUs for parallel pretranslation. 52 Transit/TermStar NXT Reference Guide

4.3 Customising the system environment 4 4.3.3 Restricting a background search with shared dictionaries Transit NXT provides the possibility that a number of users can share access to dictionaries across a network. As default, the background search is started in a dictionary as soon as a user opens a language pair in Transit NXT. If a number of users simultaneously access a dictionary across a network, this can impair the speed of the individual computers. File Range Parameter Possible values starte.ini [Options] MultiUserBGS 0 (Default) Background search enabled 1 Background search restricted to the current segment and the next segment that has not yet been translated Tab. 4-2: Parameter MultiUserBGS In such cases, you can limit the background search to the current segment and the next segment that has not yet been translated. To do so, insert the following entry in the file. How to restrict the background search for shared dictionaries: 1 In the area [Options], add the following line or, if applicable, modify it as follows: MultiUserBGS=1 2 Save and close the file and restart Transit NXT. Transit NXT limits the background search to the current segment and the next segment that has not yet been translated. Transit/TermStar NXT Reference Guide 53

4 Customising Transit/TermStar NXT 4.3.4 Updating common dictionaries You can also specify in the file starte.ini how often these dictionaries are updated for the individual users for the background search. The default setting is an interval of ten minutes. File Range Parameter Possible values starte.ini [Options] Update Interval <XX> Instead of <XX> (including the characters < and >), enter the desired length of the interval in minutes. Tab. 4-3: Parameter Update Interval Recommendations for the interval You can reduce this value if you only have a small number of users. We recommend that the interval be increased in the case of a greater number of users and relatively frequent changes in the dictionaries. This will reduce data traffic over the network. How do I change the interval for updating dictionaries? 1 To change the interval for the update, in the area [Options] add the following line and enter the desired value: Update Interval=<XX> Instead of <XX> (including the < and > signs), enter the length of the interval in minutes. Example: If the dictionaries are to be updated every 45 minutes, enter the following line: Update Interval=45 2 Save and close the file and restart Transit NXT. Transit NXT updates the dictionaries at the interval specified. 54 Transit/TermStar NXT Reference Guide

4.3 Customising the system environment 4 4.3.5 Specifying dialogue box fonts Transit/TermStar NXT generally uses the optimum font for the dialogue text. You can also specify other fonts for the dialogue texts if you find it difficult to read the font used. To do this, in the starte.ini file, you should specify the fonts with which Transit/ TermStar NXT displays dialogue texts before you start Transit or TermStar. The setting only applies to the dialogue font The setting described only applies to the dialogue font which Transit/TermStar NXT uses to display menu texts and window contents. This is not relevant for the display of the language pairs or dictionary entries. You modify these in the window User preferences at Colours and fonts. How do I specify the fonts for the dialogue texts? 1 In the starte.ini file, enter the section [FontsWeight] if it is not yet available: [FontsWeight] 2 In the [FontsWeight] section, specify the fonts and the weighting: <Font> = <weighting> Instead of <Font> (including the < and > signs), use the name of the desired font. Instead of <weighting>, use the weighting with which the character set is to be used. Character sets with higher weighting are used with priority. Example: [FontsWeight] Microsoft Sans Serif = 9 Arial = 8 Times New Roman = 7 Courier New = 6 Verdana = 5 Tahoma = 4 Lucida Sans Unicode = 3 Trebuchet MS = 2 Impact = 1 Georgia = 1 Lucida Sans = 1 3 Save and close the file. Transit/TermStar NXT will now give preference to the fonts with the highest priority when selecting fonts automatically. Transit/TermStar NXT Reference Guide 55

4 Customising Transit/TermStar NXT 4.4 Spellchecking: list of unknown words When performing a spellcheck, you can record unknown words in a list. If this term occurs in another part of your text, Transit NXT will not display it again as unknown because the term is now treated as a known term. Transit NXT saves the list of unknown words for each language in a separate file. You may want to edit that list, for example to remove words added by mistake or to establish which words were not in the spellcheck dictionary or (in the case of a reference-based spellcheck) were not in the reference material from previous projects. Transit NXT saves the list in different files depending on the basis of the spellcheck: With reference-based spellcheck With Open Source dictionary Applicability of list: Project-specific (applicable only to the project concerned) User-specific (applicable to all of the user's projects) Folder: Working folder for the project (normally projects\<project name>) User folder (config\users\ <user name>) File name: <project name>_ <language code>.rsa SpellUserDic.<language code> Example (supplement for Swedish): In the project NXT_Word: nxt_word_sve.rsa SpellUserDic.sve Tab. 4-4: File for list of unknown words 56 Transit/TermStar NXT Reference Guide

4.4 Spellchecking: list of unknown words 4 4.4.1 Opening and editing the list of unknown words Transit NXT saves the list of unknown words as Unicode file so that you can add words in double byte languages such as Japanese or Chinese, too. Unicode editor necessary If you want to edit the file you need to use a Unicode editor that supports UTF- 16. Other editors are not able to save the file correctly, and this would make the list unusable for the spellcheck. For spellchecks based on Open Source dictionaries or reference-based spellchecks, the file contains an unknown word on each line. The lines are arranged in alphabetical order. Example: able Analysis application Application calculate facility important independently invoices Money profits provide track Transit/TermStar NXT Reference Guide 57

4 Customising Transit/TermStar NXT 4.5 Customising index buttons for TermStar NXT 4.5.1 Overview The letters and letter groups of the TermStar NXT index buttons are specified in a configuration file. You can create an individual configuration file for each source language to generate language-specific index buttons (e.g. St and Sch for German). 4.5.2 Configuration file for index buttons The configuration files which define the index buttons have the following name structure: buttons.<language code> Instead of <language code>, the 3-letter language code is used for the language for which TermStar NXT should display the index buttons. A list of these language codes is provided in section 15.2 3-letter language code on page 212. Examples: Configuration file for German buttons.deu Configuration file for Egyptian Arabic buttons.are The configuration files are located in the config\global folder of the Transit/ TermStar NXT installation. For each source language, TermStar NXT checks whether a configuration file is available for the language in question. If no file is available, TermStar NXT uses the default configuration file buttons.def. 4.5.3 Changing index buttons You can create and edit the configuration files with a text editor. If you are creating a new configuration file, simply copy an existing configuration file and edit the copy. The following rules apply for the configuration file: The first line contains the following: [Register] The definitions of the individual buttons have the following syntax: <no>=<character> <letter group> <no> consecutive number for the position of the index button <character> character which TermStar NXT displays on the index button <letter group> the letter group to which TermStar NXT should jump using this index button. Here, TermStar NXT treats the asterisk (*) as a wildcard for subsequent characters. TermStar NXT does not differentiate between upper and lower case. 58 Transit/TermStar NXT Reference Guide

4.6 Checking and changing abbreviation list 4 Examples: 1=A A* TermStar NXT displays an A on the first index button. If you click this index button, TermStar NXT displays the first entry beginning with A or a (TermStar NXT does not differentiate here between upper and lower case). 18=Sch SCH* On the 18th button, TermStar NXT shows Sch. If you click this index button, TermStar NXT displays the first entry beginning with Sch or sch. New buttons are only available after you have reselected the source language If you have changed or created a configuration file for a language's index buttons, you must select this language again so that TermStar NXT uses the modified configuration file. The quickest way of doing this is by swapping the source and target language twice. Press the key combination CTRL+A to swap the source and target languages. 4.6 Checking and changing abbreviation list When segmenting by sentences, Transit NXT works in each language with two files to determine whether a string is an abbreviation or not. <Language>_neg.ewl for abbreviations Transit NXT interprets a period (full stop) after these strings as an abbreviation period and does not segment the text at this point. <Language>_pos.ewl for no abbreviations Transit NXT interprets a period after these strings as the end of a sentence and segments the text at this point. Instead of <Language>, Transit NXT uses the 3-letter language code of the language. Example: The lists for British English have the following names: eng_neg.ewl eng_pos.ewl. You can create these abbreviation lists interactively if you select the option Check segmentation after import (Project Administration Settings, tab Segmentation, see Transit NXT User's Guide). Transit/TermStar NXT Reference Guide 59

4 Customising Transit/TermStar NXT Transit NXT saves the files according to the section to which the lists apply. List for all projects and customers (Global section) folder /config/global List for all projects of a customer (Customer section) folder /config/ customers/<customer> List for a project (Project section) working folder for project Transit NXT uses all accessible abbreviation lists, if necessary, therefore, global, customer-specific and project-specific abbreviation lists. How do I check and modify an abbreviation list? 1 Open the list with a text editor. <Language>_neg.ewl for abbreviations <Language>_pos.ewl for no abbreviations 2 Delete or correct incorrect entries or add missing ones. 3 Save and close the file. 60 Transit/TermStar NXT Reference Guide

5 Print definition set-up 5 5 Print definition set-up 5.1 Overview When printing files for proofreading or dictionaries, you can define the page layout by specifying margins, headers and footers, for example. You can save these settings under a separate name as a print definition to use again at a later stage (see section 5.2 Opening a print definition on page 61 and 5.2.1 Saving the print definition on page 62). The print definitions can be used to make settings: Setting page margins (section 5.2.2 on page 64) Defining separators for dictionaries (section 5.2.3 on page 65) Specifying headers and footers (section 5.2.4 on page 68) Specifying the page layout (section 5.2.5 on page 71) 5.2 Opening a print definition Before you customise the print definition settings, you can check whether suitable print definitions already exist which you could use or adapt. You can use these print definitions directly for printing or change them and save the modified print definition under a new name, if necessary. How do I open an existing print definition? 1 Select Transit button Print Page setup. Transit NXT displays the Page window with the following tabs: Page margin (Please refer to section 5.2.2 on page 64 for more detailed information) Separator letter (Only for dictionaries, for details see 5.2.3 on page 65) Header (Please refer to section 5.2.4 on page 68 for more detailed information) Footer (Please refer to section 5.2.4 on page 68 for more detailed information) Page layout (Please refer to section 5.2.5 on page 71 for more detailed information) On each tab you will see the Open, Save and Save as buttons used to manage the print definitions. A print definition always saves the settings for all tabs. Transit/TermStar NXT Reference Guide 61

5 Print definition set-up 2 To open an existing print definition, click Open. Transit NXT displays the Open print definition window with a list of all the existing print definitions (Fig. 5-1). Fig. 5-1: Open print definition window 3 Select a print definition and click Open. Transit NXT displays the settings for the print definition opened in the tabs. 5.2.1 Saving the print definition If you have changed a print definition, you can save it with the new settings. You have two options here: Save Save as an existing print definition The existing print definition is saved with the new settings. The next time you open the print definition, it will contain the new settings and the previous settings will no longer be available. Save as Save as a new print definition Transit NXT generates a new print definition so that in future both the existing print definition with the old settings and the new print definition with the modified settings are available. 62 Transit/TermStar NXT Reference Guide

5.2 Opening a print definition 5 How do I save the changes as an existing print definition? 1 Once you have made the changes in the Page window, click Save. Transit NXT saves the settings in the previously opened print definition. This will overwrite the previous settings for this print definition. How do I save the changes as a new print definition? 1 Once you have made the changes in the Page window, click Save as. Transit NXT displays the Save print definition as window (Fig. 5-2). Fig. 5-2: Save print definition as window 2 Enter a name for the new print definition in the File name field. Transit NXT shows this name in the list of the available print definitions then next time you want to open print definitions. 3 In the Scope list, select the scope for which the print definition should be available: Global Accessible for all users in all projects. Customer Only accessible to projects which have the same customer as the current project. User Can only be accessed by the current user. 4 Click Save. Transit/TermStar NXT Reference Guide 63

5 Print definition set-up Saving print page settings The print page settings are saved in the file <File name>.tpd. Depending on the location of the current project, Transit NXT saves this file in global or users\<user name> or customers\<customer name>. 5.2.2 Setting page margins You can set the following margins in the Page margin tab: Top, Bottom, Left, Right margins on all four sides Gutter additional margin along the inside for binding if you are printing doublesided (Page layout tab). For one-sided printing this is the left-hand margin. The value entered here always applies in addition to the Right and Left margins. Header and Footer distance of header from the top edge and of the footer from the bottom edge Header and footer margins Please ensure that the top and bottom page margin is larger than the header and footer margins. Otherwise headers and footers would extend into the print area of the dictionary. How do I set the margins? 1 In the Page window, select the Page margin tab: Fig. 5-3: Page window, Page margin tab 64 Transit/TermStar NXT Reference Guide

5.2 Opening a print definition 5 2 Specify the values for the margins. Transit NXT updates the preview window when you leave the modified field. Do not forget to save the print definition if you changed the print definition settings so that you can work with the modified settings in the future. Please refer to section 5.2.1 Saving the print definition on page 62 for more detailed information. Message for invalid values Most printers require a minimum margin ("offset") as they cannot print right to the paper edge. If a setting is not permitted (value too large or too small), Transit NXT displays the Properties window to warn you of this: Fig. 5-4: Properties window Adjust the value to your printer as required. 5.2.3 Defining separators for dictionaries You can use the Separator letters tab to specify if and how TermStar NXT should insert separator letters which visually separate the dictionary into different letter groups. You can use letter ranges, individual letters, digits or a combination of these options as the separator (table 5-1). TermStar NXT distinguishes between upper and lower case. If necessary, enter letters and letter ranges in both versions (upper and lower case). TermStar NXT does not print a separator for letters or digits you do not specify. Separator type Entry in separator field Meaning Letter range a-za-z TermStar NXT uses separators when printing the letter range A-Z. TermStar NXT does not use a separator when printing letters outside this character range (e.g. special characters). Tab. 5-1: Separators for printing the dictionary Transit/TermStar NXT Reference Guide 65

5 Print definition set-up Separator type Entry in separator field d-kd-k Meaning TermStar NXT uses separators when printing the letter range D-K. TermStar NXT does not use separators when printing all other characters. Individual letters aabbccåå TermStar NXT uses separators when printing the specified letters A, B and C and the special character Å. TermStar NXT does not use separators when printing all other characters. Using this method, TermStar NXT also prints letters outside the standard character range with a separator letter. Numbers 1-9 TermStar NXT uses a separator to print entries starting with the numbers 1 to 9. TermStar NXT does not use a separator when printing any entries starting with a letter. Combinations 1-5a-tA-TåÅ You can also combine the separator types mentioned. Tab. 5-1: Separators for printing the dictionary (cont.) No separator letters for German umlauts TermStar NXT sorts German umlauts (Ä, Ö, Ü) under A, O and U as in the Duden. They are not sorted separately as individual letters. For this reason, TermStar NXT does not print separators for these umlauts. 66 Transit/TermStar NXT Reference Guide

5.2 Opening a print definition 5 How do I set the separators? 1 Select the Separator letter tab: Fig. 5-5: Page window, Separator letter tab 2 From the Placement list, select where TermStar NXT should position the separator: None TermStar NXT does not print any separators. Left, Centre or Right TermStar NXT prints the separator at the left-hand margin, in the middle or at the right-hand margin. 3 From the New page list, select whether TermStar NXT should start printing on a new page when the letter being printed changes: None Each new letter will not appear on a new page. Page Each new letter will be printed on a new page. Right page Each new letter will appear on the next right-hand page. The Right page option is only relevant to double-sided layouts (Page layout tab). This may result in a blank left-hand page. 4 In the Separator field, enter the characters in front of which TermStar NXT should print a separator (see table 5-1 on page 65). 5 Select the font to be used to print the separator. To do this, click Font. In the Font window, you can change the font, type face, type size, display and colour. Confirm your entries with OK. 6 Select the background for the separator: To do this, click on Background. Transit/TermStar NXT Reference Guide 67

5 Print definition set-up Transit NXT displays the Color window: Fig. 5-6: Color window 7 In the Color window, select the background colour. Confirm your selection with OK. 8 In the Distance to text section, specify the distance between the text and the separators (before and after): Before Distance above the separator in centimetres. After Distance below the separator in centimetres. TermStar NXT updates the preview window when you leave the modified field. Do not forget to save the print definition if you changed the print definition settings so that you can work with the modified settings in the future. Please refer to section 5.2.1 Saving the print definition on page 62 for more detailed information. 5.2.4 Specifying headers and footers In the page set-up, you can specify headers and footers to be printed on each page of the printout. Headers and footers can contain the following: Fixed text (e.g. project description, department, copyrights). Variables (e.g. date, consecutive page number, file name; see Tab. 5-2) A header or footer has left, and right areas. You can add text and variables to each of these areas. You can also set a font for each area separately. 68 Transit/TermStar NXT Reference Guide

5.2 Opening a print definition 5 Finally, you can specify for the header and footer whether, and how, they are to be separated by a line from the print area. Variable Meaning Example %d Current date 08.08.2006 %t Current time 13:39 %p Page number 12 %f Transit NXT: number of the first segment on the page TermStar NXT: term of the first data record on the page %l Transit NXT: number of the last segment on the page TermStar NXT: term of the last data record on the page %n Transit NXT: working name of the language file 126 application 261 browser About Transit NXT Use in TermStar NXT inadvisable %N Transit NXT: path and file name of the language file TermStar NXT: dictionary and database name c:\programs\transit NXT\projects\ NXT_Word\About_Transit NXT MyTerms(TermStar NXT) Tab. 5-2: Variables for header and footer Transit/TermStar NXT Reference Guide 69

5 Print definition set-up How do I specify the header or footer? 1 In the Page set-up window, select the Header or Footer tab: Fig. 5-7: Page window, Header tab 2 Choose one of the three areas Left, Center or Right by selecting the respective tab in the lower section of the window. 3 Enter the text for the area selected: Enter fixed text in the Text field. Insert one of the variables by double clicking on the corresponding entry in the Field list. Edit the text (e.g. by inserting blanks between the variables). 4 Select the font to be used for printing the text of this area. To do this, click Font. In the Font window, you can change the font, type face, type size, display and colour. Confirm your selection with OK. 5 Repeat steps 2 to 4 for the remaining areas (centre and right). 6 Select Double-sided symmetrical to print the headers and footers in mirrorimage on the right and left pages. If you have selected this option, the right and left-hand areas will be swapped over between the right and left-hand pages. This means that the page numbers always appear on the outer edge of the page. The symmetrical layout is only used for double-sided layouts (tab Page Layout). 70 Transit/TermStar NXT Reference Guide

5.2 Opening a print definition 5 7 Select the Line option in the Separator lines section to insert a separating line between the header/footer and the print area of the dictionary. Specify the settings for the line: From text distance of the line from the header and footer in centimetres Line width width of the line in points Do not forget to save the print definition if you changed the print definition settings so that you can always work with the modified settings in the future. Please refer to section 5.2.1 Saving the print definition on page 62 for more detailed information. 5.2.5 Specifying the page layout The page layout settings in the page set-up define the general appearance of the printout. Page layout 1st page number This is where you specify the number from which page numbering should start. You can determine where the page number is printed by entering the variable for the page number (%p) in the header or footer (see section 5.2.4 Specifying headers and footers on page 68). Double-sided If you select Double-sided, Transit NXT prints left and right pages differently: The gutter which you specified on the Page margin tab is always added along the inside edge of the page. If you selected the Double-side symmetrical option on the Header and/or Footer tabs, the Left and Right areas are printed in mirror image. In this way, for example, you can ensure that the page numbers are always on the outside. Column layout If you wish to print the text in columns, you can specify the following settings here: Columns Number of columns Other options are available if you select more than one column: Spacing Spacing between the columns Line between TermStar NXT inserts a separating line between the columns if you select Line between. You can also specify the width of the separating line in the Thickness field. Transit/TermStar NXT Reference Guide 71

5 Print definition set-up How do I specify the page layout? 1 In the Page window, select the Page layout tab: Fig. 5-8: Page window, Page layout tab 2 Specify the page and column layout. Transit NXT updates the preview window when you leave the modified field. Do not forget to save the print definition if you changed the print definition settings so that you can work with the modified settings in the future. Please refer to section 5.2.1 Saving the print definition on page 62 for more detailed information. 72 Transit/TermStar NXT Reference Guide

6 Customising projects 6 6 Customising projects 6.1 Overview You can specify the majority of project settings by means of the ribbon bar, using Project Administration Settings. In addition, you can customise projects using further settings by opening and editing the prj project file directly in a text editor. Compressing files with formatting information (cod files) (section 6.2 on page 74) Excluding hidden or locked text from translation in Excel (section 6.3 on page 74) Optimising the pretranslation time (section 6.4 on page 76) To do so, you can open the project file in a text editor, edit it, save the changes and then close it. Please note that the changes only come into effect if you re-open the project, and if necessary import it, after closing the project file. Depending on the scope, the project file is located in one of the following subfolders in the Transit installation folder: For global projects in the folder \config\global\ For user projects in the folder \config\user\<user name>\ For customer projects in the folder \config\customer\<customer name>\ <User name> or <customer name> is the name you specified as the user or the customer. Transit/TermStar NXT Reference Guide 73

6 Customising projects 6.2 Compressing files with formatting information (cod files) During the import, Transit NXT saves formatting information to cod files. For each project, you can specify whether Transit NXT should compress the cod files. In this way, the.cod files require less disk space for very large files. To compress the cod files, make an entry into the prj project file before importing the files. Impact on the time required for importing Please be aware that this setting can slow down the import process. How do I compress the cod files? 1 Enter the following line into the [ImportExport] section of the *.prj project file or modify the existing entry: CompressCodFile=1 2 Save and close the file. Open the project again in Transit and import the files. Transit NXT now compresses the cod files of this project during import. 6.3 Excluding hidden or locked text from translation in Excel Transit NXT may exclude table cells or entire table rows or columns which are hidden or locked (i.e. protected) in an Excel sheet from the translation process. In practice, it may be useful to exclude parts of the table from translation if, for example, a table has been created in Excel which has terms in a source language in the first column with a space for the translation of these terms in the second column. You would first create the source language terms in both columns and then hide or lock the cells in the first column. You can then exclude these from translation. During subsequent export of the translated language pairs, the source language terms remain in the first column. 74 Transit/TermStar NXT Reference Guide

6.3 Excluding hidden or locked text from translation in Excel 6 For excluding hidden parts of text from translation, you have to customize the file type settings before importing the Excel file. For excluding locked parts of text from translation, you have to change the standard value for the following option in the *.prj project file before importing the Excel file: File Range Option Possible values *.prj [ImportExport] ExcelShowProtectionStatus 0 (Default) The locked text is imported and can be translated. 1 The locked text is imported and is protected as markups. Tab. 6-1: ExcelShowProtectionStatus option Excluding parts of text that are hidden in Excel from translation: 1 Open the File type settings window. For details on the file type settings refer to the section 3.5.7. Project setting File type in the Transit NXT User s Guide. 2 Deselect the Translate hidden cells/slides option. Transit NXT will not import the parts of text that are hidden in Excel. Excluding parts of text that are locked in Excel from translation: 1 In the *.prj project file in the [ImportExport] section, change the value for the ExcelShowProtectionStatus option as follows: ExcelShowProtectionStatus=1 2 Save and close the file. Open the project again in Transit and import the files. Transit NXT imports the parts of text that are locked in Excel, but these are protected as markups. Transit/TermStar NXT Reference Guide 75

6 Customising projects The markup <td> is shown with the attribute protected and the associated cell text is protected. The protected cell text is still displayed, even when you have selected that markups are not to be displayed. 6.4 Optimising the pretranslation time 6.4.1 Overview The MaxPreTransHits parameter in the project file has an effect on the duration of the pretranslation and the results achieved. It has a particularly marked effect with very large documents which contain a lot of repetitions (see section 6.4.2 The MaxPreTransHits parameter on page 76). To optimise the duration of the pretranslation process and the results achieved, you can modify the parameter in the prj project file prior to import (see section 6.4.3 Customising the MaxPreTransHits parameter on page 77). 6.4.2 The MaxPreTransHits parameter For the pretranslation, Transit searches in the reference material for segments that match the segments to be translated. On the basis of text contents and tag occurrences, Transit NXT first finds the segments that are taken into consideration for the pretranslation. Transit saves these segments in a list with decreasing correspondence. Transit now examines the segments in the list to find reference segments that are identical to the segments to be translated. When doing this, Transit NXT takes tag meaning, case and translation variants into consideration. The MaxPreTransHits parameter specifies how many segments from the list are taken into consideration and examined in detail. A value of 50 means The first 50 reference segments found are examined in detail to see if they are really identical to the segments to be translated. The higher the value of the MaxPreTransHit, the more reference segments Transit NXT examines. The number of pretranslated segments is greater, but more time is required for the pretranslation. 76 Transit/TermStar NXT Reference Guide

6.4 Optimising the pretranslation time 6 Tip: Use a reference extract If you are dealing with very large documents which have a large number of repetitions, a very high MaxPreTransHits value can result in a long pretranslation time, which sometimes may not even yield optimum pretranslation results. We recommend that you work with reference extracts for such projects. Transit compresses and optimises the information contained in the reference material. This means that you can select a low value for the MaxPreTransHits parameter and receive optimum pretranslation results in a shorter timeframe. Please refer to the Transit User's Guide for more information on how to generate a reference extract. 6.4.3 Customising the MaxPreTransHits parameter How do I optimise the pretranslation time? 1 Enter this line into the [TransMem] section of the prj project file or modify the existing entry. MaxPreTransHits=<value> Instead of <value> (including the < and > signs), enter the desired value. Example: If you wish to use the value 20, enter the following line: MaxPreTransHits=20 2 Save and close the file. Reload the project in Transit and import the files. Transit now pretranslates using the new value. Transit/TermStar NXT Reference Guide 77

7 Fields in the TermStar dictionary 7 Fields in the TermStar dictionary 7.1 Overview The following sections provide you with detailed information on the fields available in TermStar NXT: Header fields TermStar NXT displays header fields in selection lists and in the layout editor with the prefix Hdr or Header (e.g. Hdr->status or Header.status). Language fields TermStar NXT displays language fields in selection lists and in the layout editor with the prefix Language, Lang. or Target language (e.g. Language->info1, Lang.->info1 or Target language.info1). Entry fields and subentry fields TermStar NXT displays language fields in selection lists and in the layout editor with the prefix Language or Lang. (e.g. Language->Info1, Lang.->Info1 or Language.Info1). The language codes that TermStar NXT uses to identify the languages can be found in section 15.2 3-letter language code on page 212. 7.2 Field types There are the following types of field on which the maximum number of possible characters also depends: Numerical field (N) Contains an automatically assigned number; therefore the field length is irrelevant. Date field (D) Contains an automatically assigned number; therefore the field length is irrelevant. 255-character text field (255Z) Contains up to 255 bytes of text 16-kB text field (16KB) Contains 16 kb of text 78 Transit/TermStar NXT Reference Guide

7.2 Field types 7 The specified values are the maximum possible field lengths. In practice, you will not approach these theoretical restrictions. Bear in mind that the entered data volume might have to be transferred across an internet / LAN connection and processed by your computer and the database. In the following tables, the field type is marked with the abbreviation specified above in parentheses. 7.2.1 Header fields The header fields belong to a complete data record. They do not therefore relate to an individual language entry but to the overall semantic unit. Table 7-1 lists all the header fields with a description of what they do and an example of what they contain. Field name Description Type Example Data record number Number assigned to each data record in a dictionary Automatically filled in Cannot be edited N 2905 GUID Number which uniquely identifies each data record. N {2F16...EAC63} Automatically filled in Cannot be edited Project Project name that can be entered by the user (field is not filled automatically) 16KB Transit/ TermStar Reference Guide Dictionary Name of the dictionary that contains the data record 255c STAR This is entered automatically when the data record is created. Cannot be edited Status Status of the data record 16KB Revised Example: Information on the reliability or the status of the data record Tab. 7-1: Header fields Transit/TermStar NXT Reference Guide 79

7 Fields in the TermStar dictionary Field name Description Type Example Graphic / Video / Sound Linking field for linked multimedia files 16KB User1-9 Open field for the data record. 16KB Created by Name of the user who created the data record. 255c A. Smith Automatically filled in Cannot be edited Created on Point in time when the data record was created Automatically filled in Cannot be edited D 29. May 2002, 16:30 Last change by Name of the user who last changed the data record 255c A. Smith Empty as long as the data record has not been changed Automatically filled in Cannot be edited Last change on Point in time when the data record was last changed D 2. January 2015, 15:21 Empty as long as the data record has not been changed Automatically filled in Cannot be edited Created or changed by Name of the user who created the data record or who last changed it 255c A. Smith Never empty - contains at least the name of the user who created the data record Automatically filled in Cannot be edited Tab. 7-1: Header fields (cont.) 80 Transit/TermStar NXT Reference Guide

7.2 Field types 7 Field name Description Type Example Created or changed on Point in time when the data record was created or last changed D 2. January 2015, 15:21 Never empty - contains at least the point in time when the data record was created Automatically filled in Cannot be edited Remark General remarks on the entire data record 16KB Subject Subject area of the data record 16KB Data processing Tab. 7-1: Header fields (cont.) 7.2.2 Language fields The language fields relate to all entries of a language. You can, for example, use these fields to create a single description in English for several English entries in a data record. Table 7-2 lists all the language fields with a description of what they do and an example of what they contain. Field name Description Type Example Language 3-letter language code 16KB ENG Automatically filled in Cannot be edited Info1 Field available for unrestricted use, for information that applies to all the entries in this language 16KB A field in a dialogue box. Info2 Same as Info1 16KB Styleguide 2.1.15 Multimedia Linking field for linked multimedia files 16KB Tab. 7-2: Language fields Transit/TermStar NXT Reference Guide 81

7 Fields in the TermStar dictionary 7.2.3 Entry fields and subentry fields The entry and subentry fields contain the data for an entry or subentry respectively. Each subentry you attach to an entry has the same number of fields as an entry. Table 7-3 lists all the entry and subentry fields with a description of what they do and an example of what they contain. Field name Description Type Example Entry number Number which uniquely identifies each entry. Automatically filled in Cannot be edited N 195 Term Term of the entry 16KB TermStar TermStar NXT sorts the entries in the dictionary in accordance with the content of this field. Language 3-letter language code of the language of the entry 16KB ENG Automatically filled in Cannot be edited Created by Name of the user who created the entry 255c A. Smith Automatically filled in Cannot be edited Created on Point in time when the entry was created Automatically filled in Cannot be edited D 29. May 2002, 16:30 Last change by Name of the user who last changed the entry 255c A. Smith Empty as long as the entry has not been changed Automatically filled in Cannot be edited Tab. 7-3: Entry fields and subentry fields 82 Transit/TermStar NXT Reference Guide

7.2 Field types 7 Field name Description Type Example Last change on Point in time of the last change made to the entry D 2. January 2015, 15:21 Empty as long as the entry has not been changed Automatically filled in Cannot be edited Created or changed by Name of the user who created the entry or who last changed it 255c A. Smith Never empty - contains at least the name of the user who created the entry Automatically filled in Cannot be edited Created or changed on Point in time when the entry was created or last changed D 2. January 2015, 15:21 Never empty - contains at least the point in time when the entry was created Automatically filled in Cannot be edited Context Context in which the term is used 16KB Terminology management Context source Part of speech Source of the context 16KB RefGuide Part of speech of the entry 16KB Noun Gender Gender of the entry 16KB n. Grammatical information Grammatical features of the entry 16KB Proper name Status Status of the entry 16KB Revised Example: Information on the reliability or the status of the entry Data source Source of the entry 16KB STAR Terminology Department Attributes Attributes for the entry 16KB New Tab. 7-3: Entry fields and subentry fields Transit/TermStar NXT Reference Guide 83

7 Fields in the TermStar dictionary Field name Description Type Example Remark General comments on the entry 16KB Note the spelling! Subject Subject area of the entry 16KB Translation, software Phonetical information Information on the pronunciation of the term 16KB "TI@ri (theory) Crossreference Field for cross-reference Examples: 16KB Transit NXT Cross-reference to a related entry Cross-reference to an internet address Definition Definition of the entry 16KB STAR's Translation Memory Tool Source of the definition Source of the definition 16KB STAR brochure 2008 User1-9 Open field for the entry 16KB Tab. 7-3: Entry fields and subentry fields 84 Transit/TermStar NXT Reference Guide

7.2 Field types 7 7.2.4 Subentry types TermStar NXT displays fields for subentries in selection lists and in the layout editor with a corresponding prefix: Subentry Abbreviations Synonyms Alternatives Irregular forms Disallowed terms User index 1 User index 2 User index 3 User index 4 User index 5 Prefix Abbr. or Abbreviations Syn. or Synonyms Alt. or Alternatives Irreg. or Irregular forms Dis. term. U. ind.1 or User index 1 U. ind.2 or User index 2 U. ind.3 or User index 3 U. ind.4 or User index 4 U. ind.5 or User index 5 Tab. 7-4: Prefix for subentries in selection lists Transit/TermStar NXT Reference Guide 85

8 Customising layouts 8 Customising layouts 8.1 Overview TermStar NXT saves numerous settings for the display of your dictionaries in the views. A view is composed of two or three layouts. You can use these layouts to specify which fields can be edited and how TermStar NXT displays the fields of dictionaries. The following properties are specified in the layouts: Field selection for the header data Field selection for the entry data, individually by source language, target language and other languages Field layout Field formatting (font, size, colour etc.) Fixed texts which TermStar NXT displays before and after the contents of the field Static text units which TermStar NXT displays for every data record Displaying cross-references TermStar NXT is supplied with a wide range of layouts which you can use. You can also create and save layout files yourself (see section 8.2 Managing layouts on page 86). The layout editor is available for editing. It contains all the necessary selection and formatting functions (see 8.3 Working with the layout editor on page 91). To use a new layout in TermStar NXT, you must assign it to one of the existing views (see section 10.4 Customising the dictionary window in the TermStar NXT User's Guide). 8.2 Managing layouts 8.2.1 Overview Every dictionary layout is saved in its own file. Layout files contain the file name extension *.tld. The layout files can be copied as often as required and sent on to other users. The layout files are stored in different folders according to their scope: Global available for all users and in all projects: In the folder config\global of your Transit/TermStar NXT installation 86 Transit/TermStar NXT Reference Guide

8.2 Managing layouts 8 Project only available for the project in which it was created: In the working folder of the project. Customer only for projects with the same customer as the project in which it was created: In the folder config\customers\<customer folder> of your Transit/ TermStar NXT installation User can only be called by the user who created it: In the folder config\users\<user folder> of your Transit/TermStar NXT installation 8.2.2 Creating a new layout Use an existing layout as the basis You can use the layout editor to create a completely new layout. However, it is generally easier and sufficient to open an existing layout (see section 8.2.3 Opening existing layouts on page 87), save it under a different name and then edit it. How do I create a new layout? 1 Select View Terminology display Create. Then select one of the following options in the list box: Dictionary layout Create library layout Create address layout TermStar NXT opens the layout editor The layout editor displays a new layout. Only the field for the source language term is selected in this layout. Now you can edit this layout and then save it (see section 8.3 Working with the layout editor on page 91). 8.2.3 Opening existing layouts You have the following options for opening an existing view: Open current left-hand layout Open current right-hand layout Open current layout for the editing mode Open other layout Transit/TermStar NXT Reference Guide 87

8 Customising layouts How to open an active layout: 1 Depending on the layout you want to edit, select one of the following options: View Terminology display Left Change Open current left-hand layout in the layout editor View Terminology display Right Change Open current right-hand layout in the layout editor View Terminology display Edit Change Open current editing layout in the layout editor View Terminology display Change Select another layout and open it in the layout editor TermStar NXT opens the selected layout in the layout editor. 2 Modify this layout according to your needs (see section 8.3 Working with the layout editor on page 91) and then save it. How do I open an existing layout? 1 Select View Terminology display Change. Then select one of the following options in the list box: Dictionary layout Library layout Address layout 2 TermStar NXT displays the window Open with the existing layouts (Fig. 8-1). Fig. 8-1: Open window with layouts available 88 Transit/TermStar NXT Reference Guide

8.2 Managing layouts 8 3 Select the layout which you want to edit and confirm your choice by clicking Open. TermStar NXT opens the layout in the layout editor 4 Modify this layout according to your needs (see section 8.3 Working with the layout editor on page 91) and then save it. 8.2.4 Saving the layout and closing the layout editor If you have edited a layout in the layout editor, you must save it so that your changes are not lost. Save prompt when closing the layout window When you close the window of a layout you have changed but not yet saved, the layout editor displays a prompt asking you whether you wish to save the changes. In this way, the layout editor prevents you from forgetting to save a modified layout. There are two ways of saving a layout: Save The layout editor saves the layout under the same name and in doing so overwrites your old layout. Save under a new name The layout editor saves the layout under a new name. In this way, you create a new layout and your old layout remains unchanged. How do I save a layout? 1 In the header of the layout editor, click on X. If you have changed the currently opened layout, Transit NXT displays the following message: Layout <name> (<area>) has been changed. Save? 2 Decide what you want to do with the changes to the layout: Click on Yes to save the changes to the layout. Transit NXT saves the changes and closes the layout editor. Click on No if you do not want to save the changes. Transit NXT closes the layout editor without saving the layout changes. Transit/TermStar NXT Reference Guide 89

8 Customising layouts How to save a layout under another name: 1 Select Transit button Save as. TermStar NXT displays the Save window with the existing layouts (Fig. 8-2).. Fig. 8-2: Save window with existing layouts 2 Enter a name for the new layout in the File name field. 3 Select the access scope for the new layout from the Scope list: Global all projects accessible to all users Project only accessible from within the current project User only accessible to the current user Customer only for current customer projects 4 Click Save to confirm the information entered. Transit NXT saves the layout under a new name. 90 Transit/TermStar NXT Reference Guide

8.3 Working with the layout editor 8 8.3 Working with the layout editor 8.3.1 Areas of a layout Each layout consists of the following two areas: Normal In this area you can specify how TermStar NXT should display the normal main entries and associated subentries. Cross-reference In this area you can determine how TermStar NXT displays the subentries as separate entries in the dictionary and how the automatic cross-reference to the main entry should appear. The layout defined in the area Cross-reference also applies to the following areas: Abbreviation Alternative Irregular form Synonym Disallowed term User index 1 - User index 5 If required, you can define separate display options for each of these areas. Transit/TermStar NXT Reference Guide 91

8 Customising layouts 8.3.2 Layout editor interface When you open or create a layout, TermStar NXT opens the layout editor. The layout editor has its own menu items and toolbars which you can use to edit layouts (see Fig. 8-3) 1 2 1 3 5 4 Fig. 8-3: Elements of the layout editor: 1 Tab for layout editor, 2 Layout editor toolbar, 3 Area Available Fields, 4 Area Fields in Layout, 5 Area Preview The layout editor window consists of the following sections: Available fields All available fields, i.e. the fields which you have not yet selected for the layout (see section 8.3.3 Available Fields on page 93). Fields in layout Fields which have already been inserted into the layout. Preview A preview of the layout in which the layout editor shows the position and formatting of the fields. 92 Transit/TermStar NXT Reference Guide

8.3 Working with the layout editor 8 8.3.3 Available Fields The layout editor display available fields in the Available Fields section. The fields are arranged in a tree structure with four main layers, each of which has further sublayers. The arrangement corresponds to the hierarchy of the TermStar NXT fields (see TermStar NXT User's Guide). The four main units form the top layer of the tree structure of the available fields: Fig. 8-4: Top layer with the four main units - header, source language, target language and additional languages Header Header fields which belong to a data record. Source language Fields of the current source language. For example, if you select the Term, Context, Part of speech and Gender fields, TermStar NXT displays the source language with the contents of these fields. Target language Fields of the current target language. For example, if you select the Term, Context, Part of speech and Gender fields, TermStar NXT displays the target language with the contents of these fields. Additional languages Fields for other languages (i.e. for all the languages which are neither the source language nor target language). These fields are only relevant for dictionaries which contain entries in more than two languages. If you select these fields for your layout, you can also create and display multi-language dictionaries. Transit/TermStar NXT Reference Guide 93

8 Customising layouts 8.3.4 Structure of the language units The structure of the three language units (source language, target language and additional languages) is identical (Fig. 8-5, Structure of a language unit taking the source language as an example). 1 2 3 Fig. 8-5: Structure of a language unit 1 Language unit fields, 2 Entry fields, 3 Subentry fields Language fields The Multimedia, Info1 and Info2 language fields appear once per language in a data record. If, for example, a data record contains several entries in the target language English, you can enter a common definition which applies to all the English entries of a data record. Entry fields The Entry subgroup of a language unit contains the entry fields for this language. You can specify whether TermStar NXT should display several entries for the language unit. This means that if a data record has two entries in the German target language, for example, TermStar NXT displays both entries (see 8.5.3 Formatting entries and subentries on page 101). Language pseudo-field TermStar NXT should often display the language code of the entry. For this purpose, the language pseudo-field is available in the layout editor. This can be selected and edited like a normal entry file. 94 Transit/TermStar NXT Reference Guide

8.3 Working with the layout editor 8 If you use this field in the layout, TermStar NXT displays the corresponding languages in the field for a language variant. The display can be in the form of the 3-letter language code or a long name. The display mode depends on which variable has been inserted in the text field of the window Field properties (see section 8.5.4 Formatting the fields on page 103 or section 8.5.6 Variables on page 105). Multimedia field The field Multimedia provides the possibility to integrate multimedia files in a data record, thus enabling the illustration of any data record by linking to graphic, video or audio files. For each language unit, you can insert one multimedia file or a number of multimedia files. The field Multimedia contains reference paths for integrated graphic, video or audio files. Subentry fields Subentries with their own fields are available as subgroups in addition to the fields. You must add these subentries to the layout to be able to add and display subentries such as synonyms or alternatives to the current entry. A subentry has the same number of fields as the subgroup Entry. Just as for the entries, the Term field is the index field whose contents is sorted in the dictionary as an individual entry. Term field in the source language Please note that the Term field for the source language entry is mandatory in order to be able to save a layout. If this field is missing, TermStar NXT displays the following message: Layout <name> has been changed and is invalid. Continue editing? Add the Term field to be able to save the layout. Automatic cross-references in the cross-reference layout section If you insert the field of a subentry in the normal section of a layout, TermStar NXT displays this subentry within the main entry. In the cross-reference layout section, you specify how TermStar NXT displays the term of a subentry as a separate entry with an automatic cross-reference to the main entry (see section 8.5.7 Formatting automatic cross-references on page 105). Transit/TermStar NXT Reference Guide 95

8 Customising layouts 8.4 Editing the layout 8.4.1 Selecting and removing fields for the layout Before you can enter and display data in the dictionary, you have to select the fields in layout that you want to enter and whose contents TermStar NXT should display. Select the fields from the upper left-hand Available Fields section, so that the layout editor displays them in the lower left-hand Fields in layout section and in the Preview section. A field can only be selected once TermStar NXT can display each field only once in the layout. For this reason, TermStar NXT removes all the selected fields and all the fields inserted in the area Fields in Layout from the area Available Fields. How do I add a field to the layout? 1 Select the main layer required (header, source language, target language or additional languages). Click on the plus sign in front of the name of the main layer to make TermStar NXT display the main layers or subsections. Click on the plus sign in front of the name of the subsection to make TermStar NXT display the fields in a subsection. 2 Select the field which you want to add to the layout. If you wish to add all the fields in a layer, click on the layer name (e.g. Source language for all the source language fields). 3 To add the field(s), open the context menu using the right mouse button and select Add to layout. The layout editor adds this field to the Fields in layout section. If necessary, the layout editor adds the associated section or subsection. TermStar NXT displays the field(s) in the Preview section. Please refer to section 8.5 Specifying field properties on page 99 for information on how to format the field. 96 Transit/TermStar NXT Reference Guide

8.4 Editing the layout 8 How do I remove a field from the layout? 1 Select the field from the list in the Fields in layout section. To delete all the fields in a layer, select the name of the layer instead of an individual field. 2 To remove the field(s), open the context menu using the right mouse button and select Delete. Transit NXT removes the field from the Fields in layout and Preview section and adds it to the Available Fields section. 8.4.2 Inserting and deleting static text unit In addition to fields, you can also enter static text into the layout which TermStar NXT should display at certain positions. TermStar NXT adds these text units to the Fields in layout section. You can move them just like fields (see section 8.4.3 Specifying the order of fields on page 98). Text before or after a field In addition, you can also specify text to be placed before or after each field, layer or subgroup. The advantage of using static text units over text placed before or after a value is that you can move them as an individual unit or give them a separate indentation. The static text units are always available, regardless of whether or not a field is filled in. How do I insert a static text unit? 1 Select a field from the lists in the Fields in layout section below which you wish to insert a static text unit. 2 To add a static text unit, open the context menu using the right mouse button and select Insert text. The layout editor displays the text unit with the designation static text under the selected field. Please refer to section 8.5 Specifying field properties on page 99 for information on how to enter and format the text. How do I remove a static text unit from the layout? 1 From the list in the Fields in layout section, select the static text unit which you want to remove. 2 To remove the static text unit, open the context menu using the right mouse button and select Delete. 3 Transit NXT removes the text from the Fields in layout and Preview sections. Transit/TermStar NXT Reference Guide 97

8 Customising layouts 8.4.3 Specifying the order of fields TermStar NXT arranges the fields for the layout in the order in which you add them. You can, however, rearrange the order of fields afterwards. You can do this by moving the fields in the Fields in layout section. However, it is recommended to arrange the fields in the desired order as you add them. Tips for moving fields Always move a field underneath another field. Example: You want to place the part of speech field at the start of the source language layer i.e. before the term field. To do so, proceed as follows: Move the part of speech field under the field which until now was the first field in the source language layer, i.e. the term field. Then move the term field under the part of speech field. You can move complete layers. In order to do this, you must move a layer onto another layer of the same hierarchical level (e.g. source language onto header, to move it below the header). Fields can only be moved within their own layer. This means that you cannot move any header fields into the source language layer. Nor is it possible to move one language layer onto another. This means that all the fields for a language always remain together. How do I rearrange the order of fields? 1 Select a field from the list in the Fields in layout section. 2 Click on the field and hold down the mouse button to drag it up or down. 98 Transit/TermStar NXT Reference Guide

8.5 Specifying field properties 8 In doing so, the layout editor also moves the field icon (Fig. 8-6). Fig. 8-6: Moving fields in the layout editor 3 Drag the field over another field and release the mouse button. The layout editor positions the moved field below the field selected. 8.5 Specifying field properties 8.5.1 Overview The window Field properties window opens automatically when you launch the layout editor (Fig. 8-7). You can format a field or static text using this window. 1 2 3 Fig. 8-7: Layout editor: The Field properties window: 1 Text before the field, 2 Field name or fixed text, 3 Text after the field Transit/TermStar NXT Reference Guide 99

8 Customising layouts You can leave this window open the whole time so you can format the fields. If you select a field from the Fields in layout section, the layout editor displays the formatting of the field in this window. Depending on the type of field or text selected, the layout editor displays different options in the Field properties window: Units (header, source language, target language, additional languages) see section 8.5.2 Formatting units on page 100 Subgroups (entries, subentries) see section 8.5.3 Formatting entries and subentries on page 101 Fields see section 8.5.4 Formatting the fields on page 103 Static texts see section 8.5.5 Entering and formatting static text units on page 104 To close the window, click Close. To re-open the window, please proceed as follows. How do I open the Field properties window? 1 Select a field or a static text unit in the Fields in layout or Preview section. 2 To open the Field properties window, open the context menu using the right mouse button and select Properties. Alternatively, you can also open this window via the toolbar of the layout editor. Transit NXT displays the Field properties window showing the current settings for the field or static text unit. 8.5.2 Formatting units For each of the four units (header, source language, target language, additional languages), you can specify texts or characters which frame all the fields of this unit (Fig. 8-8, table 8-1). Fig. 8-8: Field properties window for main units 100 Transit/TermStar NXT Reference Guide

8.5 Specifying field properties 8 Range Setting Meaning Text before Text which TermStar NXT displays in front of the entries of a unit, e.g. in front of the source language. Font Spacing The font, font style, size and effects of the text in front of the unit. Spacing to the previous field in pixels. Text after Text that TermStar NXT displays after the entries for a unit, e.g. after the source language (\n generates a line break, \f displays the field name, see also Tab. 8-5: on page 105). Font Spacing The font, font style, size and effects of the text after the unit. Spacing to the last unit field in pixels. Tab. 8-1: Formatting the main units 8.5.3 Formatting entries and subentries You can define text or characters for each entry and subentry which frame all the fields of this entry (Fig. 8-9, table 8-2). Fig. 8-9: Field properties window for entries Transit/TermStar NXT Reference Guide 101

8 Customising layouts Range Setting Meaning Text before Text which TermStar NXT displays in front of the fields of the entry. Font Spacing The font, font style, size and effects of the text in front of the entry. Spacing to the previous field in pixels. Text Text that TermStar NXT shows between several entries of a data record. Font Spacing The font, font style, size and effects of the text in front of the entry. Distance between several entries of a data record. Text after Text which TermStar NXT displays after the fields of an entry. Font Spacing The font, font style, size and effects of the text after the entry. Spacing to the last entry field in pixels. Option Repeatable TermStar NXT displays all the entries of a language in the same data record. Example: ENG: carrot DEU: Möhre DEU: Karotte If this option is not selected, TermStar NXT only displays one entry: ENG: carrot DEU: Möhre You can deselect this option for the source-language entries since TermStar NXT displays each entry in the dictionary anyway. Example: DEU: Möhre ENG: carrot Tab. 8-2: Formatting an entry DEU: Karotte ENG: carrot 102 Transit/TermStar NXT Reference Guide

8.5 Specifying field properties 8 8.5.4 Formatting the fields You can use the field options to determine the font formatting, spacing, indentation and before and after texts for each field (Fig. 8-10, table 8-3). Fig. 8-10: Field properties window for fields Range Setting Meaning Text before Text which TermStar NXT displays in front of the contents of the field, e.g. a designation such as Gender. Font Spacing Font, font style, size and effects of the text in front of the field contents. Spacing to the previous field in pixels. Text Layer and name of the field selected, e.g. <Entry.Context>. Cannot be edited. Font Spacing The font, font style, size and effects of the field contents. Spacing in pixels to the previous field or (if present) to the text in front of the field contents. Text after Text which TermStar NXT displays after the contents of the field. Font The font, font style, size and effects of the text after the field contents. Tab. 8-3: Formatting a field Transit/TermStar NXT Reference Guide 103

8 Customising layouts Range Setting Meaning Spacing Spacing to the field contents in pixels. Option Indentation Spacing to the left margin in pixels. Tab. 8-3: Formatting a field (cont.) 8.5.5 Entering and formatting static text units You can use the options for static text units to determine the contents, font formatting, spacing and indentation for static text units (Fig. 8-11, table 8-4). Fig. 8-11: Field propertieswindow for static text units Range Settings Meaning Text Text or characters which TermStar NXT displays as a static text unit. Font Spacing Font, font style, size and effects of the text. Spacing to the previous field in pixels. Options Indentation Spacing to the left margin in pixels. Tab. 8-4: Formatting a static text unit 104 Transit/TermStar NXT Reference Guide

8.5 Specifying field properties 8 8.5.6 Variables You can also use the following variables as text before, text and text after (see table 8-5). Variable Meaning \a Abbreviated field name TermStar NXT shows abbreviated field names in the respective dialogue language (see table 7-4 on page 85). Example: Abbr. for Abbreviations \c 3-letter language code \f Field name TermStar NXT shows the field name in the respective dialogue language or uses field names that you have changed (see section 9.2 Modifying field names on page 111). \l Language name TermStar NXT shows the name of the language in the respective dialogue language. \n Line break Tab. 8-5: Variables for text fields 8.5.7 Formatting automatic cross-references TermStar NXT displays subentries (synonyms, alternatives, abbreviations, irregular forms, user indices and disallowed terms) in the dictionary as individual entries which point to the main entry by means of a cross-reference. A separate area is available in each layout where you can specify the display for the subentries and their cross-references. This area is only relevant for displaying subentries and does not affect the display of the actual main entries. You can select and format the fields in exactly the same way as you would the normal part of the layout. Transit/TermStar NXT Reference Guide 105

8 Customising layouts However, please note the following special aspects: Additional units (Fig. 8-12): Fig. 8-12: List box Units The units Cross-reference, Abbreviation, Alternative, Irregular from, Synonym, Disallowed term and User index 1-5 correspond to the subentries in the normal layout section. Their Term field contains the synonyms, alternatives etc. As this field displays the index field for the subentries, this field is mandatory for these sections of the layout. Source language The source language Term field as the index field for the main entry creates the cross-reference to the main entry. This field must therefore be included if you wish to create an automatic cross-reference. The remaining fields of the source language correspond to those in the main entry. You can add them if TermStar NXT should display further fields of the main entry for the subentry without the user having to use the cross-reference. Target language You can use these fields to have all the target language data displayed. However, the automatic cross-reference can only be used in the source language because only this language is indexed in the dictionary. Additional languages The Additional languages layer is not available for subentries. 106 Transit/TermStar NXT Reference Guide

8.5 Specifying field properties 8 How do I edit the cross-reference section of the layout? 1 To open the cross-reference section of the currently open layout, in the list box in the toolbar select the option Cross-reference (Fig. 8-13). Fig. 8-13: Layout editor, list box TermStar NXT displays the available fields and the fields you have selected for the cross-reference section of the layout. 2 Add the Term field from the Cross-reference layer if this field does not already exist in the layout. 3 Add the Term field from the Source language layer. This field generates an automatic cross-reference to the main entry for the subentry. 4 In the Field properties window for this field, enter a string as Text before which TermStar NXT should display in front of the cross-reference (e.g. see or --->). 5 Format the field so that it can be recognised as a cross-reference. To do so, select the font colour green, for example. 6 Add additional fields, if necessary. TermStar NXT uses this layout for subentries with an automatic cross-reference to the main entry. Transit/TermStar NXT Reference Guide 107

8 Customising layouts 8.5.8 General layout settings You can make settings for each layout which control the general appearance of the layout. This is for both parts of a layout ( normal and cross-reference ). You have the following options here (table 8-6): Range Display graphics Cross-reference colour Spacing Meaning Displays the graphics which are linked in the Graphics header field: Do not scale Scale for screen width Shrink image Show file name Colour in which TermStar NXT displays the manual cross-references. You created manual cross-references using the Create cross-reference or Create special reference function. This does not affect the display of automatic crossreferences. You can specify this as explained in section 8.5.7 Formatting automatic cross-references on page 105. You can specify the following distances: Data record distance distance between two data records Left margin distance to the left margin of the book page Right margin distance to the right margin of the book page Tab. 8-6: General layout settings 108 Transit/TermStar NXT Reference Guide

8.5 Specifying field properties 8 Range Show data records Date/time format Meaning Display for data records: One data record per page TermStar NXT displays each data record on a new page. Especially useful for layouts for the right-hand page. For example, you can display word pairs on the left-hand page and detailed information about the data record selected on the right-hand page. Show empty fields TermStar NXT displays the fields of the layout even if they do not contain any information. Separator separator between units, fields and field parts (text before, text, text after) TermStar NXT displays the separator in the layout preview and when the layout is used in edit mode. Displays the date fields: Short format TermStar NXT displays the date in short format (e.g. 29.05.2002 instead of Thursday, 29th May 2002) Show time TermStar NXT displays the time as well as the date. Tab. 8-6: General layout settings (cont.) Transit/TermStar NXT Reference Guide 109

8 Customising layouts How do I change the layout settings? 1 Open the layout if it is no longer open. 2 In the toolbar of the layout editor, click on the button Layout settings. TermStar NXT displays the Layout options window: Fig. 8-14: Layout options window 3 Select the settings you require (see table 8-6) and confirm the settings with OK. Transit NXT closes the window and applies the settings immediately. You can see some of the effects of your settings already in the Preview section. 110 Transit/TermStar NXT Reference Guide

9 Customising dictionaries 9 9 Customising dictionaries 9.1 Overview You can customise TermStar NXT dictionaries to optimise your work with the dictionaries. You have the following options here: Modifying field names (section 9.2 on page 111) Setting graphics file access (section 9.3 on page 116) Specifying cross-reference separators (section 9.4 on page 117) Dictionaries protected by passwords If you want to change settings of a dictionary that is password-protected, TermStar NXT displays the Enter password window. In this case, enter the master password or a user password with administrative rights (see TermStar NXT User's Guide). 9.2 Modifying field names 9.2.1 Overview TermStar NXT uses specified field names for the fields (see section 7 Fields in the TermStar dictionary on page 78). However, you can still change the fields names whenever you want without influencing the operation of the fields: Administration fields are filled out automatically, cross-reference fields function as before. This is practical when you want to use certain fields (e.g. User1, User2) for specific purposes. You can rename the fields so that the user recognises what the fields are used for. You can change field names for language and input fields for all languages or for certain languages: If you change field names for all languages, TermStar NXT shows the same field name for all languages (section 9.2.2 Changing field names for all languages on page 112). If you change the field names for a specific language, TermStar NXT shows the field name according to the language of the input (section 9.2.3 Changing field names for specific languages on page 113). Transit/TermStar NXT Reference Guide 111

9 Customising dictionaries If you have changed field names, you can also return them to the original TermStar NXT field name (section 9.2.4 Resetting changed field names on page 114). Furthermore, you also have the option of adding changed field names from other dictionaries (section 9.2.5 Transferring field names from other dictionaries on page 115). Display of field names in TermStar NXT Use the variable \f in the dictionary layouts so that TermStar NXT displays the field names: TermStar NXT shows unchanged field names in the TermStar NXT dialogue language. If, for example, you have set English as the dialogue language, TermStar NXT displays the field names in English; when the dialogue language is German, field names are also in German. If you have changed field names for all languages (see section 9.2.2 Changing field names for all languages on page 112), TermStar NXT shows the changed field name irrespective of the dialogue language. If you have changed field names for a specific language (see section 9.2.3 Changing field names for specific languages on page 113), TermStar NXT shows the field name according to the language of the input. For more detailed information on variables in the dictionary layout, please refer to section 8.5.6 Variables on page 105. 9.2.2 Changing field names for all languages How do I change field names? 1 Select Dictionaries Dictionaries/Databases Manage dictionaries/databases from the resource bar. TermStar NXT displays the TermStar database expert window with a list of the existing databases. 2 Click on the plus sign next to a database name to make TermStar NXT display the dictionaries in a database. TermStar NXT then shows the dictionaries in the database. 3 Select the dictionary whose field name you wish to change and click on Settings. TermStar NXT displays the Settings window. 4 Select the Field names tab. TermStar NXT displays a table with field names: Standard field name column original field names User-defined field name column changed field names 5 To specify a new field name for a field, select the field and enter the new name in the User-defined field name field. 112 Transit/TermStar NXT Reference Guide

9.2 Modifying field names 9 Press the TAB key so that TermStar NXT shows the new name in the Userdefined field name column. 6 Confirm your changes with OK. TermStar NXT closes the Settings window and applies the changed field names. Click Cancel to exit the TermStar NXT dictionary expert. 9.2.3 Changing field names for specific languages You can prepare a dictionary for users with different native languages by specifying separate field names for each language. How do I change field names for a certain language? 1 Select Dictionaries Dictionaries/Databases Manage dictionaries/databases from the resource bar. TermStar NXT displays the TermStar database expert window with a list of the existing databases. 2 Click on the plus sign next to a database name to make TermStar NXT display the dictionaries in a database. TermStar NXT then shows the dictionaries in the database. 3 Select the dictionary whose field name you wish to change and click on Settings. TermStar NXT displays the Settings window. 4 Select the Field names tab. TermStar NXT displays a table with field names: Standard field name column original field names User-defined field name column changed field names 5 To specify a new field name for a field, select the field and enter the new name in the User-defined field name field. 6 To specify a field name for a certain language, click on Add. TermStar NXT displays the Add fields window. From the Fields list, select the field whose name you want to change. From the Languages list, select the language for which you want to change the field name. Confirm your selection with OK. TermStar NXT closes the Add fields window and shows the field in the table of the Field names tab. 7 To specify a new field name for a field, select the field and enter the new name in the User-defined field name field. Press the TAB key so that TermStar NXT shows the new name in the Userdefined field name column. Transit/TermStar NXT Reference Guide 113

9 Customising dictionaries 8 Confirm your changes with OK. TermStar NXT closes the Settings window and applies the changed field name in the specified language. Click Cancel to exit the TermStar NXT dictionary expert. 9.2.4 Resetting changed field names If you have changed field names, you can also return them to the original TermStar NXT field names. How do I return the field name back to its original name? 1 Select Dictionaries Dictionaries/Databases Manage dictionaries/databases from the resource bar. TermStar NXT displays the TermStar database expert window with a list of the existing databases. 2 Click on the plus sign next to a database name to make TermStar NXT display the dictionaries in a database. TermStar NXT then shows the dictionaries in the database. 3 Select the dictionary whose field name you wish to reset and click on Settings. TermStar NXT displays the Settings window. 4 Select the Field names tab. TermStar NXT displays a table with field names: Standard field name column original field names User-defined field name column changed field names 5 To return the changed field name for a field to its original name, select the field name and click on Delete. TermStar NXT removes the changed name from the User-defined field name column. 6 Confirm your changes with OK. TermStar NXT closes the Settings window and starts using the original field name again. Click Cancel to exit the TermStar NXT dictionary expert. 114 Transit/TermStar NXT Reference Guide

9.2 Modifying field names 9 9.2.5 Transferring field names from other dictionaries You can transfer renamed field names from another dictionary. This means, for example, that you use the same renamed field names for all dictionaries. How do I transfer field names from another dictionary? 1 Select Dictionaries Dictionaries/Databases Manage dictionaries/databases from the resource bar. TermStar NXT displays the TermStar database expert window with a list of the existing databases. 2 Click on the plus sign next to a database name to make TermStar NXT display the dictionaries in a database. TermStar NXT then shows the dictionaries in the database. 3 Select the dictionary from which you want to transfer the field names and click on Settings. TermStar NXT displays the Settings window. 4 Select the Field names tab. 5 To transfer field names from another dictionary, click on Take. TermStar NXT displays a list of all existing dictionaries. 6 Select the dictionary from which you want to transfer the field names and confirm your selection with OK. TermStar NXT displays the field names of the dictionary so that you can check them. 7 Decide whether you want to take over the displayed field names: Click on OK to take over all names. Click on Cancel if you do not want to take over the field names. TermStar NXT takes over the field names. If you have already changed field names in the target dictionary, TermStar NXT displays a prompt for each field asking whether it should overwrite the field names that have already been changed. 8 You decide, if necessary for each field, whether TermStar NXT should overwrite the field names that have been changed. TermStar NXT now shows the new names in the User-defined field name column. 9 Confirm your changes with OK. TermStar NXT closes the Settings window and applies the changed field name in the specified language. Click Cancel to exit the TermStar NXT dictionary expert. Transit/TermStar NXT Reference Guide 115

9 Customising dictionaries 9.3 Setting graphics file access You can specify how TermStar NXT accesses graphics that you include in a dictionary: Relative path All graphics files are located in a folder and its subfolder. Example: The files are in the C:\transit nxt\graphics folder. You specify C:\transit nxt\graphics as the relative path. If you insert a graphic from this folder, TermStar NXT only saves the name of the graphic (and subfolder if applicable). Example: TermStar NXT saves the graphic C:\transit nxt\graphics\ bitmap\bank.bmp as follows: bitmap\bank.bmp. If you move the graphics files to another drive, you only have to customise the relative path. Example: You move the graphics files to D:\doku\graphics. Then you adjust the relative path for the graphics file access to D:\doku\graphics. Absolute path For each graphics file included, TermStar NXT saves the full access path. Example: C:\transit nxt\graphics\bitmap\bank.bmp. If you move the graphics, you have to customise the access path for each individual graphic. Graphics on different drives If you incorporate graphics that are on different drives, you will have to select the absolute access path. Otherwise TermStar NXT cannot correctly access the files. How do I set the graphic file access? 1 Select Dictionaries Dictionaries/Databases Manage dictionaries/databases from the resource bar. TermStar NXT displays the TermStar database expert window with a list of the existing databases. 2 Click on the plus sign next to a database name to make TermStar NXT display the dictionaries in a database. TermStar NXT then shows the dictionaries in the database. 3 Select the dictionary whose graphics file access you wish to specify and click on Settings. 4 Select the Miscellaneous tab. 5 Specify how TermStar NXT should access graphic files in the Multi media access range: 116 Transit/TermStar NXT Reference Guide

9.4 Specifying cross-reference separators 9 Relative path All graphics files are located in a folder and its subfolder. To specify the folder, click on Browse. TermStar NXT displays the Relative path window. Select the folder which contains graphics or one where the subfolder contains graphics. Confirm your selection with OK. In the Relative path field of the Miscellaneous tab, TermStar NXT shows the path of the selected folder. Absolute path TermStar NXT saves the full access path for each incorporated graphics file. 6 Confirm your changes with OK. TermStar NXT closes the Settings window and applies the changed settings. Click Cancel to exit the TermStar NXT dictionary expert. 9.4 Specifying cross-reference separators In the Cross-reference field, you can enter several cross-references that refer to various entries. You separate the different cross-references from one another by means of a so-called Cross-reference separator. The standard cross-reference-separator is a semicolon (;). If, however, the semicolon occurs in text within the cross-reference, you cannot use it simultaneously as a cross-reference separator. In this case, you can specify another character as a cross-reference separator. How do I specify the cross-reference separator? 1 Select Dictionaries Dictionaries/Databases Manage dictionaries/databases from the resource bar. TermStar NXT displays the TermStar database expert window with a list of the existing databases. 2 Click on the plus sign next to a database name to make TermStar NXT display the dictionaries in a database. TermStar NXT then shows the dictionaries in the database. 3 Select the dictionary whose graphics file access you wish to specify and click on Settings. 4 Select the Miscellaneous tab. 5 Enter the desired character in the Cross-reference separator field. 6 Confirm your changes with OK. TermStar NXT closes the Settings window and applies the changed settings. Click Cancel to exit the TermStar NXT dictionary expert. Transit/TermStar NXT Reference Guide 117

9 Customising dictionaries 9.5 Specify additional sort field In the Additional sorting field field, you can select a field that determines the sorting within identical terms. How do I specify an additional sort field? 1 Select Dictionaries Dictionaries/Databases Manage dictionaries/databases from the resource bar. TermStar NXT displays the TermStar database expert window with a list of the existing databases. 2 Click on the plus sign next to a database name to make TermStar NXT display the dictionaries in a database. TermStar NXT then shows the dictionaries in the database. 3 Select the dictionary for which you want to define an additional sorting field and click on Settings. 4 Select the Miscellaneous tab. 5 Select the desired field from the list in the Additional sorting field section. 6 Confirm your changes with OK. TermStar NXT closes the Settings window and applies the extended sorting. Click Cancel to exit the TermStar NXT dictionary expert. 118 Transit/TermStar NXT Reference Guide

10 Spellcheck dictionaries 10 10 Spellcheck dictionaries Transit NXT uses open source dictionaries as the basis for spellchecking. Please refer to the Transit NXT User's Guide for information on how to run the spellcheck. The Transit NXT installation package includes a great number of freely available, HunSpell compatible spellcheck dictionaries. OpenOffice.org and spellcheck dictionaries The OpenOffice.org project is an open source project that aims to develop an openaccess office suite (including word processor, spreadsheet, presentation application, etc.). You can find more details on the OpenOffice.org website (http:// extensions.services.openoffice.org/en/dictionaries). The HunSpell interface is licenced under LGPL 3.0. Tab. 10-1 contains a complete list of all supported languages for which freely available, HunSpell compatible spellcheck dictionaries are installed. The required files are installed in the spell folder of the Transit NXT installation (see tab. 10-1). Existing files are not overwritten during update installation The files are installed only if they do not yet exist in the spell folder of the Transit NXT installation. This ensures that spellcheck dictionaries already installed by the user are preserved during an update of Transit NXT. Transit/TermStar NXT Reference Guide 119

10 Spellcheck dictionaries Language Language variant Original name of the dictionary Afrikaans Albanian af_za.dic af_za.aff sq_al.dic sq_al.aff Arabic Egypt ar.dic ar.aff Saudi Arabia ar.dic ar.aff Azerbaijanian Latin az.dic az.aff Basque Bulgarian Catalan Croatian Czech Danish Dutch eu.dic eu.aff bg_bg.dic bg_bg.aff catalan.dic catalan.aff hr_hr.dic hr_hr.aff cs_cz.dic cs_cz.aff da_dk.dic da_dk.aff nl_nl.dic nl_nl.aff English US en_us.dic en_us.aff Estonian Farsi UK Canada Australia New Zealand South Africa Tab. 10-1: Spellcheck dictionaries in Transit NXT en_gb.dic en_gb.aff en_ca.dic en_ca.aff en_au.dic en_au.aff en_nz.dic en_nz.aff en_za.dic en_za.aff et_ee.dic et_ee.aff fa.dic fa.aff File name used in Transit NXT af_.dic af_.aff ar_eg.dic ar_eg.aff ar_sa.dic ar_sa.aff az_az.dic az_az.aff eu_.dic eu_.aff ca_.dic ca_.aff fa_.dic fa_.aff 120 Transit/TermStar NXT Reference Guide

10 Spellcheck dictionaries 10 Language Language variant Original name of the dictionary Faeroese Finnish fo_fo.dic fo_fo.aff fi_fl.dic fi_fl.aff French France fr-moderne.dic fr-moderne.aff Galician gl_es.dic gl_es.aff German Germany de_de.dic de_de.aff Greek Gujarati Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Kannada Khmer Latvian Lithuanian Switzerland Austria de_ch.dic de_ch.aff de_at.dic de_at.aff el_gr.dic el_gr.aff gu_in.dic gu_in.aff he_il.dic he_il.aff hi_in.dic hi_in.aff hu_hu.dic hu_hu.aff is_is.dic is_is.aff id_id.dic id_id.aff ga_ie.dic ga_ie.aff it_it.dic it_it.aff kn_in.dic kn_in.aff km_kh.dic km_kh.aff lv_lv.dic lv_lv.aff lt_lt.dic lt_lt.aff Tab. 10-1: Spellcheck dictionaries in Transit NXT (cont.) File name used in Transit NXT fo_.dic fo_.aff fr_fr.dic fr_fr.aff iw_il.dic iw_il.aff gd_ie.dic gd_ie.aff kh_kh.dic kh_kh.aff Transit/TermStar NXT Reference Guide 121

10 Spellcheck dictionaries Language Language variant Original name of the dictionary Malay Malayalam Maltese Marathi Mongolian ms_my.dic ms_my.aff ml_in.dic ml_in.aff mt.dic mt.aff mr_in.dic mr_in.aff mn_mn.dic mn_mn.aff Norwegian Bokmal nb_no.dic nb_no.aff Polish Nynorsk nn_no.dic nn_no.aff pl_pl.dic pl_pl.aff Portuguese European pt_pt.dic pt_pt.aff Romanian Russian Brazilian pt_br.dic pt_br.aff ro_ro.dic ro_ro.aff ru_ru.dic ru_ru.aff Serbian Latin sr-latn.dic sr-latn.aff Slovakian Slovenian Sotho (Northern) Sotho (Southern) Cyrillic sr_yu.dic sr_yu.aff sk_sk.dic sk_sk.aff sl_si.dic sl_si.aff ns_za.dic ns_za.aff st_za.dic st_za.aff Tab. 10-1: Spellcheck dictionaries in Transit NXT (cont.) File name used in Transit NXT mt_mt.dic mt_mt.aff no_no.dic no_no.aff no_ny.dic no_ny.aff sr_cs.dic sr_cs.aff sr_yu.dic sr_yu.aff 122 Transit/TermStar NXT Reference Guide

10 Spellcheck dictionaries 10 Language Language variant Original name of the dictionary File name used in Transit NXT Spanish Spain es_es.dic es_es.aff Swahili Swedish Argentina Bolivia Costa Rica Chile Dom. Rep. Ecuador El Salvador Guatemala Honduras Colombia Mexico Nicaragua Panama Paraguay Peru Puerto Rico Uruguay es_ar.dic es_ar.aff es_bo.dic es_bo.aff es_cr.dic es_cr.aff es_cl.dic es_cl.aff es_do.dic es_do.aff es_ec.dic es_ec.aff es_sv.dic es_sv.aff es_gt.dic es_gt.aff es_hn.dic es_hn.aff es_co.dic es_co.aff es_mx.dic es_mx.aff es_ni.dic es_ni.aff es_pa.dic es_pa.aff es_py.dic es_py.aff es_pe.dic es_pe.aff es_pr.dic es_pr.aff es_uy.dic es_uy.aff sw_ke.dic sw_ke.aff sv_se.dic sv_se.aff Tab. 10-1: Spellcheck dictionaries in Transit NXT (cont.) Transit/TermStar NXT Reference Guide 123

10 Spellcheck dictionaries Language Language variant Original name of the dictionary Tamil Thai Tsonga Tswana Turkish Ukrainian ta.dic ta.aff th_th.dic th_th.aff ts_za.dic ts_za.aff ts_za.dic ts_za.aff tr.dic tr.aff uk_ua.dic uk_ua.aff Urdu Pakistan ur.dic ur.aff Uzbek Cyrillic uz.dic uz.aff Vietnamese Welsh Xhosa Zulu vi_vn.dic vi_vn.aff cy_gb.dic cy_gb.aff xh_za.dic xh_za.aff zu_za.dic zu_za.aff Tab. 10-1: Spellcheck dictionaries in Transit NXT (cont.) File name used in Transit NXT ta_in.dic ta_in.aff tn_bw.dic tn_bw.aff tr_tr.dic tr_tr.aff ur_pk.dic ur_pk.aff uz_uz.dic uz_uz.aff cy_.dic cy_.aff If required, you have the option to add freely available, HunSpell compatible spellcheck dictionaries for additional languages taken from the OpenOffice.org project or other sources or update already installed spellcheck dictionaries if newer versions are available. In this case, you require two files of the same name with the file extensions.dic and.aff: a dictionary file with the extension.dic an affix file with the extension.aff Download these files from the website of the OpenOffice.org organisation or from other sources and then extract them if necessary. 124 Transit/TermStar NXT Reference Guide

10.1 Installing a spellcheck dictionary 10 File names of aff and dic files For Transit NXT to recognise the language and language variant of the spellcheck dictionary, the aff and dic files must be named according to the following rule: <ISO language code>_<iso country code>.aff and <ISO language code>_<iso country code>.dic Examples: English (UK): en_gb.aff and en_gb.dic English (US): en_us.aff and en_us.dic In most cases, the dictionary files you have downloaded are named as required for use with Transit NXT. However, in some languages and sources the file name deviate from the naming convention. In such cases, rename the aff and dic files accordingly. For example, the ISO country code is not used in some individual language variants (see tab. 10-1): Example: Catalan: ca_.aff and ca_.dic 10.1 Installing a spellcheck dictionary 1 If Transit NXT is running, close it. 2 Copy the aff and dic files to the spell folder in your Transit NXT installation folder. If you are using Windows Vista, Windows 7 or Windows 8, determine the storage location of the spell folder using an entry in the starte.ini file in your Transit NXT installation folder. As a rule, this is in the directory C:\Program Files\Transit NXT\bin. In the starte.ini file in the section PATHS, you will find an entry beginning with SPELL which specifies a path. Example: SPELL=C:\Users\Public\Documents\Transit NXT\spell The next time you start Transit NXT, the newly added or updated spellcheck dictionary will be available for use in the spellcheck. Please refer to the Transit NXT User's Guide for information on how to run the spellcheck. Transit/TermStar NXT Reference Guide 125

10 Spellcheck dictionaries 10.1.1 Uninstalling spellcheck dictionaries If you want to deinstall a spellcheck dictionary you installed yourself, simply remove the.aff and.dic files of the corresponding spellcheck dictionary from the spell folder of your Transit NXT installation. We recommend that you do not delete the files but move them to a different folder. In that way, you can copy them back again later on if you decide to use the spellcheck dictionary again. 126 Transit/TermStar NXT Reference Guide

11 Managing database links 11 11 Managing database links 11.1 Overview TermStar NXT is linked to the databases in which dictionaries are stored by means of database links. You can manage the links using a wide range of functions: Creating a database link (section 11.2 on page 127) Deleting a database link (section 11.3 on page 137) Transferring database connections to other computers (section 11.4 on page 138) Deleting incorrect database links (section 11.5 on page 141) Compressing databases and dictionaries (section 11.6 on page 142) Database driver information (section 11.7 on page 142) 11.2 Creating a database link 11.2.1 Overview If you want to work with a database and its dictionaries, a database link must first exist so that TermStar NXT can access the data. If you create a new database using TermStar NXT, TermStar NXT automatically creates the database link so you do not have to worry about it. However, you must create the database link if you are copying an existing database to your computer from another computer, for example. If more than one driver is installed on your computer for ODBC access to databases, you can select the driver TermStar NXT should use: Microsoft Access Standard TermStar databases, this driver is automatically installed with the installation of TermStar (see section 11.2.2 Connecting an MS Access database on page 128). MS SQL For SQL databases (see section 11.2.3 Connecting an MS SQL database on page 133). Link each database once only Make sure that you do not create more than one link to each database on your computer. Transit/TermStar NXT Reference Guide 127

11 Managing database links Use the name of the database as the name for the ODBC connection We strongly recommend that you use the name of the database as the name for your ODBC connection. In this way, you can easily recognise at any time which database link belongs to which database. What you need to know here: The DSN (Data Source Name) is a data structure describing the access data that Transit/TermStar NXT needs to setup a connection to a TermStar database. During database linking you can select the DSN type. Doing so, you determine where the DSNs are saved and to whom the particular database connection is available: DSNs can be saved in the registry of the local computer: User DSN The database connection is only available to you as the current user on the computer on which you setup the connection. System DSN The database connection is available to all users of the computer on which you setup the connection. DSNs can be saved as DSN files in the \config directory of the Transit/TermStar installation: File DSN (global scope) The DSN file is saved to the config\global folder. Thus, the database connection is available to all Transit users. File DSN (user scope) The DSN file is saved to the config\users\<user_name> folder. Thus, the database connection is available only to the current Transit user. For a network host installation or in case of individual workstations accessing common network resources, those DSN types offer the following advantages: The DSN files are saved centrally and can be managed centrally. Is is no longer necessary to setup each database connection on each client separately or to transfer them using ODBCDataSaver/ODBCDataLoader. The DSN files are subject to centralised data backup. This way, the database connections can be restored if necessary and do not have to be saved using ODBCDataSaver. 11.2.2 Connecting an MS Access database How do I connect an MS Access database? 1 Select Dictionaries Dictionaries / Databases Link database from the resource bar. 128 Transit/TermStar NXT Reference Guide

11.2 Creating a database link 11 If more than one driver is installed on your computer for ODBC access to databases, TermStar NXT displays the ODBC driver selection window containing a list of all drivers installed: Fig. 11-1: ODBC driver selection window, Access Database driver selected 2 For standard TermStar databases select the Access Database driver and confirm your choice by clicking Next. Transit/TermStar NXT Reference Guide 129

11 Managing database links TermStar NXT displays the Specify database file window: Fig. 11-2: Specify database file window, no database selected 3 Click on Browse to select the folder that contains the database file. TermStar NXT displays the window Open: Fig. 11-3: Open window 130 Transit/TermStar NXT Reference Guide

11.2 Creating a database link 11 4 Select the desired database and, if applicable, also the directory that contains the database and confirm your selection by clicking on Open. TermStar NXT displays the Specify database file window. TermStar NXT displays the path of the selected database file in the Database file field: Fig. 11-4: Specify database file window, database selected 5 Click on Next to confirm your selection. Transit/TermStar NXT Reference Guide 131

11 Managing database links TermStar NXT displays the ODBC connection window: Fig. 11-5: ODBC connection window with selected database 6 Enter the name for the ODBC connection. We recommend that you use the name of the database as the name for your ODBC connection. In this way, you can easily recognise which link belongs to which database file. However, if you still want to give the ODBC connection another name, change the name in the New ODBC connection field as required. 7 In the DSN type section, select the desired DSN type. For information on this selection see section What you need to know here: on page 128. 8 Confirm the name of the ODBC connection and the selected DSN type by clicking on Finish. TermStar NXT displays the following message: Database C:\Programs\Transit NXT\db\<file name> successfully linked. 9 Confirm the message by clicking on OK. The ODBC connection window will be closed automatically. TermStar NXT has established the database connection. You can now access the database. 132 Transit/TermStar NXT Reference Guide

11.2 Creating a database link 11 11.2.3 Connecting an MS SQL database How do I connect an MS SQL database? 1 Select Dictionaries Dictionaries / Databases Link database. If more than one driver is installed on your computer for ODBC access to databases, TermStar NXT displays the ODBC driver selection window containing a list of all drivers installed: Fig. 11-6: ODBC driver selection window, driver Microsoft SQL Server selected 2 For SQL databases select the Microsoft SQL Server driver and confirm your choice by clicking Next. TermStar NXT displays the Database server selection window (Fig. 11-7). In the Database servers list, TermStar NXT displays all the database servers which you can currently access. The servers in this list can depend on the configuration of the individual database servers. It can therefore occur that although a database server is available it is not displayed in the list. In this case, you have the possibility to enter the name of this database server directly in the Selected database server field. Transit/TermStar NXT Reference Guide 133

11 Managing database links Fig. 11-7: Database server selection window 3 Specify the access to the database server whose database you want to connect to: Click in the Database servers list on the desired database server: With the entry (local), you select the database server on your own computer, if present. If you select a database server on another computer, please remember that you only have access when the other computer is running. TermStar NXT displays the selected database server in the Selected database server field. In the User name and Password fields, enter the user name and the password which gives you access to the database server selected. Select the option Trusted connection if you want to connect a local database server or if you are sure that the database server you have selected accepts this connection. If you select this option, it is not required to enter a user name and password. The relevant fields, User name and Password, are then greyed out. 4 Click Next to confirm the information entered. 134 Transit/TermStar NXT Reference Guide

11.2 Creating a database link 11 TermStar NXT displays the Specify database window. In the Databases list, TermStar NXT displays all the databases of the database server selected: Fig. 11-8: Specify database file window 5 From the Databases list, select the database to which you want to establish a link. Confirm your selection by clicking on Next. Transit/TermStar NXT Reference Guide 135

11 Managing database links TermStar NXT displays the ODBC connection window. This is where you can specify the name of the ODBC connection: Fig. 11-9: ODBC connection window 6 Enter the name for the ODBC connection. We recommend that you use the same name for the ODBC connection and the database. In this way, you can easily recognise which link belongs to which database file. However, if you still want to give the ODBC connection another name, change the name in the New ODBC connection field as required. 7 In the DSN type section, select the desired DSN type. For information on this selection see section What you need to know here: on page 128. 8 Confirm the name of the ODBC connection and the selected DSN type and establish the database connection by clicking on Finish. TermStar NXT displays the following message: Database <file name> successfully linked. 9 Confirm the message by clicking on OK. The ODBC connection window will be closed automatically. TermStar NXT has established the database connection. You can now access the database. 136 Transit/TermStar NXT Reference Guide

11.3 Deleting a database link 11 11.3 Deleting a database link You can use the TermStar database expert window to delete the link to a database. The database file itself will not be deleted. You can re-link at a later date if necessary (see section 11.2 Creating a database link on page 127). When deleting, select the database link not the dictionary! Make sure when you are deleting that you select the whole database in the TermStar Dictionary Expert window. If you only select a dictionary in a database, the whole dictionary and its contents will be deleted irreversibly! How do I delete a database link? 1 Select Dictionaries Dictionaries/databases Manage dictionaries/databases from the resource bar. TermStar NXT displays the TermStar database expert window containing a list of all database connections available: Fig. 11-10: TermStar database expert window 2 Select the database connection which you want to delete. Make sure when you are deleting that you select the whole database not a single dictionary in a database. If you only select a dictionary in a database, the whole dictionary and its contents will be deleted irreversibly! 3 Click Delete to confirm your selection. Transit/TermStar NXT Reference Guide 137

11 Managing database links TermStar NXT displays the following message: Are you sure you want to delete the database link <file name>? 4 Confirm the message by clicking Yes if you want to delete the link. The link remains if you click No or Cancel. Confirm the message by clicking Yes to delete the link. TermStar NXT no longer displays this link in the list of available databases. Click Cancel to exit the TermStar NXT dictionary expert. 11.4 Transferring database connections to other computers If you have set up a TermStar database on the server, you must set up a database connection to the server database on each client machine so that all TermStar NXT users can access the database. To simplify that process, you can transfer the database connection settings from one computer to another. In other words, you set up the database connection on one computer and then transfer the settings to the other computers (destination computers). There are two programs available for this: ODBCDataSaver.exe You use this program on the first computer to save the database connection settings to a file. ODBCDataLoader.exe You use this program on the destination computer to set up the database connection using the saved settings. SQL database support In order that a connection to an SQL database can be correctly established, the appropriate support (e.g. for MS SQL or Oracle) must be installed on the destination computers concerned. Connection settings for MS Access databases Transferring the connection settings for MS Access databases only makes sense if the path and file name for the database (mdb file) are identical on all computers. This is generally true in the following cases: Network database All computers use the same path to access the same centrally located mdb file. Local database Each computer accesses its own local mdb file. The drive designation, path and file name are the same on each computer. 138 Transit/TermStar NXT Reference Guide

11.4 Transferring database connections to other computers 11 How do I save the ODBC settings to a file? 1 Start the program ODBCDataServer.exe by double-clicking it. The program is located in the \bin folder of the Transit/TermStar NXT installation. The program displays the following window showing all connections to SQL databases: Fig. 11-11: The program shows all the database connections In order to display connections to MS Access databases as well, select Show also Microsoft Access data sources. You can then save and transfer settings for MS Access databases as well. 2 Select the connections that you want to transfer. 3 Click on Write to file to save the connection settings. TermStar NXT displays the Save as window: Fig. 11-12: Save as window Transit/TermStar NXT Reference Guide 139

11 Managing database links 4 You have the following options for saving the settings: Save the settings in the specified file odbc_data_exchange.ini in the \bin folder. If a file of that name already exists in the \bin folder, the program displays a message informing you that it will be overwritten. To overwrite the existing file and save the new connection data, acknowledge the message by clicking Yes. The old version of the file is overwritten. Save the settings in the specified file odbc_data_exchange.ini in another folder of your choice. To do so, select the desired folder and click on Save to save the file. Save the settings in a new file by renaming the odbc_data_exchange.ini file. At File name, enter a new file name and, if applicable, select another folder in which to save the file. Click on Save to confirm your entry. 5 To exit the program, click the X on the window title bar. The program saves the settings for the selected database connections to the corresponding ini file so that you can set up those connections on another computer. How do I set up the saved ODBC settings on the destination computer? 1 Copy the ini file onto the target computer or, if applicable, into the desired folder on a corresponding network drive. 2 Start the program ODBCDataLoader.exe by double-clicking it. The program is located in the \bin folder of the Transit/TermStar NXT installation. The program displays the following window showing all saved database connections: Fig. 11-13: The program shows all saved database connections 3 Select the connections that you want to set up on the destination computer. 4 To set up the connections, click Install. 140 Transit/TermStar NXT Reference Guide

11.5 Deleting incorrect database links 11 If a database connection of the same name already exists on the destination computer, the program displays a message informing you that the settings will be overwritten. To overwrite the existing database connection, click Yes in the message box. 5 To exit the program, click the X button on the window title bar. The program sets up the selected connections so that the data sources are then available on the destination computer. 11.5 Deleting incorrect database links The program ODBC Data Cleanup checks database connections and displays all connections with errors. How do I delete incorrect links? 1 Start the program ODBCDataCleanup.exe by double-clicking it. The program is located in the \bin folder of the Transit/TermStar NXT installation. The program displays the following window showing all database connections with errors: Fig. 11-14: The program shows all database connections with errors. 2 Select the connections that you want to delete. 3 To delete the connections, click Delete ODBC connection. The program displays a precautionary question. To delete the selected connections, click Yes in the message box. Click No or Cancel if you do not want to delete the connections. 4 To exit the program, click the X button on the window title bar. The program deletes the selected database connections. Transit/TermStar NXT Reference Guide 141

11 Managing database links 11.6 Compressing databases and dictionaries TermStar NXT also provides the possibility to compress databases and dictionaries. For this, the TermStar Database Wizard window contains the Compress function. How to compress a database or dictionary: 1 Select Dictionaries Dictionaries/databases Manage dictionaries/databases from the resource bar. TermStar NXT displays the TermStar database expert window containing a list of all database connections available (see Fig. 11-10 on page 137). 2 In the Databases/Dictionaries list, select the database or the individual dictionary you want to compress and click on Compress. TermStar NXT displays one of the following messages: Are you sure you want to compact the dictionary <name>? or Are you sure you want to compact the database? 3 The following options are available: To compact the dictionary or database confirm the message by clicking Yes. To not compress the dictionary or database, click on No or Cancel. If you have selected Yes, after completing the compression TermStar NXT opens the Database Administrator window with the following message: Compacting completed successfully. 4 Click on OK to finish the procedure and to close the window. 11.7 Database driver information In the TermStar Database Wizard window, you can call up the current driver information for databases listed at ODBC Info. How to call up database driver information: 1 Select Dictionaries Dictionaries/databases Manage dictionaries/databases from the resource bar. TermStar NXT displays the TermStar database expert window containing a list of all database connections available (see Fig. 11-10 on page 137). 2 Select the database for which you need the driver information in the Databases/ Dictionaries list. 142 Transit/TermStar NXT Reference Guide

11.7 Database driver information 11 Make sure that you select the whole database not a single dictionary in a database. If you only select a dictionary in the database, you cannot call up the driver information. 3 Click on ODBC Info. TermStar NXT displays the Driver info window containing the driver information on the selected database: Fig. 11-15: Driver info window 4 Click on OK to close the window. Transit/TermStar NXT Reference Guide 143

12 Compacting Microsoft Access database or transferring it to SQL server 12 Compacting Microsoft Access database or transferring it to SQL server 12.1 Overview If you use Microsoft Access databases for your dictionaries, the database files can become very large in the course of intensive terminology work. This impairs the performance of the databases in such a way that any access by Transit/TermStar NXT needs more time. It can therefore make sense to compress the databases occasionally. To do so, use the Windows ODBC data source administrator. Compression makes the database significantly more efficient, faster and smaller. It goes without saying that the content of the database itself (i.e. your dictionaries and terminology) is not changed. Compression makes sense in particular after the following work: When you have made comprehensive changes or manipulated a great deal of data When you have carried out comprehensive imports When you have deleted entire dictionaries or large stocks of terminology If you regularly receive projects with dictionaries (database TermStar Received) Closing Transit/TermStar NXT before compression Make sure that you close Transit/TermStar NXT before you start the compression. In doing so, you ensure that Transit/TermStar NXT does not access the database while it is being compressed. 144 Transit/TermStar NXT Reference Guide

12.1 Overview 12 Alternative: Use Microsoft database MS SQL Server 2005 Express or another SQL database In the case of intensive terminology work, it can make sense to use a Microsoft MS SQL Server database or another SQL database. You can transfer existing TermStar databases from Microsoft Access to MS SQL Server. Further information on this you find in section 12.2 Transferring TermStar databases from Microsoft Access to an SQL server on page 148. Optional interfaces are available for the SQL databases Oracle Database, IBM DB2 and MySQL. Please contact your local STAR office for details. How to compress a Microsoft Access database: 1 Make sure that Transit/TermStar NXT is closed. 2 Start the Windows ODBC data source administrator. Windows 8: In the Start menu, select Control Panel Administrative Tools and double-click ODBC Data Sources. Windows 7: In the Start menu, select Control Panel Administrative Tools and double-click Data Sources (ODBC). Windows Vista: In the Start menu, select Control Panel Administrative Tools and double-click Data Sources (ODBC). Windows displays the ODBC Data Source Administrator window: Fig. 12-1: ODBC Data Source Administrator window (Windows XP), User DSN tab Transit/TermStar NXT Reference Guide 145

12 Compacting Microsoft Access database or transferring it to SQL server 3 Select the User DSN tab or the System DSN tab You will find the TermStar NXT and TermStar NXT Received databases on the System DSN tab. Both databases are created automatically during the installation of Transit/TermStar NXT. You will find the databases you have created yourself using Transit/TermStar NXT on the User DSN tab. 4 Select the database that Windows is to compress in the list of system data sources and click on Configure. The ODBC data source administrator displays the ODBC Microsoft Access Setup window: Fig. 12-2: ODBC Microsoft Access Setup window 5 Leave the settings in this window unchanged and click on Compress. The ODBC data source administrator displays the Source Database window: Fig. 12-3: Source Database window; the database to be compressed is selected automatically. 146 Transit/TermStar NXT Reference Guide

12.1 Overview 12 6 Leave the settings unchanged and confirm the automatically selected source database with OK. The ODBC data source administrator displays the Target Database window: Fig. 12-4: Target database window; as format, select Version 4.x The database that Windows is to compress is selected as the target database. This is correct, as the existing uncompressed database is to be replaced by the compressed database. 7 As format, select Version 4.x, leave all other settings unchanged and confirm your selection with OK. The ODBC data source administrator displays the following message: <file name> already exists. Do you want to replace it? 8 Confirm the message by clicking Yes. The ODBC data source administrator compresses the database and replaces the existing uncompressed database with the compressed database. If you have selected the wrong format, the ODBC data source administrator displays the following message: The operation cannot be executed; Functions of this version are unavailable in databases with older formats. Make sure you select the right format (see step 7 on page 147) and try again to compress the database. After successful compression, the ODBC data source administrator displays the following message: Database <file name> has been successfully compressed to <file name> This means you have successfully compressed the database. You can now close all the windows of the ODBC data source administrator and the control panel. Transit/TermStar NXT Reference Guide 147

12 Compacting Microsoft Access database or transferring it to SQL server 12.2 Transferring TermStar databases from Microsoft Access to an SQL server If you install Microsoft MS SQL Server on your computer, you can transfer your TermStar databases from Microsoft Access to the SQL server. Transit/TermStar NXT supports the following versions of MS SQL Server: MS SQL Server 2005 or MS SQL Server 2005 Express MS SQL Server 2008 or MS SQL Server 2008 Express MS SQL Server 2008 R2 or MS SQL Server 2008 R2 Express MS SQL Server 2012 or MS SQL Server 2012 Express Disk space required Please mind the memory capacity that is required on the hard drive for installing the particular version Microsoft MS SQL Server (e. g. for MS SQL Server 2008 R2 Express at least 1 GB). The remaining memory requirement depends on the size of the TermStar databases to be transferred from MS Access to the SQL server. Only local installation supported! Please note that Transit/TermStar NXT only supports local installations of Microsoft MS SQL Server, not installation of Microsoft MS SQL Server on a network server. This is why only the transfer to locally installed databases is supported. As the database TermStar NXT Received usually contains the dictionaries to be transferred, the following section describes the transfer using this database as an example. The following steps are necessary for the transfer: Renaming the existing ODBC connection with the designation TermStar NXT Received in Windows (see section Renaming an ODBC connection in Windows ) Creating a new SQL database TermStar NXT Received (see section Creating a database in Transit/TermStar NXT ) Transferring the renamed Access database to the newly created SQL database (see section Transferring a database from Access to an SQL server ) 148 Transit/TermStar NXT Reference Guide

12.2 Transferring TermStar databases from Microsoft Access to an SQL server 12 Renaming the existing ODBC connection only if the new ODBC connection should have the same name Please note that it is possible to transfer not only the TermStar database TermStar NXT Received but also any other database from MS Access to an SQL server. As it is not possible to keep two ODBC connections of the same name, renaming the existing ODBC connection is always required when the new ODBC connection for the SQL database is to have the same name. Renaming the ODBC connection requires administrator rights! In order to rename the ODBC connection via the Windows Control Panel, you must have sufficient rights. Make sure that you have administrator rights or the corresponding authorisations. 12.2.1 Renaming an ODBC connection in Windows 1 Select Start Control Panel System and Security Administrative Tools. The Administrative Tools window is displayed: Fig. 12-5: Administrative Tools window 2 Select the Data Sources (ODBC) option. Transit/TermStar NXT Reference Guide 149

12 Compacting Microsoft Access database or transferring it to SQL server The ODBC Data Source Administrator window is displayed: Fig. 12-6: ODBC Data Source Administrator window 3 Switch to the System DSN tab. 4 Click in the System Data Sources list on the entry TermStar NXT Received and then click on Configure. The ODBC Microsoft Access Setup window is displayed: Fig. 12-7: ODBC Microsoft Access Setup window 5 In the Data Source Name field, change the name of the ODBC connection, e.g. to TermStar NXT Access, and confirm the change by clicking OK. 150 Transit/TermStar NXT Reference Guide

12.2 Transferring TermStar databases from Microsoft Access to an SQL server 12 The ODBC Data Source Administrator window is displayed with the changed ODBC connection: Fig. 12-8: ODBC Data Source Administrator window 6 Click OK to complete the operation. 12.2.2 Creating a database in Transit/TermStar NXT 1 Select Dictionaries Dictionaries / Databases Manage dictionaries / databases from the resource bar. Transit/TermStar NXT displays the TermStar database expert window: Fig. 12-9: TermStar database expert window Transit/TermStar NXT Reference Guide 151

12 Compacting Microsoft Access database or transferring it to SQL server 2 Click New to create a new database. Transit/TermStar NXT displays the Create new dictionary or database window: Fig. 12-10: Create new dictionary or database window 3 Select the Create a new database option and click on Next. Transit/TermStar NXT displays the ODBC driver selection window: Fig. 12-11: ODBC driver selection window 4 In the ODBC driver list, select the Microsoft SQL Server (MS SQL) driver and click Next. 152 Transit/TermStar NXT Reference Guide

12.2 Transferring TermStar databases from Microsoft Access to an SQL server 12 Transit/TermStar NXT displays the Database server selection window: Fig. 12-12: Database server selection window The Selected database server field shows the (local) option. 5 Keep this preselection and click Next. Transit/TermStar NXT displays the Specify database window: Fig. 12-13: Specify database window 6 In the New database field, enter the name TermStar NXT Received and click Next. Transit/TermStar NXT Reference Guide 153

12 Compacting Microsoft Access database or transferring it to SQL server Transit/TermStar NXT displays the ODBC connection window: Fig. 12-14: ODBC connection window 7 Make sure that you keep the designation TermStar NXT Received! If applicable, enable the option System DSN so that this ODBC connection is also available to other users of this computer. Click Next to confirm the entries. Transit/TermStar NXT displays the TermStar dictionary window: Fig. 12-15: TermStar dictionary window 154 Transit/TermStar NXT Reference Guide

12.2 Transferring TermStar databases from Microsoft Access to an SQL server 12 8 Enable the option Create empty database without dictionary and then click Finish. Transit/TermStar NXT displays the New dictionary or database window: Fig. 12-16: New dictionary or database window 9 Click OK to complete the operation. In the TermStar database expert window, the Databases/Dictionaries list contains the TermStar NXT Received database. 12.2.3 Transferring a database from Access to an SQL server 1 Select Dictionaries Dictionaries / Databases Manage dictionaries / databases from the resource bar. Transit/TermStar NXT displays the TermStar database expert with the TermStar NXT Received entry: Fig. 12-17: TermStar database expert window, select source database window 2 Click in the Databases/Dictionaries list on the database with the content you want to transfer and then click Copy. Transit/TermStar NXT Reference Guide 155

12 Compacting Microsoft Access database or transferring it to SQL server Transit/TermStar NXT displays the Select target database window: Fig. 12-18: Select target database window 3 In the Target database list, highlight the entry TermStar NXT Received and confirm your selection with OK. Transit/TermStar NXT transfers the content of the TermStar NXT Access database to the TermStar NXT Received database. The progress is indicated in the following window: Fig. 12-19: Progress bar for database transfer 4 Once Transit/TermStar NXT has completed the transfer, it displays the following message in the window: Completed successfully. 5 Click OK to close this window. 156 Transit/TermStar NXT Reference Guide

12.2 Transferring TermStar databases from Microsoft Access to an SQL server 12 Transit/TermStar NXT displays the TermStar database expert window. The dictionaries which were previously only in the TermStar NXT Access database are now also displayed in the TermStar NXT Received database: Fig. 12-20: TermStar database expert window, TermStar NXT Received database with transferred dictionaries 6 Now delete the TermStar NXT Access database connection. Click in the list on the TermStar NXT Access database. Then click Delete. Transit/TermStar NXT displays the following confirmation prompt: Do you really want to delete the database connection TermStar NXT Access? 7 Confirm this message by clicking Yes. Transit/TermStar NXT Reference Guide 157

12 Compacting Microsoft Access database or transferring it to SQL server Transit/TermStar NXT has removed the TermStar NXT Access database connection from the list of available databases and dictionaries: Fig. 12-21: TermStar database expert window, the TermStar NXT Access database connection has been removed Only the ODBC connection is deleted; the database file remains The Delete command in the TermStar database expert window only deletes the ODBC database connection. The database file in question (*.mdb) is still located in the db subfolder of your Transit/TermStar NXT installation. 158 Transit/TermStar NXT Reference Guide

13 Regular expressions 13 13 Regular expressions 13.1 Overview 13.1.1 What are regular expressions? Regular expressions are used to define character strings that match a specific pattern. You can use them in any situation where you want Transit NXT or TermStar NXT to search for and/or replace items of text. That gives you much flexibility so that you can even perform complex Find and Replace sequences in a single operation. When performing a normal search without using regular expressions, you can only specify a set search phrase. Example: You want to find all occurrences of the expressions Year 2003, Year 2004 and Year 2005. If you enter the search phrase Year 2004 in the Transit editor, Transit will find each occurrence of precisely the phrase Year 2004. With a standard search, therefore, you would have to run three separate searches for the phrases Year 2003, Year 2004 and Year 2005 respectively. However, if you entered the regular expression Year 200[3-5], Transit NXT would find all three phrases in a single search operation. The precise meaning of the expression is explained later on (see section 13.5.2 on page 165). Transit NXT and TermStar NXT support regular expressions You can use regular expressions in both Transit NXT and TermStar NXT; syntax and function are for the most part identical. Wherever this chapter describes a regular expression for use in Transit, you can also use it in TermStar NXT. In the few cases where a distinction between Transit NXT and TermStar NXT is necessary, it is explicitly indicated. 13.1.2 Basic settings for searches in Transit NXT Unless you change them, Transit NXT uses the following basic settings for searches: No distinction between upper and lower case By default Transit NXT does not distinguish between upper and lower case. Example: If you enter the regular expression STAR to search for STAR, Transit NXT will also find the character strings Star, star or even star. To force Transit NXT to find only those occurrences that match the case of your search string, you must select the option Match case. Transit/TermStar NXT Reference Guide 159

13 Regular expressions No distinction between whole words and parts of words By default Transit NXT does not distinguish between whole words and parts of words. Example: If you enter the regular expression star to search for star, Transit NXT will also find Elstar, start and starring. To force Transit NXT to find whole words only, you must select the option Find whole words only. Regular expressions not recognised By default, Transit NXT interprets search strings literally rather than as regular expressions in its various search functions (e.g. Find and Find/Replace in the Transit editor, Find/Replace in TermStar). To force Transit NXT to interpret a search string as a regular expression and to recognise the meta characters, you must select the option Regular expression. 13.1.3 What can you use regular expressions for? You can use regular expressions in the following functions: In Transit NXT Find Find/Replace Segment Filter Translation exceptions File type definition (tag definition and protection; segmentation) In TermStar Data record filter Input verification Data manipulation (Find/Replace) Dictionary import (preprocessing, field definitions in expert mode, substitutions) 160 Transit/TermStar NXT Reference Guide

13.2 Defining regular expressions 13 13.2 Defining regular expressions Regular expressions are made up of the following components: Standard characters Transit NXT searches for the standard characters (referred to as terminal characters ) as they appear in the regular expression. They have no special meaning. The standard characters are letters, numbers and special characters excepting those characters that serve as meta characters (. & * +? [ ] ( ) $ ^! \ #). More details of the meta characters are given later on. Example: The character a in a regular expression will find the character a. The character string star-group in a regular expression will find the character string star-group. Unicode characters and control characters Control characters are non-printing characters that control the appearance of the text (e.g. tabulator, line break, etc.). Control characters can also be used to search for Unicode characters or replace characters with Unicode characters. For a more detailed description of control characters, refer to section 13.3 Control characters on page 162. Meta characters Meta characters have special meanings when used in regular expressions. They are used to define the pattern that Transit NXT searches for. Transit NXT treats the following characters as meta characters:. & * +? [ ] ( ) $ ^! \ # The meanings of the individual meta characters are explained in section 13.4 on page 163. For the moment we will simply say this: if you wish to search for one of those characters literally (in order words treat it as a standard character and not as having a special meaning) you must place a backslash in front of it. Example: The character string Miller&Sons in a regular expression does not find the character string Miller&Sons because the & character has a special meaning. If you want to find the actual phrase Miller&Sons, you must enter the search string as Miller\&Sons. For a more detailed description of the meta characters, refer to section 13.4 Overview of meta characters on page 163. Transit/TermStar NXT Reference Guide 161

13 Regular expressions 13.3 Control characters Control characters are non-printable characters that control the appearance of the text (e.g. tabulator, line break, etc.). Control characters can also be used to search for Unicode characters or replace characters with Unicode characters. Control characters are introduced by a backslash (\). Type Meta characters Meaning Control characters \b Backspace \e Escape (ESC) Tab. 13-1: Control characters \f Form feed (new page) \n New line Please note that the control character \n finds line breaks inside segments. It does not find line breaks created by segment markers (e.g. new paragraphs). To find such line breaks you can use the control character \o (for segment markers). The expression \n is used to find the end of a line. The characters ^ and $ are used to search for the search string at the beginning and end of a line respectively. Under certain circumstances both expressions may return the same result but there can be differences both in usage and outcome. For more detailed information, refer to the note on page 178. \o Segment marker (in Transit editor only) \s Space \t Tabulator 162 Transit/TermStar NXT Reference Guide

13.4 Overview of meta characters 13 Type Meta characters Meaning Unicode characters \u<code> Unicode characters <code> is the hexadecimal code for the Unicode character (four digits with leading zeros where required). Examples: \u20ac Unicode character 20AC (hexadecimal, equivalent to decimal value 8364) = euro symbol. \u0394 Unicode character 394 (hexadecimal, equivalent to decimal value 916 = character. Tab. 13-1: Control characters (cont.) Backslash also meta character for escapement The backslash not only introduces control characters, it also serves as a meta character for an escapement so that a meta character can be searched for in its literal form. For more detailed information, refer to section 13.7 Escapement: \ on page 172. Finding/replacing control characters without using regular expressions You can also use control characters in Find and Replace operations without regular expressions. If you do not wish to use meta characters in a Find/Replace operation, you can deselect the option Regular expressions. Transit NXT will still find the control characters. 13.4 Overview of meta characters Meta characters have special meanings when used in regular expressions. They are used to define the pattern that Transit NXT searches for. Transit NXT recognises the following types of meta character (summarised in Table 13-29 on page 197): Wildcards:. [ ] & see section 13.5 on page 164 Wildcards are characters that are used to represent any single character or sequence of characters. You may be familiar with the use of wildcard characters in DOS commands or the Find function in TermStar NXT. Quantifiers: +*? see section 13.6 on page 169 By using what are known as quantifiers you can specify how many instances of a character are to be found. Transit/TermStar NXT Reference Guide 163

13 Regular expressions Escapement: \ see section 13.7 on page 172 If you wish to search for a meta character literally (in order words treat it as a standard character and not as having a special meaning) you must place a backslash in front of it. Applying meta characters to character strings: ( ) see section 13.8 on page 174 By using round brackets ( ) in a regular expression, you can specify that a meta character applies to a character string rather than a single character. Placement: ^ $ see section 13.9 on page 176 The meta characters that define placement are used to specify whether occurrences of the character string at the beginning or end of a line (in Transit NXT) or entry field (in TermStar NXT) are to be searched for. Negation:! see section 13.10 on page 178 The exclamation mark (!) is used to negate part of a regular expression. In that way you can instruct Transit NXT to find characters that do not match the negated part of the expression. Alternatives: see section 13.11 on page 183 The pipe character ( ) allows you to search for alternatives. The pipe character acts as a logical OR between parts of a regular expression. Variables: # see section 13.12 on page 186 You can use variables in a Find and Replace operation to define variable components of the character string that Transit NXT is to search for. That gives you much greater flexibility so that you can perform complex Find and Replace sequences in a single operation. 13.5 Wildcards:. [ ] & Wildcards are characters that are used to represent any single character or sequence of characters. You may be familiar with the use of wildcard characters in DOS commands or the Find function in TermStar NXT. 13.5.1 Wildcard for any single character:. (dot) You can use a dot (.) to search for any single character. As far as Transit NXT is concerned, "any character" means any letter (including letters with accents), number, special character (e.g. @, %, _), character used as a meta character (e.g. $,. or &), space character, control character (e.g. tabulator) or double-byte character. 164 Transit/TermStar NXT Reference Guide

13.5 Wildcards:. [ ] & 13 Control character for line break The only character that Transit NXT does not find is the control character for a line break. Regular expression Matches Does not match st.r On.line STAR stir st@r stör On-line On line On.line STAAR st r Online Tab. 13-2: Wildcard for any single character: 13.5.2 Wildcard for any of a specified group or class: square brackets ([]) If you want Transit NXT to search for any one of a particular group of characters you can define a character group or class. To do this, place the valid characters in square brackets [ ]. You can specify character groups, classes or a combination of both. Character group a group of multiple individual characters Example: [aeiou] this group consists of all of the vowels Character class a contiguous range of characters This is a simpler way of specifying a group of consecutive characters rather than listing each character in a group. Examples: [a-k] all letters from a to k inclusive (equivalent to character group [abcdefghijk]) [3-5] the numbers 3, 4 and 5 (equivalent to character group [345]) [\u3349-\u4221] Unicode characters 3349 to 4221 (see also Table 13-1 on page 162) To define a character class, you specify the first and last characters of a consecutive group. Transit NXT treats all characters that are between the specified characters in the ANSI or Unicode table as belonging to the character class. Transit/TermStar NXT Reference Guide 165

13 Regular expressions Combination of character groups and classes You can combine character groups and classes inside the square brackets. Example: [a-zäöü] letters a to z plus German umlaut characters Regular expression Matches Does not match st[aeiou]r star stir stor stör strr STAAR 200[3-5] 2003 2004 2005 1905 2002 2035 st[a-zäöü]r [a-z][0-9] star stör strr a4 k3 z5 stár STAAR st@r 1a mx 68 Tab. 13-3: Wildcard with character group or class Use of case in character group/class definitions When defining character groups/classes remember to take account of the Match case option setting in Transit NXT. Example: The character class [a-d] can signify either of the following: If the Match case option is not selected: All letters from a to d regardless of case (i.e. a, b, c, d, A, B, C, D). If the Match case option is selected: Only all the lower-case letters from a to d (i.e. a, b, c, d). If the Match case option is selected, and you want to find all letters in the character class regardless of case, you must enter upper and lower-case letters in the class definition (i.e. [a-da-d]). 166 Transit/TermStar NXT Reference Guide

13.5 Wildcards:. [ ] & 13 Negation of a character group You can specify that a character group does not include specific characters. This significantly simplifies the definition of character groups. For a more detailed description of using negation in a character group, refer to section 13.10.2 on page 180. Meta characters within square brackets Within square brackets, almost all meta characters lose their special meanings (a list of meta characters can be found in section 13.4 Overview of meta characters on page 163). The following characters have a special meaning even within the square brackets: You can use a (!) at the start of a line to specify which characters a character group is not permitted to contain. For a more detailed description of using negation in character groups, refer to section 13.10.2 Negation of a character group on page 180. A hyphen (-) placed between two characters specifies a range. Example: [a-ka-k] applies to all character strings with upper and lower-case letters from A to K. Umlauts, accented letters, etc. Please note that the character class [a-z] does not include letters with umlauts, accents, etc. If you wish to search for character groups that include such characters, you must add those characters to the class definition (e.g. [a-zäöüß] for the German alphabet). 13.5.3 Wildcard for any sequence of characters: ampersand (&) You can use the and sign or ampersand (&) to represent any sequence of characters. It is used to define an unlimited sequence of any characters bounded by delimiters. When you use the ampersand (&) you must always specify the characters by which the sequence is bounded (the beginning delimiter and the end delimiter ). Example: s&r finds s followed by any combination of any number of characters followed by r. As far as Transit NXT is concerned, any character means any letter (including letters with accents), number, special character (e.g. @, %, _), character used as a meta character (e.g. $,. or &), space character, control character (e.g. tabulator) or double-byte character. Transit NXT only finds occurrences where the beginning and end delimiters are in the same segment. If there is a segment marker between the beginning and end delimiters, Transit NXT does not find the search string. Transit/TermStar NXT Reference Guide 167

13 Regular expressions Example: s&r finds s followed by any combination of any number of characters followed by r. In the following two segments, Transit NXT does not find the expression because the beginning and end delimiters are not in the same segment. solid<<29>> as a rock<<30>> If, however, the beginning and end delimiters are in the same segment Transit NXT finds the character string. solid as a rock<<29>> Regular expression Matches Does not match s&r STAR Saint Peter S?.!R SR s r (line break) mar (beginning delimiter s is missing) stone (end delimiter r is missing) solid<<29>> as a rock<<30>> (segment marker between beginning and end delimiters) Tab. 13-4: Wildcard for any sequence of characters: Don't forget beginning and end delimiters! If either the beginning or end delimiter is missing, the regular expression is invalid. The following regular expressions would be incorrect: s& (end delimiter missing) and &r (beginning delimiter missing). When you enter a regular expression using the ampersand, Transit NXT searches as follows: Transit NXT first searches for the beginning delimiter. Transit NXT starts highlighting/marking the text from the first occurrence found. Transit NXT then searches for the end delimiter while continuously extending the highlight. As soon as Transit NXT finds the end delimiter, it highlights it and stops searching. Example: You search for the regular expression s&r in the following passage of text: The stars are shining bright. 168 Transit/TermStar NXT Reference Guide

13.6 Quantifiers: +*? 13 The passage contains three consecutive occurrences of the specified regular expression. The stars are shining bright. The stars are shining bright. The stars are shining bright. If you perform the search three times in succession, Transit NXT will thus find the following three character strings: star s ar shining br More examples are given in the section on quantifiers (see Table 13-6 on page 171). Distinction between ampersand (&) and the expression.* You can use the and sign or ampersand (&) to represent any sequence of characters. The expression.* is used to find any single or multiple occurrence of any character or no character. Under certain circumstances both expressions may return the same result but there can be differences both in usage and outcome. For more detailed information, refer to the note on page 172. 13.6 Quantifiers: +*? By using what are known as quantifiers you can specify how many instances of a character are to be found. Question mark x? Finds occurrences of absence or a single instance (0-1 instances) of the preceding character. Example: the regular expression a? finds a single letter a or the absence of it. Plus sign x+ Finds occurrences of a single instance or multiple instances (1 - n instances) of the preceding character. Example: the regular expression a+ finds a single letter a or multiple sequences of it (a, aa, aaa etc.). Asterisk x* Finds occurrences of the absence, a single instance or multiple instances (0 - n instances) of the preceding character. Example: the regular expression a* finds a single letter a, a multiple sequence of it, or its absence (a, aa, aaa etc. or nothing). Transit/TermStar NXT Reference Guide 169

13 Regular expressions When searching, Transit NXT only searches as far as a segment marker or line break and extends the highlight up to the last character preceding the segment marker or line break. Example: on the basis of the regular expression a* Transit NXT searches for the absence of the letter a, a single instance of it or a multiple sequence of it. In the following two lines, Transit NXT first finds only the string aa as it is followed by a line break. baa as sheep do On continuing the search, Transit NXT finds the single a on the next line. baa as sheep do Regular expression Matches Does not match sta?r sta+r sta*r str star star staaaar str star staaaar staaaar stra stir str stra stir staa aar (only searches as far as line break) stra stir staa aar (only searches as far as line break) Tab. 13-5: Searching for a specified number of a specific character You can also use quantifiers to specify how many instances of a character in a character group or class are to be found. To do so, you place the quantifier after the square brackets in which the character group or class is defined (see section 13.5.2 Wildcard for any of a specified group or class: square brackets ([]) on page 165). 170 Transit/TermStar NXT Reference Guide

13.6 Quantifiers: +*? 13 Example: The regular expression [0-9]+ finds any sequence of numbers (0, 15, 290504 etc.). Regular expression Matches Does not match [0-9]+ Finds sequences of one of more numbers. Other characters are not found. st[aeiou]*r Finds sequences of one or more vowels or absence of vowels between the delimiters. Other characters are not found. [A-Z][a-z]* Finds any single upper-case letter followed by any sequence of (or absence of) lower-case letters. Other characters are not found. [A-Z][a-z]+ Finds strings where at least one lower-case letter follows an upper-case letter. Other characters are not found. Star[a-z]? Finds strings where the literal string is followed by nothing or a single letter. Other characters are not found. 0 15 290504 str star stir staaaaar stair D Star Transit Star Transit Star Start Stars XV star stör stpr st@r translation Böblingen TermStar D translation Böblingen TermStar Star3 Starter Tab. 13-6: Quantifiers for character classes and groups Use of case in character group/class definitions When defining character groups/classes remember to take account of the Match case option setting in Transit NXT. For more detailed information, refer to the note Use of case in character group/class definitions on page 166. Transit/TermStar NXT Reference Guide 171

13 Regular expressions Quantifiers for character strings Normally, a quantifier applies to the character that immediately precedes it. By using round brackets ( ) in a regular expression, you can specify that the quantifier applies to a character string rather than a single character. For more detailed information, refer to section 13.8 Applying meta characters to character strings: ( ) on page 174. Distinction between ampersand (&) and the expression.* The expression.* is used to find any single or multiple occurrence of any character or no character. You can use the and sign or ampersand (&) to represent any sequence of characters. Under certain circumstances both expressions may return the same result but there can be differences both in usage and outcome: & requires beginning and end delimiters. By contrast, the expression.* can also be used without specifying a beginning or end delimiter. & also finds line breaks within a segment. By contrast, the expression.* does not find line breaks and highlights the character string up to the last character preceding the line break. For a more detailed description of using the ampersand, refer to section 13.5.3 on page 167. 13.7 Escapement: \ Meta characters have special meanings when used in regular expressions. They are used to define the pattern that Transit NXT searches for. If you wish to search for a meta character literally (in order words treat it as a standard character and not as having a special meaning) you must place the character \ (backslash) in front of it. The backslash acts as what is called an escapement, in other words it prevents the meta character from being interpreted as having a special meaning. This function is also referred to as masking. The same applies to the backslash itself, as it too is a meta character. If you want to search literally for a backslash, you have to place another backslash in front of it. 172 Transit/TermStar NXT Reference Guide

13.7 Escapement: \ 13 Examples: You want to search for the string readme.txt. The dot, however, is a meta character (wildcard character representing any single character, see section 13.5.1 on page 164). So that Transit NXT searches literally for a dot, you have to place a backslash in front of it thus: readme\.txt You want to search for the string +TermStar. However, the plus sign is a meta character (quantifier, see section 13.6 on page 169). So that Transit NXT searches literally for a plus sign, you have to place a backslash in front of it thus: Transit\+TermStar You want to search for the string folder \temp. However, the backslash is a meta character (escapement) and also introduces control characters (e.g. the tabulator \t). So that Transit NXT searches literally for a backslash, you have to place another backslash in front of it thus: folder \\temp Table 13-7 shows the use of the escapement in regular expressions for literal searches for meta characters. The same expressions without the escapement do not produce the desired results (see Table 13-8). Regular expression Matches Does not match readme\.txt readme.txt readmextxt readme-txt readmetxt Transit\+TermStar Transit+TermStar TransiTermStar TransitTermStar TransitttttTermStar folder \\temp folder \temp folder temp folder emp Tab. 13-7: Literal searches for meta characters using escapement Transit/TermStar NXT Reference Guide 173

13 Regular expressions Regular expression Matches Does not match readme.txt (no escapement) Transit+TermStar (no escapement) folder \temp (no escapement) readme.txt readmextxt readme-txt TransitTermStar TransitttttTermStar folder emp (\t is the control character for the tabulator) readmetxt Transit+TermStar TransiTermStar folder \temp folder temp Tab. 13-8: Incorrect results produced by literal searches for meta characters without using escapement Backslash also introduces control characters The backslash not only serves as a meta character for an escapement, it also introduces control characters. For a more detailed description of control characters, refer to section 13.3 Control characters on page 162. 13.8 Applying meta characters to character strings: ( ) By using round brackets ( ) in a regular expression, you can specify that a meta character applies to a character string rather than a single character. Example: the plus sign specifies that the preceding character should occur once or more than once (see section 13.6 on page 169). If you enclose a character string in round brackets, the plus sign applies to the entire character string thus: the regular expression (ha)+ finds sequences in which the string ha occurs once or any number of times (ha, haha, hahaha, etc.). 174 Transit/TermStar NXT Reference Guide

13.8 Applying meta characters to character strings: ( ) 13 By combining character strings, character groups and quantifiers, you can define complex patterns as illustrated below: Regular expression Matches Does not match s(ta)+r s followed by one or more occurrences of ta followed by r T(ra)+[a-z]+ Finds T followed by one or more occurrences of ra followed by any single letter or sequence of letters star statar statatatar Transit Traransit Transfer Trararas sr stat statr Termstar Tra2004 Tra-nsit Tab. 13-9: Effect of round brackets on meta characters Every open bracket requires a closing bracket Make sure that for every opening bracket in the regular expression there is a corresponding closing bracket. The regular expression is otherwise invalid. Tip: use round brackets to structure the expression You can also use round brackets to structure regular expressions and make them clearer even if use of the brackets is not strictly necessary for syntax reasons. In addition, round brackets are also required when using the following meta characters: Negation (!) (see section 13.10 on page 178) Alternatives ( ) (see section 13.11 on page 183) Variables (#) (see section 13.12 on page 186) Transit/TermStar NXT Reference Guide 175

13 Regular expressions 13.9 Placement: ^ $ The meta characters that define placement are used to specify whether occurrences of the character string at the beginning or end of a line (in Transit NXT) or entry field (in TermStar NXT) are to be searched for. Circumflex and dollar sign are logical characters: Transit NXT checks whether the search string is at the beginning or end of a line or field but does not highlight the beginning or end itself. Circumflex ^ By using the circumflex you can specify that Transit NXT should search for occurrences of the search string at the beginning of a line or field: In Transit NXT: at the beginning of a line (i.e. after a line break) In TermStar: at the beginning of an entry field To do so, you place the circumflex at the beginning of the regular expression. Example: the regular expression ^STAR tells Transit NXT to search for occurrences of STAR at the beginning of a line. Dollar sign $ By using the dollar sign you can specify that Transit NXT should search for occurrences of the search string at the end of a line or field: In Transit NXT: at the end of a line (i.e. before a line break) In TermStar: at the end of an entry field To do so, you place the dollar sign at the end of the regular expression. Example: the regular expression STAR$ tells Transit NXT to search for occurrences of STAR at the end of a line. Regular expression Matches Does not match ^STAR STAR$ ^&$ (Any sequence of characters between beginning and end of line) STAR in STAR Group STAR in with STAR The STAR Group in The STAR Group STAR in The STAR Group STAR in STAR Group STAR in STAR. The STAR group (spans more than one line) Tab. 13-10: Regular expression at the start of a line 176 Transit/TermStar NXT Reference Guide

13.9 Placement: ^ $ 13 Transit editor: line break is not the same as segment marker Please note that in the Transit editor the meta characters for placement check whether the search string is before or after a line break, i.e. before or after the control character \n. It does not find line breaks created by segment markers (e.g. new paragraphs). To find such line breaks you can use the control character \o (for segment markers). Correct placement of meta characters Take care to place the meta characters correctly within the regular expression: Circumflex (for beginning of line) at the beginning of the regular expression. Dollar sign (for end of line) at the end of the regular expression. Otherwise the regular expression will not be correct and Transit NXT will not be able to interpret it properly. Negation of beginning/end of line You can also specify that Transit NXT is to search for occurrences of the regular expression that are not at the beginning/end of a line. To do so, you use the exclamation mark to negate the beginning/end of the line (13.10.3 Negation of beginning/end of line on page 181). Circumflex/dollar sign within character groups/classes is not a meta character Transit NXT does not interpret the circumflex and dollar sign as meta characters for the beginning/end of a line when they are placed inside a character group or class. When they are used inside a character group, Transit NXT interprets the circumflex and dollar sign literally, i.e. searches for the circumflex and dollar sign characters themselves (see section 13.5.2 on page 165). Transit/TermStar NXT Reference Guide 177

13 Regular expressions Control character \n versus placement characters ^ and $ The expression \n is used to find the end of a line. The characters ^ and $ are used to search for the search string at the beginning and end of a line respectively. Under certain circumstances both expressions may return the same result but there can be differences both in usage and outcome: ^ and $ must be placed at the beginning and end of the regular expression respectively. By contrast, the control character \n can also be placed within the regular expression. In that way you can search for character strings that span line breaks. ^ and $ do not find the line break itself. By contrast, the control character \n finds and highlights the line break itself. In that way you find and replace the line break if you wish. For a more detailed description of control characters, refer to section 13.3 on page 162. 13.10 Negation:! The exclamation mark (!) is used to negate part of a regular expression. In that way you can instruct Transit NXT to find characters that do not match the negated part of the expression. Difference in highlighting between negation of character string and character group/class Please note that Transit NXT behaves differently when characters and character strings are negated than when character groups or classes are negated. When characters or character strings are negated, Transit NXT does not highlight the negated character as found. When character groups or classes are negated, Transit NXT also highlights the negated character as found. For examples, refer to the Tables 13-11 on page 179 and 13-13 on page 180. 178 Transit/TermStar NXT Reference Guide

13.10 Negation:! 13 13.10.1 Negation of a character or character string You can specify that Transit NXT is to search for sequences that do not include a specific character or character string. To do so, you place the exclamation mark and the character or characters inside round brackets. In contrast with the negation of character classes (see section 13.10.2 on page 180), Transit NXT does not highlight the negated character as found. Example: the regular expression ST(!ONE) finds any occurrence of the string ST that is not followed by the string ONE. that means that Transit NXT will find ST but not the negated string ONE. Regular expression Matches Does not match ST(!ONE) ST in STAR ST in STIR ST in ST ST in STP ST in STONE Tab. 13-11: Negation of character strings Exclamation mark for negation must always prefix character string Transit NXT only interprets the exclamation mark as a meta character for negation if it is placed as the first character of the character string inside the round brackets. Otherwise, Transit NXT interprets the exclamation mark literally, i.e. it searches for the exclamation mark itself. Regular expression Matches Does not match ST(ON!E) STON!E STONE STAR STIR ST STP Tab. 13-12: If the exclamation mark is not the first character it is interpreted literally Transit/TermStar NXT Reference Guide 179

13 Regular expressions 13.10.2 Negation of a character group You can specify that a character group does not include specific characters. This significantly simplifies the definition of character groups. For a more detailed description of character groups, refer to section 13.5.2 on page 165. To negate a character group you place the exclamation mark as the first character of the character group inside the square brackets. Example: you want to define a character group that includes all characters except s. Without using negation, you would have to specify all characters in the group and run the risk of omitting one or other of them: [a-rt-z0-9ß?-=@] (Umlauts and special characters omitted) By using negation, the definition is much simpler and you have greater certainty of including all the required characters: [!s]. In contrast with the negation of character strings (see section 13.10.1 on page 179), Transit NXT also highlights the negated character as found. Example: the regular expression ST[!ONE] finds any character string that begins with ST and does not end in O, N or E. That means that Transit NXT finds any character string that consists of three characters, starts with ST and does not end in O, N or E. Regular expression Matches Does not match ST[!ONE] STA in STAR STP in STP STO in STONE STE in STELLA ST in ST Tab. 13-13: Negation of character groups 180 Transit/TermStar NXT Reference Guide

13.10 Negation:! 13 Exclamation mark for negation must always prefix character group/class Transit NXT only interprets the exclamation mark as a meta character for negation if it is placed as the first character of the character group/class inside the round brackets. Otherwise, Transit NXT interprets the exclamation mark literally, i.e. it searches for the exclamation mark itself. Regular expression Matches Does not match ST[ON!E] STO STN ST! STE STA ST5 Tab. 13-14: If the exclamation mark is not the first character it is interpreted literally 13.10.3 Negation of beginning/end of line By negating the meta characters that define placement (circumflex and dollar sign) you can specify that Transit NXT is to search for occurrences of the character string that are not at the beginning or end of a line. For a more detailed description of the meta characters for placement, refer to section 13.9 on page 176. To do so, you place the exclamation mark and the circumflex or dollar sign inside round brackets. Examples: The regular expression (!^)STAR tells Transit NXT to search for occurrences of STAR that are not at the beginning of a line. The regular expression STAR(!$) tells Transit NXT to search for occurrences of STAR that are not at the end of a line. Regular expression Matches Does not match (!^)STAR STAR(!$) STAR in The STAR Group STAR in STAR Group STAR in STAR. STAR in STAR Group STAR in with STAR Tab. 13-15: Negation of beginning or end of line Transit/TermStar NXT Reference Guide 181

13 Regular expressions If you only want to negate the beginning/end of line placement, take care to place the appropriate meta character in round brackets on its own. Otherwise the entire expression would be negated. Example: The regular expression ST(!AR$) finds any occurrence of the string ST that is not followed by the string AR and the end of a line. Regular expression Matches Does not match ST(!AR$) Negation of entire string AR plus end of line ST in STAR Group ST in with ST ST in with STAR Tab. 13-16: Negation of entire string AR plus end of line Exclamation mark for negation must always prefix character string Transit NXT only interprets the exclamation mark as a meta character for negation if it is placed as the first character of the character string inside the round brackets. Otherwise, Transit NXT interprets the exclamation mark literally, i.e. it searches for the exclamation mark itself. Regular expression Matches Does not match ST(AR!$) STAR! in STAR! STAR in with STAR STAR! in STAR! Group Tab. 13-17: If the exclamation mark is not the first character it is interpreted literally 182 Transit/TermStar NXT Reference Guide

13.11 Alternatives: 13 13.11 Alternatives: The pipe character ( ) allows you to search for alternatives. The pipe character acts as a logical OR between parts of a regular expression. Example: the regular expression Transit TermStar finds either the character string Transit or TermStar. Transit NXT finds the first match with either of the two alternatives. It makes no difference in which order the alternatives are specified in the regular expression. Example: In the passage TermStar and Transit are using regular expressions. Transit NXT will first find the string TermStar because it is the first occurrence of either of the two alternatives specified in the regular expression. 13.11.1 What does Transit NXT interpret as an alternative? By default, Transit NXT interprets everything from the beginning of the regular expression to the first pipe character, between two pipe characters or from the last pipe character to the end of the regular expression as an alternative. Example: Transit NXT interprets the regular expression You can use the English German Swedish interface as the following three alternatives: From the beginning to the first pipe character: You can use the English From that pipe character to the next: German From the last pipe character to the end: Swedish interface To limit the boundaries of the alternatives you can enclose them in round brackets. Example: Transit NXT interprets the regular expression You can use the (English German Swedish) interface as follows: Normal text: You can use the followed by the three alternatives: English or German or Swedish followed by normal text: interface Regular expression Matches Does not match (TermStar Transit) from STAR TermStar Transit from STAR TermStar from STAR Transit from STAR TermStar Transit from STAR TermStarTransit from STAR TermStar TermStarTransit from STAR TermStar from STAR Tab. 13-18: Search for alternatives Transit/TermStar NXT Reference Guide 183

13 Regular expressions 13.11.2 Alternatives and character groups/classes Alternatives are not always useful or necessary in the following cases: Alternatives between individual characters Alternatives between multiple individual characters are not useful because the characters can be defined by a character group or class as part of which they will in any case be treated as alternatives. Example: (a b c) means either the character a or b or c. Instead of that you can search for those alternatives by defining the character group [abc] Alternatives between character classes Alternatives between character groups or classes are not useful because the characters can be defined by a character class as part of which they will in any case be treated as alternatives. Example: ([a-z] [0-9]) means any character from a to z or any character from 0 to 9. Instead of that you can search for those alternatives by defining the single character group [a-z0-9] Alternatives within character classes Alternatives within a character group or class are not useful because Transit NXT treats the individual characters as alternatives in any case. For that reason, Transit NXT interprets the pipe character within a character group literally, i.e. it searches for the pipe character itself. Example: [abx] means a or b or x. Pipe character within character groups/classes is not a meta character Transit NXT does not interpret the pipe character as a meta character for alternatives when it is placed inside a character group or class. When you use it inside a character group, Transit NXT interprets the pipe character literally, i.e. it searches for the pipe character itself. Regular expression Matches Does not match st[ab x]r star stbr st r stxr str stabr staxr Tab. 13-19: If the pipe character is inside a character group it is interpreted literally 184 Transit/TermStar NXT Reference Guide

13.11 Alternatives: 13 13.11.3 Alternatives and negated character strings Alternatives between negated character strings are not generally useful. Such an approach would appear to make sense initially if want to exclude certain character strings from your search however, it produces incorrect results. Example: You want to search for character strings that start with A followed by two-digit number. However, you do not want Transit NXT to find character strings that contain 05 or 29. You want Transit NXT to find: A06, A09, A68 You don't want Transit NXT to find: X7, A05, A29 You therefore decide to use the following regular expression: A(!05!29)[0-9][0-9] This regular expression, however, does not produce the desired results. It will also find A05 and A29. Why? On the basis of that regular expression, Transit NXT searches for the following character string: The letter A followed by a character sequence that is not 05 or 29 followed by any number [0-9] followed again by any number [0-9] At least one of the alternatives will always be matched. If the A is followed by the number 05 then that is a character string that is not 29. The second alternative is thus a match. If the A is followed by the number 29 then that is a character string that is not 05. The first alternative is thus a match. If the A is followed by another number then that is a character string that is neither 29 nor 05. Both alternatives are thus a match. This regular expression therefore does not prevent Transit NXT finding A05 or A29. The desired result is obtained by using the following regular expression: A(!05)(!29)[0-9][0-9] On the basis of that regular expression, Transit NXT searches for the following character string: The letter A not followed by 05 and not followed by 29 followed by any number [0-9] followed again by any number [0-9] Transit/TermStar NXT Reference Guide 185

13 Regular expressions Now Transit NXT proceeds as follows: If the A is followed by the number 05, the first negation means it is not a match because it specifies that A cannot be followed by 05. Transit NXT thus does not find A05. If the A is followed by the number 29, the first negation allows a match (not followed by 05). However, the second negation prevents a match because it specifies that A cannot be followed by 29. Transit NXT thus does not find A29. If the A is followed by another number, the first and second negations allow a match. Transit NXT thus does find A06, A09, A68, etc. 13.12 Variables: # 13.12.1 Why use variables? When performing a normal Find and Replace without using variables, you can only specify a set string with which to replace the search string. You can use variables in a Find and Replace operation to define variable components of the character string that Transit NXT is to search for. That gives you much greater flexibility so that you can perform complex Find and Replace sequences in a single operation. Example: you want to replace the phrase Year 2003 or Year 2004 or Year 2005 by 2003 Edition or 2004 Edition or 2005 Edition respectively. With a normal Find and Replace you would have to run three separate searches to replace Year 2003 with 2003 Edition, Year 2004 with 2004 Edition and Year 2005 with 2005 Edition. If, however, you use the regular expression Year 200#([3-5])0, Transit NXT will find any of the three phrases in the same search and substitute the appropriate replacement specified by the regular expression 200#0 Edition. The precise meaning of the expressions is explained later on (see section 13.12.2 on page 187). Other practical examples: You want every single-digit number to have a leading zero: 1 is to be changed to 01; 2 is to be changed to 02, etc. You want Transit NXT to change all numbers in the format x.y to the format x,y: 2.1 is to be changed to 2,1; 2.2 is to be changed to 2,2, etc. You want Transit NXT to change all hyphenated combinations (abc-xyz) to the format abc_xyz. On-line is to be changed to On_line; reference-based changed to reference_based, etc. 186 Transit/TermStar NXT Reference Guide

13.12 Variables: # 13 Because it is not possible with "normal" regular expressions to replace a random character string by itself, you have to define variables for such cases (see section 13.12.2 on page 187). When performing a Find and Replace using variables, you can also specify whether Transit NXT is to convert the string when replacing: Changing the case when replacing 13.12.3 on page 189 Changing number formats when replacing 13.12.4 on page 190 Performing mathematical calculations when replacing 13.12.5 on page 191 Rounding figures when replacing 13.12.6 on page 193 13.12.2 How are variables used? In order that it can use parts of the character string that it finds to replace what it finds, Transit NXT has to memorise those items during the search. To enable it to do so, you use variables which you define in the regular expression for the search and in which Transit NXT stores components of the character string. You then use the same variables in the regular expression for the replacement so that Transit NXT uses the stored data when performing the replacement. Syntax for regular expression for search string: #(regular expression)variable number Transit NXT will thus store the characters that it finds on the basis of the regular expression in the specified variable. You can use up to ten variables in a Find/ Replace operation (variable numbers 0 to 9). Example: the following format is used to refer to keyboard keys in a document: Ins key, DEL key, PgUp key, return key, etc. You want to run a Find and Replace so that the names of the keys are placed in quotation marks thus: "Ins" key, "DEL" key, "PgUp" key, "return" key, etc. You can use the following regular expression for the search: #([a-z]+)0\skey On that basis Transit NXT will search for a sequence of letters ([a-z]) followed by a space (\s) followed by the string key. Transit NXT saves the sequence of letters found as the variable 0. If you use only the variable number in the search and do not specify a wildcard character or character string, Transit NXT uses the wildcard character & as the regular expression. That means that Transit NXT will search for any sequence of any number of characters and will store it as the specified variable. Since the wildcard character & always requires a beginning and end delimiter, you must specify them. However, they are not stored in the variable. Example: you use the expression s#9r for the search string Transit/TermStar NXT Reference Guide 187

13 Regular expressions Transit NXT interprets that expression as s#(&)9r. Transit NXT therefore searches for s followed by any sequence of any number of characters followed by r. Transit NXT stores that sequence of characters as the variable 9. The beginning delimiter s and the end delimiter r are not stored in the variable. Syntax for regular expression for replacement string: #Variable number Example: in the above example involving the format for the key names, you could use the following regular expression for the replacement: "#0" key Transit NXT then replaces the string found with inverted commas followed by the contents of the variable 0 followed by the string " key. The following table lists further practical examples: Application Search text Replacement text Assign a leading zero to single-digit numbers Replace single-digit numbers in the notation x.y with the notation x,y Replace the hyphen in compound words with an underscore \s#([0-9])0 Transit NXT searches for a space (\s) followed by a number ([0-9]). Transit NXT stores the number as the variable 0. \s#([0-9])0\.#([0-9])1 Transit NXT searches for a space (\s) followed by a number ([0-9]) followed by a decimal point (\.) followed by a number ([0-9]). Transit NXT saves the first number as the variable 0 and the second number as the variable 1. #([a-z]+)0-#([a-z]+)1 Transit NXT searches for a sequence of letters ([a-z]+) followed by a hyphen (-) followed by a sequence of letters ([a-z]+). Transit NXT saves the first sequence of letters as the variable 0 and the second sequence of letters as the variable 1. \s0#0 Transit NXT replaces what it finds with a space, a zero and the contents of the variable 0 (the number found). \s#0,#1 Transit NXT replaces what it finds with a space, the contents of the variable 0 (the first number found), a comma and the contents of the variable 1 (the second number found). #0_#1 Transit NXT replaces what it finds with the contents of the variable 0 (the first sequence of letters found), an underscore and the contents of the variable 1 (the second sequence of letters found). Tab. 13-20: Replacements using variables 188 Transit/TermStar NXT Reference Guide

13.12 Variables: # 13 13.12.3 Changing the case when replacing If you use variables when searching and replacing, Transit NXT can change the case of the variable contents when replacing. Upper and lower case To force Transit NXT to distinguish between upper and lower case when searching, select Match case in the in the Transit/TermStar NXT window. Otherwise Transit NXT will ignore differences in case. Syntax for regular expression for replacement string: #(<option>)variable number In place of <option> you can enter one of the following options to specify how Transit NXT is to change the case: Option ^ ^1 _ Meaning Change replacement string to all capitals Change first letter of replacement string to capital. Leave all other letters unchanged. Change replacement string to all lower case _1 Change first letter of replacement string to lower case. Leave all other letters unchanged. ~ Invert case of all letters in replacement string (i.e. change lower case to upper case and upper case to lower case) ~1 Invert case of first letter in replacement string (i.e. change lower case to upper case or upper case to lower case). Leave all other letters unchanged. Tab. 13-21: Options for changing case Example: the following format is used to refer to keyboard keys in a document: Ins key, DEL key, PgUp key, return key, etc. You want to use a Find and Replace to change the case of the key names. To do so, you use the following regular expression for the search: #([a-za-z]+)0\skey Transit/TermStar NXT Reference Guide 189

13 Regular expressions The following table shows the results obtained by the various options for changing case. Replace Ins key DEL key PgUp key return key #(^)0 key INS key DEL key PGUP key RETURN key #(^1)0 key Ins key DEL key PgUp key Return key #(_)0 key ins key del key pgup key return key #(_1)0 key ins key del key pgup key return key #(~)0 key ins key del key pgup key RETURN key #(~1)0 key ins key del key pgup key Return key Tab. 13-22: Examples of changing case 13.12.4 Changing number formats when replacing If you use variables when searching and replacing, Transit NXT can change the number format of the variable contents when replacing. Syntax for regular expression for replacement string: #(={(<format>)}x)<variable number> In place of <format> you enter a format option to specify how Transit NXT is to change the number format. Format Meaning # Show number only if value is not zero 0 Always show number whether value is zero or not _ Show space if value is zero Tab. 13-23: Format options for changing number format If you do not specify a number format, Transit NXT applies the number format specified in the Windows system settings. Example: a document contains decimal numbers in a variety of formats: 1.1, 10.123, etc. You want to use Find and Replace to change the format of the numbers. To do so, you use the following regular expression for the search: #([0-9]+\.[0-9]+)0 190 Transit/TermStar NXT Reference Guide

13.12 Variables: # 13 The following table shows the results obtained by the various options for changing number format. Replace 1.1 10.123 #(={ _.00}x)0 1.10 (with four leading spaces) 10.12 (with three leading spaces) #(={00000.00}x)0 00001.10 00010.12 #(={0.##}x)0 1.1 10.12 #(={}x)0 1 10 Tab. 13-24: Examples of changing number format Rounding numbers If you reduce the number of decimal places, Transit NXT does not automatically round the number, it simply cuts off the surplus decimal places. However, by specifying an additional calculation in the replacement, you can have Transit NXT round the number. For more detailed information, refer to section 13.12.6 on page 193. 13.12.5 Performing mathematical calculations when replacing If you use variables when searching and replacing, Transit NXT can perform mathematical calculations on the variable contents when replacing. Syntax for regular expression for replacement string: #(={<format>}<formula>)<variable number> You use <format> to specify how Transit NXT is to change the number format, if required (see section 13.12.4 on page 190). In our examples, however, we have left out the format option so as not to confuse the explanation of the mathematical calculations. In place of <formula> you enter the mathematical formula that Transit NXT is to apply to the number. In that formula you can use the following mathematical operators: Operator Meaning + Addition - Subtraction / Division Tab. 13-25: Operators for mathematical calculations Transit/TermStar NXT Reference Guide 191

13 Regular expressions Operator Meaning * Multiplication () Brackets x Number to be converted Tab. 13-25: Operators for mathematical calculations (cont.) Example: a document contains a variety of decimal numbers: 295200.2, 0.123, 3.4, etc. You want to use Find and Replace to perform a calculation on the numbers. To do so, you use the following regular expression for the search: #([0-9]+.[0-9]+)0 The following table shows the results obtained by various mathematical calculations. Replace 295200,2 0,123 3,4 #(={}x)0 Round off to whole number #(={}x+5)0 Addition #(={}x-5)0 Subtraction #(={}x*5)0 Multiplication #(={}x/5)0 Division #(={}x*-9)0 Multiplication with negative value #(={}x*x)0 Multiply by itself (= x 2 ) 295200 0 3 295205 5 8 295195-4 -1 1476001 0 17 59040 0 0-2632501 -1-30 87143153664 0 11 Tab. 13-26: Examples of mathematical calculations 192 Transit/TermStar NXT Reference Guide

13.12 Variables: # 13 Rounding numbers If you reduce the number of decimal places, Transit NXT does not automatically round the number, it simply cuts off the surplus decimal places. However, by specifying an additional calculation in the replacement, you can have Transit NXT round the number. For more detailed information, refer to section 13.12.6 on page 193. Other practical examples: Replace dimensions in inch by dimensions in centimeter A document contains dimensions in inch. They are to be replaced by the equivalent dimensions in centimeter. Regular expression for the search string: #([0-9]+0 inch Regular expression for the replacement string: #(={}x*2.54)0 cm Result: The width is 5 inch. is replaced by The width is 12.7 cm. Where distance quoted in miles add equivalent distance in kilometres A document contains distances in miles. You want Transit NXT to add the equivalent distance in kilometres in each case. Regular expression for the search string: #([0-9]+)0 miles Regular expression for the replacement string: #0 miles (#(={}x*1.609)0 km) Result: Distance Ramsen Böblingen 90 miles is replaced by Distance Ramsen Böblingen 90 miles (144 km) 13.12.6 Rounding figures when replacing If you use variables when searching and replacing, Transit NXT can change the number format of the variable contents when replacing (see section 13.12.4 Changing number formats when replacing on page 190). If the change of format reduces the number of decimal places, Transit NXT does not automatically round the number, it simply cuts off the surplus decimal places. Example: reduce all decimal numbers to one decimal place A document contains decimal numbers with varying numbers of decimal places. You want to change them all to decimal numbers with only one decimal place. Transit/TermStar NXT Reference Guide 193

13 Regular expressions Regular expression for the search string: #([0-9]+\.[0-9]+)0 Regular expression for the replacement string: #(={0.0}x)0 Result: Transit NXT cuts off the surplus decimal places thus: Number found Replaced by same number reduced to one decimal place 1.01 1.0 1.04 1.0 1.05 1.0 1.06 1.0 1.09 1.0 Tab. 13-27: Example: Reducing numbers to one decimal place However, by specifying an additional calculation in the replacement, you can have Transit NXT round the number: values up to and including 4 will be rounded down, values of 5 or greater will be rounded up. Example: when replacing you add 0.05 to the numerical value. As a result Transit NXT increases the numerical value by 0.05 when replacing and then cuts off the surplus decimal places. The resulting figures are thus rounded to the nearest tenth. Regular expression for the search string (same as above): #([0-9]+\.[0-9]+)0 Regular expression for the replacement string: #(={0.0}x+.05)0 Result: Transit NXT rounds the values up or down to the nearest tenth Number found Number found plus 0.05 Replaced by same number reduced to one decimal place 1.01 1.06 1.0 1.04 1.09 1.0 1.05 1.10 1.1 1.06 1.11 1.1 1.09 1.14 1.1 Tab. 13-28: Example: Rounding numbers to one decimal place 194 Transit/TermStar NXT Reference Guide

13.13 Invalid regular expressions 13 To determine the amount to be added, take the smallest decimal fraction required and divide it by 2. Examples of determining the amount to be added: Rounding to one decimal place smallest decimal fraction 0.1 divided by 2 equals 0.05. To round figures, add the value 0.05. Rounding to two decimal places smallest decimal fraction 0.01 divided by 2 equals 0.005. To round figures, add the value 0.005. Rounding to five decimal places smallest decimal fraction 0.00001 divided by 2 equals 0.000005. To round figures, add the value 0.000005. 13.13 Invalid regular expressions 13.13.1 Ambiguous regular expressions Regular expressions must be unambiguous, in other words there must only be one way in which they can be interpreted. If you use quantifiers it is possible in some cases that the regular expression may be invalid because it may allow a number of different interpretations so that the search does not produce a definite result. Examples of ambiguous regular expressions: 3*3 invalid because the second number 3 is already found by 3* Correct syntax: 33* Easier: 3+ [3-7]*4 invalid because 4 is already found by [3-7]* T.*ion invalid because ion is already found by.* Correct syntax: T&ion 13.13.2 Syntax errors The syntax of regular expressions can become very complex particularly where the requirements of the search are themselves very complex. As a result, syntax errors can creep in and invalidate the regular expression. Examples of typical syntax errors Please note that the expressions quoted as "alternative syntax" are only suggestions and in some cases return very different results. They are not universally applicable corrections for the syntax errors concerned but rather produce the desired results for specific requirements. Transit/TermStar NXT Reference Guide 195

13 Regular expressions Wy\ invalid because the backslash must not be the last character The backslash is a meta character (escapement) or introduces a control character. In either case, it has to be followed by another character (see sections 13.3 on page 162 and 13.7 on page 172). Alternative syntax: Wy\\ [9-0]+ invalid because the character class contains an invalid range. When you define a character class, you have to keep to the order in which the characters appear in the ANSI character table (see section 13.5.2 on page 165). Alternative syntax: [0-9]+ [09]+ [0-9]& invalid because the ampersand must not be the last character The ampersand is a meta character (wildcard character representing any sequence of any number of characters). It has to be bounded by beginning and end delimiters (see section 13.5.3 on page 167) Alternative syntax: [0-9]& $ [0-9].*$ key no invalid because the pipe character must not be the last character The pipe character is a meta character (alternative). The pipe character is placed between two alternatives, i.e. it must be followed by the second alternative (see section 13.11 on page 183). Alternative syntax: key no key no yes key no\ (key no invalid because the closing bracket is missing When you use brackets to structure regular expressions, every opening bracket must have a corresponding closing bracket (see section 13.8 on page 174). Alternative syntax: (key no) (key no] invalid because you cannot mix different types of bracket Regular expressions permit the use of round brackets (for structuring) and square brackets (for character groups/classes). Make sure that you do not mix the two types (see sections 13.5.2 on page 165 and 13.8 on page 174). Alternative syntax: (key no) (key [no]) 196 Transit/TermStar NXT Reference Guide

13.14 Appendix overview of meta and control characters 13 *a invalid because the asterisk must not be the first character The asterisk is a meta character (quantifier) and specifies how many instances of the preceding character are to be found. Therefore, it has to be preceded by another character (see section 13.6 on page 169). Alternative syntax: R*a 13.14 Appendix overview of meta and control characters The table below summarises the meta and control characters used in regular expressions. For a more detailed description of the individual characters, refer to sections quoted. Type Meta characters Meaning Control characters \b Backspace \e Escape (ESC) \f Form feed (new page) \n New line \o Segment marker (in Transit editor only) \s Space \t Tabulator \u<code> Unicode characters See Table 13-1 on page 162. Please note: the backslash is also a meta character for an escapement (see section 13.7 on page 172). Tab. 13-29: Meta characters and control characters used in regular expressions Transit/TermStar NXT Reference Guide 197

13 Regular expressions Type Meta characters Meaning Wildcard/ character class Quantifier Escapement Dot:. Square brackets: [xyz] Ampersand: & Question mark: x? Plus sign: x+ Asterisk: x* Backslash: \x Wildcard for any single character. See section 13.5.1 on page 164. Character class: Wildcard for any character of a specified group or class See section 13.5.2 on page 165. Wildcard for any sequence of any number of characters. See section 13.5.3 on page 167. Finds occurrences of absence or a single instance (0-1 instances) of the preceding character. See section 13.6 on page 169. Finds occurrences of a single instance or multiple instances (1 - n instances) of the preceding character. See section 13.6 on page 169. Finds occurrences of the absence, a single instance or multiple instances (0 - n instances) of the preceding character. See section 13.6 on page 169. Forces character to be interpreted literally instead of as a meta character. See section 13.7 on page 172. Please note: The backslash also introduces control characters (see section 13.3 on page 162). Structural Round brackets: (xyz) Structure: You can use round brackets to structure a regular expression to determine, for example, for which part of the expression a preceding meta character should apply. See section 13.8 on page 174. Tab. 13-29: Meta characters and control characters used in regular expressions (cont.) 198 Transit/TermStar NXT Reference Guide

13.14 Appendix overview of meta and control characters 13 Type Meta characters Meaning Logical operator Circumflex: ^ Dollar sign: $ Exclamation mark: (!xxx) [!x] Pipe character: Expression1 Expression2 Beginning of line or field: the expression must occur at the beginning of a line or entry field. See section 13.9 on page 176. End of line or field: the expression must occur at the end of a line or entry field. See section 13.9 on page 176. Negation: The expression which follows may not occur. See section 13.10 on page 178. Alternative: Combines two expressions with a logical OR operation. Finds expression 1 or expression 2. See section 13.11 on page 183. Variable #( )<nr> Variable (in search): stores character string for use in replacement. See section 13.12 on page 186. #<nr> Variable (in replacement): inserts the variable stored by the search operation in the replacement. See section 13.12 on page 186. Tab. 13-29: Meta characters and control characters used in regular expressions (cont.) Transit/TermStar NXT Reference Guide 199

14 Keyboard shortcuts 14 Keyboard shortcuts 14.1 Overview You can also perform many functions in Transit/TermStar NXT using shortcuts. If you are familiar with the shortcuts, you will be able to work significantly faster than with the mouse. In this section you will find a compilation of all keyboard shortcuts of Transit/ TermStar NXT and the Alignment Tool. 14.2 Keyboard shortcuts for Transit NXT 14.2.1 General functions Table 14-1 shows the shortcuts for general functions. Function Close file Save file Save the file and exit Transit Delete the character at the cursor position Find Find next Replace Go to Print file Undo Close window Shortcut CTRL+F4 CTRL+S ALT+F4 DEL CTRL+F ALT+CTRL+Y CTRL+H CTRL+G CTRL+P ALT+BACKSPACE key ESC Tab. 14-1: Transit General functions 200 Transit/TermStar NXT Reference Guide

14.2 Keyboard shortcuts for Transit NXT 14 14.2.2 Moving between windows Table 14-2 shows the shortcuts for moving between windows: Function Back one open language pair Forward one open language pair Switch between tabs Switch to the source-language section of the Transit editor Switch to the target-language section of the Transit editor Switch to the Terminology window Switch to the Notes window Switch to the Source Fuzzy window Switch to the Target Fuzzy window Switch to the Markup window Switch to the viewer (depending on availability) (e. g. InDesign, PowerPoint --> PDF viewer, HTML files --> HTML viewer) Shortcut ALT+F7 ALT+F8 CTRL+TAB ALT+1 ALT+2 ALT+3 ALT+4 ALT+5 ALT+6 ALT+7 ALT+8 Tab. 14-2: Transit Moving between windows 14.2.3 Translating in the Transit editor Table 14-3 lists the shortcuts you can use when translating in the editor: Function Confirm active segment, assign new segment status, move cursor to the next segment that has to be edited and search for fuzzy matches for this segment. Search for fuzzy matches for the current segment Shortcut ALT+INSERT ALT+ENTER Tab. 14-3: Transit Translating in the Transit editor Transit/TermStar NXT Reference Guide 201

14 Keyboard shortcuts Function Undo translation of current segment. To the previous untranslated segment To the next untranslated segment To the previous partially translated segment To the next partially translated segment To the previous segment to be edited. To the next segment to be edited. Delete update marker Shortcut CTRL+ALT+BACKSPACE key CTRL+MINUS (numeric keypad) CTRL+PLUS (numeric keypad) ALT+MINUS (numeric keypad) ALT+PLUS (numeric keypad) CTRL+ALT+MINUS (numeric keypad) CTRL+ALT+PLUS (numeric keypad) In the target-language section of the Transit editor or the Fuzzy window: ALT+U Tab. 14-3: Transit Translating in the Transit editor (cont.) 14.2.4 Working with terminology Table 14-4 shows the shortcuts for working with terminology. Function Replace a word with its (first) translation from the dictionary. Replace a word with its (first) translation from the dictionary and change case Select term to replace a word when there are several dictionary suggestions Select a term to replace a word when there are several dictionary suggestions and change case Insert a translation from the dictionary without replacing a word. Shortcut ALT+T ALT+ SHIFT+T ALT+K, <letter> <Letter> here refers to the letter which is in front of the particular translation in the dictionary window. ALT+K, SHIFT+<letter> <Letter> here refers to the letter which is in front of the particular translation in the dictionary window. ALT+G, <letter> <Letter> here refers to the letter which is in front of the particular translation in the dictionary window. Tab. 14-4: Transit Working with terminology 202 Transit/TermStar NXT Reference Guide

14.2 Keyboard shortcuts for Transit NXT 14 Function Insert translation from the dictionary, without replacing, and change case Switch to the Terminology window Shortcut ALT+G, SHIFT+<letter> <Letter> here refers to the letter which is in front of the particular translation in the dictionary window. ALT+3 Tab. 14-4: Transit Working with terminology (cont.) 14.2.5 Moving the cursor Table 14-5 shows the shortcuts for moving the cursor in the editor. Function Character to the left Character to the right Word to the left Word to the right To the start of segment To the end of segment To the beginning of the line To the end of the line To the next segment Back one segment Up one line Down one line Insert/overwrite To the first line of the file To the last line of the file To the first line in the active window To the last line in the active window To the previous screen Shortcut ARROW LEFT ARROW RIGHT CTRL+ARROW LEFT CTRL+ARROW RIGHT ALT+ARROW LEFT ALT+ARROW RIGHT HOME END PLUS (numeric keypad) MINUS (numeric keypad) ARROW UP ARROW DOWN INSERT CTRL+HOME CTRL+END CTRL+PAGE UP CTRL+PAGE DOWN PAGE UP Tab. 14-5: Transit Moving the cursor Transit/TermStar NXT Reference Guide 203

14 Keyboard shortcuts Function To the next screen Shortcut PAGE DOWN Tab. 14-5: Transit Moving the cursor (cont.) 14.2.6 Formatting text manually Table 14-6 shows shortcuts for formatting text manually in editor: Function Bold Italics Underline Subscript Superscript Shortcut CTRL+SHIFT+B CTRL+SHIFT+I CTRL+SHIFT+U CTRL+] CTRL+\ Tab. 14-6: Transit Formatting text manually 14.2.7 Selecting and editing text blocks Table 14-7 shows shortcuts for selecting and editing text blocks in editor. Function Highlight one character to the left of the cursor Highlight one character to the right of the cursor Highlight to the beginning of a word Highlight to the end of a word Highlight to the beginning of a line Highlight to the end of a line Highlight to the beginning of a segment Highlight to the end of the segment Highlight to the beginning of a file Shortcut SHIFT+ARROW LEFT SHIFT+ARROW RIGHT CTRL+SHIFT+ARROW LEFT CTRL+SHIFT+ARROW RIGHT SHIFT+HOME SHIFT+END SHIFT+ALT+ARROW LEFT SHIFT+ALT+ARROW RIGHT CTRL+SHIFT+HOME Tab. 14-7: Transit Selecting and editing text blocks 204 Transit/TermStar NXT Reference Guide

14.2 Keyboard shortcuts for Transit NXT 14 Function Highlight to the end of a file Highlight one line up Highlight one line down Highlight one screen up Highlight one screen down Cut selected text Copy selected text Delete selected text Paste selected text Change the case of the highlighted text Shortcut CTRL+SHIFT+END SHIFT+ARROW UP SHIFT+ARROW DOWN SHIFT+PAGE UP SHIFT+PAGE DOWN CTRL+X CTRL+C DEL CTRL+V SHIFT+F3 Tab. 14-7: Transit Selecting and editing text blocks (cont.) 14.2.8 Searching for notes Table 14-8 shows the keyboard shortcuts that can be used in the Notes window to search for notes. Function Shortcut Source language notes (Project manager): Previous note Next note ALT+MINUS (numeric keypad) ALT+PLUS (numeric keypad) Target language notes (Translator): Previous note Next note CTRL+MINUS (numeric keypad) CTRL+PLUS (numeric keypad) Source or target language notes: Previous note Next note ALT+CTRL+MINUS (numeric keypad) ALT+CTRL+PLUS (numeric keypad) Tab. 14-8: Transit NXT Searching for notes Transit/TermStar NXT Reference Guide 205

14 Keyboard shortcuts 14.3 Keyboard shortcuts for TermStar NXT 14.3.1 General functions Table 14-1 shows the shortcuts for general functions. Function Close file Save file Exit TermStar Print dictionary Menu bar Close window Search Edit mode Edit mode on right-hand side Data record filter Swap languages Display graphics Undo Redo Shortcut CTRL+F4 CTRL+S ALT+F4 CTRL+P ALT or F10 ESC CTRL+F ENTER or CTRL+E CTRL+ENTER CTRL+L CTRL+A CTRL+G CTRL+Z CTRL+Y Tab. 14-9: TermStar NXT General functions 14.3.2 Navigating within a dictionary Table 14-10 shows the keyboard shortcuts for moving the cursor within a dictionary. Function First data record Last data record Previous page Shortcut CTRL+HOME CTRL+END PAGE UP Tab. 14-10: TermStar NXT Moving the cursor 206 Transit/TermStar NXT Reference Guide

14.3 Keyboard shortcuts for TermStar NXT 14 Function Next page Previous data record Next data record Scrolling up within a data record (right-hand side of the dictionary) Scrolling down within a data record (right-hand side of the dictionary) Cross-reference back Shortcut PAGE DOWN MINUS (numeric keypad) PLUS (numeric keypad) CTRL+ARROW UP CTRL+ARROW DOWN ALT+CTRL+MINUS (numeric keypad). Tab. 14-10: TermStar NXT Moving the cursor (cont.) 14.3.3 Editing data records Table 14-11 shows the keyboard shortcuts for editing data records. Function Insert new data record Delete data record Cut data record Copy data record Insert cut/copied data record Shortcut ALT+PLUS (numeric keypad) ALT+MINUS (numeric keypad) ALT+DIVIDE (numeric keypad) ALT+MULTIPLY (numeric keypad) ALT+ENTER Tab. 14-11: TermStar NXT Editing data records 14.3.4 Edit mode Table 14-7 shows the keyboard shortcuts which you can use in the edit mode. Function Next field Previous field Insert new entry Delete entry Shortcut TAB SHIFT+TAB CTRL+PLUS (numeric keypad) CTRL+MINUS (numeric keypad) Tab. 14-12: TermStar NXT Edit mode Transit/TermStar NXT Reference Guide 207

14 Keyboard shortcuts Function Cut entry Copy entry Insert cut/copied entry Exit edit mode Shortcut CTRL+DIVIDE (numeric keypad) CTRL+MULTIPLY (numeric keypad) CTRL+ENTER ESC Tab. 14-12: TermStar NXT Edit mode (cont.) 14.4 Keyboard shortcuts for Alignment Table 14-8 shows the keyboard shortcuts that can be used to carry out an alignment. Function Move cursor to next aligned segment Move cursor to previous aligned segment Move cursor to next synchronized segment Move cursor to previous synchronized segment Move a segment Delete entire segment Shortcut ALT + MINUS (numerical keypad) ALT + PLUS (numerical keypad) PLUS (numerical keypad) MINUS (numerical keypad) ALT + click right mouse button ALT + DEL Tab. 14-13: Transit NXT Alignment 208 Transit/TermStar NXT Reference Guide

15 Codes and extensions 15 15 Codes and extensions 15.1 Files in Transit/TermStar NXT Table 15-1 provides you with an overview of the most important files used by Transit/ TermStar NXT. File <File name>.<code> <File name>.cod pos_<code>.ewl neg_<code>.ewl <file name>.fpx default.prf Meaning After import, Transit NXT stores the textual information in language files with the file extensions representing the source and target languages. Example: userguide.eng Language file for British English from the original file userguide.doc File with formatting information. Example: userguide.cod File with formatting information from the original file userguide.doc File with the list of abbreviations / list of words which are not abbreviated. Examples: pos_eng.ewl List of abbreviations for British English neg_eng.ewl List of abbreviated words for British English File with information regarding configuration of the windows in Transit NXT Example: userguide_pdf_viewer.fpx Example of window configuration with PDF display File contains user profile settings: all specified user preferences all created macros all settings below Edit Miscellaneous Tab. 15-1: Files in Transit/TermStar NXT Transit/TermStar NXT Reference Guide 209

15 Codes and extensions File <Project name>.prj <project name>.ppf default_<language>.ppx default_tr_<language>.qpx default_ts_<language>.qpx default_tss_<language>.qpx <project name>.tpf Meaning File with project settings Example: userguide.prj File for the project userguide Compressed file with all the files required for sending a project. The project manager sends this file to the translator. Example: userguide.ppf File for sending the project userguide File with information for configuration of the project browser Example: default_eng.ppx Configuration file for the project browser, dialogue language British English File with information regarding configuration of the quick start bar in Transit NXT, TermStar NXT or TermStar NXT Standalone Examples: default_tr_sve.ppx Configuration file for the quick start bar in Transit NXT, dialogue language Swedish default_ts_sve.ppx Configuration file for the quick start bar in TermStar NXT, dialogue language Swedish default_tss_sve.ppx Configuration file for the quick start bar in TermStar NXT Standalone, dialogue language Swedish Compressed file with the translated language files This file is sent back to the project manager by the translator. Example: userguide.tpf File for sending the project translations userguide Tab. 15-1: Files in Transit/TermStar NXT (cont.) 210 Transit/TermStar NXT Reference Guide

15.1 Files in Transit/TermStar NXT 15 File <file name>.tpx <file name>.tsvd <file name>.tvd <code1><code2>.ast _aextr_1.<code> _extr_.<code> Meaning File with information regarding the window configuration in TermStar NXT Example: web-suche_zeichentabelle.tpx Window configuration with web search and character table on display File with information regarding the view in TermStar NXT Example: userguide_terminology.tsvd Example of configuration file for terminology display in TermStar NXT File with information regarding configuration of the view (View tab) in Transit NXT (e.g. presentation of text in the editor) Example: markup_lang.tvd Example of configuration file for display of text in the editor with markups in long form Statistics generated during alignment It contains statistics on the relative word and segment lengths in different language combinations and helps you optimise future alignments. Example: engdeu.ast Statistics for an English- German alignment Reference extract file Example: _aextr_2.eng File for an English reference extract Translation extract file Example: _extr_.eng File with English translation extract Tab. 15-1: Files in Transit/TermStar NXT (cont.) Transit/TermStar NXT Reference Guide 211

15 Codes and extensions File <Script name>.tid <Layout name>.tld <Script name>.tmd Meaning File with settings for import script when importing dictionaries Example: my_import.tid File for import script my_import File with settings for dictionary layout Example: all_langs.tld File for dictionary layout all_langs File with settings for merge script when importing dictionaries Example: my_merge.tmd File for import script my_merge Tab. 15-1: Files in Transit/TermStar NXT (cont.) 15.2 3-letter language code Transit/TermStar NXT uses the 3-letter language code specified by Microsoft (Table 15-2 sorted by language code, table 15-3 on page 220 sorted by language name). 3-letter language code AFK AMH ARA ARB ARE ARG ARH ARI ARJ ARK Language Afrikaans Amharic Arabic (Saudi Arabia) Arabic (Lebanon) Arabic (Egypt) Arabic (Algeria) Arabic (Bahrain) Arabic (Iraq) Arabic (Jordan) Arabic (Kuwait) Tab. 15-2: 3-letter language codes and languages 212 Transit/TermStar NXT Reference Guide

15.2 3-letter language code 15 3-letter language code ARL ARM ARO ARQ ARS ART ARU ARY ASM AZC AZE BEL BGR BNG BOC BOS CAT CHS CHT CSY DAN DEA DEC DEL DES DEU DE1 Language Arabic (Libya) Arabic (Morocco) Arabic (Oman) Arabic (Qatar) Arabic (Syria) Arabic (Tunisia) Arabic (United Arab Emirates) Arabic (Yemen) Assamese Azerbaijani (Cyrillic) Azerbaijani (Latin) Byelorussian Bulgarian Bengali Bosnian (Cyrillic, Bosnia and Herzegovina) Bosnian (Latin, Bosnia and Herzegovina) Catalan Chinese (PR China) Chinese (Taiwan) Czech Danish German (Austria) German (Liechtenstein) German (Luxembourg) German (Swiss) German German (plain language) Tab. 15-2: 3-letter language codes and languages (cont.) Transit/TermStar NXT Reference Guide 213

15 Codes and extensions 3-letter language code EDO EFI ELL EN1 ENA ENB ENC END ENG ENH ENI ENJ ENL ENM ENN ENO ENP ENS ENT ENU ENW ENZ ESA ESB ESC ESD ESE Language Edo Efik / Ibibio Greek English (Simplified) English (Australia) English (Caribbean) English (Canada) English (India) English (UK) English (Hong Kong) English (Ireland) English (Jamaica) English (Belize) English (Malaysia) English (Indonesia) English (Singapore) English (Philippines) English (South Africa) English (Trinidad and Tobago) English (US) English (Zimbabwe) English (New Zealand) Spanish (Panama) Spanish (Bolivia) Spanish (Costa Rica) Spanish (Dominican Republic) Spanish (El Salvador) Tab. 15-2: 3-letter language codes and languages (cont.) 214 Transit/TermStar NXT Reference Guide

15.2 3-letter language code 15 3-letter language code ESF ESG ESH ESI ESL ESM ESO ESP ESR ESS ESU ESV ESY ESZ ETI EUQ FAR FIL FIN FOS FR1 FRA FRB FRC FRE FRG FRH Language Spanish (Ecuador) Spanish (Guatemala) Spanish (Honduras) Spanish (Nicaragua) Spanish (Chile) Spanish (Mexico) Spanish (Colombia) Spanish (Traditional sorting) Spanish (Peru) Spanish (Argentina) Spanish (Puerto Rico) Spanish (Venezuela) Spanish (Uruguay) Spanish (Paraguay) Estonian Basque Persian Filipino (Philippines) Finnish Faroese French (Rationalised) French French (Belgium) French (Canada) French (Senegal) French (Congo) French (Haiti) Tab. 15-2: 3-letter language codes and languages (cont.) Transit/TermStar NXT Reference Guide 215

15 Codes and extensions 3-letter language code FRI FRL FRM FRO FRR FRS FRU FRV FRW FRY FUB GAE GAL GDH GRC GUA GUJ HAU HAW HEB HIN HRB HRV HUN HYE IBO IND Language French (Mali) French (Luxembourg) French (Monaco) French (Cameroon) French (Morocco) French (Swiss) French (Reunion) French (Ivory Coast) French (West Indies) Frisian (Netherlands) Fulfulde Adamawa Gaelic (Ireland) Gallegan/Galician Gaelic (Scotland) Greek (Ancient) Guarani Gujarati Hausa Hawaiian Hebrew Hindi Croatian (Bosnia and Herzegovina) Croatian Hungarian Armenian Igbo Indonesian Tab. 15-2: 3-letter language codes and languages (cont.) 216 Transit/TermStar NXT Reference Guide

15.2 3-letter language code 15 3-letter language code ISL ITA ITS JII JPN KAN KAT KAZ KHM KIR KOR LAO LAT LTH LVI MAL MAR MKD MNG MSB MSL MTL MYA NBL NDE NLB NLD Language Icelandic Italian Italian (Swiss) Yiddish Japanese Kannada Georgian Kazakh Khmer Kirghiz Korean Lao Latin Lithuanian Latvian Malayalam Marathi Macedonian FYRO Mongolian Malay (Burnei Darussalam) Malay Maltese Burmese Ndebele (Southern) Ndebele (Northern) Dutch (Belgium) Dutch Tab. 15-2: 3-letter language codes and languages (cont.) Transit/TermStar NXT Reference Guide 217

15 Codes and extensions 3-letter language code NLS NON NOR NSO ORI ORO PAN PLK PTB PTG QUE RMS ROM ROV RUM RUS SAN SCM SRM SIN SKY SLV SML SQI SRB SRC SRH Language Dutch (Special) Norwegian (Nynorsk) Norwegian (Bokmal) Sotho (Northern) Oriya Oromo Punjabi Polish Portuguese (Brazil) Portuguese Quechua Rhaeto-Romanic Romanian (Standard) Romanian (Moldova) Russian (Moldova) Russian (Standard) Sanskrit Serbian (Cyrillic, Montenegro) Serbian (Latin, Montenegro) Sinhalese Slovak Slovenian Somali Albanian Serbian (Cyrillic) Serbian (Cyrillic, Bosnia and Herzegovina) Serbian (Latin, Bosnia and Herzegovina) Tab. 15-2: 3-letter language codes and languages (cont.) 218 Transit/TermStar NXT Reference Guide

15.2 3-letter language code 15 3-letter language code SRL SSW SVE SWK SXT SZI TAM TEL TGE TGL TGY THA TKM TNA TRK TSG UKR URD URI UZB UZC VEN VIT WEL XHS YBA ZHH Language Serbian (Latin) Siswati Swedish Swahili Sotho (Southern) Sami Tamil Telugu Tigrinya (Eritrea) Tagalog (Philippines) Tigrinya (Ethiopia) Thai Turkmen Tswana Turkish Tsonga Ukrainian Urdu (Pakistan) Urdu (India) Uzbek (Latin) Uzbek (Cyrillic) Venda Vietnamese Welsh Xhosa Yoruba Chinese (Hong Kong) Tab. 15-2: 3-letter language codes and languages (cont.) Transit/TermStar NXT Reference Guide 219

15 Codes and extensions 3-letter language code ZHI ZHM ZUL Language Chinese (Singapore) Chinese (Macau) Zulu Tab. 15-2: 3-letter language codes and languages (cont.) Language Afrikaans Albanian Amharic Arabic (Algeria) Arabic (Bahrain) Arabic (Egypt) Arabic (Iraq) Arabic (Jordan) Arabic (Kuwait) Arabic (Lebanon) Arabic (Libya) Arabic (Morocco) Arabic (Oman) Arabic (Qatar) Arabic (Saudi Arabia) Arabic (Syria) Arabic (Tunisia) Arabic (United Arab Emirates) Arabic (Yemen) Armenian Assamese Azerbaijani (Cyrillic) 3-letter language code AFK SQI AMH ARG ARH ARE ARI ARJ ARK ARB ARL ARM ARO ARQ ARA ARS ART ARU ARY HYE ASM AZC Tab. 15-3: Languages and 3-letter language codes 220 Transit/TermStar NXT Reference Guide

15.2 3-letter language code 15 Language Azerbaijani (Latin) Basque Bengali Bosnian (Latin, Bosnia and Herzegovina) Bosnian (Latin, Montenegro) Bulgarian Burmese Byelorussian Catalan Chinese (Hong Kong) Chinese (Macau) Chinese (PR China) Chinese (Singapore) Chinese (Taiwan) Croatian Croatian (Bosnia and Herzegovina) Czech Danish Dutch Dutch (Belgium) Dutch (Special) Edo Efik / Ibibio English (Australia) English (Belize) English (Canada) English (Caribbean) 3-letter language code AZE EUQ BNG BOS BOC BGR MYA BEL CAT ZHH ZHM CHS ZHI CHT HRV HRB CSY DAN NLD NLB NLS EDO EFI ENA ENL ENC ENB Tab. 15-3: Languages and 3-letter language codes (cont.) Transit/TermStar NXT Reference Guide 221

15 Codes and extensions Language English (Hong Kong) English (India) English (Indonesia) English (Ireland) English (Jamaica) English (Malaysia) English (New Zealand) English (Philippines) English (Simplified) English (Singapore) English (South Africa) English (Trinidad and Tobago) English (UK) English (US) English (Zimbabwe) Estonian Faroese Filipino (Philippines) Finnish French French (Belgium) French (Cameroon) French (Canada) French (Congo) French (Haiti) French (Ivory Coast) French (Luxembourg) 3-letter language code ENH END ENN ENI ENJ ENM ENZ ENP EN1 ENO ENS ENT ENG ENU ENW ETI FOS FIL FIN FRA FRB FRO FRC FRG FRH FRV FRL Tab. 15-3: Languages and 3-letter language codes (cont.) 222 Transit/TermStar NXT Reference Guide

15.2 3-letter language code 15 Language French (Mali) French (Monaco) French (Morocco) French (Rationalised) French (Reunion) French (Senegal) French (Swiss) French (West Indies) Frisian (Netherlands) Fulfulde Adamawa Gaelic (Ireland) Gaelic (Scotland) Gallegan/Galician Georgian German German (Austria) German (Liechtenstein) German (Luxembourg) German (plain language) German (Swiss) Greek Greek (Ancient) Guarani Gujarati Hausa Hawaiian Hebrew 3-letter language code FRI FRM FRR FR1 FRU FRE FRS FRW FRY FUB GAE GDH GAL KAT DEU DEA DEC DEL DE1 DES ELL GRC GUA GUJ HAU HAW HEB Tab. 15-3: Languages and 3-letter language codes (cont.) Transit/TermStar NXT Reference Guide 223

15 Codes and extensions Language Hindi Hungarian Icelandic Igbo Indonesian Italian Italian (Swiss) Japanese Kannada Kazakh Khmer Kirghiz Korean Lao Latin Latvian Lithuanian Macedonian FYRO Malay Malay (Burnei Darussalam) Malayalam Maltese Marathi Mongolian Ndebele (Northern) Ndebele (Southern) Norwegian (Bokmal) 3-letter language code HIN HUN ISL IBO IND ITA ITS JPN KAN KAZ KHM KIR KOR LAO LAT LVI LTH MKD MSL MSB MAL MTL MAR MNG NDE NBL NOR Tab. 15-3: Languages and 3-letter language codes (cont.) 224 Transit/TermStar NXT Reference Guide

15.2 3-letter language code 15 Language Norwegian (Nynorsk) Oriya Oromo Persian Polish Portuguese Portuguese (Brazil) Punjabi Quechua Rhaeto-Romanic Romanian (Moldova) Romanian (Standard) Russian (Moldova) Russian (Standard) Sami Sanskrit Serbian (Cyrillic) Serbian (Cyrillic, Bosnia and Herzegovina) Serbian (Cyrillic, Montenegro) Serbian (Latin) Serbian (Latin, Bosnia and Herzegovina) Serbian (Latin, Montenegro) Sinhalese Siswati Slovak Slovenian Somali 3-letter language code NON ORI ORO FAR PLK PTG PTB PAN QUE RMS ROV ROM RUM RUS SZI SAN SRB SRC SCM SRL SRH SRM SIN SSW SKY SLV SML Tab. 15-3: Languages and 3-letter language codes (cont.) Transit/TermStar NXT Reference Guide 225

15 Codes and extensions Language Sotho (Northern) Sotho (Southern) Spanish (Argentina) Spanish (Bolivia) Spanish (Chile) Spanish (Colombia) Spanish (Costa Rica) Spanish (Dominican Republic) Spanish (Ecuador) Spanish (El Salvador) Spanish (Guatemala) Spanish (Honduras) Spanish (Mexico) Spanish (Nicaragua) Spanish (Panama) Spanish (Paraguay) Spanish (Peru) Spanish (Puerto Rico) Spanish (Traditional sorting) Spanish (Uruguay) Spanish (Venezuela) Swahili Swedish Tagalog (Philippines) Tamil Telugu Thai 3-letter language code NSO SXT ESS ESB ESL ESO ESC ESD ESF ESE ESG ESH ESM ESI ESA ESZ ESR ESU ESP ESY ESV SWK SVE TGL TAM TEL THA Tab. 15-3: Languages and 3-letter language codes (cont.) 226 Transit/TermStar NXT Reference Guide

15.3 Microsoft language code 15 Language Tigrinya (Eritrea) Tigrinya (Ethiopia) Tsonga Tswana Turkish Turkmen Ukrainian Urdu (Pakistan) Urdu (India) Uzbek (Cyrillic) Uzbek (Latin) Venda Vietnamese Welsh Xhosa Yiddish Yoruba Zulu 3-letter language code TGE TGY TSG TNA TRK TKM UKR URD URI UZC UZB VEN VIT WEL XHS JII YBA ZUL Tab. 15-3: Languages and 3-letter language codes (cont.) 15.3 Microsoft language code In the following table 15-4 you will find a list of supported languages (sorted by 3-letter language code) and their Microsoft language codes (hexadecimal and decimal). 3-letter language code Language MS Code hex. MS Code dec. AFK Afrikaans 0x0436 1078 Tab. 15-4: Microsoft language code Transit/TermStar NXT Reference Guide 227

15 Codes and extensions 3-letter language code Language MS Code hex. MS Code dec. AMH Amharic 0x045E 1118 ARA Arabic (Saudi Arabia) 0x0401 1025 ARB Arabic (Lebanon) 0x3001 12289 ARE Arabic (Egypt) 0x0C01 3073 ARG Arabic (Algeria) 0x1401 5121 ARH Arabic (Bahrain) 0x3C01 15361 ARI Arabic (Iraq) 0x0801 2049 ARJ Arabic (Jordan) 0x2C01 11265 ARK Arabic (Kuwait) 0x3401 13313 ARL Arabic (Libya) 0x1001 4097 ARM Arabic (Morocco) 0x1801 6145 ARO Arabic (Oman) 0x2001 8193 ARQ Arabic (Qatar) 0x4001 16385 ARS Arabic (Syria) 0x2801 10241 ART Arabic (Tunisia) 0x1C01 7169 ARU Arabic (United Arab Emirates) 0x3801 14337 ARY Arabic (Yemen) 0x2401 9217 ASM Assamese 0x044D 1101 AZC Azerbaijani (Cyrillic) 0x082C 2092 AZE Azerbaijani (Latin) 0x042C 1068 BEL Byelorussian 0x0423 1059 BGR Bulgarian 0x0402 1026 BNG Bengali 0x0445 1252 BOC Bosnian (Cyrillic, Bosnia and Herzegovina) 0x201A 8218 Tab. 15-4: Microsoft language code (cont.) 228 Transit/TermStar NXT Reference Guide

15.3 Microsoft language code 15 3-letter language code Language MS Code hex. MS Code dec. BOS Bosnian (Latin, Bosnia and Herzegovina) 0x141A 5146 CAT Catalan 0x0403 1027 CHS Chinese (PR China) 0x0804 2052 CHT Chinese (Taiwan) 0x0404 1028 CSY Czech 0x0405 1029 DAN Danish 0x0406 1030 DEA German (Austria) 0x0C07 3079 DEC German (Liechtenstein) 0x1407 5127 DEL German (Luxembourg) 0x1007 4103 DES German (Swiss) 0x0807 2055 DEU German 0x0407 1031 DE1 German (plain language) 0x7C07 31751 EDO Edo 0x0466 1126 EFI Efik / Ibibio 0x0469 1129 ELL Greek 0x0408 1032 EN1 English (Simplified) ENA English (Australia) 0x0C09 3081 ENB English (Caribbean) 0x2409 9225 ENC English (Canada) 0x1009 4105 END English (India) 0x4009 16393 ENG English (UK) 0x0809 2057 ENH English (Hong Kong) 0x3C09 15369 ENI English (Ireland) 0x1809 6153 ENJ English (Jamaica) 0x2009 8201 ENL English (Belize) 0x2809 10249 ENM English (Malaysia) 0x4409 17417 Tab. 15-4: Microsoft language code (cont.) Transit/TermStar NXT Reference Guide 229

15 Codes and extensions 3-letter language code Language MS Code hex. MS Code dec. ENN English (Indonesia) 0x3809 14345 ENO English (Singapore) 0x4C09 19465 ENP English (Philippines) 0x3409 13321 ENS English (South Africa) 0x1C09 7177 ENT English (Trinidad and Tobago) 0x2C09 11273 ENU English (US) 0x0409 1033 ENW English (Zimbabwe) 0x3009 12297 ENZ English (New Zealand) 0x1409 5129 ESA Spanish (Panama) 0x180A 6154 ESB Spanish (Bolivia) 0x400A 16394 ESC Spanish (Costa Rica) 0x140A 5130 ESD Spanish (Dominican Republic) 0x1C0A 7178 ESE Spanish (El Salvador) 0x440A 17418 ESF Spanish (Ecuador) 0x300A 12298 ESG Spanish (Guatemala) 0x100A 4106 ESH Spanish (Honduras) 0x480A 18442 ESI Spanish (Nicaragua) 0x4C0A 19466 ESL Spanish (Chile) 0x340A 13322 ESM Spanish (Mexico) 0x080A 2058 ESO Spanish (Colombia) 0x240A 9226 ESP Spanish (Traditional sorting) 0x040A 1034 ESR Spanish (Peru) 0x280A 10250 ESS Spanish (Argentina) 0x2C0A 11274 ESU Spanish (Puerto Rico) 0x500A 20490 ESV Spanish (Venezuela) 0x200A 8202 Tab. 15-4: Microsoft language code (cont.) 230 Transit/TermStar NXT Reference Guide

15.3 Microsoft language code 15 3-letter language code Language MS Code hex. MS Code dec. ESY Spanish (Uruguay) 0x380A 14346 ESZ Spanish (Paraguay) 0x3C0A 15370 ETI Estonian 0x0425 1061 EUQ Basque 0x042D 1069 FAR Persian 0x0429 1065 FIL Filipino (Philippines) 0x0464 1124 FIN Finnish 0x040B 1035 FOS Faroese 0x0438 1080 FR1 French (Rationalised) FRA French 0x040C 1036 FRB French (Belgium) 0x080C 2060 FRC French (Canada) 0x0C0C 3084 FRE French (Senegal) 0x280C 10252 FRG French (Congo) 0x240C 9228 FRH French (Haiti) 0x3C0C 15372 FRI French (Mali) 0x340C 13324 FRL French (Luxembourg) 0x140C 5132 FRM French (Monaco) 0x180C 6156 FRO French (Cameroon) 0x2C0C 11276 FRR French (Morocco) 0x380C 14348 FRS French (Swiss) 0x100C 4108 FRU French (Reunion) 0x200C 8204 FRV French (Ivory Coast) 0x300C 12300 FRW French (West Indies) 0x1C0C 7180 FRY Frisian (Netherlands) 0x0462 1122 FUB Fulfulde Adamawa 0x0467 1127 Tab. 15-4: Microsoft language code (cont.) Transit/TermStar NXT Reference Guide 231

15 Codes and extensions 3-letter language code Language MS Code hex. MS Code dec. GAE Gaelic (Ireland) 0x083C 2108 GAL Gallegan/Galician 0x0456 1110 GDH Gaelic (Scotland) 0x043C 1084 GRC Greek (Ancient) 0x7C08 31752 GUA Guarani GUJ Gujarati 0x0447 1252 HAU Hausa 0x0468 1128 HAW Hawaiian 0x0475 1141 HEB Hebrew 0x040D 1037 HIN Hindi 0x0439 1252 HRB Croatian (Bosnia and Herzegovina) 0x101a 4122 HRV Croatian 0x041A 1050 HUN Hungarian 0x040E 1038 HYE Armenian 0x042b 1067 IBO Igbo 0x0470 1136 IND Indonesian 0x0421 1057 ISL Icelandic 0x040F 1039 ITA Italian 0x0410 1040 ITS Italian (Swiss) 0x0810 2064 JII Yiddish 0x043D 1085 JPN Japanese 0x0411 1041 KAN Kannada 0x044B 1099 KAT Georgian 0x0437 1252 KAZ Kazakh 0x043F 1087 KHM Khmer 0x0453 KIR Kirghiz 0x0440 1088 Tab. 15-4: Microsoft language code (cont.) 232 Transit/TermStar NXT Reference Guide

15.3 Microsoft language code 15 3-letter language code Language MS Code hex. MS Code dec. KOR Korean 0x0412 1042 LAO Lao 0x0454 1108 LAT Latin 0x0476 1142 LTH Lithuanian 0x0427 1063 LVI Latvian 0x0426 1062 MAL Malayalam 0x044C 1100 MAR Marathi 0x044E 1102 MKD Macedonian FYRO 0x042F 1071 MNG Mongolian 0x0450 1104 MSB Malay (Burnei Darussalam) 0x083E 2110 MSL Malay 0x043E 1086 MTL Maltese 0x043A 1082 MYA Burmese 0x0455 1109 NBL Ndebele (Southern) 0x04EE 1262 NDE Ndebele (Northern) 0x08EE 2286 NLB Dutch (Belgium) 0x0813 2067 NLD Dutch 0x0413 1043 NLS Dutch (Special) 0x7C13 31763 NON Norwegian (Nynorsk) 0x0814 2068 NOR Norwegian (Bokmal) 0x0414 1044 NSO Sotho (Northern) 0x0830 2096 ORI Oriya 0x0448 1096 ORO Oromo 0x0472 1138 PAN Punjabi 0x0446 1094 PLK Polish 0x0415 1045 PTB Portuguese (Brazil) 0x0416 1046 Tab. 15-4: Microsoft language code (cont.) Transit/TermStar NXT Reference Guide 233

15 Codes and extensions 3-letter language code Language MS Code hex. MS Code dec. PTG Portuguese 0x0816 2070 QUE Quechua 0x046B 1131 RMS Rhaeto-Romanic 0x0417 1047 ROM Romanian (Standard) 0x0418 1048 ROV Romanian (Moldova) 0x0818 2072 RUM Russian (Moldova) 0x0819 2073 RUS Russian (Standard) 0x0419 1049 SAN Sanskrit 0x044F 1103 SCM SRM Serbian (Cyrillic, Montenegro) Serbian (Latin, Montenegro) 0x301A 12314 0x2C1A 11290 SIN Sinhala / Sinhalese 0x045B 1115 SKY Slovak 0x041B 1051 SLV Slovenian 0x0424 1060 SML Somali 0x0477 1143 SQI Albanian 0x041C 1052 SRB Serbian (Cyrillic) 0x0C1A 3098 SRC SRH Serbian (Cyrillic, Bosnia and Herzegovina) Serbian (Latin, Bosnia and Herzegovina) 0x1c1a 7194 0x181a 6170 SRL Serbian (Latin) 0x081A 2074 SSW Siswati 0x04ED 1261 SVE Swedish 0x041D 1053 SWK Swahili 0x0441 1089 SXT Sotho (Southern) 0x0430 1072 SZI Sami 0x043B 1083 Tab. 15-4: Microsoft language code (cont.) 234 Transit/TermStar NXT Reference Guide

15.3 Microsoft language code 15 3-letter language code Language MS Code hex. MS Code dec. TAM Tamil 0x0449 1097 TEL Telugu 0x044A 1098 TGE Tigrinya (Eritrea) 0x0873 2163 TGL Tagalog (Philippines) TGY Tigrinya (Ethiopia) 0x0473 1139 THA Thai 0x041E 1054 TKM Turkmen 0x0442 1090 TNA Tswana 0x0432 1074 TRK Turkish 0x041F 1055 TSG Tsonga 0x0431 1073 UKR Ukrainian 0x0422 1058 URD Urdu (Pakistan) 0x0420 1056 URI Urdu (India) 0x0820 1056 UZB Uzbek (Latin) 0x0443 1091 UZC Uzbek (Cyrillic) 0x0843 2115 VEN Venda 0x0433 1075 VIT Vietnamese 0x042A 1066 WEL Welsh 0x0452 1106 XHS Xhosa 0x0434 1076 YBA Yoruba 0x046A 1130 ZHH Chinese (Hong Kong) 0x0C04 3076 ZHI Chinese (Singapore) 0x1004 4100 ZHM Chinese (Macau) 0x1404 5124 ZUL Zulu 0x0435 1077 Tab. 15-4: Microsoft language code (cont.) Transit/TermStar NXT Reference Guide 235

Head Office of the STAR Group STAR AG Wiesholz 35 8262 Ramsen Switzerland Phone: +41 52 742 92 00 Fax: +41 52 742 92 92 E-mail: info@star-group.net www.star-group.net