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:APPENDIX/APPENDIXES From:John Bell <johnb -at- C-STONE -dot- COM> Date:Fri, 30 Aug 1996 14:11:15 -0400
Julie Hansen <julie -at- CTL -dot- COM -dot- CY> writes:
> We are producing a large manual in which the chapters are NOT numbered: 1.,
> 1.1, 1.2, 2., ... We also have a number of topics we want to include in the
> appendix area. SO do we have:
Given the choice of "appendices" vs "appendixes" I go for "appendixes". My reason
is that the plural of a book "index" is "indexes". This spelling differentiates book indexes
from the mathematical and programming use of "indices". Although it is rare for a book to
have more than one index, it is certainly more likely with technical books than it is with
Back in my early days of tech writing I was once slammed for using multiple topics
and sections within an appendix. The explanation was that appendixes are for
supplementary information. Anything that is complex enough to have sections and topics
should be made a chapter. I didn't know if I was hearing gospel or personal opinion so I
asked four or five experienced tech writers that I knew. They all agreed with my critic.
Since then I've always put complex subjects as chapters.
--- John Bell
johnb -at- c-stone -dot- com
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-