TransitNXT Advanced AdvancedFeatures ENG

Transit/TermStar NXT
G ui d e
Reference
2013-06
2013 STAR AG
All rights reserved. Reproduction of the contents of this copyrighted publication, in
whole or in part, without written permission of STAR AG is prohibited. This applies particularly to the duplication or the use of the content for training courses or electronic
systems.
The content of this publication has been checked to the best of our knowledge and
ability. STAR AG does not assume responsibility or liability for any loss caused by or
connected with the use of this publication.
STAR AG
Wiesholz 35 8262 Ramsen
Switzerland
www.star-group.net
STAR Language Technology & Solutions GmbH
Schnaicher Str. 19 71032 Bblingen
Germany
Registered trademarks
All trade names are registered trademarks of the respective producers.
130620
Transit/TermStar NXT Reference Guide
Contents
130620
Contents
1
Using startup parameters for Transit/

TermStar NXT
1.1
-U (Start with a specific user) ............................................................ 9
1.2
-H (Start with a specific user role)...........................................10
Exchanging reference material via TMX
2.1
Overview ............................................................................................... 12
2.2
Exporting language pairs to TMX file .............................................. 13
2.2.1
2.2.2
Exporting files to a TMX file ..................................................................... 13

Exporting the current project to a TMX file.............................................. 15
2.3
Importing TMX files in Transit NXT ................................................. 16
2.3.1
2.3.2
2.3.3
Naming and saving of language pairs ..................................................... 16

Performing a TMX import......................................................................... 18
Using segments from TMX import as reference material ........................ 19
2.4
Compatibility of the language and country codes of TMX files 20
2.4.1
2.4.2
2.4.3
2.4.4
Overview .................................................................................................. 20
Differences in the usage of language and country codes ....................... 20
Importing TMX files from Transit into Trados .......................................... 21
Importing TMX files from Trados into Transit .......................................... 22
Managing roles
3.1
Overview ............................................................................................... 23
3.2
Opening a role ..................................................................................... 23
3.3
Creating a new role ............................................................................. 26
3.3.1
3.3.2
3.3.3
Creating completely new roles ................................................................ 26

Editing an existing role............................................................................. 27
Allocating passwords to user roles.......................................................... 28
3.4
Overview of standard roles ............................................................... 30
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
Overview .................................................................................................. 30
Ribbon bar, general functions ................................................................. 31
Ribbon bar, Transit-specific functions..................................................... 33
Ribbon bar, TermStar-specific functions................................................. 36
Transit/TermStar button........................................................................... 37
Resource bar ........................................................................................... 38
Customising Transit/TermStar NXT
4.1
Overview............................................................................................... 41
4.2
Automating tasks using macros ........................................................ 41
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
Overview.................................................................................................. 41
Tips for creating macros ......................................................................... 42
Recording a new macro .......................................................................... 43
Running the macro .................................................................................. 44
Editing the macro .................................................................................... 45
Example macro: Inserting Unicode characters ....................................... 47
4.3
Customising the system environment ............................................. 49
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
Overview.................................................................................................. 49
Common access to settings and folders in a network............................ 49
Multithreading for multilingual projects ................................................... 50
Restricting a background search with shared dictionaries ..................... 52
Updating common dictionaries ............................................................... 53
Specifying dialogue box fonts ................................................................. 54
4.4
Spellchecking: list of unknown words ............................................ 55
4.4.1
Opening and editing the list of unknown words...................................... 56
4.5
Customising index buttons for TermStar NXT .............................. 57
4.5.1
4.5.2
4.5.3
Overview.................................................................................................. 57
Configuration file for index buttons ......................................................... 57
Changing index buttons .......................................................................... 57
4.6
Checking and changing abbreviation list ....................................... 58
Print definition set-up
5.1
Overview............................................................................................... 60
5.2
Opening a print definition................................................................. 60
5.2.1
5.2.2
5.2.3
5.2.4
5.2.5
Saving the print definition........................................................................ 61

Setting page margins .............................................................................. 63
Defining separators for dictionaries ........................................................ 64
Specifying headers and footers .............................................................. 67
Specifying the page layout ...................................................................... 70
Customising projects
6.1
Overview............................................................................................... 72
6.2
Compressing files with formatting information (cod files) ......... 73
6.3
Excluding hidden or locked text from translation in Excel ........ 73
6.4
Optimising the pretranslation time ................................................. 75
6.4.1
Overview.................................................................................................. 75
130620
Contents
130620
Contents
6.4.2
6.4.3
The MaxPreTransHits parameter..................................................... 75

Customising the MaxPreTransHits parameter .................................... 76
Fields in the TermStar dictionary
7.1
Overview ............................................................................................... 77
7.2
Field types ............................................................................................. 77
7.2.1
7.2.2
7.2.3
7.2.4
Header fields............................................................................................ 78
Language fields........................................................................................ 80
Entry fields and subentry fields................................................................ 81
Subentry types......................................................................................... 84
Customising layouts
8.1
Overview ............................................................................................... 85
8.2
Managing layouts ................................................................................. 85
8.2.1
8.2.2
8.2.3
8.2.4
Overview .................................................................................................. 85
Creating a new layout .............................................................................. 86
Opening existing layouts ......................................................................... 86
Saving the layout and closing the layout editor....................................... 88
8.3
Working with the layout editor ........................................................ 90
8.3.1
8.3.2
8.3.3
8.3.4
Areas of a layout ...................................................................................... 90

Layout editor interface ............................................................................. 90
Available Fields ........................................................................................ 92
Structure of the language units ............................................................... 93
8.4
Editing the layout ................................................................................. 95
8.4.1
8.4.2
8.4.3
Selecting and removing fields for the layout ........................................... 95

Inserting and deleting static text unit....................................................... 96
Specifying the order of fields ................................................................... 97
8.5
Specifying field properties ................................................................. 98
8.5.1
8.5.2
8.5.3
8.5.4
8.5.5
8.5.6
8.5.7
8.5.8
Overview .................................................................................................. 98
Formatting units....................................................................................... 99
Formatting entries and subentries ......................................................... 100
Formatting the fields .............................................................................. 102
Entering and formatting static text units................................................ 103
Variables ................................................................................................ 104
Formatting automatic cross-references ................................................ 104
General layout settings .......................................................................... 107
Customising dictionaries
9.1
Overview ............................................................................................. 110
9.2
Modifying field names ...................................................................... 110
9.2.1
9.2.2
9.2.3
9.2.4
9.2.5
Overview................................................................................................ 110
Changing field names for all languages ................................................ 111
Changing field names for specific languages ....................................... 112
Resetting changed field names ............................................................. 113
Transferring field names from other dictionaries................................... 114
9.3
Setting graphics file access.............................................................. 115
9.4
Specifying cross-reference separators .......................................... 116
9.5
Specify additional sort field ............................................................ 117
10
Spellcheck dictionaries
10.1
Installing a spellcheck dictionary .................................................. 124
10.1.1
Uninstalling spellcheck dictionaries ...................................................... 125
11
Managing database links
11.1
Overview............................................................................................. 126
11.2
Creating a database link .................................................................. 126
11.2.1
11.2.2
11.2.3
Overview................................................................................................ 126
Connecting an MS Access database .................................................... 127
Connecting an MS SQL database......................................................... 132
11.3
Deleting a database link .................................................................. 136
11.4
Transferring database connections to other computers ........... 137
11.5
Deleting incorrect database links .................................................. 140
11.6
Compressing databases and dictionaries ..................................... 141
11.7
Database driver information........................................................... 141
12
Compacting Microsoft Access database or

transferring it to SQL server
12.1
Overview............................................................................................. 143
12.2
Transferring TermStar databases from Microsoft Access to an

SQL server........................................................................................... 147
12.2.1
12.2.2
12.2.3
Renaming an ODBC connection in Windows........................................ 148

Creating a database in Transit/TermStar NXT ...................................... 150
Transferring a database from Access to an SQL server ....................... 154
130620
Contents
130620
Contents
13
Regular expressions
13.1
Overview ............................................................................................. 158
13.1.1
13.1.2
13.1.3
What are regular expressions? .............................................................. 158

Basic settings for searches in Transit NXT ............................................ 158
What can you use regular expressions for? .......................................... 159
13.2
Defining regular expressions ........................................................... 160
13.3
Control characters ............................................................................. 161
13.4
Overview of meta characters.......................................................... 162
13.5
Wildcards: . [ ] & ......................................................................... 163
13.5.1
13.5.2
13.5.3
Wildcard for any single character: . (dot) ............................................. 163

Wildcard for any of a specified group or class: square brackets ([])... 164
Wildcard for any sequence of characters: ampersand (&)..................... 166
13.6
Quantifiers: +*? ................................................................................. 168
13.7
Escapement: \..................................................................................... 171
13.8
Applying meta characters to character strings: ( ) .................. 173
13.9
Placement: ^ $ .................................................................................. 175
13.10
Negation: ! ......................................................................................... 177
13.10.1
13.10.2
13.10.3
Negation of a character or character string........................................... 178

Negation of a character group............................................................... 179
Negation of beginning/end of line.......................................................... 180
13.11
Alternatives: | .................................................................................... 182
13.11.1
13.11.2
13.11.3
What does Transit NXT interpret as an alternative? .............................. 182

Alternatives and character groups/classes............................................ 183
Alternatives and negated character strings ........................................... 184
13.12
Variables: # ......................................................................................... 185
13.12.1
13.12.2
13.12.3
13.12.4
13.12.5
13.12.6
Why use variables?................................................................................ 185

How are variables used? ....................................................................... 186
Changing the case when replacing ....................................................... 188
Changing number formats when replacing ........................................... 189
Performing mathematical calculations when replacing ......................... 190
Rounding figures when replacing .......................................................... 192
13.13
Invalid regular expressions .............................................................. 194
13.13.1
13.13.2
Ambiguous regular expressions ............................................................ 194

Syntax errors.......................................................................................... 194
13.14
Appendix overview of meta and control characters .............. 196
14
Keyboard shortcuts
14.1
Overview ............................................................................................. 199
14.2
Keyboard shortcuts for Transit NXT .............................................. 199
14.2.1
14.2.2
14.2.3
14.2.4
14.2.5
14.2.6
14.2.7
14.2.8
General functions .................................................................................. 199

Moving between windows..................................................................... 200
Translating in the Transit editor............................................................. 200
Working with terminology...................................................................... 201
Moving the cursor ................................................................................. 202
Formatting text manually....................................................................... 203
Selecting and editing text blocks .......................................................... 203
Searching for notes ............................................................................... 204
14.3
Keyboard shortcuts for TermStar NXT ......................................... 205
14.3.1
14.3.2
14.3.3
14.3.4
General functions .................................................................................. 205

Navigating within a dictionary ............................................................... 205
Editing data records .............................................................................. 206
Edit mode .............................................................................................. 206
14.4
Keyboard shortcuts for Alignment................................................. 207
15
Codes and extensions
15.1
Files in Transit/TermStar NXT ........................................................ 208
15.2
3-letter language code ..................................................................... 211
15.3
Microsoft language code ................................................................. 226
130620
Contents
1 Using startup parameters for Transit/TermStar NXT
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.
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
-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
130620
Syntax of the
startup parameter
-U[<UserShortName>]
Using startup parameters for Transit/TermStar NXT
Attribute <UserShortName> (optional):
Attribute
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).
Sample call
"d:\Transit_NXT\bin\transitnxt.exe" -Ucon
Transit/TermStar NXT starts with the user with the short

