RE: MIL STD 38784 - Tech. Man. Style and Format Reqs.

Subject: RE: MIL STD 38784 - Tech. Man. Style and Format Reqs.
From: "Sue Ahrenhold" <SAhrenhold -at- IpdSolution -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 9 Oct 2002 14:36:20 -0400


This Mil Spec is supported by an entire branch of the tech writing community, based on SGML implementation of the associated DTDs and FOSIs.

For additional information, see
http://navycals.dt.navy.mil/dtdfosi/38784.html
(I googled to find this page).

The extremely sophisticated DTD is supported in Arbortext's word processing software, and (I think) in FrameMaker and InterLeaf.

I don't think it's possible in Word. The specification was written to get around the whole issue of proprietary formats and conversions, since SGML is just marked-up ASCII.

I think your employer should have clued you in on some of this.

-----Original Message-----
From: Justin Ressler [mailto:JRessler -at- ewa-denver -dot- com]
Sent: Wednesday, October 09, 2002 1:46 PM
To: TECHWR-L
Subject: MIL STD 38784 - Tech. Man. Style and Format Reqs.

I am working from MIL STD 38784 - Tech. Man. General Style and Format
Requirements, and have found that a couple of things it specifies are
archaic, or are not easily accomplished within Word (I don't know about
Framemaker). I have run into this with some other requirements, including
the preparation of Maintenance Requirement Cards, which would make creating
the documents easier using a typewriter and candlelight in a cave rather
than Word.

Has anyone worked from extremely revised copy of MIL STD-38784. Both
contracts that I have worked on with this MIL STD have edited certain
portions so they are more applicable, but nothing great. Also, the person
approving the documents bends to my suggestions sometimes, but not others.

The aforementioned MIL STD was last revised in July of 1995. I believe that
is before the world's most popular word processing program was widely
implemented. I understand that some concepts and ideas don't change, but
capability does. Am I wrong in thinking "Hey, time for an update here;
review your requirements...they don't make much sense anymore. Not only are
you getting less from your documentation than you could, you are shooting
yourself in the foot for future updates."

That is my mini-rant for today.

Justin
Who doesn't usually require much more than a mini-rant.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Buy ComponentOne Doc-To-Help 6.0, the most powerful SINGLE SOURCE HELP
AUTHORING TOOL for MS Word. SAVE $100 on the full version and $50 on the
upgrade. Offer ends 10/31/2002 (code: DTH102250).
http://www.componentone.com/d2hlist1002

All-new RoboHelp X3 is now shipping! Get single sourcing, print-quality
documentation, conditional text and much more, in the most monumental
release ever. Save $100! Order online at http://www.ehelp.com/techwr-l

---
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.



Previous by Author: RE: ambiguous sentences
Next by Author: RE: Symbols in product names
Previous by Thread: Re: MIL STD 38784 - Tech. Man. Style and Format Reqs.
Next by Thread: RE: MIL STD 38784 - Tech. Man. Style and Format Reqs.


What this post helpful? Share it with friends and colleagues:


Sponsored Ads