tt4t.net
tips & tricks
for translators
SDLX, Transit, & WordFast  
Contents  
SDLX

Working with SDLX files (.itd)

???


1. Load itd file in SDLX Edit. You have to do this file by file :-(

TIP: (MIri Ofek) - SDLX does not export locked rows to TTX. E.G.: It is possible to lock all 100% matches or fuzzy matches (see Edit menu).

2. Export using Export to TTX format. Resulting file ending in ttx.
Go to File > Trados > Export to TTX Format


3. Create Trados project in DVX — be carefull to use the same sub-languages set in SDLX. E.g.: If SDLX uses EN-US, DV should use EN-US (and not EN-GB).


4. Import .ttx files into DVX


5. Translate in DVX. REMEMBER: While translating in DV, DO NOT split/join cells.


6. Export using Encoding option Unicode (not Unicode UTF-8)


7. Import using the SDLX option:
File > Trados > Harvest exported TTX translation.


8. Deactivate the SDLX options Auto-Propagate and Auto-Match before you start confirming the segments in SDLX.


9. Check the itd files and confirm every translation (Edit>confirm/unconfirm confirm all three options (100%, fuzzies. untranslated) subsequently). Most of the codes should be preserved and put in the right location.

 

WARNING (Rob Laumen):
This route does NOT work with MIF files being translated in SDLX. From SDL:

The Export to Trados S-tag and Harvest TTX functions are not suitable for working with FrameMaker files.

The workaround would be to export the ITD to TTX anyway (perhaps even locking full matches if the client does not want you to touch those), import the TTX file in DVX, translate the file in DVX, export the memory, import it into your SDLX memory and work through the segments in SDLX.

OR

From Norbert Hofmann

    1. Open the itd file in SDLX.

    2. Select the whole right-hand column. For me the easiest way is by clicking in front of the very first word, scrolling down to the end of the file, holding Shift and clicking with the left mouse button.

    3. Ctrl+C

    4. Open an empty Word file.

    5. Ctrl+V into the Word file. The whole text of the itd is in the Word file then. The segments are in individual paragraphs. Save the file.

    6. Translate this Word file as usual in Déjà Vu and export.

    7. Select the whole text in the translated Word file.

    8. Select the whole right-hand column in the itd in SDLX again.

    9. Insert the text (Ctrl+V).

    10. Carry out format painting in SDLX.

    11. Confirm all translations in SDLX.


Top - Home/Disclaimer

Cannot import files back into SDLX

The two main reasons for not being able to import files back into SDLX are:

1 - Wrong encoding option selected in DV

When exporting your file from DV, the encoding option should be UNICODE (and not DV's default UNICODE UTF-8).

2 - Sub-languages are different

DV's and SDLX's sub-languages should be the same. E.g.: if US-EN in DV and US-GB in SDLX, re-import fails.


Top - Home/Disclaimer

 

TRANSIT

Working with PFX files

PXF is a compressed (zipped) file. Unzip your PXF file and import language pair file (SGML format) into Déjà Vu using Déjà Vu's specific filter (TransitSGML.dvt). 

Alternatively

Alessandra Muzzi

I use the OpenOffice filter and it works like a charm. Here are the full
instructions:

1) Rename your Transit PE project file, filename.pxf, to filename.zip. Unzip its
content to a folder. You will get a set of files with two types of extensions
for source and target (e.g. .ENG and .DEU).

2) Import the target files (e.g. .DEU) into DV via Project Explorer. Under
" Properties", select the following settings:
Filter: SGML, XML
Filter Definition File (or segmentation file): OpenOffice.dvflt (you will find
it in your DVX installation folder, under Templates.)
Prevent Segmentation: activated
Encoding: (Default)

3) Translate as usual.

4) When you export the files, select the following settings:
Encoding: Unicode
Export special characters as entities: deactivated (note that, if there are
special characters in tags, these should be converted to entities - in this case
the exported files will have to be amended manually)

5) Copy the exported files back in the original folder, overwriting the old
files.

6) If you have Transit, use it to send the project (and optionally confirm
segments and check that everything is OK before creating the TXF file).
Otherwise, just zip everything back and rename filename.zip to filename.txf.

NOTE:

The target files should be imported. Before the project is translated, they will contain source text. Should any segment be pretranslated, it should be just copied to target. OTOH, if a large part of the project is pretranslated, and you want to send all appropriate source-target pairs to the memory database, the procedure is a bit more complicated, since you have to align source and target (only the pretranslated parts) and send the TUs to an empty MDB, then create a project and import _source_ files, then run a pretranslate using the memory from alignment. Been there, done that.


Top - Home/Disclaimer

Sentences broken in several TUs

Roy Oestensen

Edit sentence delimiters (Tools > Options > Sentence delimiters). Add the following rules (Exceptions side):

Before split: 

After split:

>

^?

>^w

^?

^#

<

^$

<

^?

<

^w

<


Top - Home/Disclaimer

Working with Transit XV

Klas Törnquist, Eva G., & Ignacio Hermo—it seems this was in DV's and ProZ's lists.

I have copied the following from ProZ (thanks to Ignacio Hermio!):

Here is an example to process Transit XV files with DVX:

1) Change extensions of the target language Transit files, for example, .ESP (Spanish) will be .xml. To rename a batch of files at one time, you can use freeware, such as CKrename. (Klas' comment: You can do that in DOS session: "ren *.swe *.xml")

2) Import the xml files into Déjà Vu via Project Explorer. Under "Properties", select the following settings:

        • Filter: SGML, XML
        • Filter Definition File: OpenOffice.dvflt (look for it in the appropriate folder)
        • Prevent Segmentation: activated
        • Encoding: (Default)

3) Translate as usual.

4) When you export the files, select the following settings:

        • Encoding: Unicode
        • Export special characters as entities: deactivated

5) Rename the xml files back to the corresponding target language extension. In this example, rename it to .ESP.


Top - Home/Disclaimer

Importing a Transit Termstar dictionary

Hans

1. Export the Termstar dictionary to ANSI (using Termstar).

2. Import into DVX.


Top - Home/Disclaimer

WORDFAST

Importing a WordFast TM (.txt) into DV

Rene

Save it as .TMX and import it as such,

or

Remove all columns except source an target and import as tab-delimited file.


Top - Home/Disclaimer