name con.
1.2
-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).
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
-H[<n>]
Attribute
Attribute <n> (optional):
User role with which Transit/TermStar NXT should start.
10
130620
1.2 -H
(Start with a specific user role)
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
130620
Transit NXT starts with the Super User user role.
11
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 13.
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 16.
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 20 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.
12
130620
2.2 Exporting language pairs to TMX file
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 13
Exporting the current project to a TMX file on page 15
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:
130620
Fig. 2-1: Create TMX file window
13
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.
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.
14
Click OK to close the Export progress window.
130620
2.2 Exporting language pairs to TMX file
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 13).
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
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
130620
the file name extension .tmx. Click Save to confirm the information specified.
15
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.
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:
Transit has saved the TMX file to the folder you selected.
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.
16
130620
2.3 Importing TMX files in Transit NXT
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 20.)
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:
130620
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.
17
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
Click . to the right of the TMX import file field to select the TMX file you want
to import.
Select the TMX file you wish to import. Confirm your choice by clicking Open.
Specify the file names and folder for the language files which Transit NXT should
generate from the TMX file.
Transit NXT displays the Open TMX file window.
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.
18
130620
2.3 Importing TMX files in Transit NXT
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:
Transit NXT has imported the TMX files and saved them to the language files in
the folder you selected.
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.
130620
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.
19
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 20) or country codes (Table 2-2 on page 21) 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)
nn
no
no
Norwegian
(Bokml)
nb
no
no
Serbian
sr
sr
sh
Tab. 2-1: Language codes according to ISO 639-1 in Transit NXT and in SDL Trados
20
130620
2.4 Compatibility of the language and country codes of TMX files
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
130620
Tab. 2-3: Identifier from Transit NXT as per standard
21
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
22
130620
3 Managing roles
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 23)
as well as to create your own roles (see section 3.3 Creating a new role on page 26).
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 30).
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)
130620
Other elements of a role definition are the windows and views linked to the role.
23
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):
Fig. 3-1: Manage user roles window
24
Select Open.
130620
3.2 Opening a role
Transit/TermStar NXT opens the Open user role window (Fig. 3-2):
Fig. 3-2: Open user role window
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.
130620
You will find the view in Transit/TermStar NXT assigned to the role in the View
section.
25
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 23), 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.
Click Create.
Transit/TermStar NXT opens the Manage user roles window.

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
23.
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,
activate the Hide greyed-out groups in the ribbon bar option.
26
Click Save to save the information entered.
130620
3.3 Creating a new role
Transit/TermStar NXT displays the Save user role window with the existing
roles (Fig. 3-3).
Fig. 3-3: Save role window with existing roles
Enter a name for the new role in the Filename field.
Select a scope of validity for your new role at Scope.
Click Save to confirm the information entered.

Transit/TermStar NXT saves the role under the selected name.
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 23.
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.
Click Save As.

Transit/TermStar NXT displays the Save user role window with the existing
roles (Fig. 3-3).
Enter a name for the new role in the Filename field.
Select a scope of validity for your new role at Scope.
130620
Transit/TermStar NXT saves the role under the selected name.
27
Managing roles
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 23.
If you do not want to display groups on the ribbon bar which are completely
inactive, activate the Hide greyed-out groups in the ribbon bar option.
As an option, a password can be allocated for the role
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 26 or 3.3.2 Editing an existing role on page 27).
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).
Fig. 3-4: Manage user roles window, tree structure
28
130620
3.3 Creating a new role
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).
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.
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.
If Transit/TermStar NXT is already open, the role can be opened as described in

section 3.2 Opening a role on page 23.
130620
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).
29
Managing roles
Transit/TermStar NXT opens the Enter password window.
Fig. 3-6: Enter password window
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 31.
Tab. 3-2: Roles and Transit-specific functions of the ribbon bar on page 33.
Tab. 3-3: Roles and TermStar-specific functions of the ribbon bar on page 36.
Tab. 3-4: Roles and the Transit/TermStar button on page 37.
Tab. 3-5: Roles and the resource bar on page 38.
30
130620
3.4 Overview of standard roles
3.4.2
Ribbon bar, general functions
Project Manager
Project Calculation Manager
Translator
Reviewer
Markup Specialist
Reference Material Manager
Alignment Specialist
Terminology manager
Terminologist
Terminology Translator
Localisation Specialist
Super User
Create
Open
Open
language pair
Settings
Save
Save as
Delete
Import
Export
Merge extract
Pack
Forward project
Unpack
Group
Tab
Table 3-1 shows the effect of the selected role on the available general groups in the
ribbon bar:
Administration |
Workflow |
Project
Exchange |
130620
Tab. 3-1: Roles and general functions of the ribbon bar
31
Project Manager
Translator
Reviewer
Markup Specialist
Terminology manager
Terminologist
Super User
Unpack
translation
Project
Template
Customer
Language pairs
Terminology
Clipboard
Format
Macros
Character table
Bookmark
Set flag
Go to flag
AutoText
Read only
Change case
Miscellaneous
Administration
Activate
TermStar
Group
Tab
Pack translation
Statistics
Managing roles
Edit
Text |
Window
Tab. 3-1: Roles and general functions of the ribbon bar (cont.)
32
130620
3.4.3
Ribbon bar, Transit-specific functions
Project Manager
Translator
Reviewer
Markup Specialist
Terminology manager
Terminologist
Super User
Find
Replace
Go to
Number
Confirm
Next
Navigate
Segment status
Join
Undo join
On/Off
Next
Translate group
Navigate
Group
Tab
Table 3-2 shows the effect of the selected role on the available Transit-specific groups
in the ribbon bar:
Find |
Translate |
Editing
Internal
Repetitions |
Markups
130620
Tab. 3-2: Roles and Transit-specific functions of the ribbon bar
33
Group
Project Manager
Translator
Reviewer
Markup Specialist
Terminology manager
Terminologist
Super User
Matches
Check
Tab
Managing roles
Proofread
Spellcheck
Terminology
Format check
Dual Concordance
search
Fuzzy search
(source)
Fuzzy search
(target)
Creation
Find
Options
Automatic
insert |
Segment
Automatic
insert | File
Dynamic Linking
Alignment
Confirm proposal
Segments
Confirm man. align.
Terminology
Use |
Alignment
Tab. 3-2: Roles and Transit-specific functions of the ribbon bar (cont.)
34
130620
Group
Project Manager
Translator
Reviewer
Markup Specialist
Terminology manager
Terminologist
Super User
Tab
Segment Filter
Language pair
Segments
Display text
Terminology
layout
Save
Save as
Delete
Reset
View for Transit

editor
View
Administration |
130620
Tab. 3-2: Roles and Transit-specific functions of the ribbon bar (cont.)
35
Managing roles
3.4.4
Ribbon bar, TermStar-specific functions
Group
Project Manager
Translator
Reviewer
Markup Specialist
Terminology manager
Terminologist
Super User
Find
Editing
Tab
Table 3-3 shows the effect of the selected role on the available TermStar-specific
groups in the ribbon bar:
Data record
Language entry
Global changes
In the dictionary
Dynamic Linking
Languages
Create
Change
Delete
Data record filter
On/Off
Default data
record filter
Terminology
display
Administration
Data record filter |
View
Tab. 3-3: Roles and TermStar-specific functions of the ribbon bar
36
130620
3.4.5
Transit/TermStar button
Menu item
Project Manager
Translator
Reviewer
Markup Specialist
Terminology manager
Terminologist
Super User
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):
Open dictionaries
Open language pair
Save language pair
Save all language pairs
Save as
Printing
Close language pair
Close all language pairs
130620
Tab. 3-4: Roles and the Transit/TermStar button
37
Managing roles
3.4.6
Resource bar
Menu item
Project Manager
Translator
Reviewer
Markup Specialist
Terminology manager
Terminologist
Super User
Interfaces
Roles
Button
Table 3-5 shows the effect of the selected role on the available functions in the
resource bar:
Dual fuzzy
Standard roles
My roles
Manage roles
Role overview
MS Office
CAD
DTP
Graphics
HTML
SGML
XML
Localisation files
Text files
RTF
Trados (TTX)
Tab. 3-5: Roles and the resource bar
38
130620
Project Manager
Translator
Reviewer
Markup Specialist
Terminology manager
Terminologist
Super User
Maintain reference
material
Create reference
extract
Exchange reference
material (TMX)
Alignment
Convert reference
material
XV --> NXT
Convert reference
material
NXT --> XV
Open dictionary
Dictionaries /
databases
Dictionaries
WebTerm interface
Import terminology
Export terminology
Localisation files
Reference material
Menu item
Button
Manage reference
material
Localisation
130620
Tab. 3-5: Roles and the resource bar (cont.)
39
Project Manager
Translator
Reviewer
Markup Specialist
Terminology manager
Terminologist
Super User
x
x
x
Lgos
x
x
x
Reverso
x
x
x
Systran
x
x
x
x
x
x
x
x
x
40
130620
Menu item
Mach. trans.
Button
STAR James
-
Synchron. Preview
3
Managing roles
Tab. 3-5: Roles and the resource bar (cont.)
4 Customising Transit/TermStar NXT
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 41

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 49

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 55

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 57

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 58

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.
130620
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.
41
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 42.
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 43 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 44 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 45 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.
42
130620
4.2 Automating tasks using macros
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
In the Macro name field, enter a name for the macro.
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 45).
Confirm your entry with OK.
Transit/TermStar NXT displays the following message if you have entered a
130620
name which is already used for another macro:

Macro name already exists.
43
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.
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 43), 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 45.
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 43 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 43).
You can view or alter this hotkey at a later stage (see section 4.2.5 Editing the
macro on page 45).
Transit/TermStar NXT runs the macro selected.
44
130620
How do I run a macro using the ribbon bar?

1
Select Edit | Macros | Play.

Transit/TermStar NXT displays the Edit macro window.
From the Macro name list, select the name of the macro which you want to run.
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

Transit/TermStar NXT displays the Edit macro window (Fig. 4-2).
130620
Fig. 4-2: Edit macro window
45
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.
Click OK to close the window without changing the macro.
How do I change a macro?

1

Transit/TermStar NXT displays the Edit macro window (Fig. 4-2 on page 45).
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.
Change the commands to suit your requirements.
To confirm the changes, click Apply and close the window by clicking OK.
How do I delete a macro?

1

From the Macro name list, select the name of the macro which you want to
delete.
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

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.
In the Hotkey section, specify the keyboard shortcut with which you want to run
the macro (see Step 3 on page 43).
46
130620
4.2.6
Example macro: Inserting Unicode characters
In some languages (e.g. Venda, Sotho (Northern) and Tswana), there are Unicode
characters which cannot be simply inserted with a keystroke as other letters.
Display of Unicode characters

An appropriate font for the Transit editor must be used if you want Transit NXT to
display Unicode characters correctly. If necessary, you can make the required settings
in the User preferences window at Colours and fonts in the Font list box. Please
refer to section 8.3.5 Specifying the font and colours displayed by the editor of the
Transit NXT User's Guide for more detailed information.
To insert Unicode characters, click Edit | Text | Unicode Characters to open the
Character Table window. However, if you need the characters more often, we recommend a better option: Specify appropriate macros.
How do I record a macro which can be 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: Latin capital letter D with circumflex below.
In the Hotkey section, specify the hotkey with which you want to run the
macro.
Example: SHIFT + CTRL + D
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.
130620
In the large empty field, enter the command that Transit NXT uses for inserting
the Unicode character in text (Fig. 4-3). Table 4-1 on page 48 provides an overview of the characters and commands for the Venda, Sotho (Northern) and
Tswana languages.
47
Fig. 4-3: Macro for Unicode characters
Now, you can simply insert the Unicode character in Transit NXT (in example D with
circumflex below) with the defined shortcut (in example SHIFT + CTRL + D).
Language
Command
Character
Venda
<u_7698>
LATIN CAPITAL LETTER D WITH CIRCUMFLEX BELOW
<u_7699>
LATIN SMALL LETTER D WITH CIRCUMFLEX

