TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Assuming that the proposed localization company uses some sort of
translation memory (Trados, etc.), the only thing you should have to do
is provide them with a complete set of your original FrameMaker docs,
including all referenced files and graphics, along with some basic
information. You shouldn't have to do anything more than that.
The localization company *should* be able to take care of everything
else, including DTP of the final translated docs. If they can't, then
in my opinion you need to find another vendor, because a reputable
localization vendor should do a final Quality Assurance (QA) check on
the docs AFTER DTP to ensure that there are appropriate line breaks,
hyphenation, etc. Unless you fluently read all of the languages you are
translating into, you are not qualified to make this check. Also,
depending on the languages being translated into, you might have to
localize your computer into that language to get the proper behavior in
Frame, and that's a bit of a pain.
Here's a basic outline of what I do/suggest:
1. Create an archive of the completed FrameMaker files. (In our
department set-up, absolutely NO content changes can be made in this set
of files -- it is a copy only.) The Archive plug-in does this nicely,
pulling in all graphics and other files from wherever they might be
referenced, and making a stand-alone folder with everything in in. See http://home.comcast.net/~bruce.foster/products.htm for the Archive
plug-in.
2. Make sure that all conditions (if used) are set the way they should
appear in the final doc. Supply a list of conditions to show/hide to
the translation vendor.
3. If any graphics need to be localized, indicate which ones. If it is
software screen captures, provide the software or other means to the
vendor so they can capture the localized screens. If you can provide
the localized graphics, then include them in subfolders sorted by
language. If the English file is named graphic1.png, then the French
file should also be named graphic1.png -- this allows easy
replacement/linking in the FM files without manually reimporting the
graphics.
HINT: It is highly recommended that you do NOT embed text within a
graphic. The vendor will have to open the graphic and make the
translation inside the graphic itself. This increases cost
significantly if you have several of them. All callouts on our graphics
are put on in FrameMaker, using text boxes (not just the text tool).
All text within text boxes is captured and then translated in the normal
process.
4. Provide a list of the languages to be translated into. Don't forget
to indicate if the part number is different for each language, as it is
for our docs.
5. If you have a glossary of terminology specific to your product, be
sure to provide it to the vendor. It will reduce questions from the
translators regarding industry-specific items.
6. If you will have in-country/native language reviewers, include them
in the process. They should review the content BEFORE the final QA.
(Translate > Initial DTP > In-Country Reviewers > Incorporate any
changes > Final DTP > Final QA).
7. The localization company should provide back to you:
A. All localized Frame files.
B. A PDF (with bookmarks) for each language.
Also, make sure IN WRITING that your translation memory (TM) belongs to
YOU/YOUR COMPANY, and not to the vendor, and that you are free to
request a copy at any time for any reason. This is standard procedure,
and if the vendor balks at this, find another vendor. One reason they
might not like hand over the TM is that you can take it and go elsewhere
if you're not happy.
Some people have the vendor include a copy of the TM with each
deliverable, so you always have the current TM. I have a great working
relationship with our vendors, so I don't feel that this is necessary in
our case.
-----Original Message-----
From: techwr-l-bounces+cmartinek=zebra -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+cmartinek=zebra -dot- com -at- lists -dot- techwr-l -dot- com] On
Behalf Of Khizran Kaleem
Sent: Tuesday, March 27, 2007 12:29 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Localizing Documentation
Hi,
I am currently working on user manuals using FrameMaker 7.2. Now the
company wants to sign a contract with a firm who would help us localize
the contents. I have absolutely no idea in what format should I send my
docs to them. I understand that if I export it to some other format, I
would have to put in quite an effort to import and do the formatting for
the contents all over again in FrameMaker. Can anyone please suggest how
should I go about it?
- CONFIDENTIAL-
This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
