The instructions Mathieu is referred to are part of what is usually called a
localization kit.  The kit includes all of the files you want translated +
the instructions.  The instructions explain what each file is, how the files
are related (FM book + chapter files, etc.) where they are included in the
zip files you send, and what you want done with the files.  This is
especialy true if you are having a product translated.  You need to explain
what you want translated and what you don't.  For example, the internal
markers (index, links, etc.) are never translated.  The vendor should know
that but it's good to make sure.  You also should include a glossary of term
used in your industry.  I have a sample kit that includes all the details if
you want it.

The internal proofreaders are usually people in the offices located in the
countries where the language(s) of the translated docs are spoken.  it is
often advantageous to include them in the process from the beginning.

This and a lot more is explained in the book I told you about.


-----Original Message-----
[ at]On
Behalf Of mathieu jacquet
Sent: Tuesday, June 06, 2006 2:40 PM
To: karyn_hunt at; framers at
Subject: RE: Framemaker and Translation


I happen to work as a project manager as well as a translator (English to
French ; Trados, Translation manager, Deja Vu, Fast Help Translation
Assistant and so on...) and technical writer (English and French ; mostly FM
and Word) in a multilingual documentation services company (translation,
technical writing, multimedia communication, etc.) based in Toulouse,

Ideally, what you just have to do is develop your documentation, using
either Word or FM or whatever tool meets the needs of your documentation
team, and then send your files, whatever the format (html, mif, xml, doc,
rtf, idd...) , to the vendor.

The vendor is supposed to take in charge the whole process of translation,
from format conversions, creation and setting of the Translation Memory
depending on your needs (if you don not have one already), alignment of
existing multilingual documents (aligning a text means taking two similar
texts, one in English and one in French and make their segments - i.e.
sentences - correspond in order to feed a TM). If you send an HTML Web site
page, then you'll receive an HTML Web site translated page ; send a pdf and
you'll have the same pdf translated ; same thing for FM, Word documents,

You can also send a .doc and ask for a .pdf, and inversely. Possibilities
are multiple.

The biggest part your team will have to do is to prepare INSTRUCTIONS as
regards : layout, products, software (are they translated or not ?),
copyright, part numbers and revisions (references, same in English and in
other languages..?), abbreviations (are they translated ..?), etc. The more
precise the instructions, the faster and the more accurate the translation.
Be sure to have available internal proofreaders at hand too...

Hope this will help, do not hesitate to contact me for more information.



Mathieu Jacquet
Raptrad-imagine (
Toulouse, France

>From: "karyn hunt" <karyn_hunt at>
>To: framers at
>Subject: RE: Framemaker and Translation
>Date: Tue, 06 Jun 2006 19:38:05 +0000
>Another place to bone up quickly: There's a company called Enlaso that does
>translations. They recently did a Webcast called Translation 101 in which
>they went over all the basics. I think they have that Webcast stored on
>their website. I found it tremendously helpful just in getting a broad
>overview of things to think about, what to look out for, what's involved,
>etc etc etc.
>From: "Ann Zdunczyk" <azdunczyk at>
>To: "'Diane Gaskill'" <dgcaller at>,"'Loren R. Elks'"
><lelks at>
>CC: 'Framers List' <framers at>,
>framers at,swiseman at
>Subject: RE: Framemaker and Translation
>Date: Tue, 6 Jun 2006 12:58:59 -0400
>>I agree with everything that has been said so far. Definitely check with
>>your vendor to make sure that they handle the technology that you are
>>writing about. Some translation houses specialize in different
>>(Medical, Telecom, Legal, etc.)
>>Trados by the way was based in Ireland and German if I remember correctly.
>>It has now been purchased by SDL.
>>If you have any other questions let me know.
>>Ann Zdunczyk
>>a2z Publishing, Inc.
>>Phone: (336)922-1271
>>Fax: (336) 922-4980
>>Cell: (336)456-4493
>>-----Original Message-----
>>From: at
>>[ at] On
>>Behalf Of Diane Gaskill
>>Sent: Tuesday, June 06, 2006 12:47 PM
>>To: 'Loren R. Elks'
>>Cc: 'Framers List'; framers at; swiseman at
>>Subject: RE: Framemaker and Translation
>>Loren, all
>>There is a book called Localization and Framemaker that explains the
>>of localization, tells you how to find, screen, and hire the RIGHT vendor
>>for the work you are doing, what you need to provide to the vendor to get
>>good estimate for your job, how to work with the vendor, and explains what
>>the vendor can actually do for you. It explains the localization process
>>(what the vendor does with your files) and contains a table of prices that
>>you can use to get a fairly good idea of how much you can expect to pay
>>their services. The book is a 24-page pdf file that you can download free
>>Note that ALL localization vendors can take a set of FM files and give you
>>the same set of FM files back, translated into as many target languages as
>>you desire.
>>Incidentally, Trados is a company based here in the Silicon Valley, not an
>>application. Trados makes a set of software tools, including the S-tagger
>>and the Translators Workbench, that is the industry standard toolset
>>But it is not the only set of tools on the market and some vendors use
>>tools instead, including home-grown ones. Some of these tools are
>>compatible with each other and some are not. When you talk to the vindor,
>>find out which toolset they use and ask about compatibility with the
>>toolset, and particularly about the TM. TM = translation memory - a
>>database that stores translated words, phrases, and paragraphs. Using the
>>TM is optional, and little more expensive if they use it to start with,
>>can save you a lot of $ when upgrading your docs, online help, software,
>>etc. They just pull the already translated text out of the TM and add the
>>changes. BTW, the data in the TM is something that you own, not the
>>and they should give it to you when the job is finished. That way, if you
>>change vendors, you can continue from where you left off and not pay to
>>the whole doc translated again.
>>Hope this helps.
>>-----Original Message-----
>>From: at
>>[ at]On
>>Behalf Of Stephen O'Brien
>>Sent: Tuesday, June 06, 2006 7:44 AM
>>To: swiseman at; 'Loren R. Elks'; framers at
>>Cc: 'Framers List'
>>Subject: RE: Framemaker and Translation
>>Hi Steve,
>>I've been reading this thread with interest as our documentation (FM) is
>>going to be translated into German and Japonese starting in January 2007.
>>The people at the other end are distributors who are going to have to put
>>together an efficient workflow. You mention in your comment being able to
>>provide details...I am very interested...
>>At 10:45 AM 6/6/2006, Steve Wiseman wrote:
>> >We use translators that can take the FM files and return them as FM
>> >files including any marker and conditional text in the document. If you
>> >want details, please let me know. We have been happy with the results.
>> >I recommend them as they use translators in the destination country
>> >rather than locals from here.
>> >
>> >For your information, they use an application called Trados that
>> >imports
>> >files.
>> >
>> >Best regards,
>> >Steve
>> >
>> >
>> >Steve Wiseman
>> >
>> >CEO, Context Documentation and Interactive Services
>> >
>> >Official MIF2GO Resellers and Trainers
>> >
>> >
>> >
>> >Tel (Isr): +972-2-999-7816
>> >
>> > (UK): +44-845-244-7802
>> >
>> > Mob: +972-522-341-957
>> >
>> >Skype: zusman
>> >
>> >
>> >-----Original Message-----
>> >From: owner-framers at [mailto:owner-framers at] On
>> >Behalf Of 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
>> >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
>> >

Reply via email to