1. New version of WebTransit

WebTransit version 2.6.0.876 supports the following new features:

Additionally supported FileZilla Server versions

As of this release, WebTransit supports FileZilla Server up to version 1.8.1.

Message if selected folder ZIP transfer is write-protected

When checking the connection, WebTransit now also displays an error message if the user has selected a write-protected folder for ZIP transfer.

NOTE: When creating a new connection, WebTransit automatically suggests a suitable ZIP transfer folder. We recommend to accept this folder unchanged.
Exception: In multi-user mode, a shared network folder must be used and can therefore not be suggested automatically. In this mode, it is up to the administrator to define an appropriate folder and to inform the users.

1. Possibility to assign "Check pretranslation" status to all pretranslated segments

By default, the Translated status is assigned to pretranslated segments during import. However, it is also possible to assign a higher status ("Pretranslation" project settings, Status for pretranslated segments options).

As of this Service Pack Update, the Check pretranslation status can also be selected there. This may be useful if all pretranslations require special attention and a complete check is necessary (e.g. if questionable reference material is used).

NOTE: The Check pretranslation status is normally used to indicate segments that have been pretranslated in a special way (e.g. segments with automatically adjusted numbers and markups, or pretranslations using reference segments with opposite language direction, etc.).

2. Import MT enhancements

Multilingual projects: Target language-specific determination of the segments to be machine-translated

Previously, Transit determined by default whether a segment needed to be machine-translated across all languages: If machine translation was required for one of the target languages, the segment was machine-translated into all target languages.

With this Service Pack Update, the default has been changed to determine the need for machine translation for each target language individually. This can significantly reduce the MT volume per language if the pretranslation rates per language are quite different.

NOTE: This change is not relevant for projects with only one target language.

Insert MT in translation extract

If translation extracts are created during import and the Insert MT suggestions in target language during import option is used (» Insert MT suggestions directly during import), the MT suggestions are now inserted in the translation extract also.

Handling of MT in repeated project imports

Until now, when performing a 2nd import, existing MT extracts were discarded and a completely new machine translation was requested.

As of this Service Pack Update, the import MT works "cumulatively": During the 2nd import, MT is only requested for new segments that have not yet been machine-translated.

If the import is repeated completely (i.e. with re-creation of the source language files), the user can decide whether the existing MT extracts should be reused. In this case, Transit displays the following message:
A machine translation has already been carried out.
Do you want to discard it and request a completely new machine translation?

With Yes existing MT extracts will be deleted and a completely new machine translation will be performed (as before).

With No existing MT extracts will be retained and only new segments will be machine-translated.

3. Export: Detailed colours for fuzzy matches inserted during import

Service Pack 16 introduced the possibility to use special text colours to indicate fuzzy matches inserted during import (» Export: Special colours for MT and fuzzy matches inserted during import and » Inserting fuzzy matches directly during import).

As of this Service Pack Update, this feature has become more detailed: Different fuzzy ranges can be exported in different colours. For this purpose, Transit now displays four entries in the "Fonts and colours" user preferences, e.g.:

Export font: segments to be checked (inserted fuzzies during import) 99-95%

Export font: segments to be checked (inserted fuzzies during import) 94-90%

Export font: segments to be checked (inserted fuzzies during import) 89-80%

Export font: segments to be checked (inserted fuzzies during import) 79-70%

The fuzzy ranges displayed are based on the report options assigned to the current project ("Report settings" project settings).

4. Value lists for specifying default values

When specifying default values for new terminology, the values can now be selected from a value list (if a value list is assigned to the corresponding field).

This applies to

project-specific default values in the project settings

general default values in the dictionary settings

1. Additional web search services and enhanced service home page call-up

Additional web search services

Transit/TermStar’s web search now supports the following additional services:

ESCO ("European multilingual classification of Skills, Competences and Occupations" provided by the European Commission)

France Terme (French terminology provided by the Délégation générale à la langue française et aux langues de France)

GDT ("Grand dictionnaire terminologique" provided by the Office québécois de la langue française)

LINGUA-PC (German-French terminology provided by the State Chancellery of Canton of Bern)

SCTA Semamdy (trilingual terminology provided by the Belgian "Service central de traduction allemande")

TermCat Cercaterm (terminology provided by the Catalan Centre de Terminologia)

Call up service home pages per click on service name

The home page of each service can now be accessed by clicking on the name of the service. Therefore, the "globe" icon is no longer necessary and has been removed.

2. Project management

Deleting working folder if project wizard is cancelled

When creating a project, Transit automatically creates a project-specific working folder in the file system.

As of this service pack, the working folder is deleted again if the user cancels the project wizard and the working folder does not yet contain any data.

In this way, Transit prevents an unused working folder from being left behind if the user has accidentally started to create a project.

Import: Use project language pairs as reference material for additional files

When subsequently adding and importing files to a project, you can now decide whether the project’s already translated files should be used as reference material for pretranslation. Transit will display a corresponding message during the import (Do you also want to use the already translated files of the project as reference material?).

Export: Individually prevent existing files from being overwritten

If you repeat an export, the new export would overwrite existing files and Transit displays a corresponding message for each file. Previously, No had the same effect as Cancel: Transit stopped the export and left all other existing files unchanged.

As of this Service Pack, the No button causes Transit to kip the file and to continue the export with the next file. The function of Cancel remains unchanged (stopping the export).

Export: Special colours for MT and fuzzy matches inserted during import

When exporting with colours for "Segment status after import", you can now use special text colours to indicate machine translations and fuzzy matches inserted during import (» Insert MT suggestions directly during import and » Inserting fuzzy matches directly during import). To do so, check the Colours for MT and fuzzy matches inserted during import option in the Export project window.

You can specify these colours in the "Fonts and colours" user preferences by changing the colours for the following entries:

Export font: segments to be checked (inserted fuzzies during import)

Export font: segments to be checked (inserted MT during import)

3. Transit Editor

Transfer selected text from source language segment

So far, you can transfer the entire content of the source language segment to the target language (with CTRL + ALT + Backspace or Reinsert source language content in the source language context menu).

As of this Service Pack, you can also do this for parts of the source language segment. To do so, select text within the source language segment, right-click your selection and select Insert selected text in target language in the context menu.

This will insert the selected text in the target language segment: If you have selected text in the target language segment, it will be replaced by the source language text. Otherwise, the source language text will be added at the cursor position.

Open all files with one click

With the new Open all (global) button in the Open language pairs window you can open all language files (except translation extracts) with a single mouse click.

Individual font sizes per window

Previously, the same font size was used for all window content.

As of this Service Pack, you can set individual font sizes in the "Colours and fonts" user preferences for language pairs, Fuzzy windows, Concordance search and Dynamic Linking windows, Segment info window, Markup window, and for bubble windows for URLs, indices, and footnotes. In addition, you can select an individual font size to display path information and TM Container attributes for fuzzy matches and concordance search matches.

Behaviour after confirming a segment as translated

When you confirm a segment as translated, Transit navigates to the next segment to be translated (i.e. the next segment which you must edit and/or confirm).

Under the Confirm icon, you can now choose between the following options to determine where Transit navigates to after confirming a segment:

After confirmation: Remain in segment: Transit remains in the segment that you have just confirmed.

After confirmation: Go to next segment: Transit navigates to the immediately following editable segment (regardless of its segment status)

After confirmation: Go to next segment to be translated: Behaviour as before (Transit navigates to the next segment that needs to be edited and/or confirmed)

NOTE: Similar options are also available for proofreading (» Behaviour after confirming a segment as checked).

4. Machine translation

Handling of newlines within segments

For machine translation, newlines within segments have not been taken into account. Therefore newlines had to be added manually to the machine translation results.

As of this Service Pack, these newlines are "translated" with the text and the MT service tries to place them in the appropriate position.

MT support for controlled languages

The controlled languages English (simplified) (language code EN1), French (rationalised) (language code FR1) and German (plain language) (language code DE1) have not been supported by standard MT services.

As of this Service Pack, these controlled languages can now be machine translated by automatically being mapped to the MT engines for the corresponding main language (i.e. ENU, FRA or DEU).

NOTE: Controlled languages have a reduced vocabulary and strict grammar rules that usually are not taken into account by MT engines (unless they have been specially trained). Therefore, MT results usually do not comply with the rules of controlled languages and need to be heavily revised.

5. Fuzzy match: Automatically insert best match / stay in target language window

If requesting a fuzzy match with ALT + INS, Transit switches to the fuzzy window by default. There you can select the desired fuzzy match and accept it with ALT + ENTER (i.e. insert it into the target language segment).

As of this Service Pack, you can specify in the "Dual Fuzzy" user preferences that Transit automatically inserts the best fuzzy match into the target language segment (Use ALT + ENTER to automatically insert best fuzzy match option).

In this case, it may make sense to also select the Stay in target language window even if fuzzy match option: Then Transit will not switch to the fuzzy window, but will remain in the target language segment so that you can edit and confirm it straight away.

TIP: If you still want to switch to the fuzzy window (e.g. to select another fuzzy match), press ALT + 5. Then you can switch back to the target language window with ALT + 2.

6. Transfer highlighted text from fuzzy match or concordance search

So far, you can transfer a complete fuzzy match or concordance search match into the target language.

As of this Service Pack, you can also transfer parts of the match. To do this, select text within the match, right-click your selection and select the following in the context menu:

For fuzzy matches: Replace target segment with selected text
This option will replace the previous content of the current segment with the selected text.

For concordance search matches: Insert selected text in target language
This option will insert the selected text in the current segment: If you have selected text in the target language segment, it will be replaced by the text from the match. Otherwise, the text from the match is added at the cursor position.

7. Quality assurance

Quality report: Include editing distance for revisions

In the quality report including segment revisions, the editing distance of the revisions is now also indicated. The distance is output in these metrics:

Similarity (fuzzy algorithm): Percentage of similarity, calculated as for fuzzy matches in transit (value range 0 -100%, high value = high similarity = fewer changes)

Levenshtein distance: Number of operations required for the change (values > 0, high value = more changes = more differences)

Levenshtein similarity: Similarity relative to the total number of characters, calculated based on the Levenshtein distance (value range 0 - 1, high value = high similarity = fewer changes)

Exclude locked segments from spellcheck, terminology check, and format check

As of this Service Pack, you can skip segments that are locked for the following checks:

Spellcheck: Select Do not check locked segments under Options.

Terminology check: Select Do not check locked segments under Start.

Format check: Select Do not check locked segments under Start.

This prevents errors from being displayed for segments that you cannot correct because they are locked.

Preset "Log as revision" for proofreading and unpacking translations

In order to track revision steps, the Log as revision option must be selected in proofreading mode and when unpacking translations.

As of this Service Pack, you can specify whether this option shall be automatically selected when you switch to proofreading mode or when you unpack a translation. To do so, select Proofreading mode / unpacking translations: Preset "Log as revision" in the "Format check" project settings.

This setting is a preselection. In proofreading mode and when unpacking projects, you can still decide whether Transit shall log changes as a revision.

Behaviour after confirming a segment as checked

As for translation, they can also choose for proofreading where Transit navigates to after confirming a segment. You will find similar options under the On/Off icon for proofreading (for details see » Behaviour after confirming a segment as translated).

8. Report Manager

Preset "Show repetition column" for regarding internal repetitions per project

When regarding internal repetitions per project, the Show repetition column option had to be reselected for each report.

As of this Service Pack, a PRJ parameter can be used to specify whether this option shall be automatically selected / deselected when generating a report with internal repetitions per project. This setting is a preselection. When generating reports, you can still decide whether to show a repetition column.

NOTE: For internal repetitions regarded file by file, the setting was always retained and automatically reused when generating the next report.

9. Modify reference material

As of this Service Pack, morphological search is supported for the Modifying reference material feature (Resource bar, Reference material). With morphological search, Transit also finds declined or conjugated forms of the search term.

For non-exact matches, the following text now indicates that the segment requires special attention after replacement:
Fuzzy/morpho match. Check carefully after replacing!

In this context, the replace buttons have been extended and improved as follows:

Replace & next: This button replaces the found text and navigates to the next hit. This function is only active for exact matches, i.e. if the search text matches the found text exactly.

Replace: This button replaces the found text, but does not navigate to the next hit. This allows you to check the segment after the replacement and adapt it if necessary.

Replace all exact matches: This button replaces all exact matches and leaves segments with non-exact matches unchanged. You can then use Replace to go through the non-exact matches one by one, replacing and adjusting them if necessary.

10. TM-Container

TMC export: Select content by attribute values / file names

When exporting from a TM container, the content to be exported was previously selected with the help of TM filters.

From now on, the content to be exported can also be selected via attribute values and file names.

To do so, select the TM Container (instead of its TM filter) in the TM Container administration and click Export. Transit then displays a window where you can select the desired files (similar to opening or deleting files from the TM container).

Reassign attribute values to imported TM Container contents

As of this service pack, it is possible to change attribute values of already imported contents.

To do so, select the TM Container in the TM Container administration and click Reassign values. Transit then displays a window where you can select the desired files (similar to opening, deleting, or exporting files from the TM container).

In the next window you can specify whether and how the assigned attribute values shall be modified. Depending on the attribute settings, you have the following options:

No modification: Transit will leave the already assigned attribute value(s) unchanged. After the modification, the same value(s) will be assigned as before.

Clear value: Transit will remove the already assigned attribute value(s). After the modification, no value will be assigned for this attribute.

Replace value + value selection in New/added value column: Transit will replace the already assigned attribute value(s) by the selected value(s). After the modification, only the newly selected value(s) will be assigned for this attribute.

Add value + value selection in New/added value column: Transit will add the selected value(s) to the already assigned value(s). After the modification, the previous and the newly selected values will be assigned for this attribute.

Enhanced import progress display when using remote TM Containers

The progress display for project import with reference material on a remote TMC has been improved: First the Progress bar (Remote) is displayed for the process on the remote computer. Then another progress bar is displayed for the processes on your local computer.

11. TermStar

Additional key combination for non-breaking space: CTRL + Space
In TermStar, it is now possible to enter a non-breaking space directly by using the shortcut CTRL + Space.

Additional key combination for editing on the right page: CTRL + ENTER
It is now possible to edit a data record on the right page by using the shortcut CTRL + ENTER.

12. UI changes

The following UI elements have been renamed to clarify their meaning (no functional changes):

User preferences "Dual Fuzzy": "Update Transit matches" renamed to "Update matches"

Resource "Interfaces": "Quicksilver" renamed to "Interleaf/Quicksilver"

Project settings "Format check" and "Format check" options

"Check that UPPERCASE segments are translated as UPPERCASE" shortened to "Check if UPPERCASE is kept"

"Check that segments with standard capitalisation are not translated as UPPERCASE" shortened to "Check if UPPERCASE is used instead of standard capitalisation"

Project settings "Segmentation"

"Check segmentation after import" renamed to "Check abbreviations for segmentation during import"
Correspondingly, the "Check segmentation" window has been renamed to "Check abbreviations for segmentation".

