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

Creating a Project | Transit Training

29/03/2018/0 Comments/in Transit, Translation /by Star Translation

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 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 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 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 message

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

Wildcards 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 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 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) 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

– 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 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 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 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 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 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 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

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

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:

Create 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 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 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 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 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:

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

Translating Text | Transit Training

29/03/2018/0 Comments/in Transit, Translation /by Star Translation

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:

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

Static and Dynamic Viewers | Transit Training

29/03/2018/0 Comments/in Transit, Translation /by Star Translation

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 window

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

PDF 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 toolbar of the HTML viewer offers the following navigation and view options:

HTML 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 window

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

What is a Dual Fuzzy? Better Translation Memory Matches

21/02/2018/0 Comments/in Transit, Translation /by Star Translation

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

First line – Match quality, icon and file containing the translation suggestion.
Clicking the icon 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 – The reference segment has the same source and target language as the current segment.
Icon – The reference segment has the reverse source and target language in comparison to the current segment.
Icon – The source and the target language of the current segment were both target languages in the project the reference segment origins from.
Icon – 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

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

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

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

– 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

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

Quick Guide to Transit NXT functions to make translation easier

06/02/2018/0 Comments/in Transit, Translation Memory /by Star Translation

Transit NXT Quick Guide

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

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

1. Find

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

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

How do I search for a string?

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

Select the string that you want to find.

2 Select Processing | Search | Find.

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

Find/Replace window, Find tab

3 Enter the search string in the Find field.

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

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

Transit expands the window to display the following options:

Expanded Find window

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

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

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

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

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

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

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

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

– Load is used to call up a saved search.

– Save is used to save the current search.

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

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

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

– Filter displays only the segments that contain the search string.

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

– Highlight all occurrences of the search string in green.

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

–

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

Transit searches for the string.

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

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

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

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

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

Messages if Transit cannot find a string

2. Find/Replace

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

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

How do I find and replace a string?

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

2 Select Processing | Search | Replace.

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

Find/Replace window, Replace tab

3 Enter the search string in the Find field.

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

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

Transit expands the window to display the following options:

Expanded Find/Replace window, Replace tab

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

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

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

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

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

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

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

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

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

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

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

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

Transit searches for the string.

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

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

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

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

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

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

Transit closes the Find/Replace window.

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

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

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

Example: 12 found, 12 replacements made

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

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

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

3.Deleting text

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

Markups which Transit deletes with the text

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

4. Moving or copying text

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

How do I move or copy text with the mouse?

1 Select the text you want to move or copy.

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

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

5. Inserting Unicode characters

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

How do I insert a Unicode character?

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

2 Select Edit | Text | Character map.

Transit displays the Character map window:

Character map window

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

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

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

Transit inserts the character at the cursor position.

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

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

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

6.Selecting the keyboard layout

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

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

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

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

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

Windows taskbar: German is selected as the input language

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

You have the following options for switching language manually:

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

Windows taskbar: switching input language

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

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

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

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

Switching off automatic keyboard-layout selection

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

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

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

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

7. Moving the cursor

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

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

Moving the cursor in internal repetitions mode

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

Moving the cursor in the editor

8. Moving the cursor to specific segments

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

Go to a segment with a specific number

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

Go to a line with a specific number

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

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

Go to a bookmark

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

Go to a retained position

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

Go to a segment for which comments have been entered

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

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

Go to search function

– Segment

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

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

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

3 Click on Go to or press the ENTER key.

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

How do I set a bookmark?

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

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

Transit displays the Bookmark window:

Bookmark window

3 Enter a number for the bookmark.

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

4 Click Set to confirm the settings.

Transit sets the bookmark at the cursor position.

How do I delete a bookmark?

1 Select Edit | Text | Bookmark.

Transit displays the Bookmark window.

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

3 Click Delete to delete this bookmark.

Transit deletes the bookmark specified.

How does Transit retain the current position of the cursor?

1 Move the cursor to the position Transit should retain.

2 Select Edit | Text | Set flag:

Retain position icon

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

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

How do I jump back to the retained position?

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

Go to flag icon

Transit moves the cursor to the retained position.

9. Formatting text manually

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

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

Manual formatting or update markups?

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

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

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

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

How do I format the text manually using formatting commands?

1 Highlight the text that you wish to format.

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

Icons for formatting text manually

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

10. Deactivating write protection for the source language

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

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

Reactivating write protection

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

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

How do I deactivate write protection for the source language?

1 Place the cursor in the source-language text.

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

Transit deactivates write protection for the source language.

3 Correct the errors in the text.

We recommend you reactivate write protection immediately afterwards.

