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.
> a) whether a sufficient level of version control exists to be able to work
> in multiple versions of that source, regardless of the release in work.
It exists, but it is designed for versions that can be frozen (that
is, version 1 has been published, and now I need to change this
object, so it becomes version 2. However, once I activate version 2, I
can no longer make changes to version 1.)
There are ways around this, but they increase the amount of complexity.
> b) what about, e.g., branding or product-based differences in inline-text?
> For instance, the permissions you mention below could easily be used to
> address differences in higher-order elements like paragraphs, but it would
> be far more complicated to do so within the context of a single sentence.
> Text entities/variables would be more useful in such instances. Are they
> available for use?
Yes. AIT has three types of variables (text, list, and file object),
so it sounds like you would want to use list.
> c) conditional text? Is its use available? How difficult is it to use and
> keep straight among a number of authors?
It is available, but it works differently from file-based tools. In
AIT, you can control conditions by style (by specifying which output
types the content can be published to). Then there are variables (the
list variables above come in handy) and embedded topics, where you
create new topics by pulling together other topic objects into a new
parent "shell".
> I'd ask these questions because one of the great aspects of using SGML or
> XML to publish documentation is the control one has over the final,
> published version of a document. Mind you, I'm not necessarily a proponent
> of one tool's use over another. Many of the XML-based authoring tools share
> similar functionalities, even if the ways they go about it might be
> different.
I agree. I jumped into this thread because I could answer the AIT questions :-)
Char James-Tanny ~ JTF Associates, Inc. ~ http://www.helpstuff.com
----------------------------------------------------------
Please send follow-up questions to the list. (Inquiries sent off-list
may not be seen.)
Contact me directly (CharJT at helpstuff dot com) with business inquiries.
----------------------------------------------------------
2006-2007 Microsoft Help MVP
Find a Help Authoring Tool at HAT-Matrix.com ~ http://hat-matrix.com
Co-author of "Managing Virtual Teams" ~ http://www.wordware.com/wiki
AuthorIT Certified Consultant, Development, and Training
STC Secretary, 2006-2008
Web site Hosting and Design ~ http://www.jtfhosting.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-
