RE: Style and Procedure Schema?

[kcronin -at- daleen -dot- com]

Tim clarifies:
> 
> What I'm suggesting would be a set of rules that define WHAT goes into
> MicroSoft's--or anyone else's--Manual of Style. And WHERE it goes, and
> HOW it's presented. So that, for example, in any standard-compliant
> document, the use of commas, or boldface, or conventions for naming doc
> files, or whatever, would be found in, for example, chapter 3, paragraph
> 2, and start with a reference to the manual they recognize as
> authoritative, followed by the exceptions they take to these rules,
> followed by any more restrictive rules imposed on top of the referenced
> manual, etc. Structure the information.


What advantage does this offer? The TOC and index should tell readers
where to find the infomation they seek.

Why is it important to know that, for example, punctuation will ALWAYS be
in Chapter 3?

As Tom Hanks said in "Big": I don't get it.

I mean, I'm glad my dictionary observes alphabetical order when listing
words, but beyond that, I don't care what chapter it assigns to
abbreviations, foreign phrases, etc. That's what the TOC and index are
for.


- Keith Cronin
___________________________________

It was the best of sigs, it was the worst of sigs...




^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Check it out! Get some cool freebies when you buy RoboHelp! You'll receive
SnagIt screen capture software and a 10% discount voucher for RoboHelp
Consulting. This special offers expires March 29, 2002.
www.ehelp.com/techwr

Have you looked at the new content on TECHWR-L lately?
See http://www.raycomm.com/techwhirl/ and check it out.

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