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 my opinion, Flare offers the same degree of single sourcing for most
> being able to store a fully formatted topic in Author-it
You can reuse fully formatted topics as well as fully formatted
"chunks", called snippets of text as part of topics. Reuse is done by
defining separate TOCs and associating targets with the TOCs. TOCs in
Flare are similar to Books in Ait.
> shared directory and access control: Flare supports the use of source
control by Microsoft Team Foundation Server.
In my humble opinion, one of the main differences between Flare and Ait
is the use of a database in Ait. This surely has advantages when working
with large projects and very complicated reuse of contents. I guess it
was more advantageous in the past, where computer CPU was low. Today, a
file-based structure without database is very good to be used for
not-too-big projects as well. In theory, you could set up all projects
inside one project in Flare and set up a quite complicated reuse scheme,
too, but I guess most people do not even need this. I rather like to
keep different projects (with no or very limited reuse) apart from each
other. I see one advantage in Flare concerning single source in the use
of conditional text and topics. Often, it is easier to mark topics or
text pieces as different for separate projects rather than setting up
separate TOCs. For example, if 90 % of the contents is identical over
several projects, it is easier setting up a single TOC with conditions.
Best regards, Christine
(By the way, I read the digest, so my postings may appear sometimes a
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-