Re: Incorporating third-party books

Subject: Re: Incorporating third-party books
From: Janice Gelb <janice -dot- gelb -at- sun -dot- com>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Wed, 25 Jan 2006 13:09:35 -0800

Jessica -dot- Nealon -at- handheld -dot- com wrote:

Does anyone on this list have experience with re-branding, re-distributing, re-writing (?) another company's manual as your own?
This is a situation where your company purchases the rights to sell another company's software product under your company's name.
The software product already has documentation from the original company that is updated with each build just like your own documentation.
As the tech writer, you have to develop some kind of strategy for the documentation your company distributes for the product. This is a product that 1) you don't know, 2) usually don't have the time to learn (because of the compressed release cycle), and 3) has documentation you inherit but have no control over from release to release.
There can be source files exchanged or not. There can lists of changes from that company or not. Lastly, you may or may not have access to the tech writing group at that company, for whatever reason. So, how do you develop a coherent strategy? Both for initial release and maintenance of your document? Do you simply re-distribute their guide at each release and write your own adjunct startup guide?

The only experience I've had that vaguely seems
similar is products from companies that we've
just bought and are about to be released.

As other people have noted, make sure you have
access to the source files. We've generally quickly
reviewed the docs to make sure they conform to our
legal guidelines, and checked them for spelling and
egregious grammar errors. We also give the other
company's writing department our editorial style
guide in the hopes they might conform to some of
it :->

-- Janice
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l

Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at http://www.componentone.com/TECHWRL/DocToHelp2005

---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
To unsubscribe send a blank email to techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.


References:
Incorporating third-party books: From: Jessica . Nealon

Previous by Author: Re: XML: XHTML vs. DITA/DocBook
Next by Author: Re: Items in a Series and Comma Use
Previous by Thread: Re: Incorporating third-party books
Next by Thread: RE: Incorporating third-party books


What this post helpful? Share it with friends and colleagues:


Sponsored Ads