"Do not segment after ;" renamed to "Do not segment after semicolon ;"

"Do not segment after :" renamed to "Do not segment after colon :"

"Do not segment after numbered lists (e.g. 1.)" renamed to "Do not segment after ordinal numbers 1. 2. 3."

File type options: "Paragraph styles" options group renamed to "Paragraph styles / character styles" (due to » Word: Character styles not to be translated). Correspondingly, the "Paragraph style list" has been renamed to "Styles list".

German UI only: User preferences "Dual concordance" and " Dynamic Linking":

"Anzahl der Treffer anzeigen" renamed to "Anzahl der angezeigten Treffer"

"Optionen für die duale Konkoranzsuche" renamed to "Aktionen beim Öffnen des Dialogs"

13. Support of Microsoft SQL Server 2022 and Microsoft SQL Server 2022 Express

Addendum to » Service Pack 15 (December 2022): Since Service Pack 15, TermStar allows to run TermStar databases on Microsoft SQL Server 2022 and Microsoft SQL Server 2022 Express.

NOTE: The support of Microsoft SQL Server 2022 is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

1. Support of Adobe InDesign 2023

Transit and the required plug-in InDesign Gate now support InDesign 2023 (Windows and Mac).

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

2. Support of additional QuickSilver versions

Transit now supports additional versions of QuickSilver up to 3.8.1.

NOTE: Interleaf/QuickSilver and Transit exchange documents in ASCII format. To do so, save the document as an ASCII file in Interleaf/Quicksilver and import it into Transit. Once the ASCII files have been translated, export them from Transit and save them as binary files in Interleaf/Quicksilver.

3. Support of COTI packages

Transit now supports the COTI interface for exchanging files to be translated with authoring systems.

NOTE: In contrast to project exchange formats such as XLIFF, a COTI package is not a translation project with language pairs, but contains the translatable files in their original format. Therefore, once unpacked, these files are imported (i.e. segmented and filtered language pairs created) so that they can be translated. Once translated, the files are exported again and the exported files are packed back into the COTI package in the original format.

For details refer to the » Document “Transit: Tips & Tricks for All File Formats”.

4. Exchange formats: Support of multilingual projects with one target language per file

Projects received from other systems (e.g. MemoQ or a COTI package) may contain several files and several target languages, whereby each file should only be translated into one of the target languages.

Transit recognises this automatically when unpacking and takes it into account in the following functions:

Opening language pairs

Creating project statistics

Forwarding the project

Importing / exporting projects from COTI packages

For details refer to the appendix of » Document “Transit: Tips & Tricks for All File Formats”.

5. DeepL glossary upload: Automatically removed leading/trailing whitespaces

When uploading DeepL glossaries, leading and/or trailing whitespaces are now automatically removed from terms. In certain cases, these whitespaces violated the requirements of DeepL and could lead to problems during the upload.

6. "Extracts" project settings: Improved dialog

In the "Extracts" project setting, the arrangement and names of options have been improved to make their meaning clearer (no functional change). The settings are used to control the creation of the project-specific reference extract and translation extract.

7. Indicate reference language direction for concordance search hits

Since Service Pack 7, Transit displays the language direction of references in the Fuzzy and Segment info windows (» Enhancements in the Transit Editor).

From now on, the language direction is also indicated for concordance search hits (icons for identical, vice-versa, indirect, and Pivot direction).

NOTE: You can configure whether the icon is displayed using the "Dual Fuzzy" user preferences (Show icon for language direction option). The option applies to fuzzy matches and to concordance search hits.

8. Additional and updated OpenOffice spellcheck dictionaries

Transit now supports OpenOffice-based spell checking also for Gaelic (Ireland), Persian, Spanish (Cuba), Spanish (US), Spanish (Venezuela), and Welsh. Additionally, the spellcheck dictionaries for 12 languages have been updated and improved.

9. J2450: Changed name of the error type SE

In all UI languages except German, the name of the error type SE is now adapted to the common use in German as "Structural error" (previously "Syntactic error").

NOTE: In the German UI, the error type SE was already named as "Strukturfehler" and will therefore remain unchanged.

10. TermStar

This Service Pack Update does not contain additional new features for TermStar. You will therefore find the latest new features for TermStar in » Service Pack 15 (December 2022).

1. Support of Windows 11 and Windows Server 2022

Transit/TermStar can be installed and run on Windows 11 and Windows Server 2022.

2. Support of Adobe FrameMaker 2022

Transit and the recommended plug-in FMGate now support FrameMaker 2022.

For 64-bit versions of FrameMaker (such as FrameMaker 2020 and FrameMaker 2022), the latest plug-in FMGate is required (version 46 or higher).

The plug-in is available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing FMGate and sharing data with Transit.

3. Support of Adobe InDesign 2022

Transit and the required plug-in InDesign Gate now support InDesign 2022 (Windows and Mac).

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

NOTE: The plug-ins for InDesign 2022 were already released in April 2022.

4. Additionally supported working languages

Transit/TermStar now supports the following working languages:

Central Kurdish / Sorani (language code KUR)

Spanish (Cuba) (language code ESK)

Luxembourgish (language code LBX)

Northern Kurdish / Kurmanji (language code KMR)

5. Additional web search service for synonyms

As an additional service, Transit/TermStar’s web search now supports monolingual Woxikon synonym dictionaries. This allows you to find synonyms for the marked word directly from the Transit editor (context menu entry Web search or CTRL + ALT + W).

NOTE: The multilingual Woxikon online dictionary with source / target language terms is already supported since Service Pack 11 (» Additional web search services).

6. Enhanced MT results for German (Switzerland)

As of Service Pack 15, Transit by default adapts the MT results for German (Switzerland) (language code DES) to the Swiss German spelling by converting the ß character to ss.

This simplifies the post-editing of machine-translated segments if the MT provider does not take the Swiss language variant into account.

7. Support of Globalese

As additional Editor MT service, Transit now supports Globalese.

The Editor MT settings are specified in the Machine translation tab of the user preferences. There you enter the URL for the service and the API key you receive from the MT service provider.

8. Enhanced support of DeepL Pro

Additionally supported languages

DeepL Pro can now generate MT suggestions also for the following working languages: Indonesian, Turkish, Ukrainian

Support of "formal/informal" feature

For some languages, DeepL now allows to choose between formal and informal tone of voice. In Transit’s MT settings for DeepL, you can now select the tone of voice to be used (e. g. Resource bar, Machine translation | DeepL or User preferences | Machine translation, DeepL Pro entry, click …).

Support of "glossary" feature

For some languages, DeepL supports bilingual glossaries. In Transit’s MT settings for DeepL, you can now select uploaded glossaries to be used for machine translation (e.g. Resource bar, Machine translation | DeepL or User preferences | Machine translation, DeepL Pro entry, click …).

You can also upload glossary files to DeepL and delete your glossaries from DeepL.

NOTES:

DeepL does not distinguish between language variants, i.e. one glossary is used for the main language and all variants. If you need to differentiate (e.g. between UK and US English), you need to create two separate glossaries, upload both and use them on a case-by-case basis.

To upload a glossary, you need a glossary file that meets the requirements of DeepL (Unicode, exactly one source language term and one target language term per line, source / target language separated by tab, no source language homonyms).

DeepL does not support glossary updates. If you want to correct or update a glossary, you must delete the uploaded glossary and re-upload the changed glossary file under the same name.

9. Enhanced support of KantanMT

KantanMT supports the usage of alias names for engines as an alternative to full engine names. The type of name KantanMT uses for your machine translations is defined in your KantanMT account.

You can now specify in Transit's MT settings for KantanMT whether Transit should access KantanMT via alias names or full engine names (e.g. Resource bar, Machine translation | KantanMT or User preferences | Machine translation, KantanMT entry, click …).

10. Additional segment filter options ("Segment info" tab)

Filter for draft segments

You can now filter for segments marked as draft. To do so, check the Segment status option and select Draft from the status list.

Filtering for draft segments is also supported by the Quick segment filter. You can call up the Quick segment filter for a language file by double-clicking the icon in the header of the info column.

NOTE: The Draft status has been implemented with Service Pack 14 to mark segments that you have not yet finished translating (e.g. if you want to clarify something or work on the wording).
The Draft status can be assigned to the current segment by selecting Processing | Translate | Assign status | Draft.
When used as reference material, segments with Draft status are considered as untranslated segments (i.e. normally not displayed as fuzzy matches / not displayed in the concordance search / not used for pretranslations if a minimum status is set).

Filter for physical reference files used

You can now filter for segments that were translated in the current project with the help of the specified physical reference file (Used physical ref. file option). This corresponds to the path displayed second (in brackets) in the Segment info window.

NOTE: In contrast to this new option, the already supported Used reference material option filters for segments with translations that were translated for the first time in the specified reference file. This corresponds to the path displayed first in the Segment info window.

Filter out markup segments

You can now hide markup segments using the segment filter (Hide markup segments option).

NOTE: As an alternative to this filter criterion, you can also hide markup segments by deselecting them in the view settings (Display | Text/Markups | Options | Markup segments).

The former Hide protected segments option (available before Service Pack 15) corresponds to the new Hide markup segments option combined with the new No locked segments option (» Filter for locked segments).

Additional options for filter on fuzzy quality:

It is now also possible to filter for segments that have fuzzy matches within a specified quality range (From ... to option).

If you have selected Lower than, Transit normally also displays segments without fuzzy matches (corresponds to a quality of 0%). As of this Service Pack, you can now hide such segments by unchecking the new Also segments without fuzzy matches option.

Filter for locked segments

You can now filter for locked or unlocked segments. To do, check Locked segments and one of the following options:

Only locked segments: Displays locked segments only / hides unlocked segments

No locked segments: Hides locked segments / displays unlocked segments

NOTES: This filter criterion refers to segments that have been locked by a user (segment context menu entry Locked segment (disallow editing)). To filter out markup segments, you can use the new Hide markup segments option (» Filter out markup segments).

11. Open working folder directly from Transit

The working folder is used to save all the files for this project (e.g. language pair and settings files that were saved in Project scope).

You can display the contents of the working folder directly from Transit. To do so, click the Open button at the top of the Folders / Filenames project settings. This opens the working folder in the Windows file explorer, with which you can copy files into the folder or copy them from the folder to another location.

12. Append target language codes to export filenames

By default, Transit leaves the filenames unchanged, i.e. the exported files are named the same as the imported files.

Append target language codes to export filenames option

However, you can specify in the Folders / Filenames project settings that Transit appends the language codes to the target language filenames when exporting (Transit language code, ISO language code, or ISO language and country code). You can also specify the delimiter to be used to separate the language code from the filename (underscore, minus, full stop, space, or no delimiter). Below these settings, Transit displays an example of a filename that would result from the settings.

NOTE: The settings only apply to the export of target language files. If you export the source language, Transit uses the unchanged original filenames.

Replace corresponding suffix in original language filenames options

In addition, you can determine whether a corresponding language code should be replaced in the source language filename.

Export all languages into the same folder option

By default, the files for each target language are saved in a separate subfolder.

However, if target language codes are appended to filenames, you can specify that the files of all target languages are exported into the same folder.

13. Enhanced Report Manager

Consider internal repetitions for pretranslated segments

Normally, Internal Repetitions shall not be taken into account for pretranslated segments.

However, you can now take them into account by checking the new Consider int. rep. also for pretrans. segments on the Report options Weighting factors tab.

Analysing and weighting machine-translated segments, locked segments and segments with higher import status

With Service Pack 15, additional segment properties can be analysed, output as separate columns and weighted separately.

To do so, you can use the following options added to the Report options Weighting factors tab:

Machine-translated segments:
For import reports: Segments for which the machine translation was inserted during the import are displayed and weighted in a separate column.
For translation reports: Segments that were machine-translated during import or translated by the user with the help of a MT suggestion are displayed and weighted in a separate column.

Locked segments: Segments that are locked at the time of the analysis are displayed and weighted in a separate column.

Pretranslated segments with import status ...: With these options, segments that have been pretranslated and assigned a higher status (e.g. Spellchecked by applying the status of the reference segment) are displayed and weighted in separate columns.

For details refer to the » Transit User Guide.

Tooltips for report column headers

In the Report Manager window, Transit now displays tooltips for the column headers to clarify their meaning (e.g. "machine translated" for MT column.).

Changed tab names in the Report options window:

The tabs in the Report options window have been renamed to clarify their meaning:

Fuzzy/Repetition tab renamed to Weighting factors

Prices tab renamed to Prices / Expansion factor

14. Additional options for Office projects

For Office projects, you can now define additional file type settings:

Create files for PDF viewer during import: If you check this option, the Create files for PDF viewer during import in the Import project window is automatically checked (supported for Word, PowerPoint and Visio files). This setting is a default. When starting the import, you can still decide whether Transit shall create PDF files or not.

File type options

Edit URLs in separate segments: If you check this option, Transit displays editable URLs in separate segments. If the option is unchecked, Transit displays the URLs within segments as an editable part of the hyperlink.

Word: Translate custom document properties: If you check this option, custom document properties can be translated. If the option is unchecked, Custom document properties will remain in the source language.
NOTE: Custom document properties are part of the Word declarations. The option is therefore only relevant if declarations are translated (i.e. if the option Do not translate declarations is not checked).

Word: Character styles not to be translated

Since Service Pack 7, you can define paragraph styles that are not to be translated (file type options, Ignore paragraph styles from list option, » Enhancements in Project settings / File type settings).

For Word projects, you can now also select character formats. Contents formatted with these character formats are then not displayed for translation and will remain in the source language.

15. Enhanced Transit Editor

Reset segment via context menu

It has always been possible to reset segment content and status so that the segment has the original language content and the status Not translated again (e.g. by CTRL + ALT + Backspace or Processing | Translate | Assign status | Not translated or Review | Proofreading | Assign status | Not translated).

As an additional option, you can now reset one or multiple segments via context menu: Right-click the segment or the selected segments to be reset, then select Reinsert source language content from the context menu. If you have selected multiple segments, Transit displays a confirmation message to prevent accidental resetting.

Enhanced display of fuzzy matches from reference extract

For fuzzy matches based on a reference extract generated from a TM Container, the fuzzy window now also displays information on the original TM Container segment (TM Container name, TM Container filename, and attributes). The extract file name is displayed as a prefix without a path and in square brackets.

Example: [_AEXTR_1] TMCTecDoc/FirstSteps (Subject=Operation, Audience=Experts).

The complete information on the reference extract file (including path) is displayed in the Segment info window.

16. Project exchange: Pack multimedia files

When packing a project, it is now possible to pack multimedia files that are used in TermStar dictionaries and have been saved in the database.

Do to so, open the TermStar options when packing a project and select Pack multimedia files.

NOTES:

Saving multimedia files in the database can be configured in the dictionary settings (Miscellaneous tab, Save in database option). This option is supported for databases created with Service Pack 9 or later, » Saving multimedia files in the database).

Multimedia files that are only saved in the file system are not packed.

