And the winner is… (2 of 2)

Welcome to the second post about the survey we organised about a month ago. In our last post about the poll, we commented on the priorities that users assigned to the different options we had suggested. This one will be dedicated to the “Others”, i.e. we would like to offer an answer to each of the points made and we’ve only left out those wishes that were already on the list that could be voted for. In those cases where the desired feature is not already part of Transit’s functionality set or the desired outcome cannot be achieved with current functions, the point will be passed on as a Request For Feature to our development.

Full number localization

There is already a feature in Transit that enables the user to revise number formats in the target language. The feature is part of the Format check functionality and it adverts the users during format check if the numbers in the target text do not comply with the selected format. There are multiple option to determine what number formats should be used in the target language. (dot to comma, dot to space, space inserted etc.). The functionality does not change the numbers though, it only issues warning messages. A “Change & Check” option during format check might be a helpful addition to that function.

Number format check options and warning message

Number format check options and warning message

Using regular expressions with the Search & Replace function in Global View can also be extremely helpful if you want to carry out global changes of number or date formats.

Better Alignment

Not very specific, but point taken.

Visors for translations for mobile phones, tablets

Forwarded as RFF.

Delete the remaining segment text in one move

This feature already exists. In the ribbon Processing, select Delete to end of segment under Confirm, and Transit will delete the entire source language text when you hit Alt-Insert to confirm the translation.

Grey-out view for pretrans (so it is visible but not editable)

Forwarded as RFF.

Improve scrolling of html preview. (Centered and synchronized)

Forwarded as RFF.

Integration with Xbench

Transit already offers multiple checking functions and this is one of many areas where continuous improvements are introduced. What error checking options are missing? Please be more specific.

Easy segment joining around hard line breaks

Transit already enables the user to join segments by using the “Virtual Segment Join” function. Thus, two sentences or segments in the source language can be joined into one segment or one sentence in the target language. To allow the user to join segments around hard line breaks would be against the principle of not allowing the user to tamper with certain formatting characteristics of the source publication. It could also have a negative effect on the segment count so that the very essence of a translation memory, the equivalence of source and target segments would get lost.

Morphology background search in Dutch that is accurate and useful

The morphological algorithms are an area of continuous improvement in Transit. To improve the morphological search yourself, you can also use the Subentry field Alternative Term to add inflected noun or verb forms to a dictionary entry.

Morphological search in action

Morphological search in action

Previews for more formats

There are already multiple views of the original file or dynamic previews available in Transit NXT. The PDF viewer offers a synchronized view of the source file for the following formats: FrameMaker, InDesign, QuarkXPress, Word, RTF, PowerPoint. The dynamic preview is available for MS Word, HTML and when you translate binary resource files (*.exe, *.dll). What other formats would you like to preview?

Ability to import and export PDF files

PDF is not a working format but a publishing format. Wherever there is a PDF file, there is a source format somewhere. If it is not possible to get the source file, the best way to deal with PDF files is to use the conversion and / or export functions of Adobe PDF or other conversion tools to create an editable format that can then be imported into Transit.

Option to save project/check/user settings and apply them to other projects

All these  features already exist in Transit.

You can create project templates in addition to the already existing ones and use these templates for project creations. The format checking options are part of the project definition and thus can also be saved into a template. Another way of reusing project definitions is to base a new project on an already existing project, as you can see in the following screenshot. Both options, creating a new project based on a template or based on an existing project, invoke the project creation wizard, but with fewer steps to fulfil since most of the project definition options are already established.

Create new project based on a template or another project

Create new project based on a template or another project




The third but a bit more tricky option is saving a project under a new name and change those settings that need to be changed (folders, for example).

With regards to user profiles, you can create different ones, save them and use them for different types of projects. They can also be passed on to other users so as to standardise the use of certain views, for example.

Deactivation of tag protection

Certain tags can be deleted and inserted in Transit, but to allow users to deactivate tag protection entirely would mean allowing them to tamper with formatting characteristics of the source document. This could hamper the export and the recreation of the original format.

Interface overhaul, get rid of ribbon interface, bring back drop down menus

