Re: Framemaker help

[Peter Gold <pgold -at- NETCOM -dot- COM>]

I'm posting this to the list as requested by Julie Mills; it's a
follow-up to an original post by Hilary Jones that Julie received from a
co-worker.

----- forwarded -----

On Mon, 3 Nov 1997 millsja -at- OHMEDA -dot- BOC -dot- COM wrote:

> Please pass this on to Hillary Jones,
>
> I setup a program at my company to compile help and quick reference guides
> out of Framemaker. The same principle saves big bucks on translations.
>
> The important thing to remember is that FRAMEMAKER is only a tool.
>
> A human must come up with a document outline
> includes the necessary text in reasonable chunks.
>
> Writers must use a common glossary or every chunk will use different words
> for the same thing - driving the end user nuts.
>
> If you plan to reuse text between products, use good programming practices
> (e.g. global variables). We use <MAX_FLOW> not 15 l/min in archived text.
>
> You need a library of chunks writers can brouse through. PDF is a good
format
> to use.
>
> Chunks need to be large enough to satand on their own through the review
> phase or you can chop documents into chunks after review.
>
> Add these items of info to the chunk database (approval date/change log).
>
> Associate translated chunks with their English base (a BIG COST saver).
>
> Regards, julie mills (home e-mail is windmark -at- execpc -dot- com)
>

Posts: mailto:techwr-l -at- listserv -dot- okstate -dot- edu
Commands: mailto:listserv -at- listserv -dot- okstate -dot- edu (e.g. SIGNOFF TECHWR-L)
Archives: http://listserv.okstate.edu/archives/techwr-l.html,
	http://www.documentation.com/, or http://www.dejanews.com/
Subjects: JOB:, QUESTION:, SUMMARY:, ANNOUNCE:, or none of these.