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.
> -----Original Message-----
> From:
> techwr-l-bounces+bgranat=granatedit -dot- com -at- lists -dot- techwr-l -dot- com
> [mailto:techwr-l-bounces+bgranat=granatedit -dot- com -at- lists -dot- techwr-l
> .com] On Behalf Of Jeff Jansen
> Sent: Wednesday, July 09, 2008 9:18 PM
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Single subheading allowed?
>
>
> Since the heading will have its own copy text that does not
> apply specifically to an individual ECM, I don't think
> merging the subheading copy with the heading copy (that is,
> omitting the subheading altogether) is appropriate. So is it
> acceptable, for the sake of cross-document consistency, that
> some documents be allowed to violate the structure
> convention? Or is there some widely accepted method for
> dealing with this?
> Has anyone dealt with this or a similar situation in another way?
>
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-
