The Transit category features blogs related to STAR’s Transit NXT translation memory software. Find useful information on troubleshooting and the latest updates here.

Transit NXT

What is a Dual Fuzzy? Better Translation Memory Matches

Transit NXT

Dual Fuzzy

A Dual Fuzzy search on your translation memory gives you more choice and reference. You can search in both source and target segments across your project – seeing how and where terms have been used before and in different contexts. This can improve your understanding of key terms and ensure consistent translation.

1. Dual Fuzzy Overview

Transit uses the Fuzzy index to suggest translations from existing translations (fuzzy matches). One innovation for fuzzy search which appears in Transit is the so-called Dual Fuzzy principle – ‘dual’ because Transit can search for matching blocks of text both in source-language and target-language segments. If no match is found in the source language, Transit can search the target-language segments for similar text while you type your translation. If Transit finds segments containing similar target-language text, these are displayed in the red Target fuzzy window, in accordance with the concept of colour-coding employed in Transit.

Target-language fuzzy search is a particularly valuable tool for the translator when source-language segments which convey the same message are written in a slightly different way, meaning that no matches are obtained using source-language fuzzy search. When it comes to the target language, however, there may well be segments with the same content as the text being translated. Using these target-language translation suggestions, the translator is able to ensure the consistency of the text by formulating identical content in exactly the same way.

Another feature of the target-language fuzzy search is that it also makes it possible to remove variations in the source language, thus allowing a higher level of consistency to be attained in the original documents as well.

For information on how to build the fuzzy index and how to edit and accept translation suggestions, please refer to section 2.“Building the fuzzy index and accepting suggestions.
The fuzzy index is then searched for segments which are similar to the segment to be translated. This involves searching:

  •  in the reference material
  •  in all language pairs in the project, including those that are not open

Transit displays fuzzy matches in the Source fuzzy window with the following information:

Source fuzzy window  Source fuzzy window

  •  First line – Match quality, icon 33 and file containing the translation suggestion.
    Clicking the icon 33 opens the reference file in a separate window.
  •  Second line – source-language segment from the reference material

Icon for language direction of the reference segment

In the second line, Transit additionally displays an icon for the language direction of the reference segment:

  •  Icon icon 2 – The reference segment has the same source and target language as the current segment.
  •  Icon icon 3– The reference segment has the reverse source and target language in comparison to the current segment.
  •  Icon icon 4– The source and the target language of the current segment were both target languages in the project the reference segment origins from.
  •  Icon icon 5– The reference segment has been translated via a Pivot language.

This information is especially of interest if you often work on multilingual projects.

If required, you may hide the icon via the Display icon for language direction option in the user preferences of the Dual Fuzzy option (see section 3.Dual Fuzzy–User preferences)

Please consider that this information can be displayed only, if the reference files you use come from projects that were created with Transit NXT Service Pack 7 or newer.

——————————————————————————–

  •  Third line – active source-language segment that you have to translate

By default, Transit highlights source-language differences between the reference segment and the current segment using a thin green line. You also have the option to display the differences using a thick line or with different font colours. To define these colours, click on the Transit button and select User preferences, then click Colours and fonts in the window and select the colour which Transit should use in these circumstances.

  • Fourth line – target-language segment from the reference material