17. Project template based on project

As of Service Pack, you can create project templates also based on a project.

Do to so, open the project, select Project | Template | Create and then select the Based on current project option.

18. Automatically open language pairs when opening a project

You can now specify if / which language pairs are automatically opened when opening a project (User preferences | Startup settings, Action when opening a project options).

19. TM-Container: Remove segment comments / revision steps on import

Segment comments and revision steps are usually only relevant while a translation project is being carried out. In the TM Container, segment comments and revision steps are often not needed or are unwanted.

From now on, you can decide whether segment comments and revision steps shall be removed when importing reference material into the TM container.

20. UI changes

The following UI elements have been renamed to clarify their meaning (no functional changes):

Transit:

Import project window: File type settings button renamed to File type options

Segment info window: Line Pretrans. qual. renamed to Quality (pretrans/fuzzy)

Project settings "Folders" renamed to "Folders / Filenames" (see also » Open working folder directly from Transit and » Append target language codes to export filenames)

Resource "Machine translation": Systran entry renamed to MT via hotfolder

Improved message when importing only a part of the project files

Improved messages when deleting projects

Report options window: See » Changed tab names in the Report options window:

TermStar:

Data record filter: Display empty fields option renamed to Also display when field is empty

In addition, the German display names for the following languages have been changed:

Weißrussisch (language code BEL) changed to Belarussisch

Französisch (Rationalised) (language code FR1) changed to Französisch (Rationalisé)

Griechisch (Alt) (language code GRC) changed to Griechisch (Altgriechisch)

21. Copy licence number to clipboard

Previously, the licence number was automatically copied to the clipboard when the About Transit or About TermStar window was opened.

From now on, the licence number is no longer copied automatically, but by clicking the Copy licence number to clipboard button in the About Transit / About TermStar window. This prevents existing clipboard contents from being replaced inadvertently by opening the About Transit / About TermStar window.

1. Support of Microsoft Office 2021

Transit now supports the translation of Microsoft Office 2021 documents (including Word 2021, Excel 2021, and PowerPoint 2021).

1. Shortcuts for machine translation and locking / unlocking segments

Request machine translation: ALT + M

It is now possible to request a machine translation for the current segment via a shortcut (corresponds to the Request machine translation context menu item).

So now you have two options to get translation suggestions via shortcut:

ALT + Enter: Fuzzy matches from the translation memory and, if necessary, MT suggestions (as before).

ALT + M: MT suggestions only (new)

NOTE: For the use of MT in the editor, an MT service must be configured (Resource bar, Machine translation).

Lock / unlock segments: CTRL + ALT + L

Locking segments prevents the segments from being accidentally edited until they are unlocked again.

Previously, segments could be locked / unlocked via the context menu only.

Now segments can also be locked CTRL + ALT + L: If the selected segment / all selected segments are unlocked, CTRL + ALT + L locks the segments (and vice versa).

If your selection contains both locked and unlocked segments, CTRL + ALT + L locks all selected segments.

2. TM-Container: Container name displayed in settings dialogue

In the TM Container settings window you can define attributes, filters, profiles, roles, and users for each TM container individually (Resource bar, Reference material | TM Containers, click Settings).

From now on the name of the container is shown in the window title so that you can always make sure that you define the settings of the correct TM container.

NOTE: The support of TM Containers is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

3. Display MT disclaimer again for interactive MT request if skipped before

Depending on the user preferences, Transit displays a message before sending data to an MT service provider. This may prevent you from accidentally sending confidential data to third parties and/or violating confidentiality agreements.

If you rejected MT usage (Skip machine translation button), the setting was valid for the current project session: To use MT anyway (e.g. for an individual, non-confidential segment), the project had to be closed and reopened.

As of this update, the MT disclaimer is displayed every time you explicitly request MT and have not yet agreed to it.

1. TermStar: Create cross-references to Internet addresses

When editing terminology, it is now possible to format any text in text fields as a cross-reference to Internet addresses (context menu Create cross-reference | To Internet address).

When you click such a cross-reference, TermStar starts your Internet browser and opens the corresponding Internet address.

NOTES:

Internet addresses entered in the Cross-reference field were already recognised and automatically treated as an Internet cross-reference.

In the Term field, cross-references are not supported.

2. TermStar: Modify cross-references

With this Update, also cross-references to data records and Internet addresses can be modified (context menu Modify cross-reference).

Depending on the cross-reference type, a corresponding window is opened (for data record selection or URL input).

1. Support of AutoCAD 2021 / AutoCAD 2022

Transit now supports to translate dxf files from AutoCAD 2021 and AutoCAD 2022.

2. Support of Adobe FrameMaker 2020

Transit and the recommended plug-in FMGate now support FrameMaker 2020.

For 64-bit versions of FrameMaker (such as FrameMaker 2020), the latest plug-in FMGate is required (version 46 or higher).

The plug-in is available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing FMGate and sharing data with Transit.

3. Export segment comments to InDesign, HTML, XML, SGML

With the new Export with segment comments option segment comments can now also be exported to InDesign documents and HTML/XML/SGML files.

InDesign: The Transit comments will then be displayed as InDesign comments. To export the comments with date and author, the latest plug-in InDesign Gate is required for sharing data with Transit (version 242 or higher).

HTML, XML, SGML: The Transit comments will then be inserted as HTML, XML, or SGML comments into the exported files:
<!-- Transit comment: .... -->

See also » Export segment comments to Microsoft Office / OpenOffice / LibreOffice documents.

4. New version of WebTransit

The Service Pack includes a new version of WebTransit. This version supports the following new features:

SFTP connections with private key files

With this version, WebTransit supports SFTP connections using private key files. Optionally, a key file password and a fingerprint (in MD5 format) can be specified in the connection settings.

TLS 1.2/1.3 for SFTP connections

For SFTP connections, WebTransit now supports TLS version 1.2 and TLS version 1.3.

Testing connections

Until now, connections were tested after they were newly created or changed. This allows you to determine if the new or changed connection is set up correctly to synchronise data with STAR CLM.

From now on, you can also test existing connections:

Active connection: Menu Connection | Test

Any connection: Context menu item Test in the connection overview

Enhanced handling of rejecting jobs

If a job is rejected that has already been unpacked (and possibly edited) in Transit, WebTransit now displays the following message: The selected job has already been unpacked in Transit. Do you really want to reject the job?

With Yes the job is rejected and can no longer be uploaded to CLM.

With No the job is not rejected and can be further processed and uploaded to CLM.

Enhanced job download order for LAN connections

Until now, the download order has been prioritised for FTP connections: Small jobs are downloaded first, so that they are already available in WebTransit, while larger jobs are still being downloaded.

As of this version, this behaviour is also implemented for LAN connections.

1. Support of Adobe InDesign 2021

Transit and the required plug-in InDesign Gate now support InDesign 2021 (Windows and Mac).

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

NOTE: The plug-ins for InDesign 2021 were already released in February 2021.

2. Support of Microsoft Visio 2019

Transit now officially supports to translate Microsoft Visio 2019 documents.

As file type for Microsoft Visio documents, you can select either Microsoft Office or Microsoft Visio.

3. Support of TextShuttle

As additional Editor MT service, Transit now supports TextShuttle.

The Editor MT settings are specified in the Machine translation tab of the user preferences. There you enter the URL for the service and the API key you receive from the MT service provider.

4. Enhanced support of DeepL Pro

Additionally supported languages

DeepL Pro can now generate MT suggestions also for the following working languages: Bulgarian, Chinese, Czech, Danish, Estonian, Finnish, Greek, Hungarian, Japanese, Latvian, Lithuanian, Romanian, Slovak, Slovenian, Swedish

Language variants for target language English

DeepL Pro can now distinguish between the language variants English (UK) and English (US) during translation. DeepL Pro automatically translates into the language variant that is set as the target language in the Transit project.

Language variants for target language Portuguese

DeepL Pro can now distinguish between the language variants Portuguese (Portugal) and Portuguese (Brazil) during translation. DeepL Pro automatically translates into the language variant that is set as the target language in the Transit project.

5. HTTP access to remote TM Containers

As of this service pack, TM containers can also be accessed via http/https.

If the function is enabled and you connect to a TM Container, you can choose between Local TM Container (connection as before) or Remote TM Container. For a remote TM Container, you then enter the access data (URL, user name, password).

NOTE: The http access to TM Containers is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

6. Enhancements for TM Containers

Display of TM filters

The order in which TM filters are displayed is now standardised and improved (e.g. when selecting a TM filter as reference material or for TM Container statistics).

Statistics for language pairs in the TM Container

From now on, the language pair statistics can also be displayed for language pairs opened from the TM Container (Statistic | Language pair | Current).

NOTE: The support of TM Containers is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

7. Inserting fuzzy matches directly during import

Until now, fuzzy matches were displayed as translation suggestions during translation.

From now on, fuzzy matches can also be inserted into the target language directly during import (project setting Pretranslation, Details button, Insert in target language during import option). There you can also define the minimum quality for fuzzy matches to be inserted automatically. We recommend setting a high quality here (e.g. 95%). Values lower than 70% are not supported.

Fuzzy matches that are not inserted (due to lower quality) will still be displayed as translation suggestions in the Fuzzy window.

Automatically inserted fuzzy matches receive the segment status Check pretranslation. This ensures that they are checked before being confirmed and used as Translated.

TIP: You can filter for these inserted fuzzy matches suggestions by combining the new Edited by Pretrans. (reference-based) filter option (» Additional segment filter options) with Fuzzy match quality Lower than 100.

8. Insert MT suggestions directly during import

Until now, MT suggestions of Import MT were displayed as translation suggestions when translating.

From now on, these MT suggestions can also be inserted into the target language directly during import (project setting Machine translation, Insert MT suggestions in target language during import option).

NOTE: The support of Import MT engines is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

Automatically inserted Import MT suggestions receive the segment status Check pretranslation. This ensures that they are checked before being confirmed and used as Translated.

TIP: You can filter for these inserted MT suggestions by using the new Edited by Pretrans. (MT-based) filter option (» Additional segment filter options).

MT suggestions of Editor MT are still displayed as translation suggestions in the Fuzzy window, as they are generated when translating in the Transit Editor.

9. Import of segments with protected spaces

Segments containing only protected spaces are treated as markup segments: They are transferred unchanged into the target language and are assigned the segment status Checked 2. If the previous and/or next segment is also a markup segment, they are combined into one markup segment.

10. Enhancements in the Transit Editor

Enhanced mouse wheel scrolling in language pairs

Up to now, the mouse wheel can be used to scroll up and down within a language file.

From now on it is also possible to scroll the other language file or both language files at the same time:

CTRL + mouse wheel: Both language files are scrolled.
NOTE: Due to the different segment lengths, the source and target languages may "diverge" (i.e. different segments are displayed).

SHIFT + mouse wheel: The other language file is scrolled. Example: If the cursor is in the target language, SHIFT + mouse wheel scrolls the source language.

CTRL + SHIFT + mouse wheel: Transit does not scroll but navigates up or down in both language files (i.e. a segment above or below is selected as the active segment). This ensures that segments are always displayed as pairs.
NOTE: CTRL + SHIFT + mouse wheel has the same function as the minus and plus keys in the number block.

Office projects: Open hyperlink addresses directly from Transit

Since Service Pack 12, URLs in hyperlinks can be localized to adapt Internet addresses to the target language(s) (» Additional options for Office projects).

From now on, you can also call up the linked addresses directly from the Transit Editor and open them in your computer's standard browser (additional context menu item Open Link in browser).

Key combination for permitting / unpermitting as reference material

By assigning the access status Not permitted as reference material, segments can be blocked from being used as reference material for fuzzy matches or pretranslation. Previously, the access status for one or more segments could be changed via the context menu only.

Now the access status can also be assigned via the key combination CTRL + ALT + R. If the selected segment / all selected segments are permitted, CTRL + ALT + R changes its access status to Not permitted (and vice versa).

If you have selected several segments with different access statuses, CTRL + ALT + R sets all selected segments to Not permitted.

Lock / unlock multiple segments

Since Service Pack 12 single segments can be locked by the user (» Lock segments (disallow editing)).

It is now possible to lock and subsequently unlock multiple segments in the Transit Editor. Depending on whether the marked segments are locked or not, the context menu displays corresponding items: Lock selected segments (disallow editing) and/or Unlock selected segments (allow editing).

11. Additional segment filter options

Filter for segments with revisions and/or comments

The existing filter options With comments and Only segments with revisions are AND-linked: If both are selected, Transit only displays segments that have revisions and comments.

It is now also possible to filter for segments with revision or comments. To do this, you check the Only segments with revisions option and the new Additionally also segments with comments option. Make sure to uncheck the With comments option in this case.

Specific filters for pretranslation type

The existing filter option Edited by Pretranslation filters for all pretranslated segments (regardless of the type of pretranslation).

With the following additional options it is now possible to differentiate according to the type of pretranslation:

Pretrans. (reference-based): Segments pretranslated by using reference material

Pretrans. (alignment-based): Segments pretranslated by using aligned reference material

Pretrans. (MT-based): Segments pretranslated by using machine translation (» Insert MT suggestions directly during import)

Pretrans. (dictionary-based): Segment pretranslated by using project dictionaries

When using one of these options, it makes sense to deselect the previous Pretranslation: It includes all the types of pretranslation and would display all types of pretranslated segments.

12. Change J2450 error type / severity

Since Service Pack 12, segments can be rated according to the quality matrix J2450 (» Quality rating in accordance with J2450).

Now it is possible to change the error category afterwards. For this, the Segment info window displays corresponding context menu items for the existing rating (Change error type and Change error severity).

13. Export segment comments to Microsoft Office / OpenOffice / LibreOffice documents

With the new option Export with segment comments target language segment comments can now be exported.

They are then displayed as comments in the exported document (Excel, Word, Powerpoint, Visio, Writer, Impress, and Calc).

14. TMX export only with segments having a target language

The translation memory of Transit is multilingual: It can contain one source language and multiple target languages. In this case, translations do not necessarily exist for all target languages. In this case, a bilingual TMX export could have contained segment pairs in which the target language was empty.

From now on, only segments are exported as TMX that have source and target language content.

15. HTTP access to remote TermStar databases

As of this service pack, TermStar databases can also be accessed via http/https.

If the function is enabled and you connect to a TermStar database, you can choose between Local database (connection as before) or Remote database. For a remote database, you then enter the access data (URL, user name, password).

NOTE: The http access to TermStar databases is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

16. TermStar: Extended data structure

The structure of TermStar data records has been extended by the following fields:

Additional header fields: Multimedia source, Remark source

Additional language fields: Info 3, Info 4, Info 5, Multimedia source

Additional language entry fields: Usage status, Remark source

17. Add context example for terminology extract

When extracting terminology (Terminology | Creation | Extract), it is now possible to include context examples directly from the language pairs in the dictionary.

To do this, select one or more examples in the Context area before you click Move ->. Multiple context examples can be selected with CTRL + mouse click. Transit displays the selected context examples in the Special terminology after the term (in brackets).

