The translation category features all blog posts related to the world of translation. Read posts on multilingual translation and translation services. Subscribe to us.

Transit NXT

Creating a Project | Transit Training

Transit NXT

Creating a Project in Transit

To translate a document using Transit, you must first create a project. A wizard helps you to do this by guiding you step-by-step through the functions so you cannot forget any settings.

Selecting Project | Administration | Create takes you to the Create new project window:

Create new project windowCreate new project window

You have the following options when creating a project:

  • You can create a new project. There are two options available for this:

– The option Based on template allows you to select from a list of user-defined project templates and adapt these to suit your current project. Please refer to section 5. “Creating a new project template” for more detailed information on creating a new project template.

– The option New project from scratch lets you create a new project from scratch.

Please refer to section 2. “Creating a new project” for more information on this topic.

  • You can create a follow-up project.

Using the option Based on project, you can create a follow-up project. With this option, Transit suggests the settings of an existing project so you only have to change the settings which differentiate the new project from the old project. Please refer to section 3 “Create a new project based on an existing project” for more information on this topic.

  • You can create an alignment project.

If you have an original and one or more translated versions of a document, with the option Alignment project, Transit gives you the option to create reference material from these original documents, which you can then use for translation projects in Transit. You also have the option of creating an alignment project using the resource bar. You can find more detailed information about creating alignment projects in chapter 2 of the “Transit NXT Alignment Tool” manual.

Shared project with TermStar

When you create a project in Transit, this is also used by the TermStar terminology management system. The Transit project also contains all the settings which TermStar requires.

This means that if you want to use or edit terminology for a translation project, there is no need to create a separate project in TermStar.

 

2. Creating a new project

Selecting Project | Administration | Create in Transit gives the user the option to create a new project from scratch or a project based on a template.

It is also possible to select predefined default project templates using the Interfaces button in the resource bar, which you can then adapt for your project (details about this can be found in section.4 “Creating a new project via the resource bar”).

Please refer to section 3 “Create a new project based on an existing project” if you want to create a follow-up project based on an existing project.

If you wish to create a new project template, please refer to section 5 “Creating a new project template”.

Selecting and creating predefined project templates

Transit provides you with project templates that are specific to the document type, which means that you do not have to make certain settings when you create a new project. Alternatively, you can also create your own project template. This is achieved either by taking an existing project template and amending it accordingly, or else by creating an entirely new project template from scratch. Please refer to section “Creating a new project template” for more detailed information on this topic.

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

How do I create a new project?

1 Select Project | Administration | Create.

Transit displays the Create new project window:

Create new project windowCreate new project window

2 To create a new project, select New project from scratch. Click Next to confirm the option selected.

Transit displays the Administration window:

Administration windowAdministration window

3 Specify the administrative information.

Project name – Enter the name of the project here. When choosing a name for the project, ensure that it does not contain any invalid characters. If an invalid character is used, the following error message appears:

Invalid filename messageInvalid filename message

The wildcards ‘?’ and ’*’ are also not allowed. If one of these characters is used, the following error message appears:

Wildcards error messageWildcards error message

Scope – Select the scope to which the project should be assigned:
Global, User (user-related) or Customer (customer-related).

– If you have selected Customer from the Scope list, select the desired customer from the Customer list.

– Click New customer to create a new customer. Transit displays the Create new customer window:

Create new customer windowCreate new customer window

Enter the name of the customer in the Customer field. Transit automatically copies the name into the Customer data folder field. Transit saves customer-specific settings to this folder.

Click Create customer to confirm the information entered for the new customer. Transit displays the Administration window again. You can now select the new customer from the Customer list.

– You can enter a comment on your project in the Project comment section.

– In the Project status section you can enter remarks on the status of the project, such as ‘Imported’, ‘Statistics created’, ‘Imported and checked before translation’, ‘Sent to translator’, etc.

Click Next to confirm the information entered in the Administration window.

Transit displays the Languages window. If you are creating a new project from scratch, the source and target language fields will be empty, because this option does not set predefined languages:

Languages windowLanguages window

4 Specify the source and target language(s) for the project.

Source language – Select the language you require from the list.

Current target language – Select the language you require from the list.

You can only select languages specified as ‘Project target languages’. When creating a new project, it is first necessary to add the required languages in the Project target languages section.

Project target languages – Transit displays all the target languages for the project in the Project target languages section.

To add a target language, click on Add. Transit displays the Add target language(s) window:

Add target language(s) windowAdd target language(s) window

Select one or more languages which you want to add to the project as target languages. To select several target languages, press and hold the CTRL key and then click on the desired languages in the list. They appear highlighted. Confirm your selection with OK.

Transit displays the Languages window again with the target languages added. You now have the chance, if required, to select a different language as your current target language:

Languages window with target languages added [spacer] Languages window with target languages added

– To remove a target language from the project, select the language in the Project target languages section and click Remove.

This does not cause Transit to delete the files for the removed target language, it just means that the language is no longer used in this project.

Click Next to confirm your settings in the Languages window.

Transit displays the Folders window with the drive and path of the working folder:

Folders windowFolders window

5 Specify the working folder which Transit should use to save all the files for this project.

Transit initially creates the appropriate folder as a subfolder of Projects in your Transit installation folder. This path for this folder is displayed in the Folders window.

– If you would like to store the project in a different folder, select the Browse option.

Transit displays the Select working folder window:

Select working folder windowSelect working folder window

– Select the desired files and confirm the selection by clicking Open.

Transit displays the Folders window again.

By default, Transit creates a subfolder of the project folder to serve as the export folder (e. g. .\EXPORT\ENG). However, it is also possible to select a different folder.

– Under Export folders for project target languages, click on Change.

Transit displays the Export folder window.

– Click on Browse.

Transit displays the Select export folder window.

– Select the desired folder and confirm by clicking Open.

Transit displays the path for the new folder in the Export folder window.

– Confirm your selection by clicking OK.

Click Next to confirm the information entered in the Folders window.

Transit displays the File type window:

File type windowFile type window

6 The window initially displays the default file type. You can now specify the type of file that you want to import.

– If you want to import a different file type, select the desired file type from the File type list.

To limit the choice of available options (for example, because you are searching for particular file types or for data for a particular customer), you can restrict the list using the Preselection (optional) section.

Font mapping lets you assign particular fonts to the target-language document which is to be created.

– Click on Options to configure additional settings for your particular file type (not available for all XML, HTML, SGML, Text and GRIPS file types).

Transit displays the File type settings window.

Specify the settings required and confirm the settings by clicking OK.

Please refer to the 3.6.8 “Additional file type settings” section and the “Tips & Tricks for All File Formats” manual for information on other settings for specific file types.

Click Next to confirm the settings made in the File type window.

Transit displays the Files window:

Files windowFiles window

7 Specify which files you want to import and translate in Transit.

– If you wish to select individual files, click Select files.

Transit displays the Select original files window. Select the desired files and confirm the selection by clicking Open.

– If you wish to select all the files in a folder, click Select folder.

Transit displays the Select folder with original files window. Select the desired folder.

Select Include subfolders if you want Transit to import the contents of all subfolders as well.

Confirm your selection by clicking Open.

– If you want to remove a file or a folder from the project, select the file/folder and click Remove.

– If you want to assign a working name to a file, select the file and click Working name.

Transit displays the Working name window:

Working name windowWorking name window

Enter the desired working name into the Working name field. Confirm your entry with OK.

– From the Display mode list, select how Transit should display the file names in the Project files section:

Working name – Transit displays the working name.

Original name – Transit displays the path and original name of the file.

– From the Display list, select the files which Transit should display in the Project files section.

Transit then indicates in the Project files section whether the corresponding language files already exist.

If the files do not yet exist, it may be that they still need to be imported for the language selected. If you are creating a new project, the source and target-language files will not usually be available, as you have not yet carried out an import.

– If you want to specify specific attribute values for the added project files, click Attributes.

By doing so, you provide the project files with additional information that you can use later on – for importing them into a TM Container and exporting them as TMX files.

For further information on this please refer to the “Transit NXT – Managing and using TM Containers” manual.

Click Next to confirm the settings made in the Files window.

Transit displays the Reference material window:

Reference material windowReference material window

8 Specify which files you want to use as reference material

– To select a project as reference material, click on Add projects.

Transit displays the Project browser window, which lists all existing projects. Select the desired project.

Confirm your selection with OK.

– To select all the files in a folder, click Add folder.

Transit displays the Select reference folder window. Select the desired folder. If the folder contains subfolders, they are automatically included in the selection.

Confirm your selection by clicking Open.

– To add individual files as reference material, click on Add files.

Transit displays the Select reference files window. Select the desired files and confirm the selection by clicking Open.

– To add a TM Container or TM Filter as reference material, click on Add TM Container.

Transit displays the Add TM Container window. Select the desired TM Container or TM Filter and confirm by clicking Select.

 

TM Container function must be activated

The Add TM Container button for adding a TM Container or TM Filter as reference material is only available if the TM Container function has been activated for your licence.

If you have any questions on this, please contact your local STAR office.

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

– If you want to remove a project, folder or file from the list of already selected reference material, select the corresponding entry and click Remove reference.

Click Next to confirm the settings made in the Reference material window.

Transit displays the Dictionaries window:

Dictionaries window [spacer] Dictionaries window

9 From the Current dictionary list, select the dictionary to which Transit should add any new terminology.

In doing so, you can only select a dictionary which has been specified as a project dictionary. If the required dictionary is not contained in the list, you must first add it to the Project dictionaries section.

To assign a dictionary to the project, click on Add in the Project dictionaries section.

Transit displays the Add dictionaries window:

Add dictionaries windowAdd dictionaries window

In the Select dictionary section Transit displays the dictionaries that you can access. In the right column Transit displays the name of the database in which the respective dictionary is saved.

By clicking on the column header Dictionary name and Database name you can sort the dictionaries or the databases alphabetically ascending or descending for a better overview.

In the Project dictionaries section Transit displays the dictionaries that are already defined as project dictionaries.

– In the Select dictionary section, select one or more dictionaries which you want to add to the project. Confirm your selection with OK.

Transit displays the Dictionaries window again with the dictionaries added. If necessary, you can now select a different current dictionary.

