Telèfon: +34 93 244 08 80+34 93 244 08 80
Working with markup ID's can be quite tedious especially if the segments have a lot of markups. And it is not possible to avoid markups because if they are not inserted correctly, you may not be able to export your file. Therefore markups require special care while translation. Let's first understand what a markup ID is.
In this tooltip, we shall see different options for printing segments. This is an extremely useful feature offered by Transit NXT for proofreading purposes. Sometimes you might want to send segments for proofreading to a reviewer who does not have Transit NXT. In such cases you can print the selected segments of the project and send them for proofreading.
Transit NXT offers the following options for printing segments:
Short cuts – Nº 5 : Using AutoText to insert frequently occurring text while translating in Transit NXT
Do you often translate documents with long syntagmas that cannot be considered terminology and cannot be retrieved easily from the memory either? Imagine you have many occurrences of the syntagma "Halten Sie die Maustaste gedrückt" in your source and need to insert "Press and hold the mouse button" in the target.
The segment filter in Transit NXT is a very handy feature that allows you to show or hide subsets of a document. As a translator, for example, you can display only the segments with a very high fuzzy match value and translate these first, a procedure that will boost your productivity. Or as a proof-reader or project manager, you may want to first look at the segments that contain translator's queries in the notes window.
Notes is a very useful and practical feature provided by Transit NXT. As a project manager, you can enter notes in the "Source" field of the Notes window to draw the translator's attention on particular segments. And as a translator, you can enter notes in the "Target" field of the Notes window for pretranslated segments for example, or point out instances of unclear wording in the source text. Lets see how this works.
Translating into R2L languages like Arabic, Hebrew, etc. requires special care, especially when some segments are bidirectional, i.e., they contain both R2L and L2R sequences of text like the one shown below:
While translating languages with non-Latin fonts like Arabic, Chinese, Hindi, etc., you might sometimes wonder why the font is not correctly displayed in the Transit NXT translation editor. If you work with any of these languages in Transit NXT, you have to map the correct font with the language in question.
We are back again with another interesting and useful mini-post! We shall see a quick tip to save time while translating in the Transit NXT translation editor.
Trados TagEditor XML (TTX) files are bilingual files created in SDL Trados 2007 Suite or earlier. They are still very much in use as an exchange format to address compatibility issues between SDL Trados versions. They also enable other Translation Environment Tools to work with SDL Trados projects.
Did you know that you can re-import and pretranslate files in Transit NXT without the original files? It is one of many unique features in Transit and it allows you to maximize the leverage of your translation memory. This tool tip will show you how to go about it and what to watch out for. When might it make sense to re-import? Imagine you have received a Transit Project Package File (PPF) from a Multilingual Language Vendor client of yours.