The context examples are saved in the Context language entry field of the target dictionary.

TIP: If the context examples are needed in another language entry field, they can be moved with the help of the data manipulation Field contents | Move.

18. Improvements for creating TermStar value lists

Spaces when collecting values

When collecting values for a value list, spaces at the beginning and end are now automatically removed.

Space when converting text field to field with value list

When converting the substrings of a text field into values of a value list, spaces at the beginning and end are now automatically removed.

19. Cross-references to data records independent of term length

To select the target data record for a cross-reference, TermStar searches for data records with the requested terms. To find similar terms, TermStar uses the fuzzy search.

As of Service Pack 14, this search is supported regardless of the length of the search string. Previously, a minimum length of 4 characters was required; very short terms (e.g. "dog") could not be searched for.

20. Additional web search service for Romansh

Transit/TermStar’s web search now supports the following additional service:

Pledari Grond (based on the linguistic database of the Lia Rumantscha for German and Romansh).

21. Additionally supported working language

Transit/TermStar now supports the following working language:

Occitan (language code OCI)

22. Display name changed for Romansh

The display name for the working language Rhaeto-Romanic (language code RMS) has been changed to Romansh.

1. Support of Windows 8 / Windows Server 2019

Transit/TermStar can be installed and run on Windows Server 2019.

2. Enhancements for TM Containers

Display of TM Container attributes for fuzzy extracts

Since Service Pack 7, attribute values are displayed for translation suggestions from the TM Container (e.g. for the fuzzy hits or in the Segment info window).

From now on, the attribute values are also displayed if Transit uses a project-specific fuzzy extract that was generated during import with the help of a TM Container.

TM Containers displayed in alphabetical order

In the TM Container administration (Reference material | TM Containers), the TM Containers are now displayed alphabetically (instead of chronologically). This makes the selection easier for customers who have divided their translation memory into many TM Containers.

3. No pretranslation for locked segments

Since Service Pack 12, segments can be locked by the user (» Lock segments (disallow editing)).

From now on and by default, these locked segments will be handled like markup segments during pretranslation (e.g. when repeating the import for untranslated segments): They are transferred unchanged into the target language and are assigned the segment status Checked 2.

4. Sorting language entries within a data record

Previously, language entries of the same entry type within the same language were displayed in alphabetical order.

From now on the dictionary setting Miscellaneous | Additional sort field controls this order also (previously only data record order):

If the sort field has a value list, TermStar sorts the language entries according to the order of the list items.

If the sort field has no value list, TermStar sorts the language entries according to the alphabetical order of the field values.

If the sort field is a date field, TermStar sorts the language entries according to the chronological order of the field values (latest date first).

If the sort field is empty or does not correspond to the input verification, the language entry is sorted in at the end.

If no sort field is defined, TermStar sorts the language entries (as before) according to the alphabetical order of the term.

1. Support of AutoCAD 2020

Transit now supports to translate dxf files from AutoCAD 2020.

2. Support of Adobe InDesign 2020

Transit and the required plug-in InDesign Gate now support InDesign 2020 (Windows and Mac).

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

3. Support of MSSQL 2019

Transit/TermStar now allows to run TM Containers and TermStar databases on MSSQL 2019.

4. Support of KantanMT

As additional Editor MT service, Transit now supports KantanMT. The Editor MT settings are specified in the Machine translation tab of the user preferences.

NOTES on configuration:

In your KantanMT account, you may define an engine as default engine. If no default engine is defined in KantanMT, you must select the engine to be used in Transit (User preferences | Machine translation tab, … button for KantanMT).

By default, Transit is configured for KantanMT engine access via full engine name. If you want to use the alias option of KantanMT instead, please contact STAR.

Translation suggestions by an Editor MT are requested manually via the Transit Editor by right-clicking on the current segment and selecting Find machine translation in the context menu.

KantanMT may have to start its server first when a request is made. According to KantanMT, the "start-ups can take a few minutes" (depending on the engine size). For this reason, the first requests from the Transit Editor may lead to timeouts until the KantanMT server runs and returns results.

5. Microsoft Translator: Support of formatted MT suggestions

Microsoft Translator can now generate MT suggestions with Transit markups. By that way, source language formatting (e.g. a bold or hyperlinked word) is automatically assigned to the corresponding content in the machine-translated segment.

6. New version of WebTransit with WebDAV support

The Service Pack includes a new version of WebTransit. With this version, WebTransit supports WebDAV as an additional connection type.

Please note that the resource button for calling WebTransit has been changed (» Improved user interface).

7. Additional and updated OpenOffice spellcheck dictionaries

Transit now supports OpenOffice-based spell checking for Gaelic (Scotland). Additionally, the spellcheck dictionaries for 42 languages have been updated and improved.

For a complete list of all supported languages and the files installed, refer to the » Transit/TermStar Reference Guide.

8. Rapid entry: Message "Source and target language terms are identical"

This message is displayed if you have defined the same terms for source language and target language in the Rapid Entry window.

You have the following options:

Yes: Add terminology with identical terms.

No: Do not add terminology.

Cancel: Do not add terminology and close the Rapid Entry window.

9. Enhanced compacting of Access databases

Up to now, the "Compact" function in the TermStar database expert was used to permanently delete data records marked for deletion and to unlock locked data records.

When an Access database is selected, the function now additionally compresses the database (including file DSN databases). It is no longer necessary to compress Access databases via the Windows ODBC data source administrator.

10. Support of additional MSSQL drivers

With this service pack, Transit/TermStar optionally also supports the following drivers for MSSQL databases:

MSSQL ODBC Driver 11

MSSQL ODBC Driver 13

MSSQL ODBC Driver 17

When creating a new database, Transit/TermStar offers the drivers that are actually installed on the computer.

If several drivers are displayed, we recommend the driver that matches the SQL version. If the SQL version is higher, select the latest driver.

11. J2450 quality rating available for all projects

Up to now, quality rating had to be enabled for the project.

Starting with Service Pack 13, quality rating is supported for all projects. For details on rating segment quality, please refer to » J2450 quality rating available for all projects.

12. Improved user interface

With the following changes to the user interface, the meaning of the options/functions becomes even clearer. The functions themselves have not been changed.

Resource bar

In the resource bar, the CLM button has been renamed to WebTransit.

Format check options

The AutoCorrection options for leading/trailing blanks and double spaces function have been renamed to Correct automatically.

Modify reference material

The Delete segments function has been renamed to Delete segment contents.

Prompt window for global terminology changes

The prompt windows for confirming global changes (deleting data records or language entries; replace, assign, delete, copy, or move field contents) have been revised to show more clearly what will be changed.

TermStar layout settings for displaying graphics:

Do not scale renamed to Show original size

Scale to screen width renamed to Fit to page width

Shrink image renamed to Shrink to page width

In addition, shortcut keys for the most important functions are now displayed directly in their tooltips.

1. Multiple J2450 quality ratings per segment

The » Quality rating in accordance with J2450 now supports multiple ratings. You can now categorise more than one incorrect term or phrase within a segment. Individual ratings can be deleted via the context menu in the Segment info window.

For more information refer to the document “Transit: Quality rating in accordance with J2450” in the » Downloads | Transit & TermStar | User Documentation area on our website.

NOTE: Evaluation of the J2450 quality ratings is now enabled in the same way as the quality report (standard function of Transit NXT Professional, optional for Freelance Pro).

1. Support of Microsoft Office 2019

Transit now supports the translation of Microsoft Office 2019 documents (including Word 2019, Excel 2019, and PowerPoint 2019).

See also » Display names changed for Office file types.

2. Additional options for Office projects

In the file type options for Office projects, you can now define further settings (File type project settings, Options button):

Adapt/localise URLs in hyperlinks: URLs in hyperlinks can be edited to adapt Internet addresses to the target language(s). If the option is unchecked, URLs remain unchanged.

Word: Adapt/localise field properties: Field options and field switches can be edited to adapt field properties to the target language(s). If the option is unchecked, field properties remain unchanged.

3. Quality rating in accordance with J2450

J2450 is a quality metric for assessing translation quality. To do this, incorrect terms or phrases are categorised by type and severity of the error. You can rate the segments via the context menu or using the key combination CTRL + Q.

Requirements:

Quality rating has been enabled for the project.

The proofreading mode is active (Review | Proofreading | On).

You have highlighted the incorrect word or phrase

Transit shows the quality rating for the active segment in the Segment info window.

To rate the translation quality, use the quality report (Statistics | Quality | Project or …| Current, Include quality ratings option). On this basis, errors can be weighted and quality scores obtained for translation projects.

NOTE: Evaluation of quality ratings via the quality report is optional and needs to be enabled by the licence number. For more information, please contact STAR (» Contact).

4. Check for unchanged fuzzy matches

During the format check, you can now find out whether fuzzy matches (<100%) were inserted and confirmed without any modifications (also see » Message "Current segment differs from reference segment").

In the file navigation, these segments are listed under the error type Translation | Unchanged fuzzy matches.

5. Leave untranslated segments empty

The project manager can specify that non-pretranslated segments should remain empty and contain no source-language text (Pretranslation project setting, Leave untranslated segments empty option). This is an alternative to the existing translation functionality "Delete to end of segment" and "Empty next segment", which translators can choose themselves (Processing | Translate ribbon, options under Confirm).

6. Lock segments (disallow editing)

It is now possible to lock and subsequently unlock individual segments in the Transit Editor (Lock segment (disallow editing) and Unlock segment (allow editing) context menu items).

The Transit Editor displays the locked segments in grey. You can change the text and background colour of locked segments in the user preferences under Colours and fonts (Font: Locked segments and Background: Locked segments)

7. Assign access status to multiple segments

The access status for segments (Permitted as reference material or Not permitted as reference material) can now be changed for multiple segments. If several segments in the Transit Editor are selected, the context menu displays the appropriate options (Permit selected segments as reference material and/or Do not permit selected segments as reference material).

8. Shortcuts for dual concordance search and non-breaking spaces

Start concordance search: CTRL + ALT + F

It is now possible to perform the concordance search via a shortcut (corresponds to the Dual concordance context menu item).

In the Transit Editor, select the term you want to start a concordance search for and press CTRL + ALT + F. You can either select a single term in the source or target language or a pair of terms in the source and target language.

Non-breaking space: CTRL + Space

In the Transit Editor, it is now possible to enter a non-breaking space directly by using the shortcut CTRL + Space.

A non-breaking space avoids line breaks e.g. between a numeric value and its unit or before punctuation characters (e.g. in target language French)

9. Additional web search services and enhanced web search call-up

Additional web search services

Transit/TermStar’s web search now supports the following additional services:

Wikipedia (free encyclopedia for more than 30 languages)

Termium (Government of Canada’s terminology and linguistic data bank for English and French)

Termdat (Swiss Federal Administration’s terminology database for German, French, Italian, Romansh, and English)

IATE (European Union terminology for more than 25 languages)

Call up from the Transit Editor via the context menu

The web search can now be called up directly via the context menu from the Transit Editor (Web search context menu item). Transit automatically detects whether the search term is in the source or target language.

10. TMX export: Identical segments once only

When exporting reference material to a TMX file, you can now specify that identical segments ("Internal Repetitions") should be exported only once if they have been translated identically (Export identical segments once only option). If identical source language segments have different translations, Transit exports all translation variants.

11. Enhancements in reference material maintenance

The Modify reference material window has been enhanced to include the following functions:

Using the new search option Whole segments only, you can specify that the string you are searching for must match the entire segment content.

You can now empty segments, i.e. delete the segment content in the source and/or target language (Delete segments section).

In the hit list, the process for selecting segments that need to be modified has been simplified and improved.

The function of assigning the access status has been simplified (Assign access status section).

The segment selection in the hit list can now be taken into consideration for segment navigation and for making replacements (Previous, Next, Replace and Replace All buttons).

12. File DSN as default connection type

When creating a new database, File DSN (User scope) is now the default connection type (it was previously User DSN). As ever, you can still select a different connection type during the creation process.

When installing Transit/TermStar for the first time, the databases that are provided – TermStar NXT, TermStar NXT Received and TermStar NXT Check – are now created as follows:

TermStar NXT database:

Location: db folder (as previously)

Connection type: File DSN (Global scope) (previously User DSN or System DSN)

The database is set up when Transit/TermStar are being installed (as before).

TermStar NXT Received and TermStar NXT Check databases:

Location: config/users/<username> folder (previously db folder)

Connection type: File DSN (User scope) (previously User DSN or System DSN)

These databases are created when a new user is set up (previously this occurred when Transit/TermStar were being installed).

13. Display name changed for Macedonian

The display name for the working language Macedonian (FYROM) (language code MKD) has been changed to Macedonian (North Macedonia).

14. Display names changed for Office file types

The display names for Office file types have been changed as follows:

MS Office 95-2016 changed to Microsoft Office

MS Excel 97-2016 changed to Microsoft Excel

MS PowerPoint 97-2016 changed to Microsoft PowerPoint

MS Word f. Windows 95-2016 changed to Microsoft Word

MS Visio 2013-2016 changed to Microsoft Visio

1. Support of Microsoft Office 365

Transit now supports Microsoft Office 365.

When you create a project to translate Office 365 documents (Word, Excel, or PowerPoint), select Microsoft Office on the File type tab.

2. Support of Adobe InDesign CC 2019

Transit and the required plug-in InDesign Gate now support InDesign CC 2019 (Windows and Mac) and InDesign endnotes.

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

3. Support of Adobe FrameMaker 2019

Transit and the recommended plug-in FMGate now support FrameMaker 2019.

The plug-in is available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing FMGate and sharing data with Transit.

NOTE: FrameMaker 2017 has been supported since Service Pack 9 Update 16.

4. Support of AutoCAD 2019

Transit now supports to translate dxf files from AutoCAD 2019.

5. Switching on / off signal sounds

Transit plays signal sounds for certain functions (e.g. when searching for fuzzy hits). Transit now supports an option to switch these sounds on and off (User preferences | Transit Editor tab, Play signal sounds … option).

If a language pair is open, the option is additionally available on the Edit ribbon (Miscellaneous group, Play signal sounds option). As part of this change, the names of the following options in group Miscellaneous have been changed as follows

Option Automatic keyboard switch renamed to Keyboard switch

Option Keep source-term caps renamed to Keep capitals

6. Enhancements in machine translation

DeepL Pro: Handling markups

DeepL Pro can now generate MT suggestions with Transit markups. By that way, source language formatting (e.g. a bold or hyperlinked word) is automatically assigned to the corresponding content in the machine-translated segment.

If the markup results from DeepL Pro are incorrect, it makes sense to deactivate markup handling (User preferences | Machine translation tab, … button for DeepL Pro). In this case, MT is provided as plain text and the markups have to be assigned by the user.

DeepL Pro: Automatic segmentation setting

The DeepL Pro segmentation is now selected automatically depending on the segmentation of the Transit project. The DeepL Pro interface option "Segment by sentence" has been removed (User preferences | Machine translation tab, … button for DeepL Pro).