– To remove a dictionary from the project, select the dictionary in the Project dictionaries section and click Remove.

Transit will not delete the dictionary data from the database when a dictionary is removed, it will merely no longer use the dictionary in this project.

Click Next to confirm the settings made in the Dictionaries window.

Transit displays the Summary window. This displays all the settings which you have previously specified for the current project:

Summary windowSummary window

10 Check your settings or specify additional, special settings:

– Click on Back if you want to change a setting.

– If you want to make additional special settings for segmentation, report settings, format check, default values, reference material, pretranslation or extracts, click Additional options.

Transit displays the Advanced project settings window, which contains the following tabs:

33 Advanced project settings window

Segmentation – Options for splitting the text into individual sections (segments). Please refer to section  “’Segmentation’ project settings” for more detailed information.

Report settings – Settings for the Report Manager for analysing and invoicing your translation project. Please refer to section  “’Report settings’ project settings” for more detailed information.

Format check – Options for verifying the consistency of formatting information, the representation of numbers and for detecting missing or redundant spaces. Please refer to section  “’Format check’ project setting” for more detailed information.

Default values – Default values for dictionary entries made while working on the project. Please refer to section  “’Default values’ project settings” for more detailed information.

Pretranslation – Settings for pretranslation based on the reference material. Please refer to section “’Pretranslation’ project settings” for more detailed information.

Extracts – Settings for the creation of reference and translation extracts. Please refer to section“’Extracts’ project settings” for more detailed information.

Machine translation – Generating translation suggestions using MT systems during import. Please refer to section  “’Machine translation’ project settings”.

Configure the desired settings and confirm them by clicking OK.

Please refer to section  “Project settings” for more information on this topic.

Once you have checked all the settings, confirm them by clicking Finish.

Transit creates the project with all the files and folders.

Once you have created a project, the next step generally is to import the files. For this reason, Transit displays the following message:
Project created successfully. Do you want to start the import process now?

11 Decide whether you want to import the files now or later:

– Click Yes if you want to import the files straight away.

Transit displays the Import project window.

– Click No if you want to import the files at a later stage.

You can carry out the import process at a later stage. However, you must import the files before you can start the translation.

 

3. Create a new project based on an existing project

If you choose to create a project based on an existing project, Transit suggests the existing settings from this project so you only have to modify the options which differentiate the new project from the old one. Please refer to section 2 “Creating a new project” if you would instead like to create a new project based on the default Transit settings.

How do I create a new project based on an existing project?

1 Select Project | Administration | Create.

Transit displays the Create new project window:

36Create new project window

2 To create a follow-up project, select Based on project.

3 Select the project from the list which you want to use as the basis for your new project.

Click Next to confirm the option selected.

Transit displays the Administration window:

Administration windowAdministration window

As the project name, Transit suggests the name of the old project with 1 appended to the end. The language pairs and reference material from the old project are set as the reference material, the old import files are discarded. All other settings from the old project remain unaltered.

4 Accept the suggested settings or change the settings for the new project. To do so, proceed as when creating a new project (see section 2 “Creating a new project” from step 4 onwards).

 

4. Creating a new project via the resource bar

The Transit resource bar contains a list of project templates in which important settings have already been predefined, allowing you to create a project quickly. A project created via the resource bar differs from a project created from scratch in the following respects:

  • Project folder: Transit automatically saves the project to C:\Program Files\Transit_NXT\projects\. For the project name, Transit uses the name you have entered under Project name in the Administration window.
  • File type: The file type is preselected when you choose the project template.
  • Dictionary: The project wizard skips the Dictionaries window when you create a project via the resource bar.

Clicking the Additional options button in the Summary window takes you to the advanced project settings. Here, you can make further project settings before you finally create the project.

You can also change the settings at a later stage via Project | Administration | Settings.

Please refer to section 2 “Creating a new project” if you would instead like to create a new project based on the default Transit settings.

How do I create a project via the resource bar?

1 Click the Interfaces button on the resource bar.

2 Select the desired file type from the list (e. g. Office -> PowerPoint).

Transit displays the Administration window:

Administration windowAdministration window

3 Specify the administrative information and proceed in the same way as when creating a new project.

File types which can be imported in Transit

The following table lists the file-type specific templates which Transit offers for project creation:Templates for project creationTemplates for project creation

These options are also available from the ribbon bar by selecting Project | Administration | Create | Based on template.

5. Creating a new project template

You can also define project templates yourself in Transit according to your specific requirements. When you create a new project template, you can either create a template from scratch or base it on one of the default project templates that is available in Transit when you create a new project either via the ribbon bar (Project | Administration | Create) or via the resource bar.

How do I create a project template via the ribbon bar?

1 Select Project | Template | Create.

Transit displays the Create project template window:

Create project template windowCreate project template window

2 Select one of the following options to create a new project template:

Create new template – Select this option if you want to create a new template from scratch.

Create new template based on template – Select this option if you want to create a new template that is based on one of the default project templates. Select the required default project template from the list.

Confirm your selection by clicking OK.

Transit displays the Save project template as window:

ave project template as windowSave project template as window

3 Specify how the new project template should be saved:

File name – Enter the name of the project template here.

Scope – Select the scope to which the project template should be assigned: Global, User (user-related) or Customer (customer-related).

Click Save to confirm the information specified.

Transit displays the Project-template settings window:

Project-template settings windowProject-template settings window

The name of the project template and the scope in brackets (e. g. Global) are also shown in the titlebar.

In addition to the project settings described in section 3.6, the Project-template settings window also contains the Wizard tab:

Project-template settings window, Wizard tabProject-template settings window, Wizard tab

4 In the Wizard tab, specify which steps should be considered when a new project is being created using this project template. The following steps (project settings) can be selected:

Languages

– Folders

– File type

– Files

– Reference material

– Dictionaries

5 Make the required settings in the other tabs.

Confirm the settings in each tab with Apply. Click OK to conclude the project-template creation process.

6. Deleting a project template

User-defined project templates can also be deleted. The project templates supplied with Transit, which are specific to particular document types, cannot be deleted.

How do I delete a project template via the ribbon bar?

1 Select Project | Template | Delete.

Transit displays the Delete project template window:

Delete project template windowDelete project template window

The list of the available project templates only displays the user-defined templates. The Delete button is greyed-out until a template is selected.

2 Select the project template which is to be deleted.

3 Click Delete.

7. Changing the default settings for new projects

If you create a new project from scratch, Transit suggests various default settings (e.g. for the source and target language; see section .2 “Creating a new project”).

You can change the default settings suggested by Transit for new projects, so that they match the requirements of your projects as closely as possible. This means that less changes will be necessary when creating a new project.

The default settings come from the project default, stored under scope Global. To change the settings, open the project default, alter the project settings and save it again under the same name.

How do I change the default settings?

1 Open the project default, which is stored under the scope Global.

– To do this, select Project | Open.

Transit opens the Project browser window.

– Select the project default from the list.

If Transit displays several projects of this name, select the default project stored under the Global scope.

– Confirm your selection by clicking OK.

Transit opens the default project.

2 Check the project settings and alter them as necessary.

– Select Project | Administration | Settings.

Transit displays the Project settings: default (Global) window. On the tabs, Transit displays the project settings which are suggested when a new project is created.

– Alter these project settings as necessary so that Transit will suggest these modified settings for future projects.

Only alter those settings which are useful as suggestions for all new projects (e.g. for the source and target language).

– Do not change any settings which usually differ from one project to the next (e.g. files, reference material, dictionaries, default values, etc.).

You will find information on the project settings in section 3.6 “Project settings”.

– Confirm the changes made with OK.

3 Save the modified project default.

– Select Project | Save as.

Transit displays the Save project window.

– Select the project default from the list.

If Transit displays several projects of this name, select the default project stored under the Global scope.

– Click Save to confirm your choice.

Transit displays a message informing you that the project already exists.

4 Click OK to confirm that you want to overwrite the existing project.

Transit saves the default project and its settings are the immediately available to act as suggested settings for new projects.

Transit NXT

Translating Text | Transit Training

Transit NXT

Translating text

If the language pair is open, the text appears in the editor window in two panes – green for the source language and red for the target language.

When you begin translation, the majority of the text in the target-language pane is usually not translated and is therefore still in the source language. If Transit has found matching segments in the reference material during the import process, these segments will already have been pretranslated.

In the target language window, you now can overwrite the text which is still to be translated. Transit shows the corresponding source language text in the source language window.

During translation, you have the choice between working using the ribbon bar or using keyboard shortcuts:

50Commands in the Translate group of the Processing tab and their associated keyboard shortcuts

How do I translate a text in the Transit editor?

1 In the target-language pane place the cursor in front of the text you wish to translate.

2 Enter your translation and delete the old text.

Transit offers additional options for this task. Clicking on the arrow at the bottom of the Confirm button opens a list containing the following options:

Options for the Confirm buttonOptions for the Confirm button

Transit indicates which options are currently selected with a checkmark to the left of each selected option. Should you wish to deselect an option, simply remove the respective checkmark by clicking on the option in question.

Delete to end of segment – Here you can specify whether the old text should be deleted automatically when the translation is confirmed.

The Delete to end of segment option is the default. If it is selected, when you click on Confirm or press the shortcut ALT+INS, Transit will automatically delete the remaining, red-underlined source text from the segment.

Check spaces – Here you can specify whether Transit should check for a space at the end of the source and target-language segment when the translation is confirmed and display respective messages in case of inconsistencies.

Check end punctuation – Here you can specify whether Transit should check for punctuation signs at the end of the source and target-language segment when the translation is confirmed and display respective messages in case of inconsistencies.

Empty next segment – Here you can specify whether Transit should empty of contents of the respective following segment when the translation is confirmed.

If the Empty next segment option is selected, when you click on Confirm or press the shortcut ALT+INS, Transit will automatically empty the following target-language segment. Selecting this option deselects the Delete to end of segment option.

3 Transit supports you in your translation work with the following functions:

– If Transit finds an entry in the dictionary for a word in the segment, this word is highlighted in yellow in the editor. In addition, Transit displays the entry in the Terminology window.

– Press the shortcut ALT + ENTER if you want Transit to display a suggested translation from the fuzzy index for this segment.

Transit displays the results in one of the fuzzy-window types, either the fixed fuzzy window or the bubble window.

