Skip navigation
Currently Being Moderated

inconsistent color definitions

Jul 18, 2008 9:41 PM

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
 
Replies
  • Currently Being Moderated
    Jul 19, 2008 2:33 AM   in reply to (aliceqiuwuyan)
    The message means that a color named "Color8" is defined in
    more than one of the files in the book, and that the definition
    differs between the files. This could be highly undesirable if
    the color is being used and you are doing color productions.
    The remedy is to make all color definitions the same in all
    files by importing color definitions to the entire book.
    BTW, the message is a warning and should not prevent you from
    printing the book.

    If you're familiar with the files in the book, and you feel
    confident that "Color8" is not used for anything important,
    and you're not doing high-quality color productions, then:

    1. In the book window, select all the files in the book.
    2. In the book windows, select File > Import > Formats
    3. Deselect everything except "color definitions"
    4. At the top, select the file you copied from Windows in
    "import from document"
    5. Click "import"
    6. Save all files and try printing again.

    If you're not familiar with the files and you're not sure if
    "Color8" could be used for anything important, you should
    either consult with someone who designed the files, or at
    least select one of the other files in the book to import
    colors from. In this case, find a file in the book that contains
    the color "Color8" (use View > Color > Definition). Once you've
    found such a file, follow the instructions above and use this
    file to import colors from.

    Even better is if you have access to a template file for the
    book that contains all definitions of formats. Then open that
    file in FM and use it to import from.

    --
    /Thomas Michanek
     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2008 10:33 PM   in reply to (aliceqiuwuyan)
    Watch the log to see which file is flagged as having an inconsistent colour, then open that file. Go to View > Colour > Definitions and try deleting the "inconsistent" colour: if it's used by anything, you'll get a warning.

    If you save a problem file as .mif and examine it (carefully, because .mif files can be a bit sensitive) in a text editor, you can search for the string "Color8" and find out exactly where the colour is being used.
     
    |
    Mark as:
  • Currently Being Moderated
    Feb 1, 2013 10:50 AM   in reply to (aliceqiuwuyan)

    I have seen this error consistantly pop up in Framemaker over many years and many versions. I have never gotten a suitable explanation of why it happens. That said, Niels is correct, remove it. Ha! today is Feb. 1, 2013 and I just got the warning again today. If anyone actaully finds the origin of this erros please share with us. I suspect it may be coming in from imported files but can not confirm this.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 1, 2013 12:49 PM   in reply to Niels Grundtvig Nielsen

    > If you save a problem file as .mif and examine it (carefully, because .mif files can be a bit sensitive) in a text editor, you can search for the string "Color8" and find out exactly where the colour is being used.

     

    That only works in the easy cases. If the named color is coming in with an external object (EPS, DWG, DXF, PDF) the name may or may not appear in the <ColorCatalog> tags, but you won't be able to find it in the main <TextFlow>.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 1, 2013 3:28 PM   in reply to Error7103

    Error7103, you are correct, I don't recall ever seeing it in the mif code.

     

    This raises the question then, is it coming from external objects? And if so, why is it always "Color8"? Maybe "Color8" is some kind of catch all?

    Today I also was reminded when I look in the Color Definitions, often there is a "Color 8"; with a space that is, in the definition also, that causes no problems. 

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 3, 2013 11:39 PM   in reply to Error7103

    So, .eps could occasionally be the culprit! well worth knowing.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 4, 2013 7:16 AM   in reply to Niels Grundtvig Nielsen

    DWGs are a particular nuisance in this regard.

     

    If I import the ACAD 13 stuff common around here (which rarely has more than a few colors used), the Color Definitions dialog instantly gets polluted with a large number of new colors in the name range "RGB 000,000,000" through "RGB 255,255,255".

     

    These names do not appear in the MIF.

    They do not go away if the culprit object is deleted.

    Delete. Save as .fm binary. Re-open. Still there.

     

    MIF wash: RGB infestation now gone.

     

    Key learning: never import DWGs (or EPSs that are mere re-saves of a DWG - same problem). DXFs probably have the same problem. PDF re-saves don't seem to have the problem.

     

    We routinely post-process DWGs in Illustrator when we need them (remove title blocks, etc.), then saving them as EPS, and this is also deleting that huge list of RGB colors.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 4, 2013 11:13 AM   in reply to Error7103

    Thanks Error7103! Perhaps you should change your name to Fix7103 :-)

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 4, 2013 11:56 PM   in reply to Error7103

    No risk of .dwg with this client, but (once again) it's good to be aware of this whole area. I'll pay special attention next time I import an .svg derived from Visio … just in case.

    .rtf files can bring a lot of baggage with them, of course, but I try to avoid that by tagging the Word source as mml and using .txt instead

    N

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)