BELOW
<u_7740>
LATIN CAPITAL LETTER L WITH CIRCUMFLEX BELOW
<u_7741>
LATIN SMALL LETTER L WITH CIRCUMFLEX

BELOW
<u_7754>
LATIN CAPITAL LETTER N WITH CIRCUMFLEX BELOW
<u_7755>
LATIN SMALL LETTER N WITH CIRCUMFLEX

BELOW
<u_7748>
LATIN CAPITAL LETTER N WITH DOT ABOVE
<u_7749>
LATIN SMALL LETTER N WITH DOT ABOVE
<u_7792>
LATIN CAPITAL LETTER T WITH CIRCUMFLEX BELOW
<u_7793>
LATIN SMALL LETTER T WITH CIRCUMFLEX

BELOW
Tab. 4-1: Macro commands for Unicode characters from Venda, Sotho (Northern) and Tswana
48
130620
4.3 Customising the system environment
Language
Command
Character
Sotho
(Northern)/
Tswana
<u_352>
LATIN CAPITAL LETTER WITH CARON
<u_353>
LATIN SMALL LETTER WITH CARON
Tab. 4-1: Macro commands for Unicode characters from Venda, Sotho (Northern) and Tswana
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:
Common access to settings and folders in a network (section 4.3.2 on page 49)
Restricting a background search with shared dictionaries (section 4.3.4 on page

52)
Updating common dictionaries (section 4.3.5 on page 53)
Specifying dialogue box fonts (section 4.3.6 on page 54)
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
Common access to settings and folders in a network
In the starte.ini file, you have to specify the paths that all users should be able to
access in order to guarantee access to common resources in a network.
The following paths are set as default in the file starte.ini:
[PATHS]
CONFIG\SYS=c:\Programs\Transit NXT\config\customers\
CONFIG\GLOBAL=c:\Programs\Transit NXT\config\global\
CONFIG\USERS=c:\Programs\Transit NXT\config\users\
130620
CONFIG\CUSTOMERS=c:\Programs\Transit NXT\config\customers\
49
PROJECTS=c:\Programs\Transit NXT\projects\
HELP=c:\Programs\Transit NXT\help\
DB=c:\Programs\Transit NXT\db\
SPELL=c:\Programs\Transit NXT\spell\
The folders have the following meaning:
CONFIG\SYS configuration files for Transit/TermStar NXT
CONFIG\GLOBAL folder for global scope
CONFIG\USERS folder for user scope
CONFIG\CUSTOMERS folder for customer scope

Transit/TermStar NXT saves the user preferences, the settings for segment
filters, lists of abbreviations, data record filters etc. in the folders for the areas
Global, Users and Customers.
PROJECTS root folder for the working folder
HELP help files
DB TermStar databases with the dictionaries
SPELL Files for dictionary-based spellchecks
How do I set up the paths for common access?

1
Open the file starte.ini in an editor and replace the specified paths with the
paths that contain the data you want to share.
Example:
When all working folders are saved in the path Z:\data\translation\jobs,
modify the line as follows:
PROJECTS=Z:\data\translation\jobs
If you do not want to change the individual default paths, leave them unchanged.
Save and close the file.

Transit/TermStar NXT now uses the folders specified in the changed paths.
If necessary, copy the files you want all users to use together to the appropriate
folders.
4.3.3
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.
50
130620
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
starte.ini
Range
[Options]
Parameter
MaxPretranThreads
Possible values
<XX>
Instead of <XX> (including the characters < and >), enter

the maximum number of CPUs or threads.
Tab. 4-2: 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.
Save and close the file and restart Transit NXT.
130620
If you do not specify this option, Transit NXT will automatically use the maximum available number of CPUs for parallel pretranslation.
51
4.3.4
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
starte.ini
Range
[Options]
Parameter
MultiUserBGS
Possible values
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-3: 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

Transit NXT limits the background search to the current segment and the next
segment that has not yet been translated.
52
130620
4.3.5
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
starte.ini
Range
[Options]
Parameter
Update Interval
Possible values
<XX>
Instead of <XX> (including the characters < and >), enter the
desired length of the interval in minutes.
Tab. 4-4: 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
130620
Transit NXT updates the dictionaries at the interval specified.
53
4.3.6
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]
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
Arial
Times New Roman
Courier New
Verdana
Tahoma
Lucida Sans Unicode
Trebuchet MS
Impact
Georgia
Lucida Sans
3
=
=
=
=
=
=
=
=
=
=
=
9
8
7
6
5
4
3
2
1
1
1

Transit/TermStar NXT will now give preference to the fonts with the highest
priority when selecting fonts automatically.
54
130620
4.4 Spellchecking: list of unknown words
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
130620
Tab. 4-5: File for list of unknown words
55
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 UTF16. 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
56
130620
4.5 Customising index buttons for 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 211.
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
130620
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.
57
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).
58
130620
4.6 Checking and changing abbreviation list
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
130620
<Language>_pos.ewl for no abbreviations

2
Delete or correct incorrect entries or add missing ones.
59
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 60 and 5.2.1 Saving the print definition on
page 61).
The print definitions can be used to make settings:
Setting page margins (section 5.2.2 on page 63)
Defining separators for dictionaries (section 5.2.3 on page 64)
Specifying headers and footers (section 5.2.4 on page 67)
Specifying the page layout (section 5.2.5 on page 70)
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 63 for more detailed information)
Separator letter (Only for dictionaries, for details see 5.2.3 on page 64)
Header (Please refer to section 5.2.4 on page 67 for more detailed information)
Footer (Please refer to section 5.2.4 on page 67 for more detailed information)
Page layout (Please refer to section 5.2.5 on page 70 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.
60
130620
5.2 Opening a print definition
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
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
130620
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.
61
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
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.
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
62
Click Save.
130620
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:
130620
Fig. 5-3: Page window, Page margin tab
63
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 61 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
64
130620
Separator type
Entry in
separator field
Meaning
d-kD-K

printing the letter range D-K.
TermStar NXT does not use separators
when printing all other characters.
Individual letters
aAbBcC

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
130620
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.
65
How do I set the separators?

1
Select the Separator letter tab:
Fig. 5-5: Page window, Separator letter tab
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 64).
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.
66
Select the background for the separator: To do this, click on Background.
130620
Transit NXT displays the Color window:
Fig. 5-6: Color window
In the Color window, select the background colour. Confirm your selection with
OK.
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.
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)
130620
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.
67
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
126
TermStar NXT: term of the first

data record on the page
application
Transit NXT: number of the

last segment on the page
261
TermStar NXT: term of the last

data record on the page
browser
Transit NXT: working name

of the language file
About Transit NXT
%l
%n
Use in TermStar NXT inadvisable

%N
Transit NXT: path and

file name of the language file
c:\Programs\Transit NXT\projects\
NXT_Word\About_Transit NXT
TermStar NXT: dictionary and da- MyTerms(TermStar NXT)

tabase name
Tab. 5-2: Variables for header and footer
68
130620
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
Choose one of the three areas Left, Center or Right by selecting the respective
tab in the lower section of the window.
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.
Repeat steps 2 to 4 for the remaining areas (centre and right).
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.
130620
The symmetrical layout is only used for double-sided layouts (tab Page Layout).
69
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
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 61 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 67).
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.
70
130620
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
Specify the page and column layout.

Transit NXT updates the preview window when you leave the modified field.
130620
71
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 73)
Excluding hidden or locked text from translation in Excel (section 6.3 on page 73)
Optimising the pretranslation time (section 6.4 on page 75)
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.
72
130620
6.2 Compressing files with formatting information (cod files)
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
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.
To do this, the standard value for an option in the *.prj project file must be changed
before importing the Excel sheet.
130620
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.
73
For parts of text which are hidden in Excel, the following option is available:
File
*.prj
Range
[ImportExport]
Option
ShowHiddenCells
Possible values
0 The hidden text is not imported and is therefore not
included in the language pairs.

1 (Default) The hidden text is imported and the text
can be edited.
Tab. 6-1: ShowHiddenCells option
For parts of text which are locked in Excel, the following option is available:
File
*.prj
Range
[ImportExport]
Option
ExcelShowProtectionStatus
Possible values
0 (Default) The locked text is imported and the text
can be edited.
1 The locked text is imported and is protected as
markups.
Tab. 6-2: ExcelShowProtectionStatus option
Excluding parts of text that are hidden in Excel from translation:

1
In the *.prj project file, change the value for the ShowHiddenCells option in
the [ImportExport] area as follows:
ShowHiddenCells=0
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
Transit NXT imports the parts of text that are locked in Excel, but these are
protected as markups.
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.
74
130620
6.4 Optimising the pretranslation time
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 75).
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 76).
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.
130620
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.
75
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
Save and close the file. Reload the project in Transit and import the files.
Transit now pretranslates using the new value.
76
130620
7 Fields in the TermStar dictionary
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 211.
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)
130620
Contains 16 kB of text
77
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
2905
{2F16...EAC63}
GUID
Automatically filled in
Cannot be edited
Number which uniquely identifies each data record.
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
16KB
Revised
Status
This is entered automatically when the data

record is created.
Cannot be edited
Status of the data record

Example: Information on the
reliability or the status of the
data record
Tab. 7-1: Header fields
78
130620
7.2 Field types
Field name
Description
Type
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
29. May 2002,

16:30
255c
A. Smith
2. August
2013, 14:38
255c
A. Smith
Created on
Last change
by
Last change
on
Created or
changed by
Cannot be edited
Point in time when the data

record was created
Cannot be edited
Name of the user who last

changed the data record
Empty as long as the data

record has not been
changed
Cannot be edited

record was last changed
Empty as long as the data

record has not been
changed
Cannot be edited

the data record or who last
changed it
Never empty - contains at

least the name of the user
who created the data
record
Cannot be edited
Example
130620
Tab. 7-1: Header fields (cont.)
79
Field name
Description
Type
Example
Created or
changed on

record was created or last
changed
2. August
2013, 14:38

least the point in time
when the data record was
created
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
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.8.13
Multimedia
Linking field for linked multimedia files
16KB
Tab. 7-2: Language fields
80
130620
7.2 Field types
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.
195
16KB
TermStar
16KB
ENG
255c
A. Smith
29. May 2002,

16:30
255c
A. Smith
Term
Cannot be edited
Term of the entry

TermStar NXT sorts the entries
in the dictionary in accordance
with the content of this field.
Language
Created by
Created on
Last change
by
3-letter language code of the

language of the entry
Cannot be edited

the entry
Cannot be edited
Point in time when the entry was

created
Cannot be edited
Name of the user who last

changed the entry
Empty as long as the entry

has not been changed
Cannot be edited
130620
Tab. 7-3: Entry fields and subentry fields
81
Field name
Description
Type
Example
Last change
on
Point in time of the last change

made to the entry
2. August
2013, 14:38
255c
A. Smith
2. August
2013, 14:38
Created or
changed by
Created or
changed on
Empty as long as the entry

has not been changed
Cannot be edited

the entry or who last changed it

least the name of the user
who created the entry
Cannot be edited
Point in time when the entry was

created or last changed

least the point in time when
the entry was created
Cannot be edited
Context
Context in which the term is