– If Transit has pretranslated the segment and given it the status Check pretranslation, it uses update markers to indicate which part of the text you should check. Please refer to section 5.6 “Markups in the Transit editor” for more detailed information.

– You may want to format the text manually in some instances, (e.g. mark as underlined or in italics).

– If there are markups in the segment, it may be necessary to reassign, copy or delete them.

– You can make comments on segments or search for comments.

– If you want to join two sentences in the source language to make one translated sentence in the target language.

4 When you are finished translating the segment, confirm the translation by pressing the shortcut ALT+INS.

Transit changes the status of the segment to Translated.

– It is also possible to assign this status by clicking Confirm under Processing | Translate.

– Transit moves the cursor to the next segment to be processed.

In doing so, Transit bypasses all the segments which have already been translated or which do not have to be translated.

– Transit automatically searches the fuzzy index for fuzzy matches for the next segment to be translated.

5 Press the CTRL+ALT+BACKSPACE shortcut if you wish to undo the translation of a segment.

Transit replaces the text translated by you or Transit with the text of the source language. This means you can also undo translations for segments which Transit automatically pretranslated during the import.

6 Continue translating as explained from point 1 onwards.

Do not forget to save the language pair when you are finished translating it.

Quality assurance after translation

To guarantee top quality of your translation, we recommend that the following items are checked after translation:

  • Spellcheck

As with every good word processing program, you can use the spellcheck function in Transit to check your spelling. You can use dictionaries and/or reference material for spellchecking

  •  Checking terminology

Using this function, you can check whether the terminology from the project dictionaries has been used in the translation.

  • Checking markups

Markup mode enables you to establish whether the markups in the source and target languages are consistent.

  • Statuses for the translation report

Using segment status, check whether the text is completely translated.

Please refer to section 6 “Quality assurance” for more information on this topic.

 

1. Update markers in the Transit editor

Overview

If a text differs from the reference text only in terms of numbers and markups, Transit accepts the text from the reference material and the markups and numbers from the file to be translated. Such segments are assigned the status Check pretranslation. The modified elements are highlighted in the Transit editor by so-called ‘update markers’:

Example of the appearance of update markers in the Transit editorExample of the appearance of update markers in the Transit editor

This helps you to quickly see what you need to check and potentially change. Transit also displays the update markers in the Source fuzzy window . The display in the Source fuzzy window makes it possible to see where the differences lie between the new segment and the reference segment. To call up or update the Source fuzzy window, press the shortcut CTRL+ENTER.

Example of the appearance of update markers in the Transit editor and in the Source fuzzy windowExample of the appearance of update markers in the Transit editor and in the Source fuzzy window

In the example in figure 5-11, the numbers in the active segment have been changed and the formatting has been changed from bold italic in the reference segment to just italic (for more details on the information given in the fuzzy windows, see section 5.4 “Dual Fuzzy windows”). Transit has carried over the translation from the reference segment and updated the numbers and markups according to what appears in the current segment.

Automatic update for differing numbers and markupsAutomatic update for differing numbers and markups

If the number of markups in the reference segment is lower than in the new segment which is to be translated, Transit still carries over the translation from the reference material, but adds update markers and gives the segment the status Check pretranslation. However, in this case, Transit does not automatically insert the ‘new’ markups:

Example of how Transit indicates a differing number of markups in the reference segment and the segment to be translatedExample of how Transit indicates a differing number of markups in the reference segment and the segment to be translated

In the example in the Figure 5-12, the markup for italics for the number ’37’ in the current target-language segment is not inserted automatically. This markup must either be inserted manually or when checking the text using markup mode. You can find more detailed information on this in section 5.6.4 “Inserting and copying markups during translation” and in section 6.5 “Checking markups”.

Transit automatically deletes update markers during the export phase

Transit automatically deletes the update markers if you assign a segment with the status Translated.

Transit automatically deletes the update markers when you export the project.

However, we recommend you delete the markers during translation or while checking the segments. In this way, you know which segments you have checked.

 

2. Segments in the Transit editor

Overview

During import, Transit breaks down the text into individual, easily-managed sections known as “segments”. These are the sections that you translate. These are also the sections of text which Transit searches for and replaces when it compares the text with existing translations.

Transit saves information for each segment so you can track exactly whether and how the segment was translated. Transit displays this information in the scratchpad window.

Each segment has a status which provides you with information on the stage of the translation process the segment has reached. In effect, the status is an indicator of the “quality“ of the segment. Transit can display this status in a column in the editor and also in the segment marker at the end of a segment:

Segment status: display options in the Transit editorSegment status: display options in the Transit editor

Under View | Segments, you can specify how Transit should display the segment status.

Display of the segment status in the Transit editor

Transit can display the segment status in the editor. The marker can either be displayed at the end of the segment or in the info column. How the segment status is displayed depends on which setting you have selected. In the info column, the segment status is displayed in a separate column, to the right of the segment number. The Example column in the following table shows how different segment markers appear at the end of a segment:

Displaying the segment status with the segment markerDisplaying the segment status with the segment marker

 

Changing the segment status while translating

In order for you to work efficiently and effectively with segment statuses, the status of a segment must always correspond to the last processing step taken for the segment. Transit offers you the following two options for this:

  • You can automatically update the segment status during translation by confirming the translation for a segment with the keyboard shortcut ALT+INS, which sets the segment status to Translated.
  • You can also manually assign the Translated status to a segment by selecting Processing | Translate | Assign status.

Automatically update the segment status during translation

We recommend that you ensure the segment status is automatically updated during translation. This allows you to track the course of the project and perform a statistical analysis of the translation.

 

3. Split a segment or join a segment to the next

In Transit, it is possible to split a source language segment “on the fly” during translation work at a particular position in the segment. It is also possible to join a source language segment to the next.

Splitting a segment may become necessary when Transit e. g. treats two sentences during segmentation as one segment because of a missing blank after the full stop in the original document.

Constraints of this functionality

Splitting and joining of source language segments is only possible if the project has only one target language.

The joining of source language segments works only within a paragraph. Joining segments beyond paragraph boundaries is not possible.

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

How do I split a segment?

1 In the source language segment, place the cursor at the position where the segment should be split in two.

2 Right-click to open the context menu and select the Split segment option.

Split segment optionSplit segment option

Transit splits the segment in the source language as well as the target language window at the desired position and updates the segment numbers of the following segments in both windows accordingly.

To undo the splitting, if required, follow the two steps described in “How do I join a segment to the next?”.

If you split a segment that has already been translated, the target language segment is split approximately at the same position as in the source language. Likely, you may need to slightly adapt the two resulting target language segments where necessary.

How do I join a segment to the next?

1 In the source language segment, place the cursor in the segment that should be joined to the next.

2 Right-click to open the context menu and select the Join segment to next option:

Join segment to next optionJoin segment to next option

Transit joins the desired segment in the source and target language windows to the next segment and updates the segment numbers of the following segments in both windows accordingly.

 

4. Joining segments virtually and split virtually joined segments

Transit gives you the option to virtually join segments. This may be of interest if content which is spread over two or more sentences or segments in the source language needs to be joined to become a single segment in the target language. This is predominantly the case with multilingual projects or for projects where the structure of the content is irregular (e.g. if sentences/units of meaning are interrupted by line breaks or similar).

Using the Join function, Transit can combine such segments. In Transit, segments which are ‘virtually’ joined in this way form a single unit, thus allowing the content to be translated according to requirements. However, the number of segments remains unchanged, meaning that the segmentation of all language pairs is still uniform. This function can be selected either from the ribbon bar, via Processing | Translate | Join or via a context menu from the editor (Virtual segment join).

Example:

A document in which the target language is English is being translated into German.

The sentences

‘Transit will save you money’

and

‘Transit will boost your productivity’

are to be joined in the target language (German) as follows (fig. 5-16):

‘Transit spart Ihnen Geld und steigert auch Ihre Produktivität’

Virtual segment joining: source language situationVirtual segment joining: source language situation

How do I virtually join segments?

1 Enter the translation into segment 26 and mark the segment as ‘Translated’ using ALT+INS.

2 Delete the text ‘Transit will boost your productivity’ in segment 27 and mark this segment as ‘Translated’ with ALT+INS as well:

Virtual segment joining: enter the translation in the first segmentVirtual segment joining: enter the translation in the first segment

3 Place the cursor in the segment which contains the translation (seg. 26) and select the option Virtual segment join from the context menu.

Transit joins the active segment and the following segment to become a single unit:

Virtual segment joining: segments joinedVirtual segment joining: segments joined

In the segment-number column, you can see that the joined segments are assigned the number of the first segment, but that the number of other segments and their numbering have not changed.

If necessary, to separate the joined segments again, either select Processing | Translate | Undo join or select Undo virtual segment join from the context menu in the active segment.

Virtual segment joining

This function can only be used for adjacent segments. There must not be any segments only containing markups between these segments.
Transit also treats virtually joined segments as a single unit when they are used as reference material.

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

If required, you have the option to split virtually joined segments again at a later point in time.

How do I split virtually joined segments:

1 Place the cursor at the position where the virtually joined segments are to be split (in the example: behind „Transit spart Ihnen Geld und“).

2 Select the option Split virtually joined segments from the context menu of the active segment.

Transit splits the virtually joined segments at the cursor position. The segment part in front of the cursor mark stays in segment 26, the segment part behind the cursor mark is taken over to the following segment 27.

Virtually joined segments split againVirtually joined segments split again

If the virtually joined segment consists of more than two joined segments, these segments continue to stay virtually joined. You may also split them, if needed.

 

5. Not permitting segments as reference material

It is possible to not permit segments to be used as reference material for certain reasons.

Example:

Due to an incorrect formatted original document a sentence is divided into two segments. Between the two segments there is a segment that only contains markups.

Due to the markup segment, joining the two text segments virtually is not possible.

In this case, it is possible to enter the translation of the complete sentence into the first target segment, empty the second target segment, and then not permit the two text segments as reference material.

How do I not permit a segment as reference material:

1 Right-click the desired segment in the target-language window.

Transit displays the context menu of the target-language window:

Context menu of the target-language windowContext menu of the target-language window

2 In the context menu, select the Do not permit as reference material entry.