This line displays the reference segment exactly how it appears in the reference file. The symbol in the second column provides information on which status the reference segment has (e.g. ‘+’ for 100% match or ‘#’ for a segment which was originally pretranslated with the status Check pretranslation (for information, see “Display of the segment status in the Transit editor”).

  • Fifth line – current, target-language translation suggestion

This line displays modifications which may be required to the target-language segment (numbers, markups, etc.). Any modifications compared to the unaltered reference segment displayed in line 4 are represented by the numbers in the left-hand field.

These numbers represent the options which you can select for updating fuzzy matches in the Update matches dropdown list, which can be found under Matches | Fuzzy search (source). These are:

1st number: numbers updated

2nd number: markups updated

3rd number: user-defined exceptions updated

4th number: terminology updated

For example, if the indicator shows 2/1/0/0, this therefore means that in the updated segment, numbers and markup information have been altered to match the information in the active source-language segment.

If Transit has found several translation suggestions, it shows the closest match, along with the following text:
Press NUM + (numeric keypad) to display more fuzzy matches.

In such a case, you can switch back and forth between the different suggestions using the PLUS and MINUS keys (numeric keypad).

Click on the Transit button and select User preferences, then click Dual Fuzzy in the window and specify the required fuzzy-match quality, and the criteria according to which Transit should accept fuzzy matches (see section 3.Dual Fuzzy – User preferences)

2.Building the fuzzy index and accepting suggestions

Transit builds the fuzzy index if you accept a translation with ALT+INS or a translation suggestion using ALT+ENTER. At the same time Transit creates and updates the fuzzy index in the background such that you do not need to wait for suggestions while you are translating. Transit saves the fuzzy matches in a temporary memory so they can be displayed in seconds.

Transit displays the translation suggestions (fuzzy matches) it has found in the Source fuzzy or Target fuzzy windows (fig. 5-22).

To check the context, you can open the reference file containing the fuzzy match. To do this, double click on the icon in the first column to the left of the path for the reference file. Alternatively you can also open the reference file via the context menu. You can also use this function to correct errors in the reference material if necessary.

Dual Fuzzy – fixed windows and bubble windows

To make working with fuzzy matches as flexible as possible, Transit offers you two different window types. You have the choice between using fixed fuzzy windows or bubble windows to display fuzzy matches. Both window types contain the same basic information. However, they differ in terms of how they are used. This is described briefly in the following.

  • Bubble window

The bubble window opens at the segment in the target language containing the cursor. When the bubble window opens, the cursor stays in the target-language segment. This offers you the opportunity to accept the translation suggestion straight into the target-language segment and to adapt it from there, if necessary.

A fuzzy match in a bubble window A fuzzy match in a bubble window

  • Fixed fuzzy window

The fixed fuzzy windows are either docked to the Transit user interface, wherever you have selected, or configured as floating windows. When a fuzzy match is displayed in one of the fixed fuzzy windows, the cursor appears in the fuzzy window at the start of the line containing the updated translation suggestion. This offers you the opportunity to adapt the translation suggestion in the fuzzy window, if necessary, and then to accept the translation into the text.

A fuzzy match in a fixed windowA fuzzy match in a fixed window

In the case of both window types,

– Pressing ALT+INS adopts the unchanged translation suggestion into the target language segment. Transit automatically assigns the segment the status that is to be assigned in accordance with the default setting (e.g. Translated or Checked 1) and moves the cursor to the next untranslated segment.

If there are a number of translation suggestions for a segment, Transit automatically adopts the first proposal from this list. If another translation suggestion from the list is to be used, you have to position the cursor manually in the line of the desired translation suggestion. Insert this suggestion in the target language segment by pressing ALT+INS.

You can prevent the ALT+INS function from adopting the translation suggestion by changing the user preferences. Please refer to section 5.4.3 “Dual Fuzzy – User preferences” for more detailed information on this topic.

– ALT+ENTER inserts the unchanged translation suggestion into the target language segment, but it is not automatically assigned the status Translated. You have the possibility to edit the translation and then confirm it by pressing ALT+INS.

Tip for proofreading

If you are checking a translation in Transit, it is recommended to use the bubble window and to disable the fixed fuzzy window if necessary. You can hide bubble windows by pressing the ESC key and then confirming the current segment by pressing ALT+INS.
If the fuzzy index is started via the fixed fuzzy window, you have to position the cursor in the target language segment manually for each fuzzy match before you can confirm this segment with ALT+INS.

——————————————————————————–

You can find information on the Dual Fuzzy settings in section 3 “Dual Fuzzy – User preferences”.

How do I search for fuzzy matches and use suggestions in my translation?

1 You have the following options when searching for fuzzy matches:

– Press the keyboard shortcut ALT+ENTER to search for source-language fuzzy matches for the active segment.

Transit searches for fuzzy matches for the active segment and displays them in the Source fuzzy window.

– Press the keyboard shortcut ALT+INS to confirm the segment selected in the target language as ‘Translated’ and to move the cursor to the next segment to be processed.

Transit moves the cursor to the next segment to be processed and searches automatically for source-language fuzzy matches in this new segment. These are then displayed in the Source fuzzy window.

– To confirm the active segment, press the shortcut ALT+INS.

Transit moves the cursor to the next segment to be processed. When you have entered more than two words into this segment, Transit starts a target-language fuzzy search. Transit displays the matches in the Target fuzzy window.

Depending on the user preferences, Transit can automatically insert the suggestion from the fuzzy index into your translation or display it in the fuzzy window as a suggestion, allowing you to check and, if necessary, adapt it (see section 5.4.3 “Dual Fuzzy – User preferences”).

2 The Source fuzzy and Target fuzzy windows allow you to do the following:

– You can alter the translation suggestion from right inside the respective fuzzy window to adapt it to fit with the current translation.

To do this place the cursor in the line containing the translation suggestion and modify it.

– Using the PLUS and MINUS keys on the keypad, you can switch back and forth between translation suggestions, if Transit has found several suggestions.

In this case, Transit displays the following message:
Press NUM + (numeric keypad) to display more fuzzy matches.

– You can check the context of a translation suggestion by opening the reference file where the translation suggestion can be found.

To do this, open the context menu by clicking on the translation suggestion in the Source fuzzy window with the right mouse button and selecting Open reference file. Transit displays the reference file to allow you to check the context. The reference file is opened in a separate editor window, indicated by the new tab at the top of the editor-window area:

Reference file tab Reference file tab

Click on the X at the top right of the editor area to close the reference file again.

The translation suggestion may also be a segment which you have already translated in the current language pair. If you select Open reference file from the context menu in this case, Transit displays the following message:

The reference segment is in the current window. Do you want to go to this segment? (You can use the ‘Go to flag’ option in the ribbon bar to return to the current segment.)

This is gives you the option to decide whether the cursor should move to the reference segment.

3 Transfer the match (which you may or may not have altered) to your translation. Press the ALT+ENTER keyboard shortcut to do this.

Transit replaces the target language segment with the suggested translation and places the cursor in this segment.

If you do not wish to accept the fuzzy match, switch back to the target-language window to translate the text there on your own. To do this, press the keyboard shortcut ALT+2 or place the cursor in the target-language pane using the mouse.

4 Now confirm the selected segment as ‘Translated’ and move the cursor to the next segment to be processed. Press the ALT+INS shortcut to do this.

Transit moves the cursor to the next segment to be processed and looks for fuzzy matches there.

3.Dual Fuzzy–User preferences

In the user preferences, you can define how high the quality of translation suggestions should be and how Transit should accept translation suggestions, independent of a specific project.

How do I configure the user preferences for Dual Fuzzy search?

1 Select Transit button | User preferences.

Transit displays the User preferences window.

2 Select Dual Fuzzy from the list on the left.

Transit displays the user preferences for Dual Fuzzy:

User preferences window, Dual fuzzy screen
User preferences window, Dual fuzzy screen

You can also open that window via the Dual fuzzy button in the resource bar.

The Source language section

– Under Minimum status, you can define from which segment status reference matches should be regarded. If you do not specify a minimum segment status for the source-language fuzzy search, Transit will suggest all segments, regardless of the segment status. These may also be segments in which only terms from the dictionary have been accepted but not the rest of the segment.

To prevent Transit from displaying such segments as translation suggestions, specify a minimum segment status for the source-language fuzzy search (e.g. Translated). Now Transit will only suggest the segments that you confirmed, e.g. as ‘Translated’.

– Under Minimum quality (%), you can specify the minimum quality of the fuzzy matches which Transit suggests. To do this, enter the desired value.

– Select the Bubble option if you want fuzzy matches to be displayed in a bubble window.

– Select the Fixed window option if you want fuzzy matches to be displayed in the fixed window.

– Under Update Transit matches, specify how Transit should update the fuzzy matches. The following options are available:

Numbers – If this option is selected, any changes to numbers will be updated and the modified segment accepted into the translation.

Markups – If this option is selected, any changes to markups will be updated and the modified segment accepted into the translation.

User-defined exceptions – If this option is selected, fuzzy matches containing a user-defined exception will be updated and the modified segment automatically accepted into the translation.

Terminology – Transit uses this function if the source-language reference segment and the segment to be translated only differ by one word. If Transit finds both words (old and new word) in the project dictionaries, it automatically uses the translation for the new word from the dictionary.

Example:

ENG reference segment: There is a bird in the garden.
DEU reference segment: Da ist ein Vogel im Garten.
ENG active segment: There is a raven in the garden.

The segments differ by the use of the word bird or raven. If there is a translation in the project dictionaries for both words, Transit will use the translation Rabe for the new word raven:
DEU active segment: Da ist ein Rabe im Garten.

– Using the option Display updates as, you can select how update markers should be displayed in the fuzzy window. The relevant selection applies both to the Source Fuzzy and the Target Fuzzy window.

Thin lines – Updates are identified using thin lines – in the source language segment, the lines are green, and in the target language translation suggestion, they are red.

Thick lines – Updates are identified using thick lines – in the source language segment, the lines are green, and in the target language translation suggestion, they are red.

Font colour – Updates are identified using preset font colour. If necessary, you can adjust these colours to suit your individual requirements, in the Colours and fonts user preferences.

– Using the Show icon for language direction option you can specify that the icon indicating the language direction is no longer displayed in the Fuzzy window in case you do not need this information (see info box “Icon for language direction of the reference segment”).

– The option Automatic segment concordance search if no fuzzy match is found automatically performs a concordance search if a fuzzy search does not produce any results.

Under Minimum quality (%), specify the minimum percentage match that Transit should take into consideration for the concordance search. Thus Transit will only suggest matches where the reference segments and the segments to be translated exhibit the specified level of similarity.

– Using the option Use ALT+INS to accept fuzzy match and to confirm segment as translated, you can specify that shortcut ALT+INS should cause Transit to accept the fuzzy match from the fuzzy window and confirm the current segment, all in a single step. If this option is deselected, Transit will not accept the fuzzy match when ALT+INS is pressed. In this case, it is first necessary to accept the fuzzy match using the shortcut ALT+ENTER, and then confirm it using ALT+INS.

If segment concordance search is selected and a match is returned, the Alt+Ins function is initially disabled. However, as soon as you have modified the match in the fuzzy window, the Alt+Ins function can be used.

The Target language section

– Select the Automatic search option if you want Transit to automatically start a search in the target language whenever the source-language fuzzy search produces no results.

Minimum status (see Source section)

Minimum quality (%) (see Source section)

Bubble (see Source section)

Fixed window (see Source section)

– Select the Phrase search option if you want to search for the precise sequence of words in the target-language fuzzy search.

– Below Search in you can select if Transit should search both the Reference material and the Working folder during the source-language fuzzy search.

3 Confirm your settings:

– Click on OK to confirm the changes and close the User preferences window.

– Click on Save to confirm the settings without closing the window. This allows you to make further changes to the user preferences.

4. Fuzzy search settings

Via the ribbon bar, you can configure additional fuzzy search options. To do this, select Matches | Fuzzy search (source)  or Fuzzy search (target).

Fuzzy search (source)

Fuzzy search (source) group Fuzzy search (source) group

– Min. status

Here you can define from which segment status reference matches should be regarded. The Source fuzzy window only suggests translations with at least the selected status.

– Ins. 100% match

Transit automatically inserts suggestions from the fuzzy index into the target-language text if the match is 100% (i.e. reference segment and segment to be translated match exactly).

However, Transit only inserts the suggestion if you search for a fuzzy match for the segment. You can select from the following options:

Always – The 100% match is accepted automatically.

If no variants exist – If this option is selected, the 100% match will only be accepted if the reference material only contains a single possible translation. If several variants exist, Transit will show you all the translation variants as fuzzy matches.

Never – The 100% match is not accepted automatically, but rather only displayed as a suggested translation. This is the default.

Min. quality

Here you can define the minimum quality level of the fuzzy matches suggested by Transit. Enter the desired value.

Thus Transit will only suggest fuzzy matches where the reference segments and the segments to be translated exhibit the specified level of similarity.

Segment concordance

If you select this option, Transit will carry out a concordance search in the source-language segments if the fuzzy search returns no matches.

Update matches

With this option, you can specify how Transit should update the fuzzy matches. You can find information on the possible settings in section 5.4.3 “Dual Fuzzy – User preferences”.

– The list Options allows you to define the following settings:

Bubble – Select this option if you want fuzzy matches to be displayed in a bubble window.

Fixed window – Select this option if you want fuzzy matches to be displayed in a fixed window.

Automatic search – Selecting this option will mean that the fuzzy search starts automatically, during translation, without the need to press the ALT+ENTER shortcut.

Match case – If you select this option, a 100% match will only be automatically accepted if there is no discrepancy in capitalisation in the segment to be translated and the reference segment. If this option is not selected, then the fuzzy search will not distinguish between upper and lower case.

Fuzzy search (target)

Fuzzy-search (target) group Fuzzy-search (target) group

On/Off – Clicking on this button switches the automatic target-language fuzzy search on or off.

Min. status (see Fuzzy search (source) ribbon-bar group)

Min. quality (see Fuzzy search (source) group)

Search in

The following options are available for the target-language fuzzy search:

Reference material – If this option is selected, the reference material will be searched for fuzzy matches.

Working folder – If this option is selected, the working folder will be searched for fuzzy matches.

– The list Options allows you to define the following settings:

Bubble (see Fuzzy search (source) ribbon-bar group)

Fixed window (see Fuzzy search (source) ribbon-bar group)

Phrase search – If this option is selected, Transit will search for the precise sequence of words in the target-language fuzzy search.

Transit NXT

Quick Guide to Transit NXT functions to make translation easier

Transit NXTTransit NXT Quick Guide

In this guide we show you how to get the most from Transit by showing some of the key features and shortcuts. As translators ourselves we’ll show you how we use Transit and the advanced features of some of the core functions.

Having read this – you will learn how to make your translation easier.

1. Find

In Transit, as with every word processing program, you can search for any string.

Transit displays various messages if it cannot find the string you are searching for (see Table 5-10).

How do I search for a string?

1 Place the cursor in the window in which you wish to search.

OR

Select the string that you want to find.

2 Select Processing | Search | Find.

Transit displays the Find tab in the Find/Replace window:

Find/Replace window, Find tabFind/Replace window, Find tab

3 Enter the search string in the Find field.

If you have selected the string previously, it is automatically inserted in the Find field.

4 To set additional options for the search, click on the + button in the Options section.

Transit expands the window to display the following options:

Expanded Find windowExpanded Find window

Match case – Select this option if you only want Transit to find strings which precisely match the case of the character string entered in the Find field.

Regular expression – Transit will interpret the string as a regular expression. Please refer to the Transit/TermStar NXT Reference Guide for details on regular expressions.

Find whole words only – Select this option if you want Transit to search for strings as whole words and not as a part of another word.

You can also specify where Transit should search for the string:

Search in text only – Transit will only search in the text, not in the markups.

Search in text and markups – Transit will search both in the text and in the markups.

Search in markups only – Transit will only search in the markups, not in the text.

You also have the option to save find operations so you can call them up again, if required, at a later point in time:

Load is used to call up a saved search.

Save is used to save the current search.

Save as is used to save a loaded search under a different name.

5 You also have the option to get an overview on the search result before searching:

Count informs you on how often the search string occurs in total.

Filter displays only the segments that contain the search string.

By clicking Filter off you can switch off the filter again.

Highlight  all occurrences of the search string in green.

By clicking Highlight off you can switch off the highlighting again.

6 Click Find next or Find previous to search for the string.

Transit searches for the string.

Transit highlights the string it has found or displays a message.

7 You can now proceed either by clicking on Find next or Find previous or by entering a different string and searching for that.

– If you no longer require the Find/Replace window, you can close it by clicking on X on the right of the titlebar.

– It is also possible to integrate the Find/Replace window with the user interface by docking it.

Transit displays one of the following messages if it cannot find the string:

Messages if Transit cannot find a stringMessages if Transit cannot find a string

 

2. Find/Replace

In Transit, as with any other data processing program, you can search for any string and have it replaced with another string.

Transit displays various messages for you to respond to if it cannot find the string you are searching for.

How do I find and replace a string?

1 Place the cursor in the window in which you wish to perform the find/replace operation.

2 Select Processing | Search | Replace.

Transit displays the Replace tab of the Find/Replace window:

Find/Replace window, Replace tabFind/Replace window, Replace tab

3 Enter the search string in the Find field.

4 In the Replace with field, enter the string which Transit will use to replace any instances it finds of the specified string.

5 To set additional options for the search, click on the + button in the Options section.

Transit expands the window to display the following options:

Expanded Find/Replace window, Replace tabExpanded Find/Replace window, Replace tab

Match case – Select this option if you only want Transit to find and replace strings which precisely match the case of the character string entered.

Regular expression – Transit will interpret the string as a regular expression. Please refer to the Transit/TermStar NXT Reference Guide for details on regular expressions.

Find whole words only – Select this option if you want Transit to search for strings as whole words and not as a part of another word.

You can also specify where Transit should search for the string:

Search in text only – Transit will only search in the text, not in the markups.

Search in text and markups – Transit will search both in the text and in the markups.

Search in markups only – Transit will only search in the markups, not in the text.

You also have the option to save find/replace operations so you can call them up again, if required, at a later point in time:

Load is used to call up a saved find/replace operation.

Save is used to save the current find/replace operation.

Save as is used to save a loaded find/replace operation under a different name.

6 Click Find next or Find previous to search for the string.

Transit searches for the string.

7 Transit highlights the string it has found. You can now specify whether you want to replace the string:

– To replace the string found, click on Replace or Replace previous.

Transit replaces this string and continues the search forwards or backwards.

– If you do not want to replace the string it has found, click on Find next or Find previous.

Transit leaves this string unchanged and continues the search forwards or backwards.

– If you want to interrupt or exit the process, click on X.

Transit closes the Find/Replace window.

– If you want to replace all strings found without further prompting, click on Replace all.

Transit will replace this string, then continue the search and automatically replace all the other matching strings it finds.

After this, Transit displays a message with the number of strings found and replaced.

Example: 12 found, 12 replacements made

Transit displays various messages similar to those seen in the Find function if it cannot find the string you are searching for.

8 If you no longer require the Find/Replace window, you can close it by clicking on X on the right of the titlebar.

– It is also possible to integrate the Find/Replace window with the user interface by docking it.

 

3.Deleting text

In Transit you can delete text in the usual manner with the BACKSPACE or the DEL key. However, it is also possible to quickly delete the text in question using the Delete to end of segment option. This can be found under Processing | Translate. The dropdown menu from the Confirm button allows you to select or deselect this option. When it is selected, Transit will automatically delete the source text (underlined in red) when the user presses the ALT+INS shortcut.

Markups which Transit deletes with the text

If there are markups you wish to delete in the text, Transit will delete these as well. Markups in the other segments are not affected by this.

 

4. Moving or copying text

You can move or copy text in Transit with the mouse.

How do I move or copy text with the mouse?

1 Select the text you want to move or copy.

– To move the text you have selected, hover the mouse pointer over the selected text, then press and hold the left mouse button. Then drag the text with the mouse to the position where you want to insert it.

– To copy the text you have selected, press and hold the CTRL key and drag the highlighted text to the position where you want to insert it.

 

5.  Inserting Unicode characters

Using the Character map option in Transit, you can insert any Unicode character which can be represented by the current character set. In doing so you can choose from various character groups.

How do I insert a Unicode character?

1 Place the cursor at the position where you want to insert the Unicode character.

2 Select Edit | Text | Character map.

Transit displays the Character map window:

Character map windowCharacter map window

3 Select a Unicode character group from the list (e.g. Latin-1).

Transit shows the characters from the group selected in the character map.

4 Click on a character to insert it at the cursor position.

Transit inserts the character at the cursor position.

The window remains open so that you can insert more Unicode characters.

5 If you no longer require the Character map window, you can close it by clicking on X on the right of the titlebar.

– It is also possible to integrate the Character map window with the user interface by docking it.

 

6.Selecting the keyboard layout

You may have defined several so-called input languages in Windows to make it possible to enter text in different languages using the respective keyboard layout.

In such a case, Transit automatically selects the correct keyboard layout for each window and each dictionary entry.

Example: you are working on a German to English translation project:

  • When the cursor is in the source-language pane (German), Transit selects the German keyboard layout.
  • When the cursor is in the target-language pane (English), Transit selects the English keyboard layout.
  • When the cursor is in a German dictionary entry, TermStar NXT selects the German keyboard layout.
  • When the cursor is in an English dictionary entry, TermStar NXT selects the English keyboard layout.

The currently selected input language is indicated in the Windows taskbar:

Windows taskbar: German is selected as the input languageWindows taskbar: German is selected as the input language

This must be enabled by selecting the appropriate setting in the Windows Control Panel (for example, in Windows 7, from the Start menu select Settings | Control Panel | Regional and Language Options, Languages tab, then the Details button).

You have the following options for switching language manually:

  • From the Windows taskbar, select the language which Windows should use:

Windows taskbar: switching input languageWindows taskbar: switching input language

This change will apply until the next time Transit selects the language automatically.

  • You can use the Windows keyboard shortcuts to switch between the different languages.

By default, Windows uses the keyboard shortcut ALT (left) + SHIFT. You can change this shortcut in the Windows Control Panel.

This change will apply until the next time Transit selects the language automatically.

Switching off automatic keyboard-layout selection

You have the following options for switching off automatic keyboard-layout selection:

– You can deselect the Automatic keyboard switch option under Edit | Miscellaneous.

Please refer to section 8.3.18 “Activating/deactivating automatic keyboard-layout switching” for more detailed information on this topic.

– Remove any languages which you do not require. Transit can only switch between languages that you have added.

 

7. Moving the cursor

You can move the cursor in the editor with ribbon bar commands or keyboard shortcuts.

The next table  shows the ribbon bar commands for moving the cursor and the relevant shortcuts.

Moving the cursor in internal repetitions mode

If you are working in internal repetitions mode, Transit provides other possibilities for moving the cursor.

Moving the cursor in the editorMoving the cursor in the editor

8. Moving the cursor to specific segments

You can also move the cursor to a particular location in the language pair which is currently open. You have the following options:

  •  Go to a segment with a specific number

You will find the number of the segment in which the cursor is located in the column on the left-hand side of each of the editor panes and in the status bar at the bottom of the window (Seg.: ). You can find more detailed information on this here.

  •  Go to a line with a specific number

You will find the number of the line in which the cursor is located in the status bar at the bottom of the window (Line.: ). You can find more detailed information on this here.

If you have the Formatting or Structure options – for ‘WYSIWYG’ display of formatting and document structure – selected under View | Text/Markups | Options, the line number is not displayed.

  • Go to a bookmark

You can bookmark text in the Transit editor so you can move the cursor quickly to the bookmarked text. The bookmarks can be deleted if you no longer need them. Transit automatically removes bookmarks during export so there are no “Transit-related” marks in the target-language original format.

  • Go to a retained position

You have the option to set a flag in the text so that Transit can ‘memorise’ a particular position in the text. After you have checked something at a different location, you can easily find your way back to the flagged position in the text.

  • Go to a segment for which comments have been entered

How do I move the cursor to a segment or to a line?

1 First select the unit type to which you want to move the cursor, under Processing | Search | Go to:

Go to search function Go to search function

– Segment

– Line – If the Formatting or Structure options are selected for ‘WYSIWYG’ display of tables and structure, this option is not available.

– Bookmark – If you have set a bookmark, Transit can move the cursor to the bookmark.

2 In the field to the right of the dropdown, enter the number of the segment, line or bookmark to which you want to move the cursor.

3 Click on Go to or press the ENTER key.

Transit moves the cursor to the selected position. The cursor does not move if you enter an invalid value.

How do I set a bookmark?

1 Move the cursor to the position at which you wish to set a bookmark.

2 Under Edit | Text, click on the Bookmark option.

Transit displays the Bookmark window:

Bookmark windowBookmark window

3 Enter a number for the bookmark.

Using this number, you can go to this position via the Processing | Search | Go to option.

4 Click Set to confirm the settings.

Transit sets the bookmark at the cursor position.

How do I delete a bookmark?

1 Select Edit | Text | Bookmark.

Transit displays the Bookmark window.

2 Enter the number of the bookmark you want to delete.

3 Click Delete to delete this bookmark.

Transit deletes the bookmark specified.

How does Transit retain the current position of the cursor?

1 Move the cursor to the position Transit should retain.

2 Select  Edit | Text | Set flag:

Retain position iconRetain position icon

 

Transit notes the position. You can now move the cursor to another position.

Transit only retains the position as long as the language file is open. Transit will no longer be able to find the position if you close the language file and open it later.

How do I jump back to the retained position?

1 To move the cursor back to the retained position, select Edit | Text | Go to flag:

Go to flag iconGo to flag icon

Transit moves the cursor to the retained position.

 

9. Formatting text manually

In addition to being able to assign markups to translated text in Transit, you can also manually assign bold, italic or underline font attributes to the font style. In this case, Transit does not use the character formats that may have been assigned in the source file or format templates. Instead it only assigns the bold, italics or underline font attributes.

This means that you can format a word more quickly if, for instance, a word is marked with quotation marks in the source language and you wish to mark it in bold in the target language.

Manual formatting or update markups?

In various programs (e.g. Word, FrameMaker), it is possible to specify so-called “Character formats”, “Character templates” or “Format templates” for the character formatting. Transit uses markups instead of these formats.

If you format the text manually, Transit does not use these markups, but rather assigns the desired attribute to the text (e.g. underline or bold).

For this reason, where applicable, you should ask your customer to confirm how the text should be formatted before formatting the text.

——————————————————————————–

How do I format the text manually using formatting commands?

1 Highlight the text that you wish to format.

2 Under Edit | Formatting click on the icon for the formatting you require:

 Icons for formatting text manually

Icons for formatting text manually

 

Transit assigns the font style to the highlighted text and inserts the appropriate markups. The appearance of markups in the Transit editor is dependent upon the settings selected under View | Text/Markups.

 

10. Deactivating write protection for the source language

The text in the source language is always write-protected so that you do not inadvertently change the text. If this happened, the language pair would no longer agree with the imported source document and you would be unable to use your translation as reference material.

However, it may be necessary to change the text in the source language in certain cases – if you have found typing errors in the original document, for example.

attentionReactivating write protection

It is recommended that you reactivate write protection for the source language as soon as you have made your changes. In this way you can avoid the source language text being changed accidentally.

——————————————————————————–

How do I deactivate write protection for the source language?

1 Place the cursor in the source-language text.

2 Uncheck the Read-only option under Edit | Text.

Transit deactivates write protection for the source language.

3 Correct the errors in the text.

We recommend you reactivate write protection immediately afterwards.

How do I reactivate write protection for the source language?

1 Place the cursor in the source-language text.

2 Click on Read-only under Edit | Text.

Transit reactivates write protection, as indicated by the checkmark in front of this option.

 

11. Using AutoText to insert frequently occurring text

In Transit, you can save frequently occurring text as ‘AutoText’. You then have two options for inserting this text into your translation:

  • Type the name of an AutoText entry and Transit will replace it

Instead of the text itself, you enter the name of an AutoText entry into the editor; Transit then automatically inserts the required text.

Example: The expression STAR Group occurs repeatedly in your text. You save these words as an AutoText entry and specify sg as the name of the entry. Then all you have to do is enter sg and Transit will replace the string with the expression STAR Group.

  • Select from the list of AutoText entries

Transit displays the names of all the expressions you have saved as AutoText entries in one window. You can select the desired entry from this list, then Transit will enter it into your translation.

How do I create an AutoText entry?

1 Select the text in Transit you want to save as an AutoText entry (in the example, STAR Group).

2 Select Edit | Text | AutoText.

Transit displays the AutoText window:

AutoText windowAutoText window

– top field – Name of AutoText entry.

The top field initially displays the text you selected as the name for the AutoText entry (in the example, STAR Group).

– middle field – List of names of all available AutoText entries.

– bottom field – Text which Transit should insert as AutoText (in the example, STAR Group).

3 In the top field, enter a name for the AutoText entry:

AutoText window with name of AutoText enteredAutoText window with name of AutoText entered

You can enter this name in your translation instead of the text itself (in the example, sg). Transit automatically replaces the name with the AutoText.

4 To confirm your entry, click Add.

Transit will use the specified name as an abbreviation for the text displayed in the bottom field. Transit now also displays the name string in the centre field.

attentionSaving AutoText entries

Transit saves AutoText entries on a user-related basis at \config\users\\ in the file default.prf. An AutoText entry appears in this file below [AutoText] as soon as you open the User preferences window and click Save.

——————————————————————————–

How do I enter AutoText while translating?

1 Enter the name of the AutoText entry in the target-language window (in the example, sg).

2 Immediately press the F3 key to make Transit replace the name with the AutoText (in the example STAR Group).

How do I select an AutoText entry from the list?

1 Place the cursor in the target-language window at the point at which Transit should insert the AutoText.

2 Select Edit | Text | AutoText.

Transit displays the AutoText window with its three fields. The centre field displays the names of all the AutoText entries saved.

3 In the centre field, select the name of the AutoText entry which Transit should insert into your translation.

Once you select a name, the bottom field displays the AutoText which will be inserted into the translation.

4 Click Insert to insert the text into your translation.

Transit enters the saved AutoText into your translation at the cursor position.

How do I delete an AutoText entry?

1 Select Edit | Text | AutoText.

Transit displays the AutoText window with its three fields. The centre field displays the names of all the AutoText entries saved.

2 In the centre field, select the name of the AutoText entry which you want to delete.

Once you select a name, the bottom field displays the AutoText which belongs to the selected name.

3 Click Delete to delete the AutoText entry.

Transit deletes the AutoText entry.

4 Close the AutoText window by clicking OK.

 

12. Opening language files using the “File navigation” window

The languages files within a project are normally opened via Project | Administration | Open language pair or via the Quick Access Toolbar. Transit offers a further possibility with the File navigation floating window. The Files tab in this window provides a separate view of all the files contained in a project and their hierarchy, and also allows you open these files in the Transit editor right from the window with a double click.

Navigation via the File navigation window is of particular use when working with resource files. Clicking on a dialog name or a particular element in the tree structure displayed in this window takes you directly to the corresponding segment in the Transit editor.

In addition, the File navigation window contains the Error (type) and Error (file) tabs that serve as error display. This error display is updated when a format check or terminology check  or a an error report via the Report Manager Quality Check  is performed.

File navigation windowFile navigation window

 

 

13. RC editor

The RC editor is a tool for localising resource files. It offers a comprehensive set of options for working with binary resource files, for example, for resizing and repositioning the window elements contained within these files. In the RC editor, you can alter the size or position of a window element, or select several elements at once to arrange them on the interface, as required. In addition, the Markup window allows you to check which letters you have already used for accelerator keys in the current translation, thus avoiding accelerators being assigned multiple times. The File navigation window provides you with a separate view of the files in the project and can also be used to jump to specific dialog names or window elements.

RC editorThe working environment when using the RC editor

For information on how to select and show the viewers, please refer to the instructions under “How do I select a viewer?”.

The RC editor toolbar offers the following view and resizing options:

Tab. 5-13: RC editor - toolbar functionsRC editor – toolbar functions

 

How do I group and edit multiple window elements?

1 Click on the first window element you want to add to the group.

The element is highlighted with blue resizing handles.

2 Press and hold the CTRL key.

3 Add other elements to the group by clicking on them.

Window elements grouped in this way are indicated by the presence of resizing handles. If, for example, the Same width and height command is selected, the last window element added to the group determines the size of all the elements in the group. This element can be identified by the blue resizing handles. The other elements are indicated by white resizing handles:

Grouping window elements in the RC editorGrouping window elements in the RC editor

If you press the SHIFT key, instead of the CTRL key as described in point 2, the first element selected will determine the dimension in question for all the elements in the group. This element can be identified by the blue resizing handles.

4 Now select the desired function from the RC editor toolbar to alter the size and position of the grouped window elements.

AutoResize with resource DLLs on WPF basis

If in resource DLLs on WPF basis the automatic size adjustment of UI elements (AutoResize) was set, this is also taken over for the localisation and display in the RC editor, i. e. the size of the elements is automatically adjusted to the text lenght. The circumstance that the height and width of elements cannot be replaced by user-defined values, is in this case volitional.

——————————————————————————–

How do I handle a translation project in the RC editor?

1 Open or unpack the project.

2 Move the mouse pointer over the resource bar and select the File navigation window from the context menu.

Transit shows the File navigation window.

3 If necessary, also call up the RC editor window and the Markup window using the method described in point 2. If you often work on projects containing binary resource files, it is recommended that you select the appropriate user role or set up a window layout which is suited to this purpose.

4 In the File navigation window, double click on the binary resource file you would like to edit. Please note that this is the only way to individually select window elements. Opening language files via the ribbon bar or the Quick Access Toolbar displays the first segment of the opened file in the Transit editor.

Transit opens the selected language file in the Transit editor.

5 Translate the text.

– If the length restriction is exceeded, the text in the segment is highlighted in light and dark red. The section of the text highlighted in dark red is the part which surpasses the length restriction .

– If it is necessary to change the position or size of window elements, proceed as described in the section “How do I group and edit multiple window elements?”.

– The process for handling and inserting accelerator keys is the same as that used for handling markups.

Example of inserting accelerator keys during translation:

The source-language term Abbrechen has been translated with Cancel. Instead of the letter A which is used in the source language, in the target language, accelerator key C for Cancel is used. Place the cursor to the left of the letter C and then press CTRL+1 to assign the accelerator key C to the Cancel command:

Accelerator keys in projects containing binary resource filesAccelerator keys in projects containing binary resource files

The accelerator key is indicated by a superscripted 1 to the left of the selected letter. In addition, the Markup window indicates which letters have already been used as accelerators in the translation of the current window or menu. This information in the Markup window is only for information purposes. After your translation is complete, you can carry out a check for unassigned accelerator keys via markup mode or format check. The check for accelerators which have been assigned more than once can only be carried out via the format check.

Using the shortcut CTRL+SHIFT+ you can define accelerator keys in the target language which have no equivalent in the source language. This may be useful if an accelerator is missing in the source language, but needs to be inserted for the target language.

6 Continue with the process described under point 5 until you have finalised the translation.

keyboard-2

Using Machine Translation with STAR Transit

keyboard-2

Machine Translation and Transit NXT

The latest version of STAR Transit integrates with a number of Machine Translation Systems. Here’s how to make your translation faster.

1. Overview

Machine Translation (MT) systems can be used when working with Transit.

Concerning MT support, Transit strictly distinguishes between the following systems:

  •  Customer-specific MT systems

In Transit, customer-specific, specially trained MT systems are used exclusively for machine translations during the import of project files. Therefore, they are referred to as Import MT.

The project-specific settings for the Import MT are specified by the client or project manager on the Machine translation tab of the Project settings window .

Import MT suggestions are displayed to you as translator in the fuzzy window, together with the fuzzy matches that may exist.

  •  Unspecific online translation services (GoogleTranslate, iTranslate4eu)

Machine translations by online services are supported only via the Transit editor. The translator needs to request them explicitly for individual segments (see section 4. “Manually requesting a machine translation”). Therefore, they are referred to as Editor MT.

The settings for Editor MT are set by the translator using the Machine translation option of the user preferences.

 

2. User preferences for Editor MT

In the user preferences you can specify – independent of a project – if you want to use Editor MT. It allows you to manually or automatically request MT suggestions from online providers via the Transit editor.

How do I configure the user preferences for Editor MT?

1- Select Transit button | User preferences.

Transit displays the User preferences window.

2- Select the Machine translation option.

Transit displays the user preferences for the Machine translation option:

User preferences group, Machine translation screenUser preferences group, Machine translation screen

3- Specify the desired settings:

Allow Editor MT (request MT suggestions via context menu) – Here you can turn the use if Editor MT on or off. It allows you to request MT suggestions using the context menu of the Transit editor.

Ask before data is sent

Here you specify when Transit should ask prompt you to confirm explicitly to send data to the MT system:

Never, Once per project or Every time

In the overview below all MT systems supported for use in the Transit editor are listed.

– The Status column displays whether the respective MT system can be used or not:

OK – The MT system can be used.

not configured – The MT system needs to be configured, i. e. the API key must be entered.

Button 40– Transit displays a window allowing you to enter the API key for using the respective MT system.

– In the Use column, you can turn the use of an MT system on and off.

Transit can only use one MT system at the time.

Automatically request MT suggestions

Here you can turn on and off if Transit should automatically request MT suggestions for segments for which there are only fuzzy matches at a low quality:

Only for segments with fuzzy matches lower than (%) – Here you specify the quality of the fuzzy matches (in percent) below which Transit should automatically request a machine translation for a segment.

Only for segments with at least (words) – Here you specify the quality of the fuzzy matches (in percent) below which Transit should automatically request an MRT suggestions for a segment.

Only for segments with not more than (words) – Here you can specify that the segments should have a specified minimum length (i.e. segments that are too short are not sent).

Ask before data is automatically sent – Here you specify when Transit should ask prompt you to confirm explicitly to send data automatically to the MT system:

Never or Once per project

 

attentionSTAR/Transit has no influence on privacy policies, costs and quality!

For machine translation, if requested by the user/customer, the texts and contents that are to be translated are transferred to the machine translation (MT) system and may be transferred to the provider of the MT system. STAR has no influence on the quality of the machine translation when the data is processed and translated externally in this way. No guarantee shall be provided for the correctness or completeness of such translations.

STAR points out that the Internet is not considered to be a secure environment and data that is transferred online may be accessible by unauthorised third parties. STAR shall accept no liability for the security of any data that is transferred online. STAR shall be excluded from any liability for losses or damage of any kind that result from the transfer of data that is to be translated to the MT system or from the use of the MT system.

Further processing and/or saving the data that is to be translated in the external MT system is not under the control of STAR. From the moment that the data is transferred to the MT system, STAR shall not be responsible for compliance with data protection regulations nor for compliance with confidentiality agreements.

Machine translation may be a paid service that is offered by the machine translation system provider. Costs may be incurred through the use of machine translation. STAR does not have any influence on the amount or billing of these costs.

3. Entering the API key for the MT system

To be able to use an online translation service or MT system from Transit, you need to enter an API key:

Entering the API keyEntering the API key

This API key you obtain from the respective provider.

Via the Check API key when closing the dialog option, you can check immediately if the API key is correct

 

4. Manually requesting a machine translation

What you should know here

Transit displays the translation suggestion of an Editor MT system in the Source Fuzzy window as follows:

Editor MT suggestionEditor MT suggestion

If the segment for which a machine translation has been requested contains markups, the display is extended by a row:

Editor MT suggestion for a segment containing markupsEditor MT suggestion for a segment containing markups

In the additional row, Transit displays if the segment text has been transferred to the MT system with or without markups.

If the respective MT system does not support the processing of markups, Transit automatically transfers the segment text without markups. In this case you will have to insert the markups after accepting the MT suggestion for your translation.

How do I manually request a machine translation?

1 In the target-language window of the Transit editor, right-click on the current segment.

Transit displays the context window of the target-language window.

2 In the context menu, select the Request machine translation entry.

If fuzzy matches exist for the segment, Transit displays the translation suggestion of the MT system at the top of the Source Fuzzy window. This way the MT suggestion can be easily compared with the fuzzy match of the highest quality.

Just like a fuzzy match, you can edit the MT suggestion and accept it for your translation.

 

5. Import MT suggestions in the fuzzy window

Transit displays the translation suggestion of an Import MT system in the Source Fuzzy window as follows:

Import MT suggestionImport MT suggestion

If the segment contains markups, the display is extended by a row:

Import MT suggestion for a segment containing markupsImport MT suggestion for a segment containing markups

In the additional row, Transit displays if the segment text has been transferred to the MT system with or without markups.

If the respective MT system does not support the processing of markups, Transit automatically transfers the segment text without markups. In this case you will have to insert the markups after accepting the MT suggestion for your translation.

Just like a fuzzy match, you can edit the MT suggestion and accept it for your translation.

transitnxt3

Translation Memory System – Introduction.

Transit NXT is STAR’s translation memory system for professional translators. Crammed with features and benefits for you – it can make you more productive and profitable with its state of the art translation editor and tools. This 38 minute video shows how Transit can help you create a project, built and use dictonaries and check your translation quality.

Transit NXT – Translation Technology for Translators Introduction from Damian Scattergood on Vimeo.

Translation technology helps real human translators create consistent accurate content. Using translation memory and terminology management systems means you only ever have to translate content once. This ensures that you get the most from your translation budgets. STAR has been developing translation technology for over 25 years, so your linguistic assets are in safe hands.

Transit is used by Professional Translators and Language Services Providers. It can be usef standalone or within the context of a global information management system. You can edit a number of native file formats including Adobe Indesign and the Microsoft Offie Suite (Word, Excel, Powerpoint). Transit can also edit and translate software file formats such as XML, HTML, CSV, JSP and many more. This demo shows how you can create projects, translate and proofread them all in the same single sourced environment.

Are you interested in using the STAR Transit NXT system for your translation projects or translation department?

https://shop.star-group.net/

Windows 10 and Transit NXT

Upgrading to Windows 10 and Transit NXT

Windows 10 and Transit NXT

Using Transit NXT and thinking of upgrading to Windows 10? Here’s what to do…

Upgrade to Windows 10, keep Transit NXT

When you upgrade your computer to Windows 10, please consider the following:

  • keep personal files and apps (selected by default)
  • keep personal files only
  • do nothing

During the upgrade process, Windows OS will display a window prompting you to choose what you want to keep.

It is absolutely necessary that you select “Keep personal files and apps” – already selected by default.

Otherwise Windows will remove your Transit NXT installation (and its activation and all other programs) from your computer, prior to installation.

Upgrade auf MS Windows 10

Beachten Sie Folgendes, wenn Sie ein Upgrade Ihres Computers auf Windows 10 durchführen:

Während des Upgrade-Prozesses, zeigt Windows ggf. ein Fenster an, in dem Sie auswählen sollen, was Sie beibehalten möchten.

  • Persönliche Dateien und Apps beibehalten (standardmäßig ausgewählt)
  • Nur persönliche Dateien beibehalten
  • Nichts

Es ist unbedingt notwendig, dass Sie die Einstellung “Persönliche Dateien und Apps beibehalten” ausgewählt lassen!

Anderenfalls entfernt Windows Ihre Transit NXT-Installation und Aktivierung (und alle anderen Programme) von Ihrem Computer, bevor Windows 10 installiert wird.

The STAR Team

Image: Windows logo, copyright of Microsoft

STAR Translation Services logo

New Languages Supported in Transit NXT Service Pack 9

Transit NXT Service Pack 9
Transit NXT Service Pack 9 ushers new languages to its arsenal

New Languages Supported in SP9

The new Transit NXT Service Pack 9 ushered in loads of new features.

As the localization industry grows, we grow along with it and enhance Transit NXT each time to suit the requirements of the industry.

One of the most important aspects of translation is being able to translate projects to and from one’s language; not just for the translator but the project manager too. SP9 packs loads of new languages in which you can now work. Gone are the days that you no longer have to depend on variants if your language was not supported; start working in one of the new languages now supported by Transit.

Eight Additional Languages

Transit supports eight additional languages and language variants. Furthermore, both Transit NXT and TermStar support more than 200 languages and cover all relevant markets in the target languages.

Asian languages: Tajik, Pashto and Dari (Persian); Maori (New Zealand); Spanish (USA) and International Spanish variants; and two other European languages are all the latest additions to Transit NXT SP9.

Language selection drop-down menu in Transit NXT
Screenshot of the source language [selection] drop-down menu in Transit.

New Asian Languages in SP9

Tajik (تاجیکی)
Tajik or Tajiki, also called Tajiki Persian is a variety of Persian spoken in Tajikistan and Uzbekistan.
Pashto (پښتو)
Pashto belongs to the south-eastern Iranian branch of Indo-Iranian languages spoken in Afghanistan, Pakistan and Iran.
Dari (دری‎‎)
Dari (Persian) is the variety of the Persian language spoken in Afghanistan.

New European Languages in SP9

Breton
Breton (Breton: Breizh; French: Bretagne) is a Celtic language spoken in Brittany, France.
Corsican
Spoken in the islands of Corsica (France) and northern Sardinia (Italy), Corsican is a Romance language of the Italo-Dalmatian subfamily.

Introducing Maori for SP9

Maori
An Eastern Polynesian language spoken by the Māori people – the indigenous population of New Zealand – Māori is one of the official languages of New Zealand since 1987.

Spanish Worldwide

Spanish (USA)
One of the most widely spoken language has a number of variants – Spanish (USA) being one.
International Spanish
Use Spanish (International) for standardizing particular Spanish language projects.

The STAR Team

STAR Group Donates Transit to Universities in Ho Chi Minh City

STAR Group Donates Transit NXT to Universities in Ho Chi Minh City, Vietnam

The STAR Group donates Transit to two universities in Ho Chi Minh City, Vietnam. They will receive Transit NXT as part of their CAT software tools; the University of Social Sciences and Humanities and Hoa Sen University.

Josef Zibung, president of the STAR Group in Ramsen, Switzerland paid visit to Ho Chi Minh City to present the STAR Transit NXT suite.

Since STAR also operates in Vietnam, they will be providing full support to the faculties involved in implementing training and use of Transit to students.

We provide Vietnamese translation of websites, brochures and documents to all our customers.

The STAR Team

Translation Support for InDesign CC 2014

translation support for indesign

Transit NXT and InDesign CC 2014

Now with Translation Support for InDesign CC

You can now translate Adobe InDesign CC 2014 files in TransitNXT!

For data exchange with Transit, there are new InDesign Gate plug-ins available for InDesign CC 2014 (Mac and Windows). Furthermore, you can now download and install enhanced InDesign Gate plug-ins for InDesign CS 2 to CS 6 and InDesign CC.

The plug-ins for your InDesign version can be found on our STAR Group website in the Download » Transit and TermStar NXT » Accessories section.

There you can also find the latest documentation on installing the InDesign Gate and sharing data with Transit.

Give us a call to discuss your next project.

The STAR Team

Transit NXT: Service Pack 2 Release

Transit NXT Service Pack 2 is now available for download from STAR.

Service Pack 2 contains the following new feature and solved issues:

Support for DITA XML

A standard file type “XML_DITA” for DITA format is now available.
DITA is a standardized document format for describing information types.

Feature updates:

Transit NXT
– Spellchecker:  improved spellchecking functionality and procedures
– Arabic:  improved format check, improved segment display
– Markup:  improved markups display, improved search within markups, markup assignment in virtually joined segments
– Improved processing of Powerpoint animations
– Improved processing of binary resource files
– Reference material: improved maintenance and organisation of reference material

TermStar NXT
– Statistics:  improved field statistics
– Import/Export:  improved import/export functionality

For further information contact your local STAR sales office.
Ireland and UK call Dublin : +353 1 8365614  of visit www.star-ts.com

Transit and TermStar XV Service Pack 24 Released

Service Pack 24 Released, Transit XV and TermStar XV

We would like to announce that Service Pack 24 is now available for download on our ftp-server and on our Website.

Detailed information on new features and improvements implemented with this Service Pack can be found in the readmetr.htm and readmets.htm
Apart from bug fixes Service Pack 24 contains the following new features (for more details please refer to the Transit readme file):

New features

  • Transit NXT Project Support

With Service Pack 24, receiving, processing, and sending of Transit NXT projects will be enabled. Additionally, a NXT-XV conversion add-on has to be installed.

The add-on is available on the Transit NXT installation CD.

  • TermStar filter functionality enhancement
  • TermStar import enhancement

For more information on the enhancements, please refer to the readmetr.htm file

Important Information

The update for TermStar is integrated in trsp24.exe which you can find in the Transit directory. An additional installation of the updates of the TermStar directory is not necessary.

In Service Pack 24 all changes and improvements of the previous Service Packs are integrated.

Please proceed as follows for the installation of the Service Pack 24:

Download the files trsp24.exe and installation_sp.pdf. Installation instructions are included in the pdf file. Detailed information on the improvements can be found in the files readmetr.htm and readmets.htm.

Please proceed as follows for the installation of the help file…

  1. Install Service Pack 24 and then the help file
  2. For installation instructions please refer to the file installation_help.pdf

The aforementioned files can be downloaded from the following… Transit Service Packs XV.

The STAR Team