used
16KB
Terminology
management
Context
source
Source of the context
16KB
RefGuide
Part of
speech
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
82
130620
7.2 Field types
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
16KB
Transit NXT
Examples:
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
130620
83
7.2.4
Subentry types
TermStar NXT displays fields for subentries in selection lists and in the layout editor
with a corresponding prefix:
Subentry
Prefix
Abbreviations
Abbr. or
Abbreviations
Synonyms
Syn. or
Synonyms
Alternatives
Alt. or
Alternatives
Irregular forms
Irreg. or
Irregular forms
Disallowed terms
Dis. term.
User index 1
U. ind.1 or
User index 1
User index 2
U. ind.2 or
User index 2
User index 3
U. ind.3 or
User index 3
User index 4
U. ind.4 or
User index 4
User index 5
U. ind.5 or
User index 5
Tab. 7-4: Prefix for subentries in selection lists
84
130620
8 Customising layouts
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 85). 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
90).
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:
130620
In the folder config\global of your Transit/TermStar NXT installation
85
Customising layouts
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 86), 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 90).
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
86
130620
8.2 Managing 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 90) 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).
130620
Fig. 8-1: Open window with layouts available
87
Customising layouts
Select the layout which you want to edit and confirm your choice by clicking
Open.
TermStar NXT opens the layout in the layout editor
Modify this layout according to your needs (see section 8.3 Working with the
layout editor on page 90) 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?
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.
88
130620
8.2 Managing 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
Enter a name for the new layout in the File name field.
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.
130620
Transit NXT saves the layout under a new name.
89
Customising layouts
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.
90
130620
8.3 Working with the layout editor
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
3
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 92).
Fields in layout
Fields which have already been inserted into the layout.
Preview
130620
A preview of the layout in which the layout editor shows the position and formatting of the fields.
91
Customising layouts
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.
92
130620
8.3 Working with the layout editor
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).
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 100).
Language pseudo-field
130620
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.
93
Customising layouts
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 102 or section 8.5.6 Variables on
page 104).
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 104).
94
130620
8.4 Editing the layout
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).
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.
130620
Please refer to section 8.5 Specifying field properties on page 98 for information on
how to format the field.
95
Customising layouts
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.
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 97).
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.
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 98 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.
To remove the static text unit, open the context menu using the right mouse
button and select Delete.
Transit NXT removes the text from the Fields in layout and Preview sections.
96
130620
8.4 Editing the layout
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.
130620
How do I rearrange the order of fields?

1
Select a field from the list in the Fields in layout section.
Click on the field and hold down the mouse button to drag it up or down.
97
Customising layouts
In doing so, the layout editor also moves the field icon (Fig. 8-6).
Fig. 8-6: Moving fields in the layout editor
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.
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
98
130620
8.5 Specifying field properties
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 99
Subgroups (entries, subentries) see section 8.5.3 Formatting entries and

subentries on page 100
Fields see section 8.5.4 Formatting the fields on page 102
Static texts see section 8.5.5 Entering and formatting static text units on
page 103
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.
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).
130620
Fig. 8-8: Field properties window for main units
99
Customising layouts
Range
Setting
Text before
Meaning
Text which TermStar NXT displays in
front of the entries of a unit, e.g. in front
of the source language.
Font
The font, font style, size and effects of

the text in front of the unit.
Spacing
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 104).
Font

the text after the unit.
Spacing
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
100
130620
Range
Setting
Text before

front of the fields of the entry.
Font

the text in front of the entry.
Spacing
Text
Text that TermStar NXT shows between

several entries of a data record.
Font

the text in front of the entry.
Spacing
Distance between several entries of a

data record.
Text after
Option
Meaning
Text which TermStar NXT displays after

the fields of an entry.
Font

the text after the entry.
Spacing
Spacing to the last entry field in pixels.
Repeatable
TermStar NXT displays all the entries of

a language in the same data record.
Example:
ENG: carrot
DEU: Mhre
DEU: Karotte
If this option is not selected,
TermStar NXT only displays one
entry:
ENG: carrot
DEU: Mhre
You can deselect this option for the
source-language entries since
TermStar NXT displays each entry in the
dictionary anyway.
Example:
DEU: Mhre
ENG: carrot
DEU: Karotte
ENG: carrot
130620
Tab. 8-2: Formatting an entry
101
Customising layouts
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
Text before
Meaning
front of the contents of the field, e.g. a
designation such as Gender.
Font
Font, font style, size and effects of the

text in front of the field contents.
Spacing
Text
Layer and name of the field selected,

e.g. <Entry.Context>.
Cannot be edited.
Font

the field contents.
Spacing
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 text after the field contents.
Tab. 8-3: Formatting a field
102
130620
Range
Option
Setting
Meaning
Spacing
Spacing to the field contents in pixels.
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
Text
Options
Meaning
Text or characters which TermStar NXT
displays as a static text unit.
Font
Font, font style, size and effects of the

text.
Spacing
Indentation
Spacing to the left margin in pixels.
130620
Tab. 8-4: Formatting a static text unit
103
Customising layouts
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 84).
Example: Abbr. for Abbreviations
\c
\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 110).
\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.
104
130620
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
130620
The Additional languages layer is not available for subentries.
105
Customising layouts
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.
Add the Term field from the Source language layer.

This field generates an automatic cross-reference to the main entry for the
subentry.
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 --->).
Format the field so that it can be recognised as a cross-reference.

To do so, select the font colour green, for example.
Add additional fields, if necessary.
TermStar NXT uses this layout for subentries with an automatic cross-reference to the
main entry.
106
130620
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
Meaning
Display graphics
Displays the graphics which are linked in the Graphics

header field:
Do not scale
Scale for screen width
Shrink image
Show file name
Cross-reference colour
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 104.
Spacing
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
130620
Tab. 8-6: General layout settings
107
Customising layouts
Range
Meaning
Show data records
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.
Date/time format
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.)
108
130620
How do I change the layout settings?

1
Open the layout if it is no longer open.
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
Select the settings you require (see table 8-6) and confirm the settings with OK.
130620
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.
109
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 110)
Setting graphics file access (section 9.3 on page 115)
Specifying cross-reference separators (section 9.4 on page 116)
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 77). 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 111).
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 112).
110
130620
9.2 Modifying field names
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 113). 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 114).
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 111), 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 112), 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 104.
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.
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.
Select the dictionary whose field name you wish to change and click on
Settings.
TermStar NXT displays the Settings window.
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
130620
To specify a new field name for a field, select the field and enter the new name
in the User-defined field name field.
111
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

existing databases.
Select the dictionary whose field name you wish to change and click on
Settings.

4


5
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
Press the TAB key so that TermStar NXT shows the new name in the Userdefined field name column.
112
130620
9.2 Modifying field names
TermStar NXT closes the Settings window and applies the changed field name in the
specified language.
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

TermStar NXT displays the TermStar database expert window with a
the existing databases.
list of
Select the dictionary whose field name you wish to reset and click on Settings.


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.
TermStar NXT closes the Settings window and starts using the original field name
again.
130620
113
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

existing databases.
Select the dictionary from which you want to transfer the field names and click
on Settings.
4
5

To transfer field names from another dictionary, click on Take.
TermStar NXT displays a list of all existing dictionaries.
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.
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.
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.
114
130620
9.3 Setting graphics file access
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

existing databases.
130620

3
Select the dictionary whose graphics file access you wish to specify and click on
Settings.
Select the Miscellaneous tab.
Specify how TermStar NXT should access graphic files in the Multi media
access range:
115
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
TermStar NXT closes the Settings window and applies the changed settings.
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

list of
Select the dictionary whose graphics file access you wish to specify and click on
Settings.
Enter the desired character in the Cross-reference separator field.
TermStar NXT closes the Settings window and applies the changed settings.
116
130620
9.5 Specify additional sort field
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

list of
Select the dictionary for which you want to define an additional sorting field and
click on Settings.
Select the desired field from the list in the Additional sorting field section.
TermStar NXT closes the Settings window and applies the extended sorting.
130620
117
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.
118
130620
10
Language
Original name of
the dictionary
File name used

in Transit NXT
Afrikaans
af_ZA.dic
af_ZA.aff
af_.dic
af_.aff
Albanian
sq_AL.dic
sq_AL.aff
Arabic
Language variant
Egypt
ar.dic
ar.aff
ar_EG.dic
ar_EG.aff
Saudi Arabia
ar.dic
ar.aff
ar_SA.dic
ar_SA.aff
Latin
az.dic
az.aff
az_AZ.dic
az_AZ.aff
Basque
eu.dic
eu.aff
eu_.dic
eu_.aff
Bulgarian
bg_BG.dic
bg_BG.aff
Catalan
catalan.dic
catalan.aff
Croatian
hr_HR.dic
hr_HR.aff
Czech
cs_CZ.dic
cs_CZ.aff
Danish
da_DK.dic
da_DK.aff
Dutch
nl_NL.dic
nl_NL.aff
Azerbaijanian
English
US
en_US.dic
en_US.aff
UK
en_GB.dic
en_GB.aff
Canada
en_CA.dic
en_CA.aff
Australia
en_AU.dic
en_AU.aff
New Zealand
en_NZ.dic
en_NZ.aff
South Africa
en_ZA.dic
en_ZA.aff
Estonian
et_EE.dic
et_EE.aff
Farsi
fa.dic
fa.aff
ca_.dic
ca_.aff
fa_.dic
fa_.aff
130620
Tab. 10-1: Spellcheck dictionaries in Transit NXT
119
10
Language
Original name of
the dictionary
File name used

in Transit NXT
Faeroese
fo_FO.dic
fo_FO.aff
fo_.dic
fo_.aff
Finnish
fi_Fl.dic
fi_Fl.aff
French
Language variant
France
Galician
German
fr-moderne.dic
fr-moderne.aff
fr_FR.dic
fr_FR.aff
gl_ES.dic
gl_ES.aff
Germany
de_DE.dic
de_DE.aff
Switzerland
de_CH.dic
de_CH.aff
Austria
de_AT.dic
de_AT.aff
Greek
el_GR.dic
el_GR.aff
Gujarati
gu_IN.dic
gu_IN.aff
Hebrew
he_IL.dic
he_IL.aff
Hindi
hi_IN.dic
hi_IN.aff
Hungarian
hu_HU.dic
hu_HU.aff
Icelandic
is_IS.dic
is_IS.aff
Indonesian
id_ID.dic
id_ID.aff
Irish
ga_IE.dic
ga_IE.aff
Italian
it_IT.dic
it_IT.aff
Kannada
kn_IN.dic
kn_IN.aff
Khmer
km_KH.dic
km_KH.aff
Latvian
lv_LV.dic
lv_LV.aff
Lithuanian
lt_LT.dic
lt_LT.aff
iw_IL.dic
iw_IL.aff
gd_IE.dic
gd_IE.aff
kh_KH.dic
kh_KH.aff
Tab. 10-1: Spellcheck dictionaries in Transit NXT (cont.)
120
130620
10
Language
Language variant
Original name of
the dictionary
Malay
ms_MY.dic
ms_MY.aff
Malayalam
ml_IN.dic
ml_IN.aff
Maltese
mt.dic
mt.aff
Marathi
mr_IN.dic
mr_IN.aff
Mongolian
mn_MN.dic
mn_MN.aff
Norwegian
nb_NO.dic
nb_NO.aff
no_NO.dic
no_NO.aff
Nynorsk
nn_NO.dic
nn_NO.aff
no_NY.dic
no_NY.aff
pl_PL.dic
pl_PL.aff
European
pt_PT.dic
pt_PT.aff
Brazilian
pt_BR.dic
pt_BR.aff
Romanian
ro_RO.dic
ro_RO.aff
Russian
ru_RU.dic
ru_RU.aff
Serbian
mt_MT.dic
mt_MT.aff
Bokmal
Polish
Portuguese
File name used