The segment is not permitted as reference material and assigned the Not as reference access status. The access status is displayed in the Access field of the Segment info window.

Segments not permitted as reference material are not taken into account:

– for translation suggestions of the current project

– for pretranslation of future projects

– for translation suggestions of future projects

– during concordance search

– when creating a reference extract

– when compacting reference material

– when exporting the reference material into a TMX file

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

How do I permit a segment as reference material:

1 Right-click the desired segment in the target-language window.

Transit displays the context menu of the target-language window:

Context menu of the target-language windowContext menu of the target-language window

2 In the context menu, select the Permit as reference material entry.

The segment is permitted as reference material again.

Context menu entry is active depending on the access status

The context menu entry Do not permit as reference material is greyed out if the segment has the access status Read only.

Transit NXT

Static and Dynamic Viewers | Transit Training

Transit NXT

Static and dynamic viewers

For particular file types, Transit offers static or dynamic viewers. Those viewers can display the document text you are translating in the Transit editor in the original layout.

  • In a static viewer the source-language document text is displayed in the original layout.
  •  In a dynamic viewer the current status of the translation into the target language is displayed as a preview in the original layout.

In Transit, these viewers are conceived as ‘floating windows’ which can be called up via the context menu of the Transit toolbar (see the instructions under “How do I select a viewer?”).

Transit offers viewers which provide a synchronised view of files with the following file types:

  • PDF viewer for the ‘static’ display of PDF files (created from the original files from FrameMaker, InDesign, QuarkXPress, Word, PowerPoint, and RTF) and the dynamic preview of MS Word files
  • HTML viewer for the ‘dynamic’ display of HTML files and user-defined, custom XML files
  •  Multimedia viewer for displaying a variety of graphics formats contained in Word files

Another preview option offered by Transit is:

  • Dynamic preview of MS Office files (Word, Excel, PowerPoint) in the respective MS Office program

How do I select a viewer?

1 Move the mouse pointer to the area to the right of the resource bar and right-click to open the context menu of the Transit toolbar.

Transit displays the context menu of the Transit toolbar. The bottom section of this menu displays a list of the available viewers.

2 Select a viewer by left-clicking on the corresponding icon.

Transit opens the window for the viewer selected. The viewers take the form of floating windows. You can also change the display mode of the viewers from ‘floating’ to ‘permanent’, alter their size and position as desired or dock them with the user interface.

 

1.PDF viewer/Word preview

In the PDF viewer/Word preview a static viewer can be combined with a dynamic preview:

  • Source language:

If a PDF file of the original document is available, it can be displayed in the PDF viewer.

The view of the source document in the PDF viewer is synchronised with the view of the language pair in the Transit editor. This means, during translation, you can see in the PDF viewer where you are in the document at any given moment by means of a red arrow.

This allows you to quickly determine, for example, whether the text to be translated next is a heading or an index entry, and to translate the text appropriately.

  •  Target language:

You can display a preview of the text in its the original layout, showing the latest status of your translation into the target language.

This preview option is currently available only for Word files.

To generate a preview proceed as follows:

– Open the context menu of the target-language section of the Transit editor.

– Select the Display preview in Transit option.

Transit editor and PDF viewer/Word preview floating windowTransit editor and PDF viewer/Word preview floating window

The toolbar of the PDF viewer/Word preview offers the following view options:

PDF viewer/Word preview – toolbar functionsPDF viewer/Word preview – toolbar function

PDF viewer is only available for certain file types

The PDF viewer is only available for the following file types:

  •  FrameMaker
  • InDesign
  •  QuarkXPress
  • Word
  • RTF
  • PowerPoint

If you are working with a different file type in your project and call up the PDF viewer, Transit displays the following message:

No PDF synchronisation available for the file type selected.

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

File for the PDF viewer must be located in the working folder

In order to use the PDF viewer in a translation project, the PDF file must be placed in the working folder which contains the associated language pair. It is also important that the PDF file have exactly the same name as the original file or the Transit language pair.

Example:

Language pair: ch_06_translation.deu/eng

PDF file: ch_06_translation.pdf

If the PDF viewer is opened and there are no PDF files in the working folder, or the name of the PDF file differs from the name of the language pair, Transit displays the following message:

No PDF file available.

Please make sure that the PDF file is located in the working folder.

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

2.HTML viewer

It is also possible to view the text synchronised in the editor and original format for projects involving HTML files or user-defined, custom XML files. In addition to the source-language, the HTML viewer can also preview the target-language version of the original file, thus providing a continually updated view of the latest status of the translation. This means that the target-language version is updated dynamically.

The red frame in the HTML viewer shows which part of the file is currently being edited in the Transit editor. As soon as you confirm the translation with ALT+INS, it appears in the target-language pane of the HTML viewer:

The Transit editor and the HTML viewer floating window

The Transit editor and the HTML viewer floating window

The toolbar of the HTML viewer offers the following navigation and view options:

HTML viewer – toolbar functionsHTML viewer – toolbar functions

 

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

The HTML viewer is only for HTML files and custom XML files

The HTML viewer is only for use with projects containing HTML files and user-defined, custom XML files. The HTML viewer cannot be used for projects containing standard XML files or other file types. If you are working in your project with a file type other than those two mentioned above and call up the HTML viewer, Transit displays the following message:

The HTML viewer does not support the selected file type.

3.Multimedia viewer

In Transit, the Multimedia viewer gives you the option to display images contained in a Word file. The Multimedia viewer supports the following formats:

  • Windows Bitmap (*.bmp)
  • Multipage Paintbrush (*.dcx)
  • Drawing Interchange Format (*.dxf)
  •  Encapsulated PostScript (*.eps)
  • Kodak FlashPix (*.fpx)
  • IBM Linkway (*.fmf)
  • Graphics Interchange Format (*.gif)
  • GEM Paint (*.img)
  •  Joint Photographic Experts Group, JPEG (*.jpg)
  •  JPEG 2000 (*.jp2)
  • Kodak Photo CD Format (*.pcd)
  •  Paintbrush (*.pcx)
  •  Portable Network Graphics (*.png)
  • PDF Image Format (*.pdf)
  • Targa Image File (*.tga)
  • Tagged Image Format (*.tif)
  •  Windows Metafile (*.wmf)
  • Word Perfect Graphics (*.wpg)

Instead of having to refer back to the original file or, for example, to a PDF version of the document, thanks to the Multimedia viewer, you can easily establish the contextual relationship between the text and the image information without leaving the Transit working environment. The Multimedia viewer displays the image which belongs to the respective text segment:

The Transit editor and the Multimedia viewer floating windowThe Transit editor and the Multimedia viewer floating window

attentionPacking and forwarding project files

Please note that when packing or forwarding Transit projects containing image information for the Multimedia viewer, the cod file must also be packed. The cod file contains the image information and must therefore be included in the project file. Only then will the recipient of such a project be able to display the images in the Multimedia viewer (information on packing and forwarding project files can be found in section 4.3 “Packing a project” and 4.7 “Forwarding a project”).

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

The toolbar of the Multimedia viewer offers the following navigation and view options:

Multimedia viewer – toolbar functionsMultimedia viewer – toolbar functions

4. Dynamic preview of MS Office files

When translating MS Office files (Word, Excel, PowerPoint), you have the option to open a preview of the file from the Transit editor in the respective MS Office program, showing the latest status of your translation. When doing so, the respective MS Office program is opened in the foreground.

How do I open a preview of an MS Office file in the respective MS Office program?

1 Right-click on a segment in the target-language pane of the Transit editor.

2 From the context menu which is then displayed, select the option Display preview in Office application.

Transit opens the respective MS Office program and displays a preview of the file, showing the latest status of your translation.

The segment on which you right-clicked to open the preview, is highlighted. If this belongs to a paragraph, the entire paragraph is highlighted. This enables you to see at a glance where you are in the file.

Alternatively, for MS Word files, you may open the preview in the Transit window PDF viewer/Word preview (see section 5.9.1 “PDF viewer/Word preview”).

 

5.Synchronised View – User preferences

If Synchronised View is activated for the source and/or target language, then this runs in the background, even if the viewer in question is not currently being used in a project. This can, in turn, have a major effect on the performance of the application. It is therefore possible in the user preferences to define, in each individual case, on which viewers Synchronised View should be active:

User preferences window, Synchronised View screenUser preferences window, Synchronised View screen

How do I define the user preferences for Synchronised View?

1 Select Transit button | User preferences.

Transit displays the User preferences window.

2 Select the Synchronised View option.

Transit displays the Synchronised View screen of the User preferences window.

3 Specify the desired settings, e. g.:

Automatically synchronise multimedia viewer option in the Subtitling section

When translating the subtitling of a movie, Transit can automatically synchronise the playback of the movie in the Multimedia viewer.

Use this option to specify whether a segment should be played back automatically in the in the Multimedia viewer as soon as you place the cursor in it.

Cute Robot

Working with Terminology | Transit Training

 Cute Robot 

Overview

A key component of Transit is the TermStar NXT terminology management system. In TermStar NXT, you can create dictionaries and save general or project-specific terminology to them.

You use TermStar NXT in Transit in the following ways:

  • Terminology search (see section 5.7.3 “Searching for terminology”).
  • View terminology suggestions in dictionaries for the active segment and transfer these to your translation (see section 5.7.6 “Transferring a translation from the dictionary”).
  • Add terminology from Transit to a dictionary (see section 5.7.7 “Adding terminology to the dictionary”).
  • Check terminology to determine whether you used the translations from the dictionaries (see section 6.6 “Format check”).
  • Automatically accept all terms from the dictionary (see section 5.7.8 “Accepting all terms”).
  • Add specialist terminology from a language pair to a dictionary (see section 3.11 “Creating, editing and managing dictionaries”).

If you have already created a dictionary for your terminology in TermStar NXT, you can assign it to a Transit project. If you do this, Transit also opens the dictionary simultaneously with the project.

If you add terminology to a dictionary, Transit saves the new terminology to the ‘current‘ dictionary. This dictionary can be defined in the project settings. Please refer to section 3.6.13 “’Dictionaries’ project settings” for more detailed information on how to assign a dictionary to a project and how to specify your ‘current’ dictionary.

You will find detailed information on TermStar NXT in the TermStar NXT User’s Guide.

