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.
Get over your reasons. The issue here is usability. If your
company expects your customers to do something with your
documents after receiving them. you need to provide them
in a form that they can use. However, since most of your
customers are unlikely to be readily able to use Frame, the
simple answer to both concerns is to convert the source
files to RTF/Word.
----- Original Message -----
From: "Trina Pearce" <tpearce -at- ubiquitysoftware -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Sent: Wednesday, August 02, 2006 7:34 AM
Subject: Crazy situation: Customer responsible for translation
My company has decided that we will not translate our docs. Our
customers will be responsible.
So now, our doc team is faced with the task of determining what type of
files to provide our customers with so they can have the documentation
Currently, our delivered English documentation is via PDFs.
Has anyone run into this issue before? If so, what type of files to you
provide to your customer in order for them to translate?
For several reasons, as you can imagine, our team doesn't want to hand
over the source Frame files to the customer.