in Transit NXT
Latin
sr-Latn.dic
sr-Latn.aff
sr_CS.dic
sr_CS.aff
Cyrillic
sr_YU.dic
sr_YU.aff
sr_YU.dic
sr_YU.aff
Slovakian
sk_SK.dic
sk_SK.aff
Slovenian
sl_SI.dic
sl_SI.aff
Sotho (Northern)
ns_ZA.dic
ns_ZA.aff
Sotho (Southern)
st_ZA.dic
st_ZA.aff
130620
121
10
Language
Language variant
Original name of
the dictionary
Spanish
Spain
es_ES.dic
es_ES.aff
Argentina
es_AR.dic
es_AR.aff
Bolivia
es_BO.dic
es_BO.aff
Costa Rica
es_CR.dic
es_CR.aff
Chile
es_CL.dic
es_CL.aff
Dom. Rep.
es_DO.dic
es_DO.aff
Ecuador
es_EC.dic
es_EC.aff
El Salvador
es_SV.dic
es_SV.aff
Guatemala
es_GT.dic
es_GT.aff
Honduras
es_HN.dic
es_HN.aff
Colombia
es_CO.dic
es_CO.aff
Mexico
es_MX.dic
es_MX.aff
Nicaragua
es_NI.dic
es_NI.aff
Panama
es_PA.dic
es_PA.aff
Paraguay
es_PY.dic
es_PY.aff
Peru
es_PE.dic
es_PE.aff
Puerto Rico
es_PR.dic
es_PR.aff
Uruguay
es_UY.dic
es_UY.aff
Swahili
sw_KE.dic
sw_KE.aff
Swedish
sv_SE.dic
sv_SE.aff
File name used

in Transit NXT
122
130620
10
Language
Language variant
Original name of
the dictionary
File name used

in Transit NXT
Tamil
ta.dic
ta.aff
ta_IN.dic
ta_IN.aff
Thai
th_TH.dic
th_TH.aff
Tsonga
ts_ZA.dic
ts_ZA.aff
Tswana
ts_ZA.dic
ts_ZA.aff
tn_BW.dic
tn_BW.aff
Turkish
tr.dic
tr.aff
tr_TR.dic
tr_TR.aff
Ukrainian
uk_UA.dic
uk_UA.aff
Urdu
Pakistan
ur.dic
ur.aff
ur_PK.dic
ur_PK.aff
Uzbek
Cyrillic
uz.dic
uz.aff
uz_UZ.dic
uz_UZ.aff
Vietnamese
vi_VN.dic
vi_VN.aff
Welsh
cy_GB.dic
cy_GB.aff
Xhosa
xh_ZA.dic
xh_ZA.aff
Zulu
zu_ZA.dic
zu_ZA.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
130620
Download these files from the website of the OpenOffice.org organisation or from
other sources and then extract them if necessary.
123
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.
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.
124
130620
10
10.1 Installing a spellcheck dictionary
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.
130620
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.
125
10
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 126)
Deleting a database link (section 11.3 on page 136)
Transferring database connections to other computers (section 11.4 on page 137)
Deleting incorrect database links (section 11.5 on page 140)
Compressing databases and dictionaries (section 11.6 on page 141)
Database driver information (section 11.7 on page 141)
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 127).
MS SQL For SQL databases (see section 11.2.3 Connecting an MS SQL database on page 132).
Link each database once only

Make sure that you do not create more than one link to each database on your
computer.
126
130620
11
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?
130620
Select Dictionaries | Dictionaries / Databases | Link database from the

resource bar.
127
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
128
For standard TermStar databases select the Access Database driver and
confirm your choice by clicking Next.
130620
11
TermStar NXT displays the Specify database file window:
Fig. 11-2: Specify database file window, no database selected
Click on Browse to select the folder that contains the database file.
TermStar NXT displays the window Open:
130620
Fig. 11-3: Open window
129
11
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
130
Click on Next to confirm your selection.
130620
11
TermStar NXT displays the ODBC connection window:
Fig. 11-5: ODBC connection window with selected database
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 127.
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.
Confirm the message by clicking on OK.
130620
The ODBC connection window will be closed automatically. TermStar NXT has
established the database connection. You can now access the database.
131
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
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.
132
130620
11
Fig. 11-7: Database server selection window
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.
130620
Click Next to confirm the information entered.
133
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
From the Databases list, select the database to which you want to establish a
link.
Confirm your selection by clicking on Next.
134
130620
11
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
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 127.
Confirm the name of the ODBC connection and the selected DSN type and
establish the database connection by clicking on Finish.
Database <file name> successfully linked.
Confirm the message by clicking on OK.
130620
The ODBC connection window will be closed automatically. TermStar NXT has
established the database connection. You can now access the database.
135
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 126).
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
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!
136
Click Delete to confirm your selection.
130620
11
11.4 Transferring database connections to other computers

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
130620
Each computer accesses its own local mdb file. The drive designation, path and
file name are the same on each computer.
137
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.
Click on Write to file to save the connection settings.

TermStar NXT displays the Save as window:
Fig. 11-12: Save as window
138
130620
11
11.4 Transferring database connections to other computers
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.
Start the program ODBCDataLoader.exe by double-clicking it.

The program displays the following window showing all saved database connections:
130620
Fig. 11-13: The program shows all saved database connections
Select the connections that you want to set up on the destination computer.
To set up the connections, click Install.
139
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 displays the following window showing all database connections
with errors:
Fig. 11-14: The program shows all database connections with errors.
Select the connections that you want to delete.
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.
140
130620
11
11.6 Compressing databases and dictionaries
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

of all database connections available (see Fig. 11-10 on page 136).
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 wand to compact the dictionary <name>?
or
Are you sure you want to compact the database?
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

of all database connections available (see Fig. 11-10 on page 136).
130620
Select the database for which you need the driver information in the Databases/
Dictionaries list.
141
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
142
Click on OK to close the window.
130620
11
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.
130620
In doing so, you ensure that Transit/TermStar NXT does not access the database
while it is being compressed.
143
12
Compacting Microsoft Access database or transferring it to SQL server
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 147.
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.
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
144
130620
12
12.1 Overview
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
Leave the settings in this window unchanged and click on Compress.

The ODBC data source administrator displays the Source Database window:
130620
Fig. 12-3: Source Database window; the database to be compressed is selected

automatically.
145
12
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?
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 146) 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.
146
130620
12
12.2 Transferring TermStar databases from Microsoft Access to an 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 R2 or MS SQL Server 2008 R2 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.
130620
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)
147
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
148
Select the Data Sources (ODBC) option.
130620
12
The ODBC Data Source Administrator window is displayed:
Fig. 12-6: ODBC Data Source Administrator window
Switch to the System DSN tab.
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
130620
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.
149
12
The ODBC Data Source Administrator window is displayed with the changed
ODBC connection:
Fig. 12-8: ODBC Data Source Administrator window
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
150
130620
12
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
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
130620
In the ODBC driver list, select the Microsoft SQL Server (MS SQL) driver
and click Next.
151
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
152
In the New database field, enter the name TermStar NXT Received and click
Next.
130620
12
Transit/TermStar NXT displays the ODBC connection window:
Fig. 12-14: ODBC connection window
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:
130620
Fig. 12-15: TermStar dictionary window
153
12
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
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
154
Click in the Databases/Dictionaries list on the database with the content you
want to transfer and then click Copy.
130620
12
Transit/TermStar NXT displays the Select target database window:
Fig. 12-18: Select target database window
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
Once Transit/TermStar NXT has completed the transfer, it displays the following
message in the window:
130620
Click OK to close this window.
155
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
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
156
Confirm this message by clicking Yes.
130620
12
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
130620
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.
157
12
Regular expressions
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 164).
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.
158
130620
13
13.1 Overview
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, substitu-
130620
tions)
159
13
Regular expressions
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 161.
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 162.
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 162.
160
130620
13
13.3 Control characters
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)
\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
177.
\o
Segment marker
(in Transit editor only)
\s
Space
\t
Tabulator
130620
Tab. 13-1: Control characters
161
13
Regular expressions
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 171.
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 196):
Wildcards: . [ ] & see section 13.5 on page 163

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 168

By using what are known as quantifiers you can specify how many instances of
a character are to be found.
162
130620
13
13.5 Wildcards: . [ ] &
Escapement: \ see section 13.7 on page 171

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

173
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 175

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 177

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 182

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 185

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.
130620
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.
163
13
Regular expressions
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
STAR
STAAR
stir
st
st@r
str
On.line
On-line
Online
On line
On.line
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 161)
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.
164
130620
13
13.5 Wildcards: . [ ] &
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
str
stir
strr
stor
STAAR
2003
1905
2004
2002
2005
2035
star
str
str
STAAR
strr
st@r
a4
1a
k3
mx
z5
68
200[3-5]
st[a-z]r
[a-z][0-9]
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).
130620
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]).
165
13
Regular expressions
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 179.
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
162).
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 179.
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.
166
130620
13
13.5 Wildcards: . [ ] &
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
mar
Saint Peter
S?.!R
SR
s
r
(line break)
(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:
130620
You search for the regular expression s&r in the following passage of text:
The stars are shining bright.
167
13
Regular expressions
The passage contains three consecutive occurrences of the specified regular

expression.

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 170).
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 171.
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).
168
130620
13
13.6 Quantifiers: +*?
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
str
staaaar
star
stra
stir
sta+r
star
str
staaaar
stra
stir
staa
aar
(only searches as far
as line break)
sta*r
str
stra
star
stir
staaaar
staa
aar
(only searches as far
as line break)
Tab. 13-5: Searching for a specified number of a specific character
130620
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 164).
169
13
Regular expressions
Example: The regular expression [0-9]+ finds any sequence of numbers (0, 15,
290504 etc.).
Regular expression
Matches
Does not match
[0-9]+
XV
Finds sequences of one

of more numbers. Other
characters are not found.
15
star
st[aeiou]*r
str
str
Finds sequences of one

or more vowels or
absence of vowels
between the delimiters.
Other characters are not
found.
star
stpr
stir
st@r
[A-Z][a-z]*
translation
Finds any single

upper-case letter
followed by any
sequence of (or absence
of) lower-case letters.
Other characters are not
found.
Star
Bblingen
Transit
TermStar
[A-Z][a-z]+
Star
Finds strings where at

least one lower-case
letter follows an
upper-case letter. Other
characters are not found.
Transit
translation
Star[a-z]?
Star
Star3
Finds strings where the

literal string is followed
by nothing or a single
letter. Other characters
are not found.
Start
Starter
290504
staaaaar
stair
Bblingen
TermStar
Stars
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 165.
170
130620
13
13.7 Escapement: \
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 173.
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.
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 166.
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.
130620
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.
171
13
Regular expressions
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 163). 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 168). 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
172
130620
13
13.8 Applying meta characters to character strings: ( )
Regular expression
Matches
Does not match
readme.txt
readme.txt
readmetxt
(no escapement)
readmextxt
readme-txt
Transit+TermStar
TransitTermStar
Transit+TermStar
(no escapement)
TransitttttTermStar
TransiTermStar
folder \temp
folder
folder \temp
(no escapement)
emp
(\t is the control
character for the
tabulator)
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 161.
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.
130620
Example: the plus sign specifies that the preceding character should occur once
or more than once (see section 13.6 on page 168). 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.).
173
13
Regular expressions
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
star
sr
s
followed by one or more
occurrences of ta
followed by r
statar
stat
statatatar
statr
T(ra)+[a-z]+
Transit
Termstar
Finds T followed by one

or more occurrences of
ra followed by any single
letter or sequence of
letters
Traransit
Tra2004
Transfer
Tra-nsit
Trararas
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 177)
Alternatives (|) (see section 13.11 on page 182)
Variables (#) (see section 13.12 on page 185)
174
130620
13
13.9 Placement: ^ $
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
STAR
in
STAR Group
STAR$
STAR
in
with STAR
in
The STAR Group
STAR
in
STAR Group
STAR
in
STAR.
^&$
(Any sequence of characters between beginning
and end of line)
The STAR Group
in
The STAR Group
The
STAR
group
(spans more than one line)
130620
Tab. 13-10: Regular expression at the start of a line
175
13
Regular expressions
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 180).
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 164).
176
130620
13
13.10 Negation: !
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.
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 161.
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.
130620
For examples, refer to the Tables 13-11 on page 178 and 13-13 on page 179.
177
13
Regular expressions
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 179),
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
ST
in STAR
in STONE
ST
in STIR
ST
in ST
ST
in STP
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
178
130620
13
13.10 Negation: !
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 164.
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 178),
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
STO
in STAR
STP
in STP
in STONE
STE
in STELLA
ST
in ST
130620
Tab. 13-13: Negation of character groups
179
13
Regular expressions
Exclamation mark for negation must always prefix character group/class

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
Regular expression
Matches
Does not match
ST[ON!E]
STO
STA
STN
ST5
ST!
STE
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 175.
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(!$)
STAR
in
STAR Group
STAR
in
STAR Group
in
with STAR
STAR
in
STAR.
Tab. 13-15: Negation of beginning or end of line
180
130620
13
13.10 Negation: !
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$)
ST
ST
Negation of entire string