2Dynamic Linking

With Dynamic Linking, Transit can display all the segments which contain particular pairs of terms. This quickly and easily provides you with an overview of where, and in what context a source-language term and its translation are used. It also allows you to effortlessly obtain up-to-date examples at any time in the context of the current project for terminology maintenance purposes (see section 5.11 “Dynamic Linking”).


5.7.2 Switching between the Transit editor and TermStar

You can switch back and forth between the Transit editor and the TermStar project dictionaries by clicking on the corresponding tab or by pressing the keyboard shortcut CTRL+TAB:

1

  Fig. 5-41: The language pair and TermStar (project dictionaries) tabs

5.7.3 Searching for terminology

Searching for Terminology in TermStar dictionaries

Information on searching for terminology in TermStar can be found in the TermStar NXT User’s Guide, section 5.4 “Searching for a word”.

Searching for terminology via TermStar Gate

Using the TermStar Gate plug-in, you can search for translations or enter terminology from Microsoft Word or Adobe FrameMaker. This gives Microsoft Word or Adobe FrameMaker direct access to TermStar NXT and thus your local project dictionaries.

Information on these plug-ins you find in the “TermStar Gate for Word – Installation & Usage” and “TermStar Gate for FrameMaker – Installation & Usage” documents.
5.7.4 Searching for terminology and translations via Web search

Web search allows you to access the internet from within Transit, to search for translations and terminology online:

1

  Fig. 5-42: Web search window

The icons at the top of the window are used to access the following functions:

5

  Tab. 5-9: Web search: functions

4How do I use the “Web search” tool?

1 Open the Web search window (detailed information on calling up tools can be found in the section “How do I display a floating window?”).

Alternatively, it is also possible to open this window via Windows | Open | Web search.

Transit displays the Web search window.

2 To search for a term or a translation on the internet, proceed as follows:

– Select the services which you want to search from the Search in list.

Select a service by checking the box on the left of the service name. Alternatively, you can also select all services by clicking on the Check all option in the icon bar.

– Select Source language from the icon bar if you want to search for the search term in the source language of the project which is currently open. Select Target language from the icon bar if you want to search for the search term in the target language of the project which is currently open.

– Enter a search term into the field and press the Enter key or click on Search.

If one of the services finds the search term, a green light appears to the left of the corresponding list entry, and the word Go appears to the right (next to the globe icon). If a red light appears instead, then the search query returned no results for this service.

– You can display the search results for a particular service by clicking the Go button.

Transit displays the search results for the respective service in the right-hand portion of the Web search window.

2Opening the website of the search engine without a search

You can call up the website of the search service also without carrying out a search. To do so, click on the globe icon in the corresponding list entry.


2No suitable search engine for the selected search language

The available search engines may not support the selected search language. If no search engine can be found for a language, Transit displays the following message:

No suitable search engine could be found for the selected language.

2Disabling script debugging

When you select a search result, an error message may appear in the Web search window referring to a script error in the page being displayed. To prevent these error messages from being displayed, script debugging must be disabled in Internet Explorer. To do this, select the Disable Script Debugging option under Settings | Control Panel | Internet Options | Advanced.

5.7.5 Terminology search – User preferences

In the user preferences, you can define how and which folders to search for terminology. You can also determine how terms are displayed in the language pair and the Terminology window.

4How do I configure the user preferences for Terminology search?

1 Select Transit button | User preferences.

Transit displays the User preferences window.

2 Select the Terminology search option.

Transit displays the Terminology search user preferences:

1

  Fig. 5-43: User preferences window, Terminology search screen

3 In the Search type section, you can specify how to search for terminology:

Morphology-based – Transit carries out a morphological search which means that during search for dictionary entries all inflected forms of a search term (i. e. declined or conjugated forms) are taken into account.

2Support for more than 15 languages

Transit supports morphology-based search for the following languages:
German, English, French, Italian, Spanish, Basque, Catalan, Czech, Danish, Dutch, Hungarian, Norwegian, Polish, Portuguese, Romanian, Russian, Slovak, Slovene, Swedish.


Exact matches only – Transit performs a search for terms which match the search term precisely. This option disables morphological search; the option Morphology-based is deselected.

Match case – Ignore – Transit ignores differences in case.

Match case – Match, but ignore for 1st character – Transit ignores a difference in the case of the first character.

Match case – Match – Transit pays attention to differences in case.

Regard formatted strings from the working folder – Transit searches the working folder for terms containing formatting information, for example, italic, bold or underline and displays the source-language term and its translation in the Terminology window.

To distinguish these terminology suggestions from found dictionary entries in the Terminology window, they are not marked yellow, but blue.

Regard formatted strings from the reference material – Transit also searches the reference material for terms containing formatting information, for example, italic, bold or underline.

To distinguish these terminology suggestions from found dictionary entries in the Terminology window, they are not marked yellow, but blue.

Source language: Regard disallowed terms – When background scanning for dictionary entries and performing the terminology check, Transit also takes into account data records that contain the term used in the source language as a disallowed term.

In case of documents using incorrect terminology we recommend to use this option. This allows you to take into account the terminology quality of the documents to be translated and optimise the terminology check.

In case of documents using correct terminology we recommend not to use this option.

4 In the section Highlight in language pair, you can specify which terms should be highlighted in colour in the language pair.

all – All terms are highlighted.

if target language exists – A term will be highlighted only if there is a translation for it in the currently selected language.

if target language is missing – A term will be highlighted in the source-language segment if it has no translation in the currently selected target language.

5 In the Display in “Terminology” window section, you can specify which terms will be displayed in the Terminology window.

all – All terms are displayed.

if target language exists – A term will be displayed only if there is a translation for it in the currently selected language.

6 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.

5.7.6 Transferring a translation from the dictionary

Transit automatically searches the project dictionaries for appropriate entries while you translate. By default, Transit carries out a morphological search and also finds declined or conjugated forms of existing entries. If required, you can determine that Transit displays only exact matches.

Dictionary entries which have been found in TermStar NXT are highlighted by default with a yellow background and displayed in the Terminology window. When translating a segment, there are several ways to accept a term:

  •  Replace a word with its translation from the project dictionary.
  •  Select the translation which will replace the word, if more than one translation is found.
  • Insert a translation without replacing a word.

Transit can also automatically accept all terms from the dictionary. Please refer to section 5.7.8 “Accepting all terms” for more detailed information on this topic.

2Dynamic Linking for dictionary suggestions

With Dynamic Linking, Transit can display all the segments which contain the suggestions from the dictionary. This quickly and easily provides you with an overview of where, and in what context a source-language term and its target-language equivalent are used. It also allows you to effortlessly obtain up-to-date examples at any time in the context of the current project for terminology maintenance purposes (see section 5.11 “Dynamic Linking”).


4How do I replace a word with its translation from the dictionary?

1 Place the cursor onto, or at the beginning of, the word you wish to replace.

Transit shows the dictionary entry in the Terminology window.

2 To accept this translation, press the keyboard shortcut ALT+T

Transit replaces the selected word with the translation from the project dictionaries.

If you also want to change the case of the initial letter when inserting the term, press ALT+SHIFT+T instead of the shortcut mentioned above.

4How do I select the term to replace a word when there are several dictionary suggestions?

1 Place the cursor onto, or at the beginning of, the word you wish to replace.

Transit shows the dictionary entries in the Terminology window.

2 To accept the translation, press the keyboard shortcut ALT+K, <Letter>.

<Letter> here refers to the letter which is in front of the particular translation in the Terminology window.

Transit replaces the selected word with the translation selected.

If you also want to change the case of the initial letter when inserting the term, press ALT+K, SHIFT+<Letter> instead of the keyboard shortcut mentioned above.

4How do I insert a translation from the dictionary without replacing the source-language word?

1 Position the cursor at the position at which you wish to insert the translation.

Transit shows the dictionary entries in the Terminology window.

2 To accept the translation, press the shortcut ALT+G, <Letter>.

here refers to the letter which is in front of the particular translation in the Terminology window.

Transit inserts the translation selected at the cursor position.

If you also want to change the case of the initial letter when inserting the term, press ALT+G, SHIFT+ <Letter> instead of the keyboard shortcut mentioned above.

2If Transit inserts a space as the translation from the dictionary

Consider the following scenario: Transit indicates that it has found an entry in the dictionary, that you want to accept; however Transit only enters a space. This may be explained by the following:

Transit highlights a word if it finds it as a source-language entry in the dictionary. This is the case even if there is no entry in the dictionary for your current target language, (but for other languages which you are not working with at the moment). If you then want to transfer the (non-existent) translation from the dictionary, Transit inserts a space because no translation is available.

If your dictionary is incomplete and does not contain a target-language entry for every source-language entry, you have the following options:

– In the Terminology search user preferences, you can select the if target language exists option under Display in “Terminology” window. The Terminology window will then only display the entries which have a translation in the currently selected target language.

– You can create a separate dictionary containing only data records which have a term in both the source and target language.


5.7.7 Adding terminology to the dictionary

You can add terminology to the current TermStar dictionary while you are translating in Transit.

The following options are available:

  • Adding selected terms to dictionary

Select a word in the source language and its translation in the target language and add it straight to the current dictionary as a new data record.

  • Adding terminology to the dictionary using rapid entry mode

Select a word and use the rapid entry function to add it as a new data record or a new entry to a dictionary.

With the rapid entry function, you can add extra information to the dictionary, apart from the term (e.g. subject, context). In addition, you can also specify to which project dictionary the terminology should be added.

  • Adding terminology suggestions based on markups to the dictionary

Adding selected terms to dictionary

You can select words in the source and target language and immediately add them to the dictionary as a new data record. With this function, you can only specify the source and target-language terms for this entry or data record.

3Transit saves selected terms to the current dictionary

If you add a selected term to the dictionary, Transit always saves it to the ‘current‘ dictionary. Which dictionary this is can be specified in the project settings (see section 3.6.13 “’Dictionaries’ project settings”).

Please ensure that you have specified the required dictionary as the current dictionary.


4How do I add selected terms to the current dictionary?

1 Select the term in the source language and the translation in the target language.

2 Select Terminology | Creation | Insert selected.

Transit inserts the pair of terms into the dictionary as a new data record.