I know from my own experience that it takes some time to get used to the ribbon interface, but once you get to grips with it, it is actually better than the old drop down menus. That is the general feedback from most of the users and to return to drop down menus is therefore an improbable scenario. To gain more space, the ribbons can be hidden from the view so that a ribbon only opens when it is selected.

Seperate import of slides and notes of PPTX files, not just slides

Transit’s File type options for MS Office already include an option for the processing of the notes.


File type settings for MS Office


Internal repetitions in pretranslated segments

In addition to internal repetitions mode for translation purposes Transit NXT offers a special mode for displaying and checking internal repetitions – internal repetitions proofreading mode. Internal repetitions proofreading mode allows the user to check internal repetitions for consistency in a targeted manner. Please be more specific if this is not what you meant with your suggestion.

I hope we covered most of the points. Please feel free to send more detailed comments or suggestions if you are not entirely satisfied with our answers. And once again, thank you for you help.

About Michael Scholand

GILT professional with over 15 years experience in technical translation, business software and games localization. CEO and founder of STAR Servicios Lingüísticos. CAT tools and Translation Management Systems expert.
This entry was posted in Uncategorized and tagged , , , , , , , , , , , . Bookmark the permalink.

7 Responses to And the winner is… (2 of 2)

  1. örjan skoglösa says:

    One more feature other tools offer and we miss very much in Transit is the export/import for external review. Together with track changes it´s very useful, easy to handle and a real time saver. We use it a lot. BR, Örjan

    • Hello Örjan, thank you for your contribution. If you have imported the original file(s) in the first place, you can export at any time to the original format and send that to the revisor. If you have received the project from a client, then you need the .COD file(s) to export. If neither is the case the “Print” option might help. You can print segment pairs (w/ or w/o notes, w/ or w/o revision bars etc.), either to your printer or into a PDF file and send that on to an external revisor. Hope one of these options does the trick for you!

      • örjan skoglösa says:

        Hi Michael,
        Thanks a lot for your reply. Although, I think you should have a closer look at how your competitors feature works. The trick is that you regardless of prior handling, e.g. also after the reception of project packages, are able to export source and target segments to a format (most easily a table) into which the proof reader inserts the proposed changes with track changes on.
        The file is then returned to the translator who re-imports it into the tool, directly replacing the former target. The translator accepts or rejects the suggested corrections either in the file or after import in the tool.
        The most serious advantage is that the work just needs to be done once and in a way that keeps the bilingual structure (and thus the future memory) updated.
        The need for double work was formerly a big issue with all tools, as it still is with Transit.
        BR, Örjan
        PS. To an amateur it seems like an augmented segment pair printing feature should be a good starting point.

      • Hello Örjan. There are QA reasons why there is no export/import for external review. Export into and import from external formats adds further complexity to the process and is highly error prone, just think of tag and segmentation issues that might occur. Also you can define your output (your export format) but you don’t have control about the input (the reviser might send you back anything). Additionally, many of the advantages that a reviser has in Transit are not necessarily available in external formats (context, revision history, comments, terminology support, automated quality checks [tag, format, numbers and number formats, terminology, untranslated words or segments, etc.]. STAR has a tool called Webcheck for online in-country reviews, i.e. you can access Transit files via your web browser, revise, comment and modify them, but right now, the tool is only available as part of STAR’s Corporate Language Management Solution. I have been just thinking about another possible, elegant workaround, that might be viable for certain projects. You can export your current project into TMX, have the reviser proof-read the TMX, import the TMX back into Transit and use the resulting Transit files as reference material.

  2. Gero says:

    Deactivation of tag protection was a useful feature in Transit XV and very helpful, for example, in cases that you have to make reports to your PM. In my daily work I often need to to pick-up content informations of the tags but just even cannot copy and paste them!

    THE solution for not allow every “user” to change these informations in order to prevent export problems could be to unlock this option only in combination with the “super user” profile choosed by starting NXT – this could ensure that only experienced users could use that function.

    • Hello Gero, hit F4 in any window (source, target, TM) to bring up the “old” display options dialogue. There you can select “Deactivate Markup Protection”. This will at least allow you to copy whatever tag and maybe some other actions as well.

      • Gero says:

        Hello Michael
        many thanks for this hint ! This is indeed very helpful for me.
        Have a nice day

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s