AW: Documenting an OEM product

["Reng, Winfried" <winfried -dot- reng -at- msi-muenchen -dot- de>]

Hi,

> I'm on my own and flying blind. My client develops telecom 
> products that 
> will be OEM'd to one or more resellers (who are likely to be 
> very large 
> companies). I'm producing "user" documentation that 
> encompasses multiple 
> audience levels and multiple task types. My question is this:
> 
> Given that my documents will probably not be distributed in 
> their native 
> state, what are the most useful formats and doc structures 
> for you writers 
> out there who will get to "productize" my documents?  In other words, 

Our products are also sold by resellers and partners. But we
change layouts, product names etc. according to the specification
of the reseller. Our resellers get PDF files on CDs or printed
documentation as they like. They don´t get the original FM files.

I guess it depends on the contract.

If there aren´t any specific file formats or types of manuals
specified choose whatever you like.

Cheers,

Winfried

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr

  Your monthly sponsorship message here reaches more than
  5000 technical writers, providing 2,500,000+ monthly impressions.
  Contact Eric (ejray -at- raycomm -dot- com) for details and availability.

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.