– If a data record containing an identical pair of terms already exists, Transit displays the following message:

Data record "< …>" already exists.

– If the new data record has the same source-language term but a different target-language term as an existing data record, Transit displays the following message:

Entry "< …>" already exists.

Decide whether you want a new data record to be created or the existing data record to be expanded:

New data record – The terminology is added to the current dictionary as a new data record.

Insert – The terminology is appended as a new entry to the existing data record in the current dictionary.

Cancel – No terminology is added to the current dictionary.

Adding terminology to the dictionary using rapid entry mode

You can add words to the current dictionary using the rapid entry mode.

Transit displays the following fields in the Rapid entry window:

  • Dictionary to which the entries should be added
  • Current source-language term
  • Current target-language term
  • Fields with input verification

You can specify these fields in the dictionary settings. Please refer to the TermStar NXT User’s Guide for more detailed information.

If one of the terms you have entered already exists in the dictionary, you can choose one of the following options:

  •  New data record – TermStar NXT creates a new data record with both entries.

Always create a new data record if the terms have a different meaning than the existing data record.

  •  Insert – TermStar NXT inserts the new term as a new entry in the data record of the existing term.

Always insert an entry into the existing data record if the term has the same meaning as the existing data record.

2TermStar NXT only checks the target dictionary

When making new entries, TermStar NXT only checks the dictionary to which you are adding the new entries, i.e. the dictionary that you selected in the Rapid entry window. Entries which exist in other dictionaries are not taken into consideration.


4How do I add terminology to a project dictionary using the rapid entry function?

1 Select Terminology | Creation | Rapid entry.

Transit displays the Rapid entry window with the following fields:

1 

  Fig. 5-44: Rapid entry window

– Target dictionary to which the terminology is added

– Source-language term which you have selected

– Target-language term which you have selected

– Other fields, for which an input verification has been defined, may also appear

2 Select the dictionary to which Transit should add the terminology.

3 Correct the source-language or target-language term, if necessary.

4 Fill in the other fields, if necessary.

5 Confirm your entry with Save.

– If a data record containing an identical pair of terms already exists, Transit displays the following message:

Data record "< …>" already exists.

– If the new data record has the same source-language term but a different target-language term as an existing data record, Transit displays the following message:

Entry "< …>" already exists.

Decide whether you want a new data record to be created or the existing data record to be expanded:

New data record – The terminology is added to the selected dictionary as a new data record.

Insert – The terminology is appended as a new entry to the existing data record in the dictionary selected.

Cancel – You return to the Rapid entry window without having added the terminology to the dictionary.

As the Rapid entry window remains open, you can create further data records.

To close the Rapid entry window, click Cancel or click Save if all the fields are empty.

Adding terminology suggestions based on markups to the dictionary

The Terminology window can also display terminology suggestions based upon already translated terms from your working folder or in the reference material that contain formatting information, for example, italic, bold or underline. Terminology suggestions based on markups are indicated in blue in the Terminology window.

For the Terminology window to display terminology suggestions based upon markups, you need to select the options Regard formatted strings from the working folder and/or Regard formatted strings from the reference material in the User preferences for Terminology search (see section 5.7.5 “Terminology search – User preferences”).

You can either immediately accept these terminology suggestions into the current dictionary as a new data record, or use the rapid entry function to add them to a dictionary as new data records or new entries.

4How do I add terminology suggestions based on markups to a dictionary?

1 Open the context menu in the Terminology window by right-clicking on a terminology suggestion (highlighted in blue).

2 From the context menu, select either Insert terminology in current dictionary or Rapid entry.

From this point, the procedure is exactly the same as that described in the sections “How do I add selected terms to the current dictionary?” and “How do I add terminology to a project dictionary using the rapid entry function?”.

5.7.8 Accepting all terms

Transit can automatically accept all terms from the dictionary for segments which are not translated. Transit then automatically inserts the translation of the source-language terms it finds in the dictionary into the target-language segment.

2Several translations or no translation in dictionary

If Transit finds several translations in the dictionary for one source-language term, Transit always takes the first translation.

If Transit finds a source-language term in the dictionary but no target-language translation, Transit leaves the source-language term unchanged.


4How do I accept all terms for ‘Not translated’ segments?

1 Specify via Terminology | Use | Auto-insert if you want to accept the terms just for the active segment or for the whole file.

– Select the Segment option if you want to accept the terms for the active segment,

– Select the File option if you want to accept the terms for the whole file.

Transit displays the following message:
Do you really want to accept the translation for all words found in the dictionary?

2 If you are sure you want to accept all the terms from the dictionary, click Yes.

Transit replaces all the source-language terms in segments which are not translated with the target-language terms from the dictionary.

Now Transit displays the following message:

All terms found in the dictionary have been inserted.
Cute Robot

Dynamic Linking | Transit Training

Cute Robot

Overview

Dynamic Linking works like a multilingual concordance search. It displays all the segments which contain particular pairs of terms. This quickly and easily provides you with an overview of where, and in what context a source-language term and its translation are used.

You can use Dynamic Linking also if only a source language term exists.

Compared to the static recording of examples in a dictionary, Dynamic Linking has the following advantages:

  • Subject

Dynamic Linking displays examples found in the currently used reference material, i.e. the project/subject the translator is working on.

The same term might have been translated differently in different projects: Example: English driver – German Fahrer or Treiber.

  • Context

Dynamic Linking displays examples embedded in the context of the segment they appear in.

A term on its own does not indicate a meaning as it lacks context. Example: Motor in German = motor or engine in English

  • No terminology maintenance effort

Dynamic Linking does not require additional terminology maintenance effort because examples do not need to be added to the dictionary but are created dynamically when Dynamic Linking is called up.

Examples in a dictionary requires great maintenance effort and may soon become obsolete.

  • Reduced database sizes

Dynamic Linking reduces the size of dictionary databases as the dictionaries do not need to contain the examples.

3Dynamic Linking is only useful for Transit projects with reference material

As Dynamic Linking searches the reference material for terms or pairs of terms, this function only makes sense if you are working in a Transit project that contains reference material.


5.11.2 Calling up Dynamic Linking

There are several possibilities for calling up Dynamic Linking. This means that Transit provides the ideal solution for every situation.

  • From the Terminology window
  • From the dictionary itself
  • From the Transit-toolbar context menu

Transit displays the search results in the Dynamic Linking window (fig. 5-73). Please refer to section 5.11.3 “Dynamic Linking results” for more detailed information on this topic.

4How do I call up Dynamic Linking via the Transit Toolbar?

1 Position the mouse pointer over the resource bar and right click. Select the Dynamic Linking tool from the context menu.

Transit displays the Dynamic Linking window (fig. 5-73).

2 In the Source language and/or Target language fields, enter the term in the source and/or target languages which you want to search for using Dynamic Linking and click Search.

If you want to use morphological search, please enter the base form of the term.

Transit displays the Dynamic Linking window, containing the search results (fig. 5-73). Please refer to section 5.11.3 “Dynamic Linking results” for more detailed information on this topic.

4How do I call up Dynamic Linking from the Terminology window?

1 If Transit is displaying dictionary suggestions for the current segment, double-click on the symbol to the left of the corresponding entry. This is the fastest way of opening Dynamic Linking for a term or pair of terms.

Alternatively you can open the context menu in the Terminology window by right-clicking on the dictionary entry in question.

Transit displays all the terms or the pairs of terms for which you can call up the Dynamic Linking feature:

1

  Fig. 5-71: Calling up Dynamic Linking from the Terminology window

2 Select the term or pair of terms for which you wish to call up Dynamic Linking.

Transit displays the Dynamic Linking window, containing the search results (fig. 5-73). Please refer to section 5.11.3 “Dynamic Linking results” for more detailed information on this topic.

4How do I call up Dynamic Linking from the dictionary?

1 Click on the TermStar tab.

2 Select the data record for which you wish to call up Dynamic Linking, and then open the context menu.

TermStar NXT displays the terms or pairs of terms in the submenu Dynamic Linking:

2

  Fig. 5-72: Calling up Dynamic Linking from the dictionary

3 In the submenu, select the term or pair of terms for which you wish to call up Dynamic Linking.

TermStar NXT displays the Dynamic Linking window, containing the search results (fig. 5-73). Please refer to section 5.11.3 “Dynamic Linking results” for more detailed information on this topic.

5.11.3 Dynamic Linking results

After you have called up Dynamic Linking (see section 5.11.2 “Calling up Dynamic Linking”), Transit starts searching and displays the search results in the Dynamic Linking window. Transit displays the matches, starting with the most similar match:

1

Fig. 5-73: Dynamic Linking window with search results

The matches contain the following information:

  • First line – Similarity of match and name of the file in which the text was found.
  • Second line – Source language and source-language segment (with highlighted search term, where applicable).
  • Third line – Target language and target-language segment (with highlighted search term, where applicable).

If necessary, you can use the context menu to open the reference file so you can view the context of the match.

If you no longer require Dynamic Linking, you can close the window by clicking on X on the right of the titlebar.

It is also possible to integrate the Dynamic Linking window with the user interface by docking it (for information on this, see the instructions under “How do I dock a standard window with the user interface?” in section 2.1.8 “The Transit toolbar”).

2Searching for a search term again

In the Source language and Target language lists, Transit shows all the terms which you have searched for with Dynamic Linking since starting Transit.

If you want to search again for a term that you have already entered, simply select it from the Source language or Target language list and click on Search. This feature is very helpful if you want to use different settings for different terms.


5.11.4 Settings for Dynamic Linking

In the Dynamic Linking window, you can define various settings (see figure 5-73). Clicking Options takes you to the Dynamic Linking user preferences. From there you can configure additional, project-independent settings. You can find more detailed information on this in the section5.11.5 “Dynamic Linking – User preferences”.

  • Minimum quality – Specify how similar the search term and the text in the segments should be in the source and target language. You can use this setting to define how similar matches should be.
  • Phrase search – Select this option if you want Transit to search segments for text which is a 100% match for the search string.

The following table uses examples to explain the difference between a word search and phrase search:

1

  Tab. 5-18: Examples of word and phrase searches

  •  Source language – Enter the source-language term here which you want Transit to search for.

