12 Replies Latest reply: Jul 31, 2014 7:22 AM by janet.day RSS

    inconsistent color definitions

      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
        • 1. Re: inconsistent color definitions
          Community Member
          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
          • 2. Re: inconsistent color definitions
            FieryPantone Community Member
            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.
            • 3. Re: inconsistent color definitions
              kmacdowe+brdcom

              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.

              • 4. Re: inconsistent color definitions
                Bob Niland (Error 7103) Community Member

                > 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>.

                • 5. Re: inconsistent color definitions
                  kmacdowe+brdcom Community Member

                  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. 

                  • 6. Re: inconsistent color definitions
                    FieryPantone Community Member

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

                    • 7. Re: inconsistent color definitions
                      Bob Niland (Error 7103) Community Member

                      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.

                      • 8. Re: inconsistent color definitions
                        kmacdowe+brdcom Community Member

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

                        • 9. Re: inconsistent color definitions
                          FieryPantone Community Member

                          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

                          • 10. Re: inconsistent color definitions
                            janet.day

                            Look at the color definition in either the first document in your book, or in the document listed right before the one shown in the error report. In my case, the error report was telling me that the color definition in my introduction chapter (document #2) was a problem. However, I was confused because the color definition was accurate in that one, as it was in all of the subsequent documents. However, when I looked at my title/legal page file (the first document in my book), the RGB color definition numbers had been transposed. Frame assumed the first document was the accurate one and color definitions in subsequent documents should match the first document. Does that make sense? The report is telling you that the document listed is where the color definition defined earlier has changed and not that there is a problem in that particular document. So, trying to delete the color definition in my second document (the one listed on the error report), and then importing color definitions from other files didn't help because the document listed never had the problem in the first place; the problem was in the earlier document. Hope that helps.

                             

                            JD

                            • 11. Re: inconsistent color definitions
                              FieryPantone Community Member

                              Frame assumed the first document was the accurate one and color definitions in subsequent documents should match the first document

                              It's always seems to me that's how it works, much the same thing as when Frame signals problems with conditions: it's not saying there's a problem with document 2, just that there's a discrepancy between the first place it found something defined and a different definition it's found later – it can be that document 1 is in fact set up just the way you want it.

                              Time-consuming, but if you start from View > Colour definitions and try deleting colours you're sure you don't want, you'll get a warning "Some items in {file} are assigned the colour {colour}". Save to .mif, find out where the offending colour is assigned, make necessary changes, repeat till done … If/when you get a new warning about "Colour separation out of range", post again here so I can learn from wiser answers.

                              • 12. Re: inconsistent color definitions
                                janet.day Community Member

                                Thanks for your response Niels. That was my point. Everyone is telling the readers to save their file as .mifs and to delete colors, etc. when all they have to do is look to earlier documents and not the document generating the error. The error report led me to believe that the actual document listed had the issue, so I spent two days trying to figure out where I went wrong with THAT document. Saving to the .mif didn't work, and neither did deleting the color and adding it back in, or any of the other suggestions posted on other forums because the document listed wasn't where the problem was at all. When I went through the first document, I was able to spot and correct the problem in a matter of moments. Therefore, my post was basically geared to those users who are trying everyone's suggestions and missing the entire point of the report.

                                 

                                JD