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.
Subject:Re: Advice on rewriting translated ops manuals From:Lois Patterson <loisrpatterson -at- gmail -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Tue, 25 Jun 2013 10:30:23 -0700
It's reasonable that they would be cost-conscious. What are the costs and
benefits that are likely to ensue from rewriting the manual to conform to
your style guide? Based on the examples you posted, I see only a small
benefit in terms of readability. There's going to be a significant loss of
time to do this rewrite. What would the costs be? Are you likely to lose
sales with the current state of the manual?
On the other hand, if you need to fix actual extensive errors, the style
guide improvements might come along for nearly free.
Lois Patterson
> On 6/25/2013 7:34 AM, Anonymous wrote:
>
>>
>> I'm uncomfortable re-writing this manual based on our style guide even
>> though it is for our US clients and not theirs because I don't want them
>> to
>> feel snubbed. I'm also not sure if this manual has been translated yet (I
>> have asked the project manager to find out), so that will be a factor in
>> how much I change as they are VERY cost conscious and likely will not want
>> to pay for so many updates.
>>
>
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
