I concur with Wim's analysis. Whenever I have seen this in the past it has
always been a case of someone using an incorrect version of Trados. Many
translation agencies use contract linguists and occasionally, such a
linguist will not have all of the correct filters or files when they prep
their translated work.

Your translation agency/vendor should be preparing the files and also doing
post-translation engineering to ensure that such glitches do not happen. 


Maxwell ?Hoffmann
Director, Document Globalization Practice
Globalization Partners International (GPI)???????
tel: 866.272.5874????????? direct: 503.336-5952????????mobile:
skype: maxwell.hoffmann         email:
mhoffmann at
Follow me on TWITTER:

-----Original Message-----
From: Wim Hooghwinkel - idtp [] 
Sent: Monday, January 12, 2009 12:17 AM
To: marc.creaghan at
Cc: framers at
Subject: Subject: Challenge with Trados

Hi Marc,

Indeed, best practice is to save as MIF and use that to work with Trados.
The Trados S-Tagger filters the MIF to either tagged RTF or STF - where STF
is the most reliable. This file wil be used by the translators and after
translation filtered back to MIF. STF is translated using the Trados Tag
The loss of accented characters is a known issue and indicates that your
client (or his translation agency) is not using the correct version of
Trados in combination with the right filters (i.e. compatible with FM 8.0);
The translated files (in RTF) are probably ok, but the filtering back to FM
causes the error. Using RTF for translation indicates thet probably an older
version of Trados is used. They should consult the Trados helpdesk (actually
SDL) to solve the problem.


Best wishes for 2009!

Wim Hooghwinkel

Adobe Certified Expert (ACE) in FrameMaker


International DTP and Documentation Consultancy

tel. +31652036811
info at

Reply via email to