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.
> One of our customers, having received their first documentation in PDF
> format, proceeded to ask whether they could have editable files.
> Specifically, they want to change the references to system-assigned field
> names, substituting their customized names.
I experimented many years ago with a program that could be distributed to
customers who bought highly customizable telephone sets. The idea was that
they would use the program to enter how their telephone sets were programmed
and then push a button and have custom user guides printed from their office
printer. The prototype worked fine, but it wan never developed.
This is how I would do it today:
Store the documents in either in a database or in some form of markup (XML
Write a web application in OmniMark that would take the customization
information from the user, query the database or parse the markup, and
prepare a customized version in XML form.
Next, depending on the user's selection, the OmniMark program would either
generate an HTML page with the customized information included, or generate
a TeX file call out to TeX to produce PostScript or PDF to deliver to the
customer. This file would be sent back to the customer via their browser.
This way, you give the user the ability to do the customization they need,
you don't give them source files, and you ensure that your corporate
standards are met in all documentation that bears your company name. This
method will also be easier for the customer use, and less error prone, than
having to edit the files themselves.
Senior Technical Communicator
OmniMark Technologies Corporation
1400 Blair Place
Canada, K1J 9B8
Email mbaker -at- omnimark -dot- com