• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

inconsistent color definitions

New Here ,
Jul 18, 2008 Jul 18, 2008

Copy link to clipboard

Copied

Hi, all,

I have a problem concerning inconsistent color definitions when I print a book file on the Linux system.

The error message says:
Color definition: Color8 is inconsistent

This may relate to the fact that this .fm file is copied from Windows version FrameMaker file.

How can I solve the problem?

Thank you in advance for any help.
Alice
TOPICS
Formatting and numbering

Views

10.5K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Oct 30, 2018 Oct 30, 2018

Copy link to clipboard

Copied

LATEST

Hi Heather,

Yes, I did read all of your posts and the entire thread. You stated that you used the same template for all files without any specifics about how. You didn't specifically state if you re-imported the colours from the template to the entire book nor if you tried creating a new book file. You also state that you added screen captures imported by reference. FYI, FM looks at the colours used in these every time the graphic file is opened (i.e. when FM imports these by reference), so even fixing inconsistent colours once, could add or mess them up the next time the FM file using those graphics is opened, e.g. during a book update.

Also, it doesn't matter whether a colour is actually used in a document. FM looks at the definitions for all of the colours defined in the FM document's internal colour catalog and compares them to those in the Book file's catalog.

However, as has been mentioned in several messages, inconsistent colours is not an error that will prevent FM from creating output. So, if you're having issues with creating a pdf, then the book log error message about the inconsistent colours is just a red herring.

Just trying to help and provide some background info on the mysteries of FM's internal workings.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Oct 30, 2018 Oct 30, 2018

Copy link to clipboard

Copied

Hi Arnis,

I wrote all of this already. Please read what I have written.

Cheers!

Heather Ceana Craig

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Oct 27, 2018 Oct 27, 2018

Copy link to clipboard

Copied

https://forums.adobe.com/people/heather+ceana  schrieb

The newest thing is that all of the chapters, except the front cover, now have inconsistencies in the pre-set colors: Dark Grey, Pale Green, Forest Green, Royal Blue, Mauve, Light Salmon, Olive, and Salmon.

Heather,

I have recently noticed something regarding the pre-defined color sets, which I believe to be a bug in FrameMaker:

If you have a template document with, e.g., all colors defined as "Process Colors" (instead of spot colors which most are), this information will only be maintained if you open this template document and then "Save as..." with a different name. If, however, you use this template with the "File > New > Document..." (CTRL + N) command to create a new file based on this template, all the pre-defined colors are reverted back to spot colors. No longer process colors. And if you combine these newly created documents into a book, just the first one will have the correct colors, while all the following ones (created from the first one used as a template) will have the wrong definitions.

So it's nothing you actively did, or did wrong, just creating new files using the standard routine in FrameMaker causes this problem.

Bernd

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines