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.
In Flare, if you always want a break before a header, that's easy.
The pain came when the rules-based page breaks ended up with a lot of
white space or other unprofessional-looking output. There was no way
to know where the problems were without generating the PDF and
proofing it. I'd fix one problem and that would cause a problem on
another page, which I wouldn't see until I generated a new PDF.
Training other users to understand the page-break rules and how to
work around their limitations would not have been easy. FrameMaker,
you see the issues in the editor and fix them on the fly.
I can see how modular source would be useful if you reused a lot of
content, but that has almost never been the case in my work. That
seems a lot more common in the hardware world where you'll have many
similar products with various permutations of a shared set of
features.
Flare's no more powerful at single-sourcing than WebWorks or MIF2Go,
they can each do things the others can't.
I didn't need a support contract for Flare. I got what information I
needed from MadCap's Flare forum.
Like I said, support was usually a dead end. I had a frustratingly
difficult time getting them to understand why it was a problem that
they didn't support named destinations.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