How do I reactivate write protection for the source language?

1 Place the cursor in the source-language text.

2 Click on Read-only under Edit | Text.

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

11. Using AutoText to insert frequently occurring text

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

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

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

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

Select from the list of AutoText entries

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

How do I create an AutoText entry?

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

2 Select Edit | Text | AutoText.

Transit displays the AutoText window:

AutoText window

– top field – Name of AutoText entry.

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

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

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

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

AutoText window with name of AutoText entered

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

4 To confirm your entry, click Add.

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

Saving AutoText entries

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

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

How do I enter AutoText while translating?

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

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

How do I select an AutoText entry from the list?

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

2 Select Edit | Text | AutoText.

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

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

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

4 Click Insert to insert the text into your translation.

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

How do I delete an AutoText entry?

1 Select Edit | Text | AutoText.

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

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

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

3 Click Delete to delete the AutoText entry.

Transit deletes the AutoText entry.

4 Close the AutoText window by clicking OK.

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

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

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

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

File navigation window

13. RC editor

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

The working environment when using the RC editor

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

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

RC editor – toolbar functions

How do I group and edit multiple window elements?

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

The element is highlighted with blue resizing handles.

2 Press and hold the CTRL key.

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

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

Grouping window elements in the RC editor

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

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

AutoResize with resource DLLs on WPF basis

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

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

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

1 Open or unpack the project.

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

Transit shows the File navigation window.

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

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

Transit opens the selected language file in the Transit editor.

5 Translate the text.

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

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

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

Example of inserting accelerator keys during translation:

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

Accelerator keys in projects containing binary resource files

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

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

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

Using Machine Translation with STAR Transit

31/01/2018/0 Comments/in Machine Translation, Transit, Translation /by Star Translation

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 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 – 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

STAR/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 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 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 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 suggestion

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

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.

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

Translation Memory System – Introduction.

15/05/2017/0 Comments/in Localization, Transit, Translation /by Star Translation

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

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

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

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

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

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

Upgrading to Windows 10 and Transit NXT

05/07/2016/0 Comments/in Transit /by Graham O'Mahony

Upgrade to Windows 10, keep Transit NXT

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

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

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

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

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

Upgrade auf MS Windows 10

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

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

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

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

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

The STAR Team

Image: Windows logo, copyright of Microsoft

New Languages Supported in Transit NXT Service Pack 9

17/06/2016/0 Comments/in Languages, Transit /by Graham O'Mahony

New Languages Supported in SP9

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

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

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

Eight Additional Languages

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

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

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

New Asian Languages in SP9

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

New European Languages in SP9

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

Introducing Maori for SP9

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

Spanish Worldwide

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

The STAR Team

STAR Group Donates Transit to Universities in Ho Chi Minh City

23/03/2016/0 Comments/in Transit, Translation /by Graham O'Mahony

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

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

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

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

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

The STAR Team

Creating a Project in Transit

2. Creating a new project

3. Create a new project based on an existing project

4. Creating a new project via the resource bar

5. Creating a new project template

6. Deleting a project template

7. Changing the default settings for new projects

Translating text

1. Update markers in the Transit editor

2. Segments in the Transit editor

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

4. Joining segments virtually and split virtually joined segments

5. Not permitting segments as reference material

Static and dynamic viewers

1.PDF viewer/Word preview

2.HTML viewer

3.Multimedia viewer

4. Dynamic preview of MS Office files

5.Synchronised View – User preferences

Dual Fuzzy

1. Dual Fuzzy Overview

2.Building the fuzzy index and accepting suggestions

Dual Fuzzy – fixed windows and bubble windows

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

3.Dual Fuzzy–User preferences

4. Fuzzy search settings

Transit NXT Quick Guide

1. Find

2. Find/Replace

3.Deleting text

4. Moving or copying text

5. Inserting Unicode characters

6.Selecting the keyboard layout

7. Moving the cursor

8. Moving the cursor to specific segments

9. Formatting text manually

10. Deactivating write protection for the source language

11. Using AutoText to insert frequently occurring text

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

13. RC editor

Machine Translation and Transit NXT

1. Overview

2. User preferences for Editor MT

3. Entering the API key for the MT system

4. Manually requesting a machine translation

5. Import MT suggestions in the fuzzy window

Upgrade to Windows 10, keep Transit NXT

Upgrade auf MS Windows 10

New Languages Supported in SP9

Eight Additional Languages

New Asian Languages in SP9

New European Languages in SP9

Introducing Maori for SP9

Spanish Worldwide

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

STAR TRANSLATION

CONTACT SALES

TRANSLATION SERVICES

MARKETING

TECHNOLOGY