Re: Identifying chapters

[Patrick Wright <pdoubleya -at- gmail -dot- com>]

Bill

> If you have to explain the structure of your cross-references to your
> readers, they're probably more complex than they need to be.

Sure, but I think the original reasoning is sound. The document is for
software product release notes; this product is updated frequently,
and often has complex configuration changes between releases. The
first part of the document describes what features are available, and
is intended for all readers. For new features which are related to
configuration changes, there is a reference to the section on changes
to configuration. The normal users thus know they can't use this new
feature without some administrative help, the administrators
understand what features are being configured, etc. It sounds more
complex than it is in practice.

The oddity here is that the release notes can actually be quite short,
so don't justify chapter or chapter-section headings. This means the
cross-referencing is non-standard, in my view, but something has to be
done.


Regards
Patrick

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

New from Quadralay Corporation: WebWorks ePublisher Pro!
Completely XML-based online publishing. Easily create 14 online formats, including 6 Help systems, in a streamlined project-based workflow. Word version ships in June, FrameMaker version ships in July. Sign up for a live, online demo! http://www.webworks.com/techwr-l

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.