AR plus end of line
in
STAR Group
in
with STAR
ST
in
with ST
Tab. 13-16: Negation of entire string AR plus end of line
Exclamation mark for negation must always prefix character string

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
Regular expression
Matches
Does not match
ST(AR!$)
STAR!
STAR
in
STAR!
in
with STAR
STAR!
in
STAR! Group
130620
181
13
Regular expressions
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 from STAR
TermStarTransit from
Transit from STAR
STAR
TermStar
TermStar|Transit from
STAR
TermStar
TermStarTransit from
Transit from STAR
STAR
TermStar from STAR
Tab. 13-18: Search for alternatives
182
130620
13
13.11 Alternatives: |
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
str
stbr
stabr
st|r
staxr
stxr
130620
Tab. 13-19: If the pipe character is inside a character group it is interpreted literally
183
13
Regular expressions
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]
184
130620
13
13.12 Variables: #
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 186).
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.
130620
On-line is to be changed to On_line; reference-based changed to

reference_based, etc.
185
13
Regular expressions
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 186).
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 188
Changing number formats when replacing 13.12.4 on page 189
Performing mathematical calculations when replacing 13.12.5 on page 190
Rounding figures when replacing 13.12.6 on page 192
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
186
130620
13
13.12 Variables: #
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
\s#([0-9])0
\s0#0
Transit NXT searches for a

space (\s) followed by a
number ([0-9]).
Transit NXT replaces what

it finds with a space, a zero
and the contents of the
variable 0 (the number
found).
Transit NXT stores the number

as the variable 0.
Replace
single-digit
numbers in the
notation x.y with
the notation x,y
\s#([0-9])0\ .#([0-9])1
\s#0,#1

space (\s) followed by a
number ([0-9]) followed by a
decimal point (\.) followed by
a number ([0-9]).

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).
Transit NXT saves the first

number as the variable 0 and
the second number as the
variable 1.
Replace the
hyphen in
compound words
with an underscore
#([a-z]+)0-#([a-z]+)1
#0_#1

sequence of letters ([a-z]+)
followed by a hyphen (-)
followed by a sequence of
letters ([a-z]+).

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).
Transit NXT saves the first

sequence of letters as the
variable 0 and the second
sequence of letters as the
variable 1.
130620
Tab. 13-20: Replacements using variables
187
13
Regular expressions
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.

#(<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
Meaning
Change replacement string to all capitals
^1
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
188
130620
13
13.12 Variables: #
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.

#(={(<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
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.
130620
#([0-9]+\.[0-9]+)0
189
13
Regular expressions
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
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 192.
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.

#(={<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 189). 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
190
130620
13
13.12 Variables: #
Operator
Meaning
Multiplication
()
Brackets
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.
#([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
295200
295205
295195
-4
-1
1476001
17
59040
-2632501
-1
-30
87143153664
11
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 (= x2)
130620
Tab. 13-26: Examples of mathematical calculations
191
13
Regular expressions
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 192.
Other practical examples:
Replace amount in DM by amount in euro

A document contains prices in DM. They are to be replaced by the equivalent
price in euros with two decimal places.
Regular expression for the search string:

#([0-9]+,[0-9]+)0 DM
Regular expression for the replacement string:

#(={#,00}x/1.95583)0 EUR
Result:
Price 865,58 DM (inc. 57,45 DM delivery charge)
is replaced by
Price 442,56 EUR (inc. 29,37 EUR delivery charge)
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.

#([0-9]+)0 miles

#0 miles (#(={}x*1.609)0 km)
Result:
Distance Ramsen Bblingen 90 miles
is replaced by
Distance Ramsen Bblingen 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 189).
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.
192
130620
13
13.12 Variables: #

#([0-9]+\.[0-9]+)0

#(={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

#(={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
130620
Tab. 13-28: Example: Rounding numbers to one decimal place
193
13
Regular expressions
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.
Rounding to five decimal places smallest decimal fraction 0.00001 divided

by 2 equals 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.
194
130620
13
13.13 Invalid 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 161 and 13.7 on page 171).
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
164).
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 166)
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 182).
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
173).
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 164 and 13.8 on page 173).
130620
Alternative syntax:
(key|no)
(key|[no])
195
13
Regular expressions
*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 168).
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 161.
Please note: the backslash is also a meta character for an

escapement (see section 13.7 on page 171).
Tab. 13-29: Meta characters and control characters used in regular expressions
196
130620
13
13.14 Appendix overview of meta and control characters
Type
Meta characters
Meaning
Wildcard/
character class
Dot:
.
Wildcard for any single character.
Square brackets:
[xyz]
Character class:
Wildcard for any character of a specified group or class
See section 13.5.1 on page 163.

Ampersand:
&
Wildcard for any sequence of any

number of characters.
Quantifier
Question mark:
x?
Finds occurrences of absence or a

single instance (0 - 1 instances) of the
preceding character.
See section 13.6 on page 168.
Plus sign:
x+
Finds occurrences of a single instance

or multiple instances (1 - n instances) of
the preceding character.
Asterisk:
x*
Finds occurrences of the absence, a

single instance or multiple instances (0
- n instances) of the preceding
character.
Escapement
Backslash:
\x
Forces character to be interpreted literally instead of as a meta character.

Please note: The backslash also introduces control characters

(see section 13.3 on page 161).
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.
130620
Tab. 13-29: Meta characters and control characters used in regular expressions (cont.)
197
13
Regular expressions
Type
Meta characters
Meaning
Logical
operator
Circumflex:
^
Beginning of line or field:

the expression must occur at the beginning of a line or entry field.
Dollar sign:
$
End of line or field:

the expression must occur at the end of
a line or entry field.
Exclamation mark:
(!xxx)
[!x]
Negation:
The expression which follows may not
occur.
Pipe character:
Expression1|
Expression2
Alternative:
Combines two expressions with a
logical OR operation.
Finds expression 1 or expression
2.
Variable
#()<nr>
Variable (in search):

stores character string for use in
replacement.
#<nr>
Variable (in replacement):

inserts the variable stored by the search
operation in the replacement.
Tab. 13-29: Meta characters and control characters used in regular expressions (cont.)
198
130620
13
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
Shortcut
Close file
CTRL+F4
Save file
CTRL+S
Save the file and exit Transit
ALT+F4
Delete the character at the cursor position
DEL
Find
CTRL+F
Find next
ALT+CTRL+Y
Replace
CTRL+H
Go to
CTRL+G
Print file
CTRL+P
Undo
ALT+BACKSPACE key
Close window
ESC
130620
Tab. 14-1: Transit General functions
199
14
Keyboard shortcuts
14.2.2 Moving between windows

Table 14-2 shows the shortcuts for moving between windows:
Function
Shortcut
Back one open language pair
ALT+F7
Forward one open language pair
ALT+F8
Switch between tabs
CTRL+TAB
Switch to the source-language section

of the Transit editor
ALT+1
Switch to the target-language section of

the Transit editor
ALT+2
Switch to the Terminology window
ALT+3
Switch to the Notes window
ALT+4
Switch to the Source Fuzzy window
ALT+5
Switch to the Target Fuzzy window
ALT+6
Switch to the Markup window
ALT+7
Switch to the viewer (depending on

availability) (e. g. InDesign, PowerPoint
--> PDF viewer, HTML files -->
HTML viewer)
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
Shortcut
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.
ALT+INSERT
Search for fuzzy matches for the current

segment
ALT+ENTER
Tab. 14-3: Transit Translating in the Transit editor
200
130620
14
Function
Shortcut
Undo translation of current segment.
CTRL+ALT+BACKSPACE key
To the previous untranslated segment
CTRL+MINUS (numeric keypad)
To the next untranslated segment
CTRL+PLUS (numeric keypad)
To the previous partially translated segment
ALT+MINUS (numeric keypad)
To the next partially translated segment
ALT+PLUS (numeric keypad)
To the previous segment to be edited.
CTRL+ALT+MINUS (numeric keypad)
To the next segment to be edited.
CTRL+ALT+PLUS (numeric keypad)
Delete update marker
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
Shortcut
Replace a word with its (first) translation

from the dictionary.
ALT+T
Replace a word with its (first) translation

from the dictionary and change case
ALT+ SHIFT+T
Select term to replace a word when

there are several dictionary suggestions
ALT+K, <letter>
Select a term to replace a word when

there are several dictionary suggestions
and change case
ALT+K, SHIFT+<letter>
Insert a translation from the dictionary

without replacing a word.
ALT+G, <letter>
<Letter> here refers to the letter which

is in front of the particular translation in
the dictionary window.


130620
Tab. 14-4: Transit Working with terminology
201
14
Keyboard shortcuts
Function
Shortcut
Insert translation from the dictionary,

without replacing, and change case
ALT+G, SHIFT+<letter>
Switch to the Terminology 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
Shortcut
Character to the left
ARROW LEFT
Character to the right
ARROW RIGHT
Word to the left
CTRL+ARROW LEFT
Word to the right
CTRL+ARROW RIGHT
To the start of segment
ALT+ARROW LEFT
To the end of segment
ALT+ARROW RIGHT
To the beginning of the line
HOME
To the end of the line
END
To the next segment
PLUS (numeric keypad)
Back one segment
MINUS (numeric keypad)
Up one line
ARROW UP
Down one line
ARROW DOWN
Insert/overwrite
INSERT
To the first line of the file
CTRL+HOME
To the last line of the file
CTRL+END
To the first line in the active window
CTRL+PAGE UP
To the last line in the active window
CTRL+PAGE DOWN
To the previous screen
PAGE UP
Tab. 14-5: Transit Moving the cursor
202
130620
14
Function
Shortcut
To the next screen
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
Shortcut
Bold
CTRL+SHIFT+B
Italics
CTRL+SHIFT+I
Underline
CTRL+SHIFT+U
Subscript
CTRL+]
Superscript
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
Shortcut
Highlight one character to the left of the

cursor
SHIFT+ARROW LEFT
Highlight one character to the right of

the cursor
SHIFT+ARROW RIGHT
Highlight to the beginning of a word
CTRL+SHIFT+ARROW LEFT
Highlight to the end of a word
CTRL+SHIFT+ARROW RIGHT
Highlight to the beginning of a line
SHIFT+HOME
Highlight to the end of a line
SHIFT+END
Highlight to the beginning of a segment
SHIFT+ALT+ARROW LEFT
Highlight to the end of the segment
SHIFT+ALT+ARROW RIGHT
Highlight to the beginning of a file
CTRL+SHIFT+HOME
130620
Tab. 14-7: Transit Selecting and editing text blocks
203
14
Keyboard shortcuts
Function
Shortcut
Highlight to the end of a file
CTRL+SHIFT+END
Highlight one line up
SHIFT+ARROW UP
Highlight one line down
SHIFT+ARROW DOWN
Highlight one screen up
SHIFT+PAGE UP
Highlight one screen down
SHIFT+PAGE DOWN
Cut selected text
CTRL+X
Copy selected text
CTRL+C
Delete selected text
DEL
Paste selected text
CTRL+V
Change the case of the highlighted text
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
Target language notes (Translator):