7. Highlighting used target language terms

In the language pair, Transit can automatically highlight terminology from the dictionary. Now it is also possible to highlight used target language terms (User preferences | Terminology search tab, Highlight used terms option). A target language term is highlighted if included in the dictionary as allowed translation of the source term. Disallowed target language terms are not highlighted.

8. New version of WebTransit

The Service Pack Update includes WebTransit 2.6.0.812. In this version, the following column names in the job list have been adapted to the corresponding names in STAR CLM:

Job ID changed to Order ID (German interface: Job-ID changed to Auftrags-ID)

Activity changed to Activity/service (German interface: Aktivität changed to Aktivität/Leistung)

German interface only: Termin changed to Liefertermin

Interfaces in other languages have been adapted accordingly.

9. Additional web search services

Transit’s web search now supports the following additional services (for language pairs including French and Italian):

Leo, Larousse, Linguee, Woxikon, Corriere

1. New version of WebTransit

The Service Pack Update includes WebTransit 2.6.0.809 with enhancements for deleting jobs.

1. Support of MSSQL 2017

TermStar now allows to run TermStar databases on MSSQL 2017.

2. Additionally supported MT Services

As additional Editor MT services, Transit now supports:

DeepL Pro

Microsoft Translator (as Azure service)

The Editor MT settings are specified in the Machine translation tab of the user preferences. Translation suggestions by an Editor MT are requested manually via the Transit Editor by right-clicking on the current segment and selecting Find machine translation in the context menu.

3. Support of Adobe InDesign CC 2018

Transit and the required plug-in InDesign Gate now support InDesign CC 2018 (Windows and Mac).

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

NOTE: The plugins for InDesign CC 2018 were already released in December 2017.

4. Enhanced AutoCAD support

Support of AutoCAD 2018

Transit now supports to translate dxf files from AutoCAD 2018.

Support for layers in AutoCAD

The Ignore hidden layers option in the file-type settings allows to exclude hidden layers when importing AutoCAD documents in Transit.

Using the Ignore layers from file option it is possible to exclude selected layers – regardless of whether they are hidden or shown in AutoCAD – from the import in Transit. For that purpose, a so-called layer file has to be created. The layer file then contains the names of the layers not to be imported and must be selected before the final import.

5. Support of SDL WorldServer projects (wsxz files)

Transit now can be used to translate SDL WorldServer project packages.

To unpack the project package for translation, select Interfaces | SDL WorldServer | Unpack WorldServer project package (wsxz) in Transit.

Once the project has been translated, pack the translation in Transit using Interfaces | SDL WorldServer | Pack translation as WorldServer return package (wsxz).

NOTE: Projects from SDL Trados Studio (sdlppx files) have been supported since Service Pack 8 (» Working on projects created and packed with SDL Trados Studio).

6. Quality report as standard feature of Transit NXT Professional

The quality report (Statistics | Quality) is now a standard function of Transit NXT Professional.

For other Transit product variants, the quality report is optional and needs to be enabled by licence number. If you wish to use this function and have it activated, please contact STAR (» Contact).

The quality report can save the following information as HTML, Excel, or XML file:

Format check and terminology check results (» Report Manager for Quality Check)

Variant check results (» Quality report including variant check)

Segment revisions and segment comments (» Saving quality reports with all segment revisions and segment comments)

7. QA check for unallowed characters

Transit now allows you to check for invalid characters. The invalid characters can be defined in customer-specific file format definitions. Using the Length check option in the format check settings, Transit reports invalid characters during the interactive format check, in the error navigation and in the optional quality reports.

8. Spellcheck: Additional options

Transit now supports additional spellcheck option that allow you to exclude specific text content from checking (Review | Spellcheck | Options):

Ignore UPPERCASE words

Ignore pseudo numbers (e.g. C3PO)

Ignore internet and file addresses

Ignore non-translatables

The already supported Match case option has been moved to Review | Spellcheck | Options.

9. Transit Editor improvements

Allow/suppress message "Current segment differs from reference segment"

In the user preferences Dual Fuzzy, you can now select whether Transit shall warn if fuzzy match is confirmed without changes.

NOTE: The message itself has already been introduced with Service Pack 9 Update 25.4 (» Message "Current segment differs from reference segment").

10. Dynamic Linking improvements

The Dynamic Linking function now can search monolingual reference material, too. This is a good idea if, for example, you want to use Transit reference material from projects with other target languages

For this purpose, the Dynamic Linking dialog now supports two additional options:

Display only search language: Transit only displays segments in one language as results (usually source language results). If the source language search field is empty and the target language search field contains text, Transit displays target language results only.

Display only bilingual hits: Transit only displays hits for which there are both source-language and target-language segments. If you uncheck the option, Transit will display hits for which there is only a source-language or a target-language segment as well.

11. Localisation projects: Warning if virus scanner prevents correct DLL export

Third-party virus scanners can prevent Transit from exporting DLLs correctly and can cause missing or duplicated strings.

Transit now removes these DLLs from the export folder and displays the following warning in the Export window:
<Filename>: <Target language>[Filtering] Internal error...

12. TermStar: Extended data structure

The structure of TermStar data records has been extended by the following fields

Header field: External reference

The field is filled in by import or merging only, but cannot be edited by the user. It allows to store external IDs permanently and can be used for secure data synchronisation with other systems.

13. Readme replaced by Release Notes

The previous readme files have been replaced by release notes. In addition to the service packs, they will also contain information about updates and will therefore be updated for each officially released service pack update.

The release notes of the latest Service Pack / Update are available in the » Downloads | Transit & TermStar | Service Pack area on our website.

The release notes of your installed Transit/TermStar version can be found in your Transit/TermStar installation folder (filename Transit-TermStar-NXT-Release-Notes.htm).

1. Message "Current segment differs from reference segment"

This message is displayed if a fuzzy match (<100%) is inserted and confirmed without any modifications.

To stop displaying such messages in the future, hold down the CTRL key and confirm the message with Yes.

Update: Starting with Service Pack 10, you can allow/suppress the message with a user preferences option (» Allow/suppress message "Current segment differs from reference segment").

2. New version of WebTransit

The Service Pack Update includes WebTransit 2.6.0.806 with enhancements for Agency Mode connections.

1. Support of MSSQL 2016

TermStar now allows to run TermStar databases on MSSQL 2016.

2. Support of Adobe InDesign CC 2017

Transit and the required plug-in InDesign Gate now support InDesign CC 2017 (Windows and Mac).

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

NOTE: The plugins for InDesign CC 2017 were already released in November 2017.

1. Support of Adobe FrameMaker 2015

Transit and the recommended plug-in FMGate now support FrameMaker 2015.

The plug-in is available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing FMGate and sharing data with Transit.

2. New version of WebTransit

The Service Pack Update includes WebTransit 2.6.0.804 with:

enhanced processing of jobs for agency mode connections

minor enhancements for other connection modes

1. Support of Windows 10

Transit/TermStar can be installed and run on Windows 10.

2. Support of MSSQL Server 2014 and Oracle 12

TermStar now allows to run TermStar databases on MSSQL Server 2014 and Oracle 12.

3. Support of Adobe InDesign CC 2015

Transit and the required plug-in InDesign Gate now support InDesign CC 2015 (Windows and Mac).

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

4. Support of Microsoft Office 2016 and Microsoft Visio 2013 / 2016

Transit now supports to translate Microsoft Office 2016 documents (including Word 2016, Excel 2016, PowerPoint 2016 and Visio 2016). Transit also supports Visio 2013 objects embedded in Word documents.

As file type for Microsoft Visio 2013 / 2016 documents, you can select either Microsoft Office or Microsoft Visio.

5. Support of AutoCAD 2013 - 2016

Transit now supports to translate dxf files from AutoCAD 2013 to AutoCAD 2016.

6. Support of DocBook

Transit now supports to translate XML files based on DocBook DTD.

7. Additionally supported working languages

Transit/TermStar now supports the following languages and language variants:

Breton (language code BRE)

Corsican (language code COS)

Dari (language code PRS)

Maori (language code MRI)

Pashto (language code PAS)

Spanish (International) (language code ES1)

Spanish (US) (language code EST)

Tajik (language code TAJ)

8. Enhancements in exchanging projects

Support of MemoQ projects

Transit now allows to unpack and translate MemoQ handoff packages and pack the translated files as MemoQ handback packages.

Support of zipped XLIFF projects

Transit now allows to unpack zipped XLIFF projects to a single Transit project and to pack the translation as zipped XLIFF projects. This way you can handle multiple XLIFF projects in one Transit project and you can benefit from additional Internal Repetitions and Internal Fuzzy matches.

9. Enhancements in the resource bar

Interfaces resource

It is now possible to quickly unpack MemoQ handoff packages and pack translations as MemoQ handback packages (Interfaces | MemoQ).

It is now possible to quickly create projects for DITA and DocBook files (Interfaces | DITA / DocBook | …).

10. Enhanced format check options

Segment status

Transit now allows to check for segments that do not have a selected minimal segments status.

Segments that do not have the minimal status are reported during the interactive format check and displayed in the error display of the File navigation window.

Variant check

Transit now allows to check for translation and/or source variants in your projects.

If Transit finds variants, it displays them in the Variants tab of the File navigation window.

You may perform the variant check as part of the format check (Review | Format check | Options) or separately via Review | Variants | Start.

Skip ignored errors during format check

When performing the format check, Transit now allows to skip errors that have already been ignored (i. e. confirmed as an exception) during a previous format check.

To do so, check the Do not check ignored errors option in the menu under Review | Format check | Start before performing the format check.

11. Enhancements in working with tool windows

File navigation window

Transit now provides new shortcuts for working in the error display tabs in the File navigation window:

Switch between the tabs in the File navigation window: CTRL + PAGE-UP / PAGE-DOWN

Go to the next / previous not-ignored error: CTRL + DOWN ARROW / UP ARROW

Switch to segment containing an error in the target-language window: CTRL + RIGHT ARROW

Ignore error(s): CRTL + I

Remove error(s) from list: CTRL + D

Find/Replace window

Transit now inserts the text marked in the Transit Editor automatically to the Find field of the Find/Replace window.

PDF viewer window

When you click the Open icon to select a PDF file, Transit now automatically opens the Attachments folder in the working folder.

If there is no Attachments folder, Transit opens the working folder.

Fuzzy windows / Dual Concordance window / Dynamic Linking window

Transit now allows to display the markup type not only in the Transit Editor, but also in the Fuzzy windows, the Dual Concordance window and the Dynamic Linking window.

To do so, just open the context menu of the window, open the Display options window and select Display markup ID with type.

12. Enhanced status bar

Tooltips for information in status bar

Transit/TermStar now provides tooltips for all sections of the status bar.

Information on segment filter

The status bar now provides an information on whether a segment filter is active for the source and/or target language.

Information on length check

The status bar now provides an information on the actual and setpoints values of the length check for the active segment.

13. Enhancements in Quality report options

Quality report including variant check

Transit now allows to write all translation and/or source variants that your project contains to the quality report. The quality report can be saved as HTML, Excel, XML file, or written to the variant display of the File navigation window.

NOTE: The Quality report function (Statistics | Quality) is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

14. Enhancements in reference material maintenance

Modify reference material window

The Modify reference material window has been revised and enhanced.

It now has a clear separation between search options, filter options and navigation / replace options. All segments that match the search and filter criteria are now displayed in a result list consisting of filenames and segment numbers.

Transit now allows to additionally filter segments by access status.

Via this window, Transit now also allows to permit or not permit selected segments or all segments found in a file as reference material.

15. Enhancements in TermStar

Saving multimedia files in the database

TermStar now allows to save multimedia files that you have inserted in your dictionaries in the database. Doing so, you can keep all your terminology data in one data source.

This feature is supported for databases created with TermStar NXT Service Pack 9 or later. If you want to use it for databases created with earlier Service Packs, you just have to copy the database content into a database created with TermStar NXT Service Pack 9.

Dictionary defaults for new databases

TermStar now allows to set the following default settings for all dictionaries created in a database:

Multimedia file access

Cross-reference separator

Additional sort field

Tracking changes

Creating unique identifiers (GUID).

This feature is supported for databases created with TermStar NXT Service Pack 9 or later. If you want to use it for databases created with earlier Service Packs, you just have to copy the database content into a database created with TermStar NXT Service Pack 9.

Migrating multimedia files into the database

When copying a database, TermStar now allows to migrate the multimedia files from the file system to the database.

Logging changes to data records as revisions

TermStar now allows to log each change to a data record as a revision step. Later you can compare different revision steps and, if required, reset the whole data record or particular field contents.

NOTE: This feature is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

Creating cross-references to data records

TermStar now allows to format text in any entry field as a cross-reference to a data record.

The cross-reference text does not need to match the term of the entry to which you want to refer.

If you change the term or other fields of the target data record, the cross-reference will still work. The cross-reference target is the data record ID or GUID.

Additional data record fields

The TermStar data model has been extended by:

Additional header fields Definition and Definition source for cross-language definitions

Additional language fields Definition and Definition source for all language entries of the same language

16. TermStar Gate: Support of Microsoft Word 2016

TermStar Gate now supports Microsoft Word 2016.

The Word add-in is available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing and using TermStar Gate.

17. Enhancements in TM Container

More pretranslations / fuzzy matches by using TM in any language direction

Transit now allows to specify a Pivot language when selecting a TM Container / TM Filter as reference material. This allows to use the multilingual TM flexibly in any language direction and benefit from pretranslations and fuzzy matches even for language combinations which have not been translated yet.

Enhanced editing of TM Container contents

Transit now supports filename patterns for preselecting TM Container contents to be opened.

Enhanced removal of TM Container contents

Transit now supports filename patterns for preselecting TM Container contents to be removed.

Transit now allows to select individual languages to remove them.

Enhanced TM Container export

Transit now allows to select individual languages to export them.

Transit now supports additional TMX export options (minimum segment status, export of protected segments).

Enhanced attribute properties

Transit now supports the additional attribute type Sorted list for automatically sorted value lists.

Transit now allows to change the type of existing attributes.

The previous attribute property Mandatory has been renamed to Mandatory (ID). Additionally, a new property named Mandatory is now supported.

MSSQL Server 2014 support

Transit now supports MSSQL Server 2014 as TM Container server.

NOTE: The support of TM Containers is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

1. Transit

Project import

Enhanced behaviour when importing the following file types:

Word 2007, 2010, and 2013 files

Word files containing footnotes

Microsoft Office files containing inserted formulas

Microsoft Office files containing embedded Visio 2013 objects

Excel 2010 files containing hidden sheets

Excel 2013 files containing footers

Excel files containing protected cells

PowerPoint files containing hidden slides

OpenOffice Calc files

OpenOffice Writer files (titles of index and ToC are now translatable)

AutoCAD 2010 DXF files

Project export

Enhanced behaviour when exporting the following file types:

