RE: Frame's "Print setting for color" Error Message

[Jim Stauffer <JStauffer@xxxxxxxxxxxxxxxxxxxxx>]

Yes, you can make all the inconsistencies go away... for a while. But if
you're importing content from other files, or using conditional text to any
extent, they creep back in.

By all means, spend all the time you want on this. But the warnings really
are irrelevant and my experience has been that it's faster to just click
through them.

Jim


-----Original Message-----
From: Ed Treijs [mailto:etreijs@algorithmics.com]
Sent: Thursday, March 07, 2002 10:00 AM
To: framers@omsys.com
Subject: RE: Frame's "Print setting for color" Error Message


[Quote:]
> Personally, I gave up trying to chase down this ghost and his 
> friend 'inconsistent conditional text settings.' It makes no 
> difference to the printing or postscripting process. You will
> spend much more time trying to resolve these irrelevant
> inconsistencies than it takes to just click the 'continue
> anyway' button.

On the other hand, importing formats including colour and conditional text
can make the inconsistencies go away.  Or a look at each chapter.
Sometimes, the problem is because the front page or TOC or first chapter
have different formats, because FrameMaker assumes that the first occurence
of a format is the correct one.  If you get consistent "Inconsistent
Setting" messages for many chapters, then look at the first chapter where
that setting is set.  Fix it there, and most or maybe all of the
"Inconsistent Setting" messages go away like magic!

It can also be a fail-safe when using conditional text.  Put your
conditional text in your front page or TOC, and make sure that all the
conditional text settings are the suitable default.  Usually this means
that: Conditional Text is hidden; and Condition Indicators are shown.  (This
presumes that you have conditional text like "Comment" and "Future" which is
there for the writer's reference, but shouldn't be in the final copy going
out to readers.)  As soon as you see an "Inconsistent Setting" to do with
conditional text, you know that something's up.  Because it's unlikely that
anyone will fiddle with conditional text in the first page or TOC, it will
tend to remain in the default, and it is the standard against which all
subsequent conditional text settings are checked.

I put this system in place in our template after an unfortunate experience I
had.  I don't use conditional text, and it was getting very close to release
date, so when I got a last-minute chapter from someone else to put in my
book, I did not look closely at it.  Uh-oh, I didn't see the blue-coloured
text promising support on NT for a key application (which was for the future
back then, and still is for the future now).  Red faces and revision of the
release package ensued.

Because inconsistent settings can be easily fixed, and STAY fixed if you
have a good template, I don't think there is any real excuse for not fixing
them.  They are information/warning messages, and if you ignore them you may
miss out on a warning you should have heeded.

Ed (never pays to ignore stuff when you can fix it easily) Treijs


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **

** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **