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.
Subject:Template overriding usability (Was: not a slam) From:Stuart Burnfield <slb -at- FS -dot- COM -dot- AU> Date:Wed, 10 Jun 1998 17:17:03 +0800
Barbara Karst-Sabin <Phillinion -at- AOL -dot- COM> (whose name, appropriately
enough for her profession, is an anagram of 'brain tasks') said:
> For example, in a programming doc, such as an API, it is important
> that an "if-then" in code isn't broken up. However, minor tweaking
> done to paragraph tags done to avoid just that kind of thing is
> blithely overriden before the document is sent to the printer. When
> I pointed out the problem (in an already published doc), I was told
> by the manager (a recently promoted production person) that the
> templates must be exactly the same for all docs, the "bad breaks"
> don't matter.
This won't solve the general problem, but in the case of tokens that
must stay together, you could use non-breaking spaces to join them.
For longer code samples, maybe do them as screen captures. That way
the production people *can't* mess with them.
Regards
---
Stuart Burnfield "Fun, fun, fun
Functional Software Pty Ltd In the sun, sun, sun. . ." mailto:slb -at- fs -dot- com -dot- au