PowerPoint 2010 and 2013 files

Word 2013 files

Excel 2010 files

OpenOffice Writer files

Transit Editor

Improved terminology search in the Transit Editor

Packing projects / packing translations

Enhanced behaviour when packing projects with dictionaries

Enhanced handling of markups when packing the translations of XLIFF or SDLXLIFF projects

Enhanced handling of markups when packing XLIFF projects

Enhanced behaviour when unpacking SDLPPX projects

Enhanced behaviour of projects where dictionaries have been assigned to customers via user preferences

Format check / Terminology check

Enhanced format check behaviour, e.g. when checking leading and trailing blanks

Enhanced behaviour when updating the error display

Enhanced behaviour during terminology check (finding wrong terminology)

Enhanced behaviour when checking numbers

Pretranslation / Fuzzy matches

Enhanced handling of markup pairs during pretranslation and when accepting fuzzy matches

Improved handling of bidirectional reference material

Terminology window

Enhanced behaviour when inserting terminology entries from the Terminology window (double-clicking letter combinations)

Enhanced behaviour when displaying formatted strings from the working folder as terminology

Improved display of Thai characters

Transit reports

In reports for STAR CLM (*.james, *.rep), the base of the page and the line calculation is now output in the separate element <unitbase>.

WebTransit

Enhanced behaviour when deleting a job: WebTransit now also deletes the project dictionaries.

WebTransit now also deletes the project dictionaries when deleting a job

Enhanced behaviour when downloading a job that is sent again

2. TermStar

Enhanced behaviour when importing terminology from an indirect WebTerm download into a database

Enhanced behaviour when performing a TBX export

Improved display of Thai characters

1. Support of Windows 8.1

Transit/TermStar can be installed and run on Windows 8.1.

2. Support of Adobe FrameMaker 12

Transit and the recommended plug-in FMGate now support FrameMaker 12.

The plug-in is available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing FMGate and sharing data with Transit.

3. Support of Adobe InDesign CC 2014

Transit and the required plug-in InDesign Gate now support InDesign CC 2014 (Windows and Mac).

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

4. Support of Microsoft Office 2013

Transit now supports to translate Microsoft Office 2013 documents (including Word 2013, Excel 2013, PowerPoint 2013).

5. Support of WebVVT subtitles

Transit now supports to translate subtitles in WebVVT format.

New file type in Transit: Subtitling (WebVTT)

6. Additionally supported working languages

Transit/TermStar now supports additional languages and language variants:

Armenian

Bosnian (Cyrillic., Bosn. and Herzeg.)

Burmese

Lao

Filipino (Philippines)

German (plain language)

Serbian (Latin, Montenegro)

Serbian (cyr., Montenegro)

7. Working with segment revisions

Logging and comparing revision steps

Transit now allows to log changes as revisions when editing the translation of a segment. This is especially useful in multi-stage translation processes (consisting e. g. of translation, proofreading, external review).

Revisions may be logged when working in proofreading mode and unpacking translation packages (TPF files) if

a new segment status is assigned

and/or the revision is made by a different user.

Later on, the revision steps of a translation may be displayed, compared, and reset in the Compare revision steps window.

In the Segment info window, Transit displays if and how many revisions have been logged for a segment (» Notes).

Navigating to segments with revisions

It is now possible to navigate to segments with revisions via Review | Proofreading | Navigate.

Filtering segments by revisions

Transit now allows to filter for segments for which revisions have been logged.

8. Enhancements in User preferences

Startup settings

In the new Startup settings user preferences you can now select the action Transit performs during the next startup as well as the dialogue language.

Working languages

In the Working languages user preferences you can now select the preferred working languages.

Folder selection

In the Folder selection user preferences, the individual actions have been sorted to increase clearness. Also, further folder selection options have been added.

TermStar

The TermStar now provide options for specifying in which order the additional languages should be displayed in a data record.

Current user visible

The window title of the User preferences window now shows the full and abbreviated name of the current user. This way, the user always knows what user name he/she is using. This is helpful if different users use the same Transit/TermStar installation.

9. Enhancements in Project settings

Messages for project-specific information

On the Messages tab you can now specify project-specific information that is displayed as a message when different project processing actions are performed.

As a project manager you can use these messages

to display information or working instructions for specific project processing steps to translators / reviewers or

to create yourself some kind of "digital reminder".

Format check: Open sets of format check options

Transit now allows to open a set of format check options to be assigned in the project settings (see also » Enhancements in format check).

10. Enhancements in the Transit Editor

Hiding markup segments

Transit now allows to hide markup segments (i. e. segments that only contain non-editable markups) regardless of how markups are displayed.

Highlighting segments according to a segment filter

Via the View | Segments | Colours menu, Transit now allows to highlight segments that match the criteria (regarding segment information and segment context) of a specified segment filter. In contrast to applying the segment filter, you maintain the full context of the filtered segments.

Navigating to segments according to segment filter

Via the Processing | Translate | Navigate menu and the Review | Proofreading | Navigate menu, Transit now allows to navigate to segments that match the criteria (regarding segment information and segment context) of a specified segment filter. In contrast to applying the segment filter, you maintain the full context of the filtered segments.

Navigating to segments based on the status directly after import

Transit now supports special shortcuts to navigate to segments that had the Not translated and/or Check pretranslation status directly after import. So far, it was only possible to navigate based on the current status.

11. Enhancements in Transit tools

Notes

The Notes window has been renamed to Segment info window and now offers a more clearly arranged appearance. The option for entering comments has been made more visible.

If revisions have been logged for a segment, the Segment info window also provides information on the total number of revisions and the differences between the current and the previous revision of the translation (» Working with segment revisions).

Search/Replace

The Search/Replace window has been made more intuitive.

Furthermore, the Search function has been enhanced by additional features. Before you actually start to navigate through the search results in the active editor window, you can now:

count how often the search strings is found,

filter for segments that contain the search string,

highlight every occurrence of the search string.

Opening arbitrary PDF files in the PDF viewer

Transit now allows to open arbitrary PDF files in the PDF viewer by using the Open icon.

12. Enhancements in exchanging projects

Additional pretranslation with own reference material

Transit now allows to repeat the pretranslation for an unpacked project to carry out an additional pretranslation with your own reference material. This is also supported for XLIFF and SDLPPX projects.

Attaching arbitrary files to the project

Transit/TermStar now allows the project manager to add arbitrary files to the project as attachments.

The translator can open the attachments folder containing these files by selecting Project | Exchange (Transit / XLIFF / SDLPPX) | Show attachments.

Saving options for packing / forwarding projects

Transit/TermStar now allows to save the options selected when packing or forwarding a project as default. This way, they are preselected the next time you pack / forward a project.

Working on projects created and packed with SDL Trados Studio

Transit now allows to unpack SDL project packages (*sdlppx) and pack SDL return packages (*.sdlrpx). This way, the translator can also work on projects created and packed with SDL Trados.

13. Enhancements in report options

Analysing 100% matches as fuzzy matches

Transit now allows to specify that 100% matches should not be analysed separately in the report but as part of the highest fuzzy match range.

Rounding lines and pages

Transit now allows to specify a specific number of decimals for displaying the values for lines and pages.

Calculation basis for lines and pages in the report

In reports created based on lines and pages, Transit now indicates how lines and pages were calculated.

Opening a report directly after saving

Transit now allows to open a report directly after generating it.

Saving quality reports with all segment revisions and segment comments

Transit now allows to evaluate entered comments and logged segment revisions in the Quality report that you can output as HTML, Excel, or XML file.

NOTE: The Quality report function (Statistics | Quality) is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

14. Enhancements in format check

Reusing sets of Format check settings

Transit now allows to save the settings you have selected in the Format check window. This way you can save specific sets of settings e.g. for different customers or document types.

You can select a specific set of settings directly via Review | Format check | Options (down arrow), in the Format check window and in the Format check tab of the project settings.

15. Enhancements in segment filtering

Enhanced filtering segments by fuzzy match quality

Transit now allows to filter segments by the quality of potential or actually used fuzzy matches.

Enhanced filtering for segments with comments

Transit now allows to filter for segments that contain comments with a certain content or that contain comments at all.

Enhanced filtering for segments by used reference material

Transit now allows to filter for segments that were translated using certain reference material or that were translated using reference material at all.

Filtering segments by language direction of the reference material

Transit now allows to filter for segments that were translated using reference segments that had a specific language direction (identical, vice-versa, or indirect)

16. Enhancements in Machine Translation

Support of MyMemory and Microsoft Translator as Editor MT

Transit now allows to use MyMemory and Microsoft Translator engines for requesting segment-specific machine translations via the Transit Editor.

Support of STAR MT and Asia Online as Import MT

Transit now allows to use the STAR MT and Asia Online engines for generating machine translations during the import.

NOTE: The support of Import MT engines is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

17. New version of WebTransit

The Service Pack includes WebTransit 2.5.0.782 with the following enhancements:

Switch connection from single-user mode to agency mode

WebTransit now allows to switch a connection from Single-user mode to Agency mode by the Copy connection (for agency mode) option. Note the instructions in the » WebTransit User Guide.

Improved performance of existing functions

18. TermStar: Enhanced data record filters

Filtering data records for duplicates

TermStar now provides the Duplicates filter. Using this filter you can display all duplicate entries and subentries in the source language.

Filtering data records according to the number of entries/subentries

TermStar now allows to display only data records that contain a specified number of main entries or subentries in the source language.

19. TermStar: Enhanced usability

Open dictionary

The Open dictionary window has been revised:

Project dictionaries and additional dictionaries are now displayed in two separate lists.

An icon indicates that a dictionary is opened on a separate tab.

The new Open project dictionaries again button allows to open the project dictionaries again if you have accidently closed them.

Switching back and forth between language pair and Rapid entry window

TermStar now allows to switch back and forth between the language pair in the Transit Editor and the Rapid entry window, e.g. to copy an example of use for a term.

20. TermStar: Enhanced terminology import/merging/export

Field separator for CSV export

When exporting a dictionary to the CSV format, TermStar now allows to select the field separator (semicolon or tabulator).

Merging data: Differentiate entries by term or entry GUID

On the Merge data tab of the Merging expert window, you can now select how TermStar should differentiate matching from non-matching entries: by term GUID or entry GUID.

You need to differentiate entries by entry GUID, if e.g. a dictionary has been edited by a revisor and you now merge the dictionary into the source dictionary again.

Synchronise data: Search only up to the first match

You can now check an option if the content of the synchronisation field of each imported data record corresponds to exactly one (or no) target data record.

This make usually sense if you use the data record GUID for synchronisation.

Export terminology for import in MT system

TermStar now allows to export the terminology for import into a MT system (via the TermStar database expert).

21. TermStar: Enhanced terminology editing

Enhanced check for duplicates

TermStar now checks all entries and subentries in all languages for duplicates:

when you create a new data record or

when you copy / paste a data record from one dictionary to another or

when you copy a language entry from one data record to another.

Enhanced replacing / assigning / deleting of field contents

TermStar now allows to search and replace text in all fields of all languages. Furthermore, you can now assign or delete text in a selected field in all languages.

Creating new data records on right page of the dictionary

TermStar now allows to create new data records on the right page of the dictionary.

You can open a new data record on the right page of the dictionary by

selecting New (Right page) in the context menu of the dictionary or

by pressing the CTRL key when clicking Processing | Data record | Create.

22. TermStar: Enhanced dictionary administration

Generating dictionary statistics via the TermStar database expert

TermStar now allows to generate statistics on data records and entries via the TermStar database expert.

Creating GUIDs to existing data records and entries

When you check the Create unique identifiers (GUIDs) options in the dictionary settings, TermStar now can add GUIDs for all existing entries and/or data records.

When you uncheck the options, TermStar can now delete the GUIDs of all existing entries and/or data records.

Sorting values within a values list alphabetically

TermStar now allows to sort values in a flat or hierarchic monolingual values list alphabetically.

1. New version of WebTransit

The Service Pack Update includes a revised version of WebTransit with the following enhancements:

Last events: Overview on new jobs and messages for all connections

The Last events window now keeps you informed of new jobs and messages for all connections to STAR CLM servers. You can display this window always on top and move it to any position while you are working in Transit, for example.

Improved user-friendliness by revised design of GUI elements

The entire WebTransit GUI provides newly designed meaningful icons.

You can now display tooltips for each job explaining the meaning of the icons shown in the job list.

The job list and the Job Details window now contains more precise information on jobs.

The options in the Connection settings window have been reorganised, and the tabs have been given more meaningful names.

WebTransit now contains an online help.

Deleting jobs made more comfortable

You can now delete multiple jobs at the same time without WebTransit displaying a security query for each job.

You can now delete all finished jobs whose deadline has been before a specified date and time.

When deleting a job, you can now retain the working folder containing the Transit project files e.g. as reference material.

Enhanced behaviour for connection managing

When setting up a new connection or changing connection settings, you can now test the connection before setting it up permanently.

Double-clicking on a connection in the connection overview now changes it to be the active connection.

It is now possible to reject jobs when working with a connection in Multi-user mode. You have to allow this feature via the connection settings.

Support of reference material organised in TM Containers

WebTransit now supports the use of reference material organised in TM Containers.

Copying details of the job list into another application

It is now possible to copy (using CTRL + C) and paste the entire job list or parts of it into e.g. an Excel sheet or a Word table.

More flexibility for customers

Customers now have the option to cancel a job already provided to a supplier. WebTransit informs the supplier if this is the case.

1. Support of Adobe FrameMaker 11

Transit and the recommended plug-in FMGate now support FrameMaker 11.

The plug-in is available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing FMGate and sharing data with Transit.

2. Support of OpenOffice/LibreOffice

Transit now supports the following OpenDocument based formats:

OpenOffice (version 2.0 or higher)

LibreOffice (version 3.3 or higher)

IBM Lotus Symphony 3.x

New file type in Transit: OpenOffice/LibreOffice/OpenDocument

For more information refer to » Document “Transit: Tips & Tricks for All File Formats”.

3. Support of translating subtitles

With Transit, you can now also import and translate the subtitles of videos or presentations.

For these file types, Transit supports the synchronisation of the multimedia file with the Transit Editor: In the Media viewer, Transit plays the corresponding film sequence of a segment, so that you can identify the context in which the subtitle is used. You can choose whether Transit plays back the film sequence automatically (as soon as you place the cursor into a segment) or manually on demand.

New file types in Transit:

Subtitling (SubRip): For subtitles in SubRip format

Subtitling (Text): For subtitles in text format

NOTE: These file types are optional and need to be enabled by licence number. For more information contact STAR (» Contact).

4. Integration of Microsoft Word spellchecking

It is now possible to perform the spellcheck based on Microsoft Word spellcheck dictionaries.

The Microsoft Word spellchecking can be selected from the Based on... option list under Review | Spellcheck.

NOTE: The MS Word option is selectable if you have installed Microsoft Word 2002 or higher. Transit uses the Microsoft Word spellcheck dictionaries that are installed on your computer.

5. Integration of Machine Translation

Now systems for Machine Translation (MT) can be used when working with Transit. Transit distinguishes between:

Import MT with customer-specific MT systems (e. g. SYSTRAN, SmartMATE)

In Transit, customer-specific MT systems are used exclusively on the import of project files.

The project-specific Import MT settings are specified in the Machine translation tab of the Project settings window. If a segment has been sent to and translated by an Import MT, the MT suggestions are displayed in the Fuzzy window.

NOTE: The support of Import MT is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

Editor MT with unspecific online translation services (Google Translate, iTranslate4eu)

Machine translations by online services are supported only in the Transit Editor where the translator requests them explicitly for individual segments.

The user-specific Editor MT settings are specified in the Machine translation tab of the user preferences.

Translation suggestions by an Editor MT are requested manually via the Transit Editor by right-clicking on the current segment and selecting Find machine translation in the context menu.

6. Morphological search supported for additional languages

The morphological search for dictionary entries is now available for the following additional languages:

Basque, Catalan, Portuguese, Danish, Norwegian (Bokmal), Swedish, Dutch, Polish, Czech, Slovak, Slovenian, Hungarian, Russian, Romanian

7. Multilingual projects: Saving statistics for all target languages in one step

When saving a report as Excel or HTML file, you can now select whether Transit should save a combined statistics for all target languages or individual statistics for all target languages.

8. Enhancements in Terminology extraction

The procedure of extracting terminology from language pairs and importing it to a dictionary has been optimised as follows:

Extraction of multiple-word terms

Transit now can extract also multiple-word terms (especially helpful e.g. for English and Roman languages).

Change terms to basic form during extraction

You can now edit the suggested terms directly in the Extract terminology window to change the terms to their basic form before saving them in the dictionary.

To edit a suggestion, select it in the Suggestion column. Then click the suggestion again, edit it and confirm the change with the ENTER key.

Additional information on terminology suggestions

The Extract terminology window now offers the following information for each terminology suggestion:

Occurrences column: Displays how many times a term occurs in the language pair.

Words column: Displays how many words a term consists of.

Occurrences display field: Displays the text of all the segments in which the selected term occurs.

Limiting amount of terminology suggestions

You now can limit the number of terminology suggestions offered by using the following criteria:

By specifying the minimum and/or maximum number of times a suggestion should occur in the language pair.

By specifying the minimum and/or maximum number of words a suggestion should consist of (multiple-word terms).

Selecting target dictionary for extracted terminology

Additionally to the import to a new dictionary, the extracted terminology can now be imported to an existing dictionary. The new data records resulting from the terminology extraction are appended, not merged.

9. Enhancements in Project settings / File type settings

Excluding hidden cells/slides from the import

Transit now allows to exclude

hidden cells (columns and rows in Excel or OpenOffice Calc)

hidden slides (PowerPoint or OpenOffice Impress)

from being imported.

This ensures that hidden cells/slides remain untouched during translation.

For that purpose, the File type settings window has been added a new option Translate hidden cells/slides.

This function is available for Microsoft Office and OpenOffice/LibreOffice/OpenDocument projects.

Excluding text with certain paragraph styles from the import

The Ignore paragraph styles from list option now allows to exclude text components having been assigned certain paragraph styles from being imported. This ensures that contents with certain paragraph styles remain untouched during translation.

For that purpose, a list of paragraph styles not to be imported has to be created and selected beforehand.

This new option is supported for the following file formats:

Adobe FrameMaker

Adobe InDesign

QuarkXPress

Microsoft Word

OpenOffice / LibreOffice / OpenDocument

RTF

WordPerfect

For more information refer to » Document “Transit: Tips & Tricks for All File Formats”.

Optimising source language formatting during import

Transit now provides options for removing unnecessary formatting in the source language files during import. This way you can reduce time and effort for translating and assigning markups by avoiding these markups from being shown in Transit.

For that purpose, the File type settings window has been added a new section Optimise source language formatting.

Before importing the files you can select to remove the following unnecessary formatting:

Formatting on section/column/page breaks and tabs

Formatting for bold/italic on single spaces

All font formatting on single spaces

This function is available for all file types that are included with Transit as standard (except Interleaf, AutoCAD, and XML).

Importing bookmark names of InDesign files

Transit now supports the names of bookmarks in InDesign files so they can be translated.

You can specify in the PRJ file that bookmark names should be imported:

Make sure that the project is not open.

Open the *.PRJ file in an editor, go to section [ImportExport] and insert the following line:
ShowBMTitle=1

Save the PRJ file, open the project and import the project.

With value 0 (default), the bookmark names are not imported, but remain untouched during translation.

NOTE: With earlier Service Packs the bookmark names were not imported. This can reduce pretranslation results when using reference material that has been created with Transit before Service Pack 5.

10. Enhancements in Pretranslation options

Additional priority option for pretranslation: Language direction

For pretranslation, Transit now can prioritise reference files having the same language direction as the current language pair (i. e. the same source and target language). For this purpose an additional list box and the Language direction value has been added in the Translation priority section on the Pretranslation tab of the project settings.

NOTE: This new priority option is not compatible with earlier Service Packs.

If you use an earlier Service Pack while working on a project created with Transit Service Pack 7, consider the following:

For pretranslation, the Language direction priority option is ignored. The other options are considered according to their selected degree of priority.

On the Pretranslation tab of the project settings, the Language direction priority option cannot be displayed. Instead the default values of the respective list boxes are displayed.

As the selected priority options also define the order in which fuzzy matches are displayed in the Fuzzy window, you may check these values and change them if required.

Excluding unaltered segments from being used as reference material

On the Pretranslation tab of the Project settings window it is now possible to specify that unaltered segments in the reference material are not used for pretranslation (by checking the No pretranslation with unaltered segments option).

"Unaltered segments" are segments with an identical content (including markups) in source and target language.

11. Enhancements in Project exchange

Warning message when unpacking a TPF file twice

When unpacking a TPF file by double-clicking it, now a warning message is displayed if the TPF file has already been unpacked. This way the user can avoid overwriting existing data.

12. Enhancements in the Transit Editor

Information on language direction of references shown in Fuzzy window and Notes window

In the Fuzzy window, icons now indicate the language direction. You can specify whether the icon should be displayed or not. To do so, use the Show icon for translation direction option in the user preferences of the Dual Fuzzy option.

The Notes window now provides an additional row Language direction of references with one of the following values:

Identical: Reference has same source and target language

Vice-versa: Reference has reverse source and target language

Indirect: Reference has the current source and target language as target languages

NOTE: The language direction of a reference file can only be displayed if the reference files were created with Transit Service Pack 7 or later.

Displaying the content of footnotes or indices directly at the corresponding markup

Transit now allows to immediately find out which footnote or index corresponds to which segment. This helps you to improve the translation of both the current segment and the footnote or index.

To display the content of a footnote or index, Transit displays a bubble window when hovering the cursor over the markup of a footnote reference or index anchor. Using the context menu or shortcuts you can easily navigate between the current segment and the referenced footnote or index.

Displaying the markup type additionally to the markup ID

On the ribbon bar under View | Text/Markups | Options, the new Markup ID with type option displays the markup type additionally to the markup ID. This helps you to easily identify the markup type (an image, an index, a different font, boldface etc.).

The identification codes of the different markup types are also displayed in the Markup window.

13. Enhancements in Usability

Improved windows for file type settings

The following windows / tabs have been improved allowing the user to use the options more easily:

File type tab in the Project settings window

Filter tab in the File type settings window

Import project window

The usability of the Import project window has been enhanced:

Option for opening the File type settings window directly via the newly added File type settings button

Self-explanatory options in the Options for repeating the import section (especially useful for re-importing a project with new/additional reference material)

Improved messages during terminology check

During terminology check Transit now displays improved messages when you have not used the terminology from your project dictionaries.

New icon for calling up Dynamic Linking from the Terminology window

For or calling up the Dynamic Linking feature, the Terminology window now uses the same icon as the ribbon bar.

TermStar: Opening dictionaries by double-clicking

It is now possible to open a TermStar dictionary from the Open dictionaries window by just double-clicking its name.

14. Enhancements in User Preferences

New Transit Editor preferences

The following options can now be preset on the Transit Editor tab:

Display bubble window for indices and footnotes

Automatic keyboard switch

Keep capitalisation for capitalised terms in the source text

Create backup copy (interval in minutes)

Enhanced Dual Fuzzy preferences

The Dual Fuzzy tab now contains all options that are available via the ribbon bar selecting Matches | Fuzzy search (source) or Matches | Fuzzy search (target).

Switching on/off consideration of disallowed terms

In the Terminology search tab, the new Source language: Regard disallowed terms option allows to specify if disallowed terms in the source language should be considered during for background scanning for dictionary entries and performing terminology checks.

15. Enhancements in TMX export

Exporting the current project as TMX file

It is now possible to export the current project as a TMX file.

For that purpose, the Export current project as TMX option has been added to the menu of the Reference material resource.

New options for exporting data as TMX file

When exporting the current project or other data (any project, reference folder, reference file) as a TMX file, Transit now offers two more options:

Also export unaltered segments: Include or exclude segments with identical source- and target-language content from the export

Minimum segment status: Export only segments that have a specified minimum status

For more information refer to the » Transit/TermStar Reference Guide.

16. Enhancements in Internal Repetitions support

XLIFF: Support of Internal Repetitions

When unpacking an XLIFF project, Transit now analyses the unpacked data for Internal Repetitions.

This way, XLIFF projects now support the same Internal Repetitions functions as for language pairs created by a normal Transit import (e.g. the Internal Repetitions mode or Internal Repetitions in the Transit report).

TTX: Enhanced support of Internal Repetitions

When creating a Trados TTX project and importing TTX files, Transit now analyses the resulting language pairs for Internal Repetitions, even if the Use pretranslated segments from TTX file and skip Transit pretranslation option is checked.

This way, you can use the same Internal Repetitions functions for the resulting language pairs as for language pairs created by a normal Transit import (e.g. the Internal Repetitions mode or Internal Repetitions in the Transit report).

17. Enhancements in Reference material handling

New option for not permitting individual segments as reference material

You now have the option to not permit individual segments to be used as reference material. It is also possible to permit these segments to be used as reference material again.

You can also filter for segments that have not been permitted as reference material.

New function for storing language pairs as reference material

Via the Copy current project to reference folder option of the Reference material resource, Transit now helps you to store the language pairs of a finished project as reference material in a structured way.

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

18. Managing reference material in TM Containers

It is now possible to manage reference material in TM Containers.

For that purpose, the user creates a TM Container on a server and fills it by importing reference language pairs or TMX files. The reference language pairs or TMX files that are imported can be assigned specific attributes, e.g. a specific customer or subject. Based on these attributes, it is then possible to create different views of the TM Container.

The user can then use a specific view of the TM Container as reference material for a specific project, so that only the references e.g. for the specific customer or subject are used.

NOTE: The support of TM Containers is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

19. Enhancements in Tool windows

Web search tool has been enhanced

The web search tool has been enhanced as follows:

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

After entering the search string you can start the web search just by pressing the ENTER key.

PDF viewer window now also supports target-language Word preview

The PDF viewer displaying the source-language PDF file now also supports a target-language Word preview.

For generating a Word preview, open the context menu of the target-language section of the Transit Editor and check the Display preview in Transit option.

20. TermStar: Changing the entry type

Via the Change entry type to option in the context menu of the edit mode, TermStar now allows to change the entry type quickly and easily.

This way you can change e.g. a synonym into a disallowed term (subentry to subentry) or a main entry into a subentry, and vice versa.

21. TermStar: Support of File DSNs

TermStar now supports new DSN types when setting up ODBC connections to databases.

The DSN (Data Source Name) contains access data that TermStar needs for setting up a database connection. It can now be saved as a DSN file in the \config\global or \config\users\<user_name> folder of the Transit/TermStar installation.

This has many advantages especially if you have a network host installation or individual workstations accessing common network resources. The DSN files are saved centrally and can be managed centrally. It is no longer necessary to setup each database connection on each client separately.

Names of ODBC connections with file DSN are displayed with the suffix (Global) or (User).

22. TermStar: Extended data structure

Extended structure of data records

The structure of TermStar data records has been extended by the following fields / subentries:

Header field: Data record GUID

Entry and subentry fields: Entry GUID

Subentries: User index 1 to User index 5 (instead of only one User index)

Automatically created data record GUIDs and entry GUIDs

You can now specify for each dictionary separately if TermStar automatically creates an unique ID (GUID = Globally Unique Identifier) when creating data records and/or adding main entries or subentries.

The created GUIDs are displayed in the GUID header field or the GUID field of the main entry or subentry.

By means of the GUID, each data record created and each main entry or subentry added can be clearly identified.

NOTE ON WEBTERM: If you want to use the new fields (data record GUID, entry GUID, subentry GUID) or the additional subentry types (User index 2 to User index 5) in your WebTerm installation, your WebTerm installation needs to be updated. For more information, contact STAR (» Contact).

23. WebTransit: New version supporting additional Multi-user mode and XLIFF projects

The Service Pack includes a new version of WebTransit with the following enhancements:

Multi-user mode designed especially for translation agencies: This mode allows to switch the user processing a job ("User change possible within one job" mode). The complete job list, the connection settings and the files of all projects are available to all users at any time.

To this end, the data stored in the Transit directories config\global and projects must be available on the local network.

Support of XLIFF projects

24. General enhancements

Enhanced sorting of project templates

In all lists of project templates, the user-created project templates are now shown at the top of the list.

File type Microsoft Office for the predefined default project

The predefined Default project now uses the Microsoft Office file type.

Transit Freelance Pro: Microsoft Office filter now available

The Microsoft Office filter is now available for the Transit Freelance Pro product variant. The Microsoft Office filter allows to translate Word, PowerPoint, and Excel documents in one common project.

1. Support of Windows 8 / Windows Server 2012

Transit/TermStar can be installed and run on Windows 8 and Windows Server 2012.

NOTE: Transit/TermStar requires Microsoft .NET 2.0. During the installation of Transit/TermStar on a Windows 8 or Windows Server 2012, Microsoft .NET Framework 3.5 is turned on automatically. This requires an active internet connection and may slow down the installation process.

You may turn this feature on before installing Transit/TermStar: In Windows’ Control Panel | Programs | Programs and Features | Turn Windows features on or off menu, select the .NET Framework 3.5 (includes .NET 2.0 and 3.0) option.
NOTE: This also requires an active internet connection.

2. Support of InDesign CS6

Transit and the required plug-in InDesign Gate now support InDesign CS6 (Windows and Mac).

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

3. Support of QuarkXPress 9, 9.1, and 9.2

Transit and the required XTension XGate now support QuarkXPress 9 to 9.2 (Windows and Mac).

The XTensions are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing XGate and sharing data with Transit.

4. Support of AutoCAD R13/R14/2000/2012

Transit now supports to translate dxf files from AutoCAD R13/R14 and AutoCAD 2000 to AutoCAD 2012.

5. PDF viewer for RTF files

PDF files created from RTF files can now be displayed in the PDF viewer.

6. Additionally supported working languages

Transit/TermStar now supports the following Indian languages:

Assamese, Kannada, Malayalam, Marathi, Oriya, Punjabi, Sanskrit, Sinhala, Tamil, Telugu

7. OpenOffice spellcheck dictionaries

Many freely available spellcheck dictionaries (HunSpell compatible) are now installed to the spell folder of the Transit installation folder. Spellcheck dictionary files that are already existing in the spell folder are not overwritten.

For a complete list of all supported languages and the files installed, refer to the » Transit/TermStar Reference Guide.

8. Additional priority option for pretranslation

Transit now can prioritise matches having the highest segment status (e.g. Checked 1). For that purpose, an additional list box having the default value Segment status has been added in the Translation priority section on the Pretranslation tab of the project settings.

NOTE: This new priority criterion is not compatible with earlier Service Packs. If you use Transit Service Pack 5 (or earlier) to work on a project created with Transit Service Pack 6 (or later), consider the following:

On the Pretranslation tab of the project settings, the Segment status priority option cannot be displayed. Instead the default values of the respective list boxes are displayed.

For pretranslation, the Segment status priority option is ignored. The other criteria are considered according to their selected degree of priority.

As the selected priority criteria also define the order in which fuzzy matches are displayed in the Fuzzy window, you may check these values and change them if required.

9. Splitting virtually joined segments

Transit now allows to split virtually joined target-language segments at a particular cursor position. This option is available in the context menu of the Transit Editor.

10. Enhancements in working languages

With Service Pack 6 the display names for the following working languages have been changed:

Ibibio/Efik (language code EFI) changed to Efik/Ibibio

Flemish (language code NLB) changed to Dutch (Belgium)

In the Chinese user interface, the sorting of working languages was been revised completely.

11. TermStar: Importing more than one term per language into one data record

When importing a customised file format (e. g. an Excel terminology list exported as CSV or Unicode), it is now possible to import more than one term per language into one data record (corresponds to more than one main entry or subentry in TermStar).

REQUIREMENT: The columns of the import file must be arranged in a way that TermStar is able to assign the corresponding fields to the specific main entry or subentry correctly: The main entry term or subentry term must be followed by each of the respective fields before the next main entry term or subentry term follows.

For detailed information refer to » Document “TermStar Import/Export”.

1. Support of Adobe FrameMaker 10

Transit and the recommended plug-in FMGate now support FrameMaker 10.

The plug-in is available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing FMGate and sharing data with Transit.

2. Support of Adobe InDesign CS5.5

Transit and the required plug-in InDesign Gate now support InDesign CS5.5 (Windows and Mac).

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

3. Support of QuarkXPress 9, 9.1, and 9.2

Transit and the required XTension XGate now support QuarkXPress 9 to 9.2 (Windows and Mac).

The XTensions are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing XGate and sharing data with Transit.

4. Support for layers in Adobe InDesign and QuarkXPress

The new Ignore hidden layers option in the file-type settings allows to exclude hidden layers when importing Adobe InDesign and QuarkXPress documents in Transit.

Using the new Ignore layers from file option it is possible to exclude selected layers – regardless of whether they are hidden or shown in Adobe InDesign or QuarkXPress – from the import in Transit. For that purpose, a so-called layer file has to be created. The layer file then contains the names of the layers not to be imported and must be selected before the final import.

5. Support for MSSQL Server 2008 R2 Express SP1

TermStar now allows to run TermStar databases on MSSQL Server 2008 R2 Express SP1.

6. Splitting and joining segments in the source language

It is now possible to split a segment in the source language. This is especially helpful in case of wrong segmentation (which occurs e. g. if a blank is missing between two sentences in the original document).

Joining a segment with the next segment is also possible in the source language.

The corresponding segment in the target language is then split or joined automatically.

7. Report Manager for Quality Check

The Report Manager for Quality Check allows to analyse which and how many errors a translation contains in the check ranges Format check and Terminology check.

The errors found are displayed in the File navigation window, sorted by error type or by file (included in Transit as standard). Additionally, a quality report can be saved as HTML, Excel, or XML file (optional feature, needs to be enabled by licence number).

NOTE: The Report Manager for Quality Check is not supported by Transit Freelance.

8. Support for resource DLL files on WPF basis

With the Binary Resource File filter, it is now possible to import resource libraries on WPF basis and localise them in Transit.

NOTE: This feature requires Microsoft.NET Framework Client 4 and Microsoft Visual C++ 2008 SP1 Redistributable Package on your system (each with x86 or x64, depending on the Windows operating system).

Microsoft.NET Framework Client 4 itself requires Windows XP SP3, Windows Vista SP1, or Windows 2003 Server SP1.

9. Notes window: Display of previous translation (before modification in STAR WebCheck)

If a segment of a Transit translation has been corrected in STAR WebCheck, the previous translation (before modification in WebCheck) as well as the differences between the current translation and the previous translation are shown in the Notes window.

New shortcuts:

In the Notes window:

SHIFT + PLUS: Next modification from WebCheck

SHIFT + MINUS: Previous modification from WebCheck

SHIFT + CTRL + PLUS: Next target-language comment or next modification from WebCheck

SHIFT + CTRL + MINUS: Previous target-language comment or previous modification from WebCheck

In the target-language window of the Transit Editor:

SHIFT + PLUS: Next segment modified in WebCheck

SHIFT + MINUS: Previous segment modified in WebCheck

 

1. Support of Microsoft Office 2010

Transit now supports to translate Microsoft Office 2010 documents (including Word 2010, Excel 2010, PowerPoint 2010).

2. Support of Quicksilver 3.5

Transit now supports to translate Quicksilver 3.5 documents.

3. Preview for Microsoft Office formats

When translating Microsoft Office files (Word, Excel, PowerPoint) it is now possible to open a preview of the file in the corresponding Microsoft Office application. The Open Preview option can be found in the context menu that opens when right-clicking on a segment in the target language.

4. Rename option for unpacking project dictionaries

With a new project settings option, it is now possible to have project dictionaries renamed automatically upon unpacking a PPF file. The project manager can set this option in the project settings file (*.PRJ) of the project for which this function shall be available:

Make sure that the project is not open.

Open the *.PRJ file in an editor, go to section [Exchange] and insert the following line:

ReceiveDicsProjectMode=1

Save the PRJ file, open the project and pack the PPF file.

If the PPF with dictionaries is unpacked, TermStar will automatically add the project name to the name of the dictionary: <dictionary name>_<project name>.

If you delete this unpacked project, the project dictionaries can be deleted, too.

1. Support of MSSQL 2008

TermStar now allows to run TermStar databases on MSSQL 2008.

2. Support of Microsoft Office 2007

Transit now supports to translate Microsoft Office 2007 documents (including Word 2007, Excel 2007, PowerPoint 2007).

NOTE: If PPF files of a Word 2007 project is sent to a translator using Service Pack 2 (or earlier), the translator has to switch off the synchronised views for multimedia files. The two options can be found in resource bar Synch View:

Formats for the source view: Multimedia

Formats for the target view: Multimedia

3. PDF viewer for Microsoft Word

PDF synchronisation is now available also for Microsoft Word. The corresponding PDF must be created via Transit during import (» PDF creation upon import).

4. Support of Adobe InDesign CS5

Transit and the required plug-in InDesign Gate now support InDesign CS5 (Windows and Mac).

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

5. Support of QuarkXPress 8 and QuarkXPress 8.1

Transit and the required XTension XGate now support QuarkXPress 8 and 8.1 (Windows and Mac).

The XTensions are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing XGate and sharing data with Transit.

NOTE: Due to internal formatting algorithms some customer data may cause problems concerning styles.

6. PDF creation upon import

With the new option Create files for PDF viewer in the Import project window Transit will create PDF files for PDF viewer upon import of the project. This works for:

Microsoft Word files

Microsoft PowerPoint files.

For Microsoft Word projects, the PDF must be created via this function in Transit.

For Microsoft PowerPoint projects, the PDF can be created via this function, but it is also possible to create the PDF in any other way without Transit.

The option is available if the following requirements are fulfilled:

For the import Word 2007/Powerpoint 2007 must be available on the same computer since the PDF will be created during import. Word 2007/Powerpoint 2007 access is not necessary for later processing in Transit.

The Microsoft Office 2007 Add-in SaveAsPDFandXPS must be installed. This add-in can be downloaded from the Microsoft website. Once installed, it applies to all Microsoft Office products.

Once installed, it applies to all Microsoft Office products. During import of a Word/PowerPoint file (2007 or older), Transit will create a PDF for each file automatically.

7. QuarkXPress: Multiple file processing and PDF creation

From XGate 7 on, the XTensions now include functions for multiple file processing:

Creation of TTQ files

Creation of PDF files

Re-import of TTQ files.

8. Enhanced alignment

It is possible to move the cursor directly to segments with a certain alignment probability. It is also possible to move the cursor only to those segments where Transit suggests to delete a segment.

9. Enhanced About window

Information on the software protection (Site Code, Machine ID) has been added to the About window in standalone installations.

10. Display of active modes

The status bar indicates in which mode the user is working (e.g. alignment, internal repetitions, proofreading).

11. Project creation and exchange

Upon unpacking a project, the folder window has been enhanced.

Furthermore, it is possible to define a default scope and default folder hierarchy for project creation and exchange (User Preferences | Working folder).

12. Statistics: Additional Internal Repetitions options

Additional options for internal repetitions counting have been implemented in the report manager. It is now possible to define which units shall be counted:

All

Internal repetitions only

Without internal repetitions

13. New format check options

There are two new options for regular expressions in the following windows:

Review | Format check | Options | List of exceptions to remain unaltered

Review | Format check | Options | Check for protected words

It is possible to check the end punctuation via Review | Format check | Options | Check end punctuation.

14. Enhanced Terminology check

It is possible to allow exceptions during terminology check. If Transit finds a terminology inconsistency it will display a window in which you can highlight the translation that you would like to allow for the term in question.

This translation will be saved in the file \config\users\<user name>\<dictionary name> (<database name>)_<extension of target language>.TCA. This file is valid for all terminology checks by the same user with the same dictionary (specified in the filename).

15. Enhanced default settings for Fuzzy Matches

Some default settings have been changed:

Shortcut ALT + INS: In the Dual Fuzzy user preferences, the Activate Alt + Ins function for window option is no longer checked by default.

Matches | Fuzzy search (source) | Ins. 100% match: The default setting has been changed to Never.

These changed default settings only apply for new installations or if a new user is being created.

Processing | Confirm (same as ALT + INS) has been enhanced by the options:

Check spaces

Check end punctuation

Empty next segment.

Furthermore, it is possible to define how the differences are displayed in the Source Fuzzy window (User Preferences | Dual Fuzzy | Source language | Highlight updates with).

16. Enhanced Segment filter for Internal Repetitions

Enhanced segment filter options for internal repetitions are available.

17. Enhanced user role management

User role management and usability have been enhanced:

Password protection can be activated for user-defined roles.

Disabled groups on the ribbon can now be hidden.

18. Interval for backup copy

It is possible to define an interval for the backup copy of language pairs via Edit | Miscellaneous | Backup copy.

19. Enhanced background search for terminology

The following options for background search have been implemented (Transit menu | User preferences | Terminology search):

Search for exact matches only

Options for match case

20. Inserting terminology from markups

Markup terminology, which is marked in blue in the Terminology window, can now be inserted in a dictionary. With right click the term in the Terminology window, you can insert terminology in the current dictionary or use the rapid entry mode.

21. New version of WebTransit

The Service Pack includes a new WebTransit version with the following enhancements:

Support of SFTP/FTPS and HTTPS

Transfer of encrypted files

22. TermStar: Enhanced windows

The following windows have been enhanced:

Opening dictionaries and adding dictionaries as project dictionary

Details window for global changes in field contents

23. TermStar: Import / Export of TMX files

TermStar now supports:

Import of TMX files

Export of TMX files

Import and export terminology with standard data record filters

24. TermStar: Enhanced data record filter

Enhanced data record filter options for language entries and subentries.

25. TermStar: Enhanced Import / Export options

The Import / Export options have been enhanced by data record filter options.

26. TermStar: Enhanced Merging

For merging dictionaries it is now possible to define more than one language for synchronisation.

1. Enhanced performance

The speed performance has been improved.

2. Support of DITA

Transit now supports to translate XML files based on DITA DTD.

1. Support of QuarkXPress 7

Transit and the required XTension XGate now support European QuarkXPress 7 (Windows and Mac).

The XTensions are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing XGate and sharing data with Transit.

NOTE: Due to internal formatting algorithms some customer data may cause problems concerning styles.

2. Enhanced installation

The installation routine has been enhanced.

3. Enhanced Alignment Tool

Alignment features have been updated for a more user-friendly design and intuitive behaviour.

4. Enhanced Report Manager

Reporting has been enhanced.

5. Enhanced Transit Editor

Processing speed has been enhanced in language pair handling. Segment handling and navigation have been improved.

6. Proof reading for Internal Repetitions

Proof reading for Internal Repetitions has been implemented.

7. Enhanced Project Browser

The Project Browser now handles UNC names.

8. Enhanced Review Tab

Review tab functionality and usability have been enhanced.

9. Enhanced user role concept and presentation

User role definitions and presentation have been improved.

10. Additionally supported working language

Transit/TermStar now supports the following language:

Khmer (language code KHM)

11. Additionally supported UI languages

Transit/TermStar now supports the following dialog languages:

Chinese

Spanish

Japanese

12. Icon for online help

The online help can be accessed via a separate icon.

13. TermStar: Enhanced data record filter

The following options for data record filtering have been added:

Display of language entries in all languages

Selectable filter application on subentries.

1. Support of Adobe FrameMaker 9.0

Transit and the recommended plug-in FMGate now support FrameMaker 9.0.

The plug-in is available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing FMGate and sharing data with Transit.

2. Enhanced support of Adobe InDesign CS2 / CS3

Enhanced plug-ins for InDesign CS2 / CS3 (Windows and Mac) are released.

The plug-ins are available in the » Downloads | Transit & TermStar | Accessories area on our website. There you can also find the latest documentation on installing InDesign Gate and sharing data with Transit.

3. Enhanced installation

The Installation routine has been enhanced.

4. Support of MySQL Version 5.x

TermStar now allows to run TermStar databases on MySQL Version 5.x.

NOTE: This feature is optional and needs to be enabled by licence number. For more information contact STAR (» Contact).

5. Enhanced setup

Setup has been enhanced.

6. Enhanced segment filter

Segment filters have been enhanced.

7. Enhanced Alignment Tool

Alignment features have been enhanced.

8. Enhanced editor

General editor capabilities have been enhanced.

Virtual joining segments feature has been enhanced.

9. Enhanced spellchecker

Reference-based spellchecking has been enhanced.

Enhanced open-source Bulgarian spellchecking is available.