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: Previous, Next and Print buttons in Help From:"McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com> To:Paul Hanson <phanson -at- Quintrex -dot- com>, TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 18 Jan 2010 14:20:18 -0500
Paul Hanson asked:
> Are you talking about using a CSS file for "media=print" to
> create the "formatted-for-nice-printing" version? Have any
> CSS to share?
Nope.
I carefully leave that sorta stuff out of my WebHelp.
Having anything of the sort just reminds/encourages requests
for "a single printable version" of your Help.
The one-and-only time I tried to oblige such requests,
I got sucked into a morass of escalating requests to
"fix it so it is formatted properly and organized properly"...
Um, it's help. Each topic page is either a standalone entity
or a member of a topical cluster of pages. A page might be a
paragraph or it might be 31 paragraphs and a bunch of
embedded diagrams. Any given page might have multiple
instances of drop-down or expanding text (or text-and-graphics).
Any given sequence of instructions might:
a) proceed directly from step to step to the end
b) branch to alternate paths (of one or more steps) for
variant product versions or customer implementations
c) keep to a single path but skip over some steps that
describe optional config or features...
d) other.
Now, tell me how to make that generate a single PDF or
Word document that flows properly and understandably...
oh, and doesn't have a bunch of redundancy.
With that said, I'm ready to make happen whatever they
want to have happen if they are willing to throw money
at us for the privilege. On that point, I'm in violent
agreement with the Product Manager who said exactly
that when I said I'd need considerably more time on the
project schedule if we really wanted to please certain
parties.
- Kevin
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-