how to prevent "Print setting for color ... is inconsistent" error?

[Seth Gordon]

When I print a FrameMaker book, I get the warning message:

Inconsistent Settings in Book
Print setting for color Black is
inconsistent in filename.fm.
The book may not print correctly.

I tried importing color definitions from one file in the book to the
rest of the files in that book, but I still get the warning.

When I check "Ignore other consistency messages" and click "Continue",
the document prints normally.

--
"The big dig might come in handy ... for a few project managers
whom I think would make great landfill." --Elaine Ashton
== seth gordon == sgo...@kenan.com == standard disclaimer ==
== documentation group, kenan systems corp., cambridge, ma ==

[Joan Goldstein]

Check your settings for Color Definitions ...View -> Color -> definitions.
Check to see if the Print As and Model settings are the same in all of
your files.

cheers,

Joan Goldstein

[Tim Murray]

Usually what you did fixes it, but here is what else you can do.

Print the book to a PostScript file. Choose Separations, and, to save disk space and time, print only even or odd. Acknowledge any errors and let it rip. The next time you print the error *should* be gone.

The error can also crop up (but not always) if one file has colors that others do not.

[Seth Gordon]

Tim Murray wrote:

I tried this, but when I try to print it a second time, I still get the warning messages. I also get the warning when I check "spot color as black/white" or when I exclude the book chapter that has color (in
our corporate logo) that no other chapter has.

[Seth Gordon]

Joan Goldstein wrote:

> Check your settings for Color Definitions ...View -> Color -> definitions.
> Check to see if the Print As and Model settings are the same in all of
> your files.
>

Checked. They're the same.

(The problem, by the way, appears in both FM 5.5.6 and FM 6.0.)

[Tim Murray]

Gee Seth, I don't know. I see this all the time, and at least one of the solutions always works.

One more thing to do. Safe the book file as a MIF. Open the MIF as text, and remove the entire color library. It starts at

<ColorCatalog

and ends at

> # end of ColorCatalog

Save the MIF as text and open it as a regular file, and resave as a book. Regenerate to build a new list of colors, then see what happens.

[Dona Martin]

To fix the problem once and for all. Open your book file. Open one of the
files in your book and import the Color Definitions from it into your book
thus globally setting the Color Definitions for all files in your book to
the same settings.
With the .book file selected, choose Import/Formats from the File menu and
then select only Color Definitions.

Hope this helps.

"Seth Gordon" <sgo...@kenan.com> wrote in message
news:39FF1AAD...@kenan.com...

[Dave Hayes]

Seth

If none of the above fixes work, it's possible that you have two Blacks in
the colour definitions, and they have different RGB settings (accurate to
six decimal places), or are getting used differently.
(I once had two Reds. I don't know how the second one got in there but it
was causing problems.)

If this is the case, delete the duplicate Black colour from the definitions.
The Frame interface won't let you delete any of the primary colours, so to
get rid of the duplicate you'll have to delete it from a MIF version of your
document.

Dave Hayes

Seth Gordon <sgo...@kenan.com> wrote in message
news:39FF1AAD...@kenan.com...

[Tim Murray]

> I once had two Reds. I don't know how the second one got in there but it was causing problems.

Used to be that importing Word 95 docs into Frame 5-point-something gave me an extra red 100% of the time.

[Seth Gordon]

Tim Murray wrote:

Regenerating the book yields a string of "Print setting for color Black is inconsistent" messages in the Book Error Log (this is Frame 6.0,
although the original problem showed up on both 6.0 and 5.5.6), and trying to print the book again leads to the same errors as before.

[Tim Murray]

Can you ZIP or otherwise compress the book and send it to me? I'd like to see this.

[Seth Gordon]

I took this problem to Adobe's tech-support hotline, which told me they were referring the problem to their "research group". After one week and
two follow-up phone calls, said research group emailed me a PDF document containing:

(a) the article from their knowledge base on this problem, which I'd already read, and which had proved unhelpful

(b) infodumps of discussions from two Web sites for FrameMaker users

One of the suggestions in (b) was to redefine Cyan, Magenta, Yellow, and Black as Process colors, rather than as Spot colors. I have no idea why
this should work, but this seems to have fixed the problem on all my books that exhibit it.

(Note that in the MIF file, the ColorCatalog doesn't say anything about which colors are Spot and which are Process -- that's in the
document-properties section.)

[Tim Murray]

Thanks for posting that solution.