To be more precise, Trados (Trados 6.0 at least) can deal with the following 
formats :

. FrameMaker and FrameMaker +SGML (.mif), Interleaf -> with converter
. RTF Workbench documents, Word documents  (.doc, .rtf), PowerPoint, Excel 
and Visio files
. Ventura tagged files (.txt)
. PageMaker tagged files (.txt)
. QuarkXpress tagged files (QSC,YTG,TTG,TAG)

When I say "deal with", I mean : the translator can open the file directly 
with Trados (Trados Workbench, S-Tagger or TAG-Editor depending on the 
format)  before translating the file.


>From: "Wim Hooghwinkel (Scriptware)" <wimh at>
>To: "Loren R. Elks" <lelks at>,"Framers (E-mail)" 
><framers at>
>Subject: RE: Framemaker and Translation
>Date: Wed, 7 Jun 2006 09:14:25 +0200
>Hello Loren
>Before you start looking for a translation company have a look at your 
>manuals and documentation and check if these are suited for translation. 
>There are many guidelines available (on the internet, perform a search for 
>'guide to localization' or similar), also from FrameMaker users. Note that 
>although your FrameMaker manuals may be set up to be perfectly printed or 
>converted to PDF, there can be many issues that frustrate proper 
>translation. Besides that, there are many issues to consider: 
>illustrations, software screens, software strings (menu items refered to in 
>the manuals), on line help, etc. You should take all this into account when 
>designing your international documentation.
>FrameMaker files can be saved as MIF and all translation tools can use MIF 
>files as input for translation, thus generating a translated MIF file that 
>can be opened in FrameMaker again. Basically all text will be replaced by 
>translated text, while keeping all formatting. But be aware that the 
>results may not be as expected when the documents are not properly 
>prepared. For example all 'tweaked' formatting and manual overrides (hard 
>returns, extra spaces) are maintained - the length of other languages will 
>differ from English text so results can be awkward (Spanish text will take 
>at least 140% more space then English text).
>If you don't use FrameMaker yet, you could consider to start creating XML 
>and publish using FrameMaker (or any other tool). XML can be translated 
>easily as well.
>You can contact me off list if you need any further help on this.
>Met vriendelijke groet / kind regards,
>Wim Hooghwinkel wimh at
>DTP and XML Management
>Scriptware bv
>tel : +31 (0)23 548 48 84
>fax : +31 (0)23 548 48 85
>info at info at
>Translation |  DTP |  Technical Writing |  Content Management |  
> >From: owner-framers at [mailto:owner-framers at] On 
> >Behalf 
> >Loren R. Elks
> >Sent: 06 June 2006 15:02
> >To: framers at
> >Cc: Framers List
> >Subject: Framemaker and Translation
> >
> >We are beginning to have to get our manuals and documentation translated.
> >What's the best way to set up this workflow.
> >
> >For example, do we develop in FM, then output to another format (say
> >RTF,etc), the translators use this format, we get it back, then convert 
> >with FM?
> >
> >
> >Sincerely,
> >Loren
>You are currently subscribed to Framers as bobitch at
>Send list messages to framers at
>To unsubscribe send a blank email to
>framers-unsubscribe at
>or visit 
>Send administrative questions to lisa at Visit
> for more resources and info.

Reply via email to