Previous note
Next note
Source or target language notes:

Previous note
ALT+CTRL+MINUS (numeric keypad)
Next note
ALT+CTRL+PLUS (numeric keypad)
Tab. 14-8: Transit NXT Searching for notes
204
130620
14
14.3 Keyboard shortcuts for TermStar NXT
14.3 Keyboard shortcuts for TermStar NXT

14.3.1 General functions
Table 14-1 shows the shortcuts for general functions.
Function
Shortcut
Close file
CTRL+F4
Save file
CTRL+S
Exit TermStar
ALT+F4
Print dictionary
CTRL+P
Menu bar
ALT or F10
Close window
ESC
Search
CTRL+F
Edit mode
ENTER or CTRL+E
Edit mode on right-hand side
CTRL+ENTER
Data record filter
CTRL+L
Swap languages
CTRL+A
Display graphics
CTRL+G
Undo
CTRL+Z
Redo
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
Shortcut
First data record
CTRL+HOME
Last data record
CTRL+END
Previous page
PAGE UP
130620
Tab. 14-10: TermStar NXT Moving the cursor
205
14
Keyboard shortcuts
Function
Shortcut
Next page
PAGE DOWN
Previous data record
MINUS (numeric keypad)
Next data record
PLUS (numeric keypad)
Scrolling up within a data record

(right-hand side of the dictionary)
CTRL+ARROW UP
Scrolling down within a data record

(right-hand side of the dictionary)
CTRL+ARROW DOWN
Cross-reference back
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
Shortcut
Insert new data record
Delete data record
Cut data record
ALT+DIVIDE (numeric keypad)
Copy data record
ALT+MULTIPLY (numeric keypad)
Insert cut/copied data record
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
Shortcut
Next field
TAB
Previous field
SHIFT+TAB
Insert new entry
Delete entry
Tab. 14-12: TermStar NXT Edit mode
206
130620
14
14.4 Keyboard shortcuts for Alignment
Function
Shortcut
Cut entry
CTRL+DIVIDE (numeric keypad)
Copy entry
CTRL+MULTIPLY (numeric keypad)
Insert cut/copied entry
CTRL+ENTER
Exit edit mode
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
Shortcut
Move cursor to next aligned segment
ALT + MINUS (numerical keypad)
Move cursor to previous aligned

segment
ALT + PLUS (numerical keypad)
Move cursor to next

synchronized segment
PLUS (numerical keypad)
Move cursor to previous

synchronized segment
MINUS (numerical keypad)
Move a segment
ALT + click right mouse button
Delete entire segment
ALT + DEL
130620
Tab. 14-13: Transit NXT Alignment
207
14
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
Meaning
<File name>.<code>
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 name>.cod
File with formatting information.

Example:
userguide.cod File with formatting
information from the original file
userguide.doc
pos_<code>.ewl
neg_<code>.ewl
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 name>.fpx
File with information regarding configuration

of the windows in Transit NXT
Example:
userguide_pdf_viewer.fpx Example
of window configuration with PDF display
default.prf
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
208
130620
15
15.1 Files in Transit/TermStar NXT
File
Meaning
<Project name>.prj
File with project settings

Example:
userguide.prj File for the project
userguide
<project name>.ppf
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
default_<language>.ppx
File with information for configuration of the

project browser
Example:
default_eng.ppx Configuration file for
the project browser, dialogue language
British English
default_tr_<language>.qpx
default_ts_<language>.qpx
default_tss_<language>.qpx

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
<project name>.tpf
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
130620
Tab. 15-1: Files in Transit/TermStar NXT (cont.)
209
15
File
Meaning
<file name>.tpx
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 name>.tsvd
File with information regarding the view in

TermStar NXT
Example:
userguide_terminology.tsvd
Example of configuration file for terminology
display in TermStar NXT
<file name>.tvd

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
<code1><code2>.ast
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 EnglishGerman alignment
_aextr_1.<code>
Reference extract file

Example:
_aextr_2.eng File for an English
reference extract
_extr_.<code>
Translation extract file

Example:
_extr_.eng File with English translation
extract
210
130620
15
15.2 3-letter language code
File
Meaning
<Script name>.tid
File with settings for import script when

importing dictionaries
Example:
my_import.tid File for import script
my_import
<Layout name>.tld
File with settings for dictionary layout

Example:
all_langs.tld File for dictionary layout
all_langs
<Script name>.tmd
File with settings for merge script when

importing dictionaries
Example:
my_merge.tmd File for import script
my_merge

Transit/TermStar NXT uses the 3-letter language code specified by Microsoft (Table
15-2 sorted by language code, table 15-3 on page 218 sorted by language name).
Language
AFK
Afrikaans
AMH
Amharic
ARA
Arabic (Saudi Arabia)
ARB
Arabic (Lebanon)
ARE
Arabic (Egypt)
ARG
Arabic (Algeria)
ARH
Arabic (Bahrain)
ARI
Arabic (Iraq)
ARJ
Arabic (Jordan)
ARK
Arabic (Kuwait)
130620
Tab. 15-2: 3-letter language codes and languages
211
15
Language
ARL
Arabic (Libya)
ARM
Arabic (Morocco)
ARO
Arabic (Oman)
ARQ
Arabic (Qatar)
ARS
Arabic (Syria)
ART
Arabic (Tunisia)
ARU
Arabic (United Arab Emirates)
ARY
Arabic (Yemen)
ASM
Assamese
AZC
Azerbaijani (Cyrillic)
AZE
Azerbaijani (Latin)
BEL
Byelorussian
BGR
Bulgarian
BNG
Bengali
BOS
Bosnian (Bosnia and Herzegovina)
CAT
Catalan
CHS
Chinese (PR China)
CHT
Chinese (Taiwan)
CSY
Czech
DAN
Danish
DEA
German (Austria)
DEC
German (Liechtenstein)
DEL
German (Luxembourg)
DES
German (Swiss)
DEU
German
EDO
Edo
EFI
Efik / Ibibio
Tab. 15-2: 3-letter language codes and languages (cont.)
212
130620
15
Language
ELL
Greek
EN1
English (Simplified)
ENA
English (Australia)
ENB
English (Caribbean)
ENC
English (Canada)
END
English (India)
ENG
English (UK)
ENH
English (Hong Kong)
ENI
English (Ireland)
ENJ
English (Jamaica)
ENL
English (Belize)
ENM
English (Malaysia)
ENN
English (Indonesia)
ENO
English (Singapore)
ENP
English (Philippines)
ENS
English (South Africa)
ENT
English (Trinidad and Tobago)
ENU
English (US)
ENW
English (Zimbabwe)
ENZ
English (New Zealand)
ESA
Spanish (Panama)
ESB
Spanish (Bolivia)
ESC
Spanish (Costa Rica)
ESD
Spanish (Dominican Republic)
ESE
Spanish (El Salvador)
ESF
Spanish (Ecuador)
ESG
Spanish (Guatemala)
130620
213
15
Language
ESH
Spanish (Honduras)
ESI
Spanish (Nicaragua)
ESL
Spanish (Chile)
ESM
Spanish (Mexico)
ESO
Spanish (Colombia)
ESP
Spanish (Traditional sorting)
ESR
Spanish (Peru)
ESS
Spanish (Argentina)
ESU
Spanish (Puerto Rico)
ESV
Spanish (Venezuela)
ESY
Spanish (Uruguay)
ESZ
Spanish (Paraguay)
ETI
Estonian
EUQ
Basque
FAR
Persian
FIN
Finnish
FOS
Faroese
FR1
French (Rationalised)
FRA
French
FRB
French (Belgium)
FRC
French (Canada)
FRE
French (Senegal)
FRG
French (Congo)
FRH
French (Haiti)
FRI
French (Mali)
FRL
French (Luxembourg)
FRM
French (Monaco)
214
130620
15
Language
FRO
French (Cameroon)
FRR
French (Morocco)
FRS
French (Swiss)
FRU
French (Reunion)
FRV
French (Ivory Coast)
FRW
French (West Indies)
FRY
Frisian (Netherlands)
FUB
Fulfulde Adamawa
GAE
Gaelic (Ireland)
GAL
Gallegan/Galician
GDH
Gaelic (Scotland)
GRC
Greek (Ancient)
GUA
Guarani
GUJ
Gujarati
HAU
Hausa
HAW
Hawaiian
HEB
Hebrew
HIN
Hindi
HRB
Croatian (Bosnia and Herzegovina)
HRV
Croatian
HUN
Hungarian
IBO
Igbo
IND
Indonesian
ISL
Icelandic
ITA
Italian
ITS
Italian (Swiss)
JII
Yiddish
130620
215
15
Language
JPN
Japanese
KAN
Kannada
KAT
Georgian
KAZ
Kazakh
KHM
Khmer
KIR
Kirghiz
KOR
Korean
LAT
Latin
LTH
Lithuanian
LVI
Latvian
MAL
Malayalam
MAR
Marathi
MKD
Macedonian FYRO
MNG
Mongolian
MSB
Malay (Burnei Darussalam)
MSL
Malay
MTL
Maltese
NBL
Ndebele (Southern)
NDE
Ndebele (Northern)
NLB
Dutch (Belgium)
NLD
Dutch
NLS
Dutch (Special)
NON
Norwegian (Nynorsk)
NOR
Norwegian (Bokmal)
NSO
Sotho (Northern)
ORI
Oriya
ORO
Oromo
216
130620
15
Language
PAN
Punjabi
PLK
Polish
PTB
Portuguese (Brazil)
PTG
Portuguese
QUE
Quechua
RMS
Rhaeto-Romanic
ROM
Romanian (Standard)
ROV
Romanian (Moldova)
RUM
Russian (Moldova)
RUS
Russian (Standard)
SAN
Sanskrit
SIN
Sinhalese
SKY
Slovak
SLV
Slovenian
SML
Somali
SQI
Albanian
SRB
Serbian (Cyrillic)
SRC
Serbian (Cyrillic, Bosnia and Herzegovina)
SRH
Serbian (Latin, Bosnia and Herzegovina)
SRL
Serbian (Latin)
SSW
Siswati
SVE
Swedish
SWK
Swahili
SXT
Sotho (Southern)
SZI
Sami
TAM
Tamil
TEL
Telugu
130620
217
15
Language
TGE
Tigrinya (Eritrea)
TGL
Tagalog
TGY
Tigrinya (Ethiopia)
THA
Thai
TKM
Turkmen
TNA
Tswana
TRK
Turkish
TSG
Tsonga
UKR
Ukrainian
URD
Urdu (Pakistan)
URI
Urdu (India)
UZB
Uzbek (Latin)
UZC
Uzbek (Cyrillic)
VEN
Venda
VIT
Vietnamese
WEL
Welsh
XHS
Xhosa
YBA
Yoruba
ZHH
Chinese (Hong Kong)
ZHI
Chinese (Singapore)
ZHM
Chinese (Macau)
ZUL
Zulu
Language
Afrikaans
AFK
Albanian
SQI
Amharic
AMH
Tab. 15-3: Languages and 3-letter language codes
218
130620
15
Language
Arabic (Algeria)
ARG
Arabic (Bahrain)
ARH
Arabic (Egypt)
ARE
Arabic (Iraq)
ARI
Arabic (Jordan)
ARJ
Arabic (Kuwait)
ARK
Arabic (Lebanon)
ARB
Arabic (Libya)
ARL
Arabic (Morocco)
ARM
Arabic (Oman)
ARO
Arabic (Qatar)
ARQ
ARA
Arabic (Syria)
ARS
Arabic (Tunisia)
ART
Arabic (United Arab Emirates)
ARU
Arabic (Yemen)
ARY
Assamese
ASM
AZC
Azerbaijani (Latin)
AZE
Basque
EUQ
Bengali
BNG
Bosnian (Bosnia and Herzegovina)
BOS
Bulgarian
BGR
Byelorussian
BEL
Catalan
CAT
Chinese (Hong Kong)
ZHH
Chinese (Macau)
ZHM
130620
Tab. 15-3: Languages and 3-letter language codes (cont.)
219
15
Language
Chinese (PR China)
CHS
Chinese (Singapore)
ZHI
Chinese (Taiwan)
CHT
Croatian
HRV
Croatian (Bosnia and Herzegovina)
HRB
Czech
CSY
Danish
DAN
Dutch
NLD
Dutch (Belgium)
NLB
Dutch (Special)
NLS
Edo
EDO
Efik / Ibibio
EFI
English (Australia)
ENA
English (Belize)
ENL
English (Canada)
ENC
English (Caribbean)
ENB
English (Hong Kong)
ENH
English (India)
END
English (Indonesia)
ENN
English (Ireland)
ENI
English (Jamaica)
ENJ
English (Malaysia)
ENM
ENZ
ENP
EN1
English (Singapore)
ENO
ENS
220
130620
15
Language
English (Trinidad and Tobago)
ENT
English (UK)
ENG
English (US)
ENU
English (Zimbabwe)
ENW
Estonian
ETI
Faroese
FOS
Finnish
FIN
French
FRA
French (Belgium)
FRB
French (Cameroon)
FRO
French (Canada)
FRC
French (Congo)
FRG
French (Haiti)
FRH
FRV
French (Luxembourg)
FRL
French (Mali)
FRI
French (Monaco)
FRM
French (Morocco)
FRR
FR1
French (Reunion)
FRU
French (Senegal)
FRE
French (Swiss)
FRS
FRW
FRY
Fulfulde Adamawa
FUB
Gaelic (Ireland)
GAE
Gaelic (Scotland)
GDH
130620
221
15
Language
Gallegan/Galician
GAL
Georgian
KAT
German
DEU
German (Austria)
DEA
DEC
German (Luxembourg)
DEL
German (Swiss)
DES
Greek
ELL
Greek (Ancient)
GRC
Guarani
GUA
Gujarati
GUJ
Hausa
HAU
Hawaiian
HAW
Hebrew
HEB
Hindi
HIN
Hungarian
HUN
Icelandic
ISL
Igbo
IBO
Indonesian
IND
Italian
ITA
Italian (Swiss)
ITS
Japanese
JPN
Kannada
KAN
Kazakh
KAZ
Khmer
KHM
Kirghiz
KIR
Korean
KOR
222
130620
15
Language
Latin
LAT
Latvian
LVI
Lithuanian
LTH
Macedonian FYRO
MKD
Malay
MSL
MSB
Malayalam
MAL
Maltese
MTL
Marathi
MAR
Mongolian
MNG
Ndebele (Northern)
NDE
Ndebele (Southern)
NBL
Norwegian (Bokmal)
NOR
Norwegian (Nynorsk)
NON
Oriya
ORI
Oromo
ORO
Persian
FAR
Polish
PLK
Portuguese
PTG
Portuguese (Brazil)
PTB
Punjabi
PAN
Quechua
QUE
Rhaeto-Romanic
RMS
Romanian (Moldova)
ROV
Romanian (Standard)
ROM
Russian (Moldova)
RUM
Russian (Standard)
RUS
130620
223
15
Language
Sami
SZI
Sanskrit
SAN
Serbian (Cyrillic)
SRB
Serbian (Cyrillic, Bosnia and Herzegovina)
SRC
Serbian (Latin)
SRL
Serbian (Latin, Bosnia and Herzegovina)
SRH
Sinhalese
SIN
Siswati
SSW
Slovak
SKY
Slovenian
SLV
Somali
SML
Sotho (Northern)
NSO
Sotho (Southern)
SXT
Spanish (Argentina)
ESS
Spanish (Bolivia)
ESB
Spanish (Chile)
ESL
Spanish (Colombia)
ESO
ESC
Spanish (Dominican Republic)
ESD
Spanish (Ecuador)
ESF
ESE
Spanish (Guatemala)
ESG
Spanish (Honduras)
ESH
Spanish (Mexico)
ESM
Spanish (Nicaragua)
ESI
Spanish (Panama)
ESA
Spanish (Paraguay)
ESZ
224
130620
15
Language
Spanish (Peru)
ESR
ESU
ESP
Spanish (Uruguay)
ESY
Spanish (Venezuela)
ESV
Swahili
SWK
Swedish
SVE
Tagalog
TGL
Tamil
TAM
Telugu
TEL
Thai
THA
Tigrinya (Eritrea)
TGE
Tigrinya (Ethiopia)
TGY
Tsonga
TSG
Tswana
TNA
Turkish
TRK
Turkmen
TKM
Ukrainian
UKR
Urdu (Pakistan)
URD
Urdu (India)
URI
Uzbek (Cyrillic)
UZC
Uzbek (Latin)
UZB
Venda
VEN
Vietnamese
VIT
Welsh
WEL
Xhosa
XHS
Yiddish
JII
130620
225
15
Language
Yoruba
YBA
Zulu
ZUL
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
AMH
Amharic
0x045E
1118
ARA
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
Tab. 15-4: Microsoft language code
226
130620
15
3-letter
language
code
Language
MS Code hex.
MS Code dec.
ARY
Arabic (Yemen)
0x2401
9217
ASM
Assamese
0x044D
1101
AZC
0x082C
2092
AZE
Azerbaijani (Latin)
0x042C
1068
BEL
Byelorussian
0x0423
1059
BGR
Bulgarian
0x0402
1026
BNG
Bengali
0x0445
1252
BOS
Bosnian
(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
0x1407
5127
DEL
German (Luxembourg)
0x1007
4103
DES
German (Swiss)
0x0807
2055
DEU
German
0x0407
1031
EDO
Edo
0x0466
1126
EFI
Efik / Ibibio
0x0469
1129
ELL
Greek
0x0408
1032
EN1
ENA
English (Australia)
0x0C09
3081
ENB
English (Caribbean)
0x2409
9225
ENC
English (Canada)
0x1009
4105
END
English (India)
0x4009
16393
130620
Tab. 15-4: Microsoft language code (cont.)
227
15
3-letter
language
code
Language
MS Code hex.
MS Code dec.
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
ENN
English (Indonesia)
0x3809
14345
ENO
English (Singapore)
0x4C09
19465
ENP
0x3409
13321
ENS
0x1C09
7177
ENT
English
(Trinidad and Tobago)
0x2C09
11273
ENU
English (US)
0x0409
1033
ENW
English (Zimbabwe)
0x3009
12297
ENZ
0x1409
5129
ESA
Spanish (Panama)
0x180A
6154
ESB
Spanish (Bolivia)
0x400A
16394
ESC
0x140A
5130
ESD
Spanish
(Dominican Republic)
0x1C0A
7178
ESE
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
228
130620
15
3-letter
language
code
Language
MS Code hex.
MS Code dec.
ESO
Spanish (Colombia)
0x240A
9226
ESP
0x040A
1034
ESR
Spanish (Peru)
0x280A
10250
ESS
Spanish (Argentina)
0x2C0A
11274
ESU
0x500A
20490
ESV
Spanish (Venezuela)
0x200A
8202
ESY
Spanish (Uruguay)
0x380A
14346
ESZ
Spanish (Paraguay)
0x3C0A
15370
ETI
Estonian
0x0425
1061
EUQ
Basque
0x042D
1069
FAR
Persian
0x0429
1065
FIN
Finnish
0x040B
1035
FOS
Faroese
0x0438
1080
FR1
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
130620
229
15
3-letter
language
code
Language
MS Code hex.
MS Code dec.
FRU
French (Reunion)
0x200C
8204
FRV
0x300C
12300
FRW
0x1C0C
7180
FRY
0x0462
1122
FUB
Fulfulde Adamawa
0x0467
1127
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
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
230
130620
15
3-letter
language
code
Language
MS Code hex.
MS Code dec.
KAT
Georgian
0x0437
1252
KAZ
Kazakh
0x043F
1087
KHM
Khmer
0x0453
KIR
Kirghiz
0x0440
1088
KOR
Korean
0x0412
1042
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
0x083E
2110
MSL
Malay
0x043E
1086
MTL
Maltese
0x043A
1082
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
130620
231
15
3-letter
language
code
Language
MS Code hex.
MS Code dec.
PLK
Polish
0x0415
1045
PTB
Portuguese (Brazil)
0x0416
1046
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
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
Serbian (Cyrillic,
Bosnia and Herzegovina)
0x1c1a
7194
SRH
Serbian (Latin,
Bosnia and Herzegovina)
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
TAM
Tamil
0x0449
1097
232
130620
15
3-letter
language
code
Language
MS Code hex.
MS Code dec.
TEL
Telugu
0x044A
1098
TGE
Tigrinya (Eritrea)
0x0873
2163
TGL
Tagalog
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
130620
233
15
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

TransitNXT Advanced AdvancedFeatures ENG

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

TransitNXT Advanced AdvancedFeatures ENG

Diunggah oleh

Hak Cipta:

Format Tersedia

Transit/TermStar NXT

Transit/TermStar NXT Reference Guide

Using startup parameters for Transit/

-U (Start with a specific user) ............................................................ 9

-H (Start with a specific user role)...........................................10

Exchanging reference material via TMX

Exporting language pairs to TMX file .............................................. 13

Exporting files to a TMX file ..................................................................... 13

Importing TMX files in Transit NXT ................................................. 16

Naming and saving of language pairs ..................................................... 16

Compatibility of the language and country codes of TMX files 20

Opening a role ..................................................................................... 23

Creating a new role ............................................................................. 26

Creating completely new roles ................................................................ 26

Overview of standard roles ............................................................... 30

Transit/TermStar NXT Reference Guide

Customising Transit/TermStar NXT

Automating tasks using macros ........................................................ 41

Customising the system environment ............................................. 49

Spellchecking: list of unknown words ............................................ 55

Opening and editing the list of unknown words...................................... 56

Customising index buttons for TermStar NXT .............................. 57

Checking and changing abbreviation list ....................................... 58

Print definition set-up

Opening a print definition................................................................. 60

Saving the print definition........................................................................ 61

Compressing files with formatting information (cod files) ......... 73

Excluding hidden or locked text from translation in Excel ........ 73

Optimising the pretranslation time ................................................. 75

Transit/TermStar NXT Reference Guide

The MaxPreTransHits parameter..................................................... 75

Fields in the TermStar dictionary

Field types ............................................................................................. 77

Managing layouts ................................................................................. 85

Working with the layout editor ........................................................ 90

Areas of a layout ...................................................................................... 90

Editing the layout ................................................................................. 95

Selecting and removing fields for the layout ........................................... 95

Specifying field properties ................................................................. 98

Overview ............................................................................................. 110

Transit/TermStar NXT Reference Guide

Modifying field names ...................................................................... 110

Setting graphics file access.............................................................. 115

Specifying cross-reference separators .......................................... 116

Specify additional sort field ............................................................ 117

Installing a spellcheck dictionary .................................................. 124

Uninstalling spellcheck dictionaries ...................................................... 125

Managing database links

Creating a database link .................................................................. 126

Deleting a database link .................................................................. 136

Transferring database connections to other computers ........... 137

Deleting incorrect database links .................................................. 140

Compressing databases and dictionaries ..................................... 141

Database driver information........................................................... 141

Compacting Microsoft Access database or

Transferring TermStar databases from Microsoft Access to an

Renaming an ODBC connection in Windows........................................ 148

Transit/TermStar NXT Reference Guide

Overview ............................................................................................. 158

What are regular expressions? .............................................................. 158

Defining regular expressions ........................................................... 160

Control characters ............................................................................. 161

Overview of meta characters.......................................................... 162

Wildcards: . [ ] & ......................................................................... 163