If you only want Transit to search in the target language, leave this field empty and only enter text in the Target language field.

  • Target language – Enter the target-language term here which you want Transit to search for.

If you only want Transit to search in the source language, leave this field empty and only enter text in the Source language field.

  • Morpho search – Select this option if you want Transit to take morphological criteria into account for Dynamic Linking. To do this, enter the base form of the term into the Source language and/or Target language fields. Transit will then also search the language pairs for conjugated and inflected forms.
  • Match case – If you want Transit to take account of case differences for Dynamic Linking.
  • Include all languages – This option is only available if you call up Dynamic Linking from TermStar NXT (see fig. 5-72).

Select this option to determine whether TermStar NXT should only take the current source and target language into account for Dynamic Linking, or whether it should consider all languages for which there are entries in the data record and reference material.

The following table shows the impact this option has for Dynamic Linking. We have used the term pair database/Datenbank as an example:

5

  Tab. 5-19: Examples of including all languages in the search

– Include all languages in the search (Include all languages selected):

TermStar NXT also compares the French entry base de données in the data record with the text of the segments. As the sample segment 2 contains another term (banque de données), this segment does not match the data record entries for all languages. Dynamic Linking does therefore not display segment 2 but only the sample segment 1.

– Do not include all languages in the search (Include all languages not selected):

TermStar NXT only compares the German and the English entry with the text of the segments. As these terms also appear in sample segment 2, the segments match the data record in the source and target language. Therefore, Dynamic Linking displays sample segment 1 and sample segment 2.

If TermStar NXT is unable to find any matches solely because ‘Include all languages’ is checked, Transit displays the following message in the results window:
Please uncheck ‘Include all languages’ and try again.

With the option unchecked, TermStar NXT would be able to find matches. If you want to display these matches, please uncheck Include all languages and search again by clicking Search.

5.11.5 Dynamic Linking – User preferences

The Dynamic Linkung user preferences can be opened

– by clicking Options in the Dynamic Linking window,

– by selecting Terminology | Dynamic Linking | Options in the ribbon bar.

Capture

Fig. 5-74: User preferences window, Dynamic Linking screen

The user preferences for Dynamic Linking are the same as for Dual Concordance (e.g. language pairs to be searched, minimum segment status) (see section 5.10.3 “Dual Concordance – User preferences”).

small-book

Document Formatting for Faster Translation Delivery

Download our latest ebook now.

Working With Machine Translation Engines

keyboard-2923535_1280

Working with Transit and Machine Translation Engines.

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

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 (see “’Machine translation’ project settings” section).

Import MT suggestions are displayed to you as translator in the fuzzy window, together with the fuzzy matches that may exist (see “Import MT suggestions in the fuzzy window” section).

  • 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 5.5.3 “Manually requesting a machine translation” on page 241). 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.

 

5.5.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.

4How 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:

1

  Fig. 5-29: User 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 2– 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

3STAR/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.


5.5.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:

1

  Fig. 5-30: Entering 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.

 

5.5.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:

1

  Fig. 5-31: Editor MT suggestion

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

5

  Fig. 5-32: Editor 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.

4How 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.5.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:

1

  Fig. 5-33: Import MT suggestion

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

5

  Fig. 5-34: Import 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.

 

Cute Robot

Organising reference material | Transit Training

Cute Robot

Storing language pairs as reference material

Transit helps you to store the language pairs of a finished project as reference material in a structured way.

You can specify how the language pairs should be copied to the selected reference folder and simply resolve any naming conflicts.

4 How do I store the language pairs of a project as reference material?

1. Open the desired project, in case it is not opened yet.

2. Select Reference material | Copy current project to reference folder from the resource bar.

Transit displays the Destination folder for reference material window:

1

  Fig. 3-67: Destination folder for reference material window

3. Specify the reference folder into which Transit should copy the language pairs.

When you open the selection list, the following directories will be offered:

– all directories specified as reference folders in the project

– all directories from which files have been specified as reference material in the project

Via the button to the right of the selection list, you can select any folder in the file system or create a new folder

4. In the Copy project language pairs section, specify how the language pairs are to be copied to the reference folder:

Copy unchanged – Transit copies the language files as they are.

Add file-name prefix – Transit adds the string from the input field as a prefix to the language file names.

As default displays the project name plus an underscore. However, the prefix can be changed as desired.

Copy to subfolder – Transit creates in the reference folder a subfolder with the name of the project and copies the language files in there.

If language pairs are stored in subfolders, the subfolder structure is retained during copying.

5. Specify whether the reference folder and the option in the Copy project language pairs section you have selected for this project should in the future be preselected for all projects,

– for which the same customer as been specified in the project settings (Use as default for customer option).

– that have the same “User” scope and no customer specified (Use as default for user option)

– that also have the “Global” scope and no customer specified (Use as default option)

Confirm the settings selected by clicking OK.

If no naming conflicts occur, Transit copies the language files as specified.

If naming conflicts occur, Transit displays the following window:

2

  Fig. 3-68: File names exist already window

In this case language files having the same name already exist in the reference folder.

Select whether you want to overwrite the existing language files or rename the new language files.

– Click Replace to overwrite the existing language files with the new ones.

– Click Rename to rename the new language files and therefore retain the old reference files.

Transit displays the following window:

3

Fig. 3-69: Rename language pairs window

Path column – Transit displays the relative original path if files from subfolders have been imported into the project.

Original name column – Transit displays the original names of the new language pairs.

Names for which a conflict occurs are displayed in red.

Rename to column – Transit gives you the option to change the original names in order to resolve naming conflicts.

Click OK to finish this process and to copy the new language files into the reference folder.

3.10.2 Organising reference material

Via the Organise reference material window, Transit offers you the opportunity to filter reference material according to certain criteria and then to copy, move or delete the filtered files:

1

Fig. 3-70: Organise reference material window

Transit offers the following filter criteria to allow you search the reference material:

5

 

Tab. 3-6: Filter criteria in the Organise reference material window

By default, the following filter criteria are set in the five filter dropdowns (from left to right):

  • Language
  • Date created
  • File size
  • Folder name
  • File extension

The Organise reference material window offers the following functions:

Capture

Tab. 3-7: Organise reference material commands

4How do I search my reference material?

  1. Select Reference material | Organise reference material from the resource bar.

Transit displays the Organise reference material window.

2. Select the folder which contains the reference material. To do so, click on Select folder containing reference material.

Transit displays the Select folder containing reference material window.

3. Select the folder containing the reference material and confirm your selection by clicking OK.

Transit displays the Organise reference material window again.

4. Click on Start to begin the scan.

Transit searches the folders based on the five filter criteria. After the scan is complete, Transit displays the results in the Scan results section. Each of the five filter windows contains the files or folders corresponding to the selected filter criterion:

Capture2

Fig. 3-71: Organise reference material window; Scan results

5. You now have the option to modify these scan results.

– If required, you can select different filter criteria from the dropdown lists:

Capture3

Fig. 3-72: Filter-options dropdown list in the Organise reference material window

– Clicking on the button to the right of the dropdown list allows you to exclude any subfolders in the filter window in question from the scan. By default, all subfolders are included in a search. This is indicated by the ‘normal’ (popped-out) appearance of the button’. Use the mouse to select the folder in the filter window whose subfolders you wish to exclude, and then click on the button to the right of the dropdown list.

The button now has a ‘pressed-in’ appearance, and the subfolders of the selected folder will no longer be included in the scan results.

When filter criteria are modified or subfolders excluded, Transit automatically updates the Scan results section. Therefore it is not necessary to restart the scan.

6. After you have achieved the desired search results, you can copy or move either individual files or all the files displayed in the Scan results section to another folder or delete the selected files. Select the files on which you would like to carry out these actions by clicking them with the mouse pointer. Hold the CTRL key at the same time if you wish to select several files from the list.

– Click on Copy selected files to copy the selected files into a different folder. In the Select destination folder window, select the folder to which you wish to copy the files. Confirm your choice by clicking OK.

– Click on Move selected files to move the selected files into a different folder. In the Select destination folder window which then opens, select the folder to which you wish to move the files. Confirm your choice by clicking OK.

– Click on Delete selected files to delete the selected files from the Scan results list.

4How do I save search results?

1. Click on Save current results.

Transit displays the Results file window.

2. Select the appropriate folder and enter a name for the file in the File name field. Click Save to confirm the information entered.

3. Transit saves the file in the folder containing the scanned reference material, or in another folder selected by you, with the name <Filename>.dat and then displays the Organise reference material window again.

4How do I load saved search results?

1. Select Reference material | Organise reference material. from the resource bar.

Transit displays the Organise reference material window.

2. Click on Open results file.

Transit displays the Results file window.

3. Select the appropriate folder and the file and confirm your selection by clicking Open.

Transit displays the Organise reference material window with the scan results loaded up.

3.10.3 Modifying reference material

In Transit, you can search for any string in the reference material and have it replaced with another string – similar to the Transit editor.

For this purpose, you use the Modify reference material window:

Capture

Fig. 3-73: Modify reference material window

In this window, you can specify the following search options:

  •  Search in… – Specify the language pairs in which Transit should search:

Reference material – Transit searches the language pairs that are selected as reference material in the current project.

Working folder – Transit searches the language pairs located in the working folder of the current project.

Both – Transit searches both in the reference material and in the working folder of the current project.

You can specify a minimum status that the segments must have to be included in the search. You can specify it for the reference material and the language pairs in the working folder separately.

  •  Phrase search – Specify if the search string must appear exactly in the order entered. Transit then automatically uses a similarity of 100%.
  •  Match case – Specify if you want Transit to take account of case.
  •  Minimum quality (%) – Specify how similar the search string and the text in the segments should be.

This value is only relevant for word searches. If the Phrase search option is selected, Transit always searches for 100% matches.

In addition, you can specify the following filter options:

  •  Additionally filter by segment content section – Here you can enter segment content with which you want to restrict the search:

Hide segments with this content – Transit searches only in segments without this segment content.

Only display segments with this content – Transit searches only segments with this segment content.

This can be a word / phrase, a regular expression or a combination of the two.

Specify if this restriction should apply to the target language or the source language.

  •  Additionally filter by access status section – Specify if Transit should only search segments that are permitted or not permitted as reference material.

4How do I search for and replace a string in the reference material?

1. Select Reference material | Modify reference material from the resource bar.

Transit displays the Modify reference material window (Fig. 3-73).

2. Enter the search string in the Find field.

3. Specify whether to search the string in the target or the source language.

4. In the Replace with field, enter the string with which Transit replaces the string that is found.

5. Select the desired search and filter options.

6. Click Find all to start the search.

If Transit finds segments that match the search criteria, it displays a result list:

Capture1

Fig. 3-74: Modify reference material window: Result list

On the right-hand side, Transit displays the content of the first segment found.

At first glance, you can see where the segments origin from:

Capture2– from the current project

Capture3– from the reference material (name of the reference file is displayed)

Capture4– from the TM Container

7. You can edit the found segments as follows:

– Navigate through the result list:

To do so, select Next and Previous.

– Replace the search string in the selected segment:

To do so, select Replace.

– Replace the search string in all found segments:

To do so, select Replace all.

– Change the access status of selected segments (keep Ctrl key or Shift key pressed to select multiple segments):

To do so, select Selected segment below Do not permit as reference material or Permit as reference material.

– Change the access status for all segments found in a file:

To do so, select the desired file in the result list and click All Segments below Do not permit as reference material or Permit as reference material.

– Save the result list in a CSV file:

To do so, click Save result list.

When you have changed a segment, Transit marks it with a red pencil icon:

Capture5

Fig. 3-75: Modify reference material window: Segment changed

8. Save your changes at any time by clicking Save all language pairs.

When you have saved a segment, Transit marks it with a green check:

Capture6

Fig. 3-76: Modify reference material window: Segment saved

9. When you are done, close the window by clicking Close.

3.10.4 Compacting reference material

Language pairs which you create during translation in Transit can be used as reference material for other projects. These language pairs may contain many identical segments if, for example, tables or lists were translated with many segments that are identical, the ‘internal repetitions‘.

Transit can compact your reference material so that it only contains a single copy of segments which occur multiple times or only differ slightly. This results in reference language pairs which are smaller in size and faster to transfer (e.g. by e-mail) and, in some circumstances, return faster pretranslations and fuzzy matches.

2Size of the compacted file

If you are using reference material with different file types, Transit generates a separate file for each individual file type. Transit also divides files if they would contain more that 15,000 segments. This means that Transit is able to generate smaller, easily-managed files.


2Reference extract and compacted reference material

Transit can create a reference extract from your reference material or compact the reference material:

  • Reference extract

Transit can create a project-related reference extract when it imports the project files. The reference extract only contains the reference segments which can be used when translating the project, and thus reduces the number of unnecessary reference segments.

  • Compacted reference material

Transit can compact your reference material, regardless of which project it appears in. The compacted reference material only contains a single copy of any reference segments which occur multiple times, thereby reducing the number of identical reference segments.

To create a reference extract, set the required options in the project settings (see section 3.6.18 “’Extracts’ project settings”) and import the project files (see section 3.7.3 “Performing an import”).


4How do I compact reference material?

1. Select Reference material | Compact reference material from the resource bar.

Transit displays the Compact reference material window:

Capture

Fig. 3-77: Compact reference material window

2. Specify the language file which you would like to compact. The window gives you the following compact options:

Transit project

– Click on Add projects if you want to compact the reference material of a certain Transit project.

Transit opens the Project browser window.

– Select the desired project and confirm your choice with OK.

Transit files in a reference folder

– Select Add folder if you want to compact the Transit data in a particular folder.

Transit opens the Select reference folder window.

– Select the desired files and confirm the selection by clicking Open.

Individual Transit files

– Select Add files if you want to compress particular Transit files.

Transit opens the Select reference files window.

– Select the desired files and confirm your selection by clicking Open.

Transit displays the selected path in the Reference material field.

3. Specify the source language of the reference material: To do this, select the appropriate language from the Source language list.

Transit requires this information to decide whether there are translation variants or not.

4. Specify where Transit should save the compacted reference material: To do so, click on … to the right of the Filename field.

In the Reference extract window, select the drive and folder and enter a filename. Confirm your selection by clicking Save.

Transit displays the path in the Filename field:

Capture

Fig. 3-78: Create reference extract window

5. Specify the segments which Transit should take into account:

Save segments where only the numbers differ only once

This setting may be useful, as Transit can partially pretranslate segments with differing numbers and then carry over the numerical values from the current segment (see the paragraph “Details”). This would make otherwise identical segments with different numbers superfluous.

Save segments where only the fonts differ only once

This setting may be useful, as Transit can partially pretranslate segments with differing fonts and then carry over the fonts from the current segment (see the paragraph “Details”). This would make otherwise identical segments with different fonts superfluous.

Save all translation variants

This setting is relevant if there are different translations for the same source-language segments.

Do not check this option if you do not want the compacted reference material to contain variants. The compacted reference material will then contain one copy of each source-language segment with one translation.

Select this option if you want the compacted reference material to contain all the variants. The compacted reference material will then contain multiple identical source-language segments, each with one translation version.

Also save context information

Select this setting if you want Transit to also save the corresponding context information along with segments whose content is identical but that differ in terms of their structure information (for example, if the same text appears once as a table heading and another time as a list point).

6. Once you have verified all the options and made any necessary changes, compact the reference material by clicking Start.

Transit displays the Reference extract window. The progress bar indicates what percentage of the reference material has already been compacted.

When Transit has compacted the reference material, it displays the following message:

Completed successfully.

7. Click Details if you want to view the statistics on the compacted reference material.

Transit displays the Details window with statistics on the compacted reference material.

– Click Save if you wish to save these statistics.

In the Save log as window, enter the drive, folder and filename for the log file. Click Save to confirm the information specified.

Close the Details window by clicking OK.

Close the Reference extract window by clicking OK.

8. Close the Compact reference material window by clicking Close.

Transit has compacted the reference material. You can now use it as reference material for your projects.

3.10.5 Importing and exporting TMX files

Transit can also import data created by other Translation Memory systems. Equally, you can export Transit language pairs to allow this data to be edited in another environment. This happens through the TMX data interchange format.

More details on exchanging data via TMX can be found in the Transit/TermStar NXT Reference Guide, chapter 2 “Exchanging reference material via TMX”.

3.10.6 Creating an alignment project

You may have reference material which was not translated in Transit and you only have in the original file format. However, Transit is only able to use translations as reference material if they are in the Transit format. An alignment project makes it possible to import source-language documents and their translations into Transit. Alignment is then carried out, and this generates Transit language pairs which can be used as reference material for other projects.

You can create an alignment project from the resource bar by selecting Reference material | Alignment | Create alignment project. You can find more detailed information about creating alignment projects in chapter 2 of the “Transit NXT Alignment Tool” manual.

Open the project browser by selecting Reference material | Alignment | Project browser. Only alignment projects will be displayed here, if any are available. To open a standard project, select Project | Administration | Open.

3.10.7 Converting Transit XV reference material

Transit NXT can also use reference material from Transit XV projects by converting them.

4How do I convert Transit XV reference material to Transit NXT?

1. Select Reference material | Convert Transit XV reference material to Transit NXT from the resource bar.

Transit displays the Convert reference material to Transit NXT window:

Capture

Fig. 3-79: Convert reference material to Transit NXT window

2. Specify the folder where the Transit XV reference material is located. To do this, click on the … button to the right of the Folder for Transit 3.0/XV reference material field.

Transit displays the Folder for Transit 3.0/XV reference material window.

3. In this window, select the drive and folder for the reference material and confirm your selection by clicking Open.

Transit displays the selected folder in the Folder for Transit 3.0/XV reference material field. When a folder is selected, Transit also takes account of any data contained in subfolders.

4. If you know it, you should now specify the source language which Transit should use as the basis for the reference material conversion. To do this, select the appropriate language from the Source language list. If you do not know the source language, select the — option. In this case, Transit will determine the source language based on the timestamp for the individual segments, i.e. it will select the language where a majority of the segments have an older timestamp as the source language.

Example: a folder which is to be converted contains language pairs for English and French. If the “—“ option is selected, Transit will compare the timestamp for the French and the English segments. If it turns out that, for example, the French segments have an older timestamp in 67 percent of cases, Transit will select French as the source language.

5. Specify where Transit should save the converted reference material. To do this, click on the … button to the right of the Destination folder field.

6. In the Destination folder window, select the drive and folder and confirm your selection by clicking Open.

Transit shows the path for the folder in the Destination folder field. The folder structure of the converted reference material in this folder will match that of the selected Transit XV reference-material folder.

7. Now you can start the reference material conversion process by clicking Start.

Transit displays the Reference material conversion window. The progress bar indicates what percentage of the reference material has already been converted. When Transit has converted the reference material, it displays the following message:

Completed successfully.

8. Close the Reference material conversion window by clicking OK.

9. Close the Convert reference material to Transit NXT window by clicking Close.

Transit has converted the Transit XV reference material. You can now use it as reference material for projects in Transit NXT.

2Unknown file format when converting reference material

If the reference material is in a user-defined file format not yet defined in Transit, the following message will appear during the conversion process:

Unknown file format

To enable Transit to interpret user-defined file formats, the ffd file (*.ffd, file format definition) must be present in the config\sys folder of your Transit installation. If this is not the case, copy the required ffd file into this folder.


2Using Transit XV reference material in Transit NXT

If you are using reference material converted from Transit XV to pretranslate in Transit NXT, it will not be possible for certain markups to be assigned automatically (for information on this, see section 6.5.3 “Markups in converted reference material”).


 

small-book

Document Formatting for Faster Translation Delivery

Download our latest ebook now.

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.

Chinese New Year 2018 : Year of the Dog February 16th 2018

Happy New Year to all our clients doing business with China.

The Chinese New Year 2018 takes place between 16 and 20 of February this year. The lunar new year starts on Feb 16th.

via GIPHY

Our offices in China will be closed from the 15th February to the 21st February. Translation into Chinese will be limited during this time. If you need Chinese translation you should start it now.

Our Chinese office will also be closed on February 28th for Peace Memorial Day.

The Korean Lunar New Year also in on 15-16 of February so our office in this region wil also be closed.

For more information on the Chinese New Years visit : https://www.chinahighlights.com/travelguide/chinese-zodiac/dog.htm

 

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.