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.
Re: Now numbering issue, was Re: This page blank...
Subject:Re: Now numbering issue, was Re: This page blank... From:Roger Mallett <roger -at- CSICAL -dot- COM> Date:Thu, 30 Apr 1998 14:08:09 -0700
A numbering system that supports the pulling/modification of procedures
is demonstrated by 16-1.2a. That is, where a dash is used to separate
the page number from the chapter number, and then a dot is used for
change pages that are slipped in, and then a lower case letter for
further revisions to the revision. Eventually, all of the revisions
are recompiled and the document renumbered at the next major change.
>----------
>From: DURL[SMTP:durl -at- BUFFNET -dot- NET]
>Sent: Thursday, April 30, 1998 10:05 AM
>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>Subject: Now numbering issue, was Re: This page blank...
>
>
> Anybody just chime in. I'm always looking for ways to handle
>revisions and updates. There doesn't seem to be any good paper way.
> In the manufacturing sector, anyway, people are used to seeing
>the
>dot numbering system. In Jill's example, that would be Chapter 16,
>Chapter
>17 now and Chapter 16, Chapter 16.1, and Chapter 17 in the future. I
>like
>Jill's approach, too, as long as one is sure that the new chapter will
>happen.
> For the nonce, I'm going with small chapters with the idea that
>you pull and replace an entire chapter rather than individual
>procedures.
>I page-number with the chapter number as a prefix to minimize the
>repagination.
> The real problem is that, without somebody responsible for
>revising the documentation, the updates, revisions, new chapters,
>etcetera
>won't be included anyway...
> Have any of you ISO types solved the problem? TIA,
> Mary
>
> Mary Durlak Erie Documentation Inc.
>East Aurora, New York (near Buffalo)
>durl -at- buffnet -dot- net
>
>On Thu, 30 Apr 1998, Jill Burgchardt wrote:
>
> snip..>
>> Insert a page with a chapter number for future sections. The page,
>>front and
>> back, would include appropriate headers and footers for the chapter.
>>The body
>> text on either side of the page would say:
>>
>> This chapter reserved for future use.
>>
>> The alternatives are adding chapters out of logical order or using
>>some altered
>> numbering scheme (such as 16a.1 between 16 and 17). Reprinting following
>> chapters with new chapter numbers is not an option.
>>
>> Comments or suggestions?
>>
>
>
>~~~
>Find contractor info at
>http://www.raycomm.com/techwhirl/contractors.htm
>
>
