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

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

Similar Messages

How do I resolve inconsistent color definition message even if all my files have the same definition

All of the files in my book have the same exact color definiti
ons: New Color1. Yet I keep getting the inconsistent color definition messag
es every time I go to print or regenerate my toc. I still get results but It's annoying!

Does EACH document have the SAME definition of NewColor1? Having the same name does not imply that they are the same definition.
Try opening the first document in the book. Then select all the documents in the book file and import the color definitions from the opened file. This will make all the documents have the same definitions as in the first document.

Request: Hide generated color definitions

I'm updating FrameMaker templates to reflect changes to my company's color palette as part of a rebranding initiative. My documents are full of overlapping conditions which means that each document's color definitions window is cluttered with dozens of "fm_gen_nnn" color definitions. It's not possible to permanently eliminate these junk color definitions because if you save as MIF, strip them out, and then reopen the file, there they are again because of the conditional text.
Request: please *hide* all these "fm_gen_nnn" color definitions in the color definitions window. They are of no use to anyone, and they make it hard to use the window.

becky,
FM's new version of conditional text creates a unique colour for *each unique* overlap condition, so, yes this really is where your "fm_gen" colours are coming from.
Unfortunately, FM's default and generated colours are always placed first in most lists (except those with full sorts, like in the Color > View panels), which kind of limits how you can interact with the colours, i.e. you may not like it, but that's the way it is.
You're suggestion of hiding the generated colours is an excellent and you should post it in the FM Feature Requests forum (http://forums.adobe.com/community/framemaker/framemaker_feature_requests) and also make an official feature request submission at: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&product=63
Note: all FM lists allow the typing of the first character as jump to the first matching item in the list. So if you name your custom colours with a unique starting character, like zLogo_color, then typing "z" when a colour list displayed would jump to that colour (or the first one that starts with "z"). This might make dealing with long lists a bit more tolerable.

Spot color definitions choices

How can I make my spot color definitions choice persistent? I read a kb item that said how to swap out the new Pantone Plus color books for the old ones, to maintain color parity with older versions. One of the steps has me going to "Spot colors" on the swatches pallette and selecting "Use CMYK Values..." instead of "Use LAB Values...". I don't want to have to do this with every file. Is there a way to make this choice persistent?

When you create new documents Illustrator opens unsaved instances of regular Illustrator documents that are selected by using the New Document Profile Menu in the New Dialog window. The profiles that you see in this menu are like any other .AI files in a folder that will show when you choose Browse... from this menu.
Just create a new document with your spot color definition and anything else you want to have when you are creating a new document and save it in that location or use Browse... from the New Document Profile menu to select it and Illustrator will remember you choice until you make another choice. You can also replace or edit the files used for profiles that came with the installation.

Pantone PLUS color definitions

One of the frustrating things with working with spot colors in the past has been that the CMYK equivalents that Adobe products used, didn't match the equivalents that Pantone provided in their books. I've seen hints that with Pantone Plus, that may no longer be a problem. Does anyone know for sure whether the Pantone Plus color definitions will be consistent from CS products across the Pantone books?
Thanks!

Adobe default CMYK value for a spot color is the Solid to Process value. To see this:
1. Add Pantone 293 Solid Coated to Swatches. You will see the CMYK icon. Wave the cursor over this icon: C=100, M=57, Y=0, K=2.
2. Add Pantone 293 Solid to Process. Wave your cursor over the CMYK icon: C=100, M=57, Y=0, K=2.
Adobe maintains this behavior to match legacy files. If they changed behavior now, then future outputs would change, and consequently new printings could look different from previous printings. This problem was encountered by Quark users with the change to version 7, when the Quark default switched from Solid to Process to Color Bridge Coated.
To download Pantone Plus libraries:
http://www.pantone.com/pages/Pantone/Pantone.aspx?pg=20721&ca=1
In previous post PDF mentioned Lab values, and that is the better way to convert Pantone colors to CMYK. But to do this you need to open the Ink Manager through the Swatches panel (in InDesign). Enable "Use Standard Lab Values for Spots". (note: Illustrator has a similar option, although it does not have an Ink Manager like InDesign). Notice that the CMYK icon changes to a Lab icon in the Swatches panel.
The conversion from Lab to CMYK is affected by the rendering intent and the Document CMYK color space. To see these, go to Edit: Assign Profiles.
If you have a spot color in InDesign, it is much better to make it process using the Ink Manager, instead of changing the color mode of the Swatch. If you need to convert one ink but not another, click on the spot icon in the Ink Manager to convert just one.
Regarding Pantone Plus: the Lab values of the spot colors have changed from the older Pantone libraries, along with the book CMYK values.
Edit: To see all the active inks in InDesign or Illustrator, use Separation Preview.

Color Definitions List - No Scroll

I have a large color definitions list that matches my standard swatches in Illustrator.
I want to go in and thin out some old/obsolete swatches (color definitions).
I've recently upgraded to FrameMaker 11. I cannot scroll in the Color Definitions Name field. I use the drop down arrow to dig into the list, but the list itself won't scroll. Hovering on the scroll arrow does nothing. Clicking it just selects that color at the bottom of the list.
Ideas? Is there any other way to scroll through the list or see the list?
I'm in FrameMaker 11.0.1
View > Color > Definitions...

As Van says, it's a very poor implementation of th scroll list. I just created an Indexed PNG to get a large list of values for the colours to test this out.
You have to click&hold on the arrow at the lower left and then drag the pointer down *outside* of the list window to start to scroll. On a fast machine, it just jumps to the end. If you let go, the list disappears. When you're past the first screen of the list, there's also an up arrow at the top that behaves in a similar way.
The FM UI designer must have been having a very bad day...

FM v11 - Can't delete color definitions

I'm trying to delete a pile of unwanted color definitions, via View > Colors > Definitions. As I recall, one should be able to select a custom color definition, and simply click Delete to remove it from the colors list.
I select a color definition (RGB 201, 231, 247), click Delete,
FM asks me to confirm (Ok),
and the color (RGB 201, 231, 247) is still listed as if I never deleted it.
Anyone know what I'm doing wrong?

It's probably due to an imported graphic that you're using actually having that specific colour - FM keeps adding it back in because it is being used.
This format of colour naming most often comes in with Indexed colours (usually a PNG or GIF file). It's easier & less frustrating to re-create the graphic and save it as a 24-bit colour image.
Also, to quickly delete these wayward colour defintions, save the file in MIF format, and then use any text editor to delete these from the <ColorCatalog... section - be careful not to remove the first 16 colours - they're special reserved FM ones.

Script for removing color definitions

I'm trying to create a script that will remove color definitions other than the default plus our corporate colors. I'm thinking some kind of "while" loop to go through the doc's color list, matching it to an array of named colors.
I see that there is a Color object and methods such as Delete(), but it's not coming together for me.
Any help would be appreciated.

Finally able to get back to this project.
Thanks for this snippet which does work great for removing a single "known" color. What I actually need to do is remove all colors except a specified list.
I've made an attempt (I'm sill relatively new to JS programming), but it only deletes the first instance instead of iterating through all the color definitions:
doc = app.ActiveDoc   //getting the active doc
col = doc.FirstColorInDoc   //getting the first color in doc
keepColors = new Array ("Black","White","Red","Green","Blue","Cyan","Magenta","Yellow","Dark Grey","Pale Green","Forest Green","Royal Blue","Olive","Salmon","Mauve","Light Salmon","Custom Color");
while (col.ObjectValid() ) //checking if the color object is valid
    if (col.Name in (keepColors)) //color exists
       break
else {
col.Delete() //delete color
col = col.NextColorInDoc

Framemaker color definitions--New

Okay. I am bewildered. I haven't done much with Frame and color, so when my company asked me to set up a 4C template, I figured I would give it a try. Here's the problem.
I need an orange color defined as M80, Y100, as defined in InDesign. When I use these values in Frame's color definition dialog box, the color is not correct (way too bright) on the display, nor does it print to PDF correctly. When I examine the color with Acrobat's Print Production preview, I get M92, Y100.
Okay, I know Frame is really an RGB-based program, so I went into Photoshop to get the equivalent RGB definition, which is R241, G90, B34. Well, Frame doesn't allow RGB numbers greater than 100%, so there's no way to enter these values.
I am stumped. I get the same results with Frame 7.1, Frame 8, Acrobat 7, and Acrobat 9. I print to a .ps file and then use Distiller to create the PDF, leaving colors unchanged. The same color outputs correctly from Photoshop.
Years ago I did some color work in Frame and don't recall having these problems.
Any suggestions?

Sue,
You also need to make an adjustment in a maker.ini setting that
affects how FM renders colours on output.
Find the entry for GetLibraryColorRGBFromCMYK in the [Preferences]
section.
Set it to: GetLibraryColorRGBFromCMYK=None
For more detailed info about this see:
http://www.techknowledgecorp.com/help/color.html at Tim Murray's site.
This info was originally posted by Mike Hardy a couple of years ago on
this site, but it's scrolled off now. Here's the original posting
content:
+++++++++++++++++++++
This post gives all the information I know about using colors in
FrameMaker
under Windows. It does not cover the use of separations. It instead
describes display, and direct output to color devices such as printers
including creating PDFs.
Color models
=====================================
FrameMaker supports three different color models:
- CMYK (Cyan, Magenta, Yellow, Key)
- RGB (Red, Green, Blue)
- HLS (Hue, Light, Saturation).
FrameMaker uses an algorithm to convert between each of these color
models.
For example:
RGB to CMYK:
C = max(R, G, B) - R
M = max(R, G, B) - G
Y = max(R, G, B) - B
K = 100 - max(R, G, B)
CMYK to RGB:
R = min(100 - K - C, 0)
G = min(100 - K - M, 0)
B = min(100 - K - Y, 0)
Color output
=====================================
Like most Windows applications, FrameMaker uses the Windows graphics
device
interface (GDI) for its output. The GDI handles both display and
printer
output.
Unfortunately, the GDI only supports the RGB color model. Any colors
that
are defined in other color models are therefore converted to RGB for
output
(see below).
The only exception to this is Encapsulated PostScript (EPS). When you
print
to a PostScript printer, or distill a PDF, the EPS is inserted
unchanged
into the PostScript. So any CMYK colors in the EPS get printed
unchanged.
This is the only way to output a CMYK color from FrameMaker under
Windows.
(Note that if you instead print to a non-PostScript printer, any EPS
files
are output using their preview bitmap, in RGB.)
Types of color in FrameMaker
=====================================
There are two types of color in FrameMaker:
- those defined by component values that you type in
- those defined by choosing a named ink from a color library.
FrameMaker handles these differently.
If you type in the component values
FrameMaker stores the color in the document as CMYK. If the color was
not
defined as CMYK, FrameMaker uses its own conversion algorithm. So the
CMYK
values that are stored are the same values that you see in the CMYK
view of
the Color Definitions dialog.
FrameMaker outputs the color as RGB. If the color was not defined as
RGB,
FrameMaker uses its own conversion algorithm. So the RGB values that
are
output are the same values that you see in the RGB view of the Color
Definitions dialog.
If you choose the color from a library
FrameMaker also supports color libraries that contain named inks.
Almost all
libraries specify both CMYK and RGB values for each ink. The important
thing
is that the mapping between the CMYK and RGB values can be very
different to
the algorithm that FrameMaker uses.
FrameMaker stores the color in the document as the color library and
ink
name. It also stores CMYK values for the color, for backup. When
FrameMaker
opens the document, it looks for the color library and ink name, first
in a
cache, then on disk:
- if it finds the color library and ink, it reads the CMYK and RGB
values
for the ink from the color library
- if it doesn't find the color library or ink, it instead uses the
CMYK
values that are stored in the document, exactly as if you'd typed them
in
(see "If you type in the component values" above).
FrameMaker outputs the ink as RGB. It can use:
- the RGB values for the ink that are stored in the library
- the CMYK values for the ink that are stored in the library,
converted to
RGB using its own algorithm.
This depends on the output device that FrameMaker is using, and the
GetLibraryColorRGBFromCMYK setting in the maker.ini file:
- If GetLibraryColorRGBFromCMYK is set to "Screen", FrameMaker does
screen
output by converting the CMYK values for the ink to RGB. For printer
output,
it instead uses the RGB values for the ink.
- If GetLibraryColorRGBFromCMYK is set to "Printing", FrameMaker does
printer and PDF output by converting the CMYK values for the ink to
RGB. For
screen output, it instead uses the RGB values for the ink.
- If GetLibraryColorRGBFromCMYK is set to "Printing&Screen",
FrameMaker does
all output by converting the CMYK values for the ink to RGB. It never
uses
the RGB values for the ink.
- If GetLibraryColorRGBFromCMYK is set to "None", FrameMaker never
uses the
CMYK values for the ink. It does all output using the RGB values for
the ink.
For the most WYSIWYG results with the predefined libraries, I'd
suggest
setting GetLibraryColorRGBFromCMYK to "None". This means that the RGB
values
in the color library get used for the screen - and they're probably
the most
faithful colors for this. The same RGB color will be printed, giving
you the
same color mismatches that you get for most other Windows
applications. And
you will often find that the RGB to CMYK conversion of your output
device
will give more faithful results than FrameMaker's own conversion.
Defining your own libraries
=====================================
Finally, note that you can define your own libraries. From the online
"Customizing FrameMaker" manual:
"ColorLib [in maker.ini] specifies the folder that contains color
library
files. These files are read in at startup and appear in the Color
Libraries
pop-up menu in the Color Definitions dialog box. You can add any
library
file formatted in the ASCII Color Format (.acf), version 2.1 or
earlier, or
in the Binary Color Format (.bcf), version 2.0. You can't use a
FrameMaker
product to save a .bcf library file."
A web search might reveal details of these file formats, but if not,
the
ASCII one is pretty obvious. Here's a file I put together:
ACF 1.0
My Color Library
LibraryVersion: 1.0
Copyright: © 2005 Mike Hardy. All rights reserved.
AboutMessage: Colors for my company
Names: Partial
Rows: 4
Columns: 4
Entries: 2
Prefix:
Suffix:
Type: Process
Models: CMYK RGB
PreferredModel: RGB
Data:
0 0.25 0.5 0.25
65535 32768 0
Burnt Orange
0.5 0.25 0 0.25
0 32768 65535
French Blue
You can then control exactly what RGB values FrameMaker uses for
display and
printing:
- determine the RGB values that you want to use for display, and note
down
the RGB values
- determine the RGB values that you want to use for printing, perhaps
by
trial and error in another application
- set the FrameMaker Color Definitions dialog to your RGB values for
printing, then change to the CMYK color model, and note down the
"equivalent" CMYK values
- define your own color library
- in your color library, define an ink with the RGB values you noted
for
display, and the CMYK values you noted for printing
- set GetLibraryColorRGBFromCMYK to "Printing"
This doesn't get you CMYK output, but it's the best you can do under
Windows. Note, however, that setting GetLibraryColorRGBFromCMYK to
"Printing" might not give such good results with the predefined color
libraries (see above).

Deleting Color Definitions

Hi All,
This is FM 10.
I have a large number of color definitions defined in the template. Please see the attached image. They have names like: RGB 000.048.127 etc.
I want to delete these definitions. I am defining a new set of colors for the template and new definitions are appearing at the end of the list. I need to browse through the entire list.
The problem is mysterious, when I try to delete these definitions, FM do ask for a confirmation whether to delete, but upon clicking OK, FM do not actually delete the entry. It do not give any errors either. They are right there, even after deleting.
Please let me know how can I get rid of them.
Regards,
Com

In addition to Anis's suggestion, Rick Quatro has a color definitions clean
up Framescript (may be part of another package) that zeros all the color
definitions out.
Art Campbell
          [email protected]
"... In my opinion, there's nothing in this world beats a '52 Vincent and
a redheaded girl." -- Richard Thompson
                                                      No disclaimers apply.
                                                               DoD 358
I support www.TheGrotonLine.com, hyperlocal news for Groton MA.

Change multiple color definitions to same pantone?

I am using FM10, I need to change a few unque color definitions to the same pantone color, I was successful with the first one but got system messages about not being able to define more colors to that same pantone. I understand this is a program rule, but I am wondering if there is a way around it because I still need to define those other colors as the same pantone. I tried a work around that failed - defining the same properties of the pantone I wish to use with regard to cmyb values but the color was not the same as the coated pantone I was trying to emulate, is there a trick I am missing here? Thanks for any help you may provide.

Disclaimer: I don't work in managed or CMYK color. We leave (sRGB) color in, but print in B&W bitmap.
I suspect that the thing that provides end-to-end color control with the Library colors is that they encode a <ColorLibraryInkName ...> which is passed into the PostScript output and also into any PDF output. The print shop or Pantone-aware RIP can see this name(tag), and knows how to render it. The encoded CMYK is probably ignored in that case (and may not match the initial Library settings in any case).
The actual CMYK values in the PS and PDF are usually trashed by the Windows GDI, which despite the fake CMYK available in Vista SP1 and later, is still an RGB engine.
If you save a document as a MIF, you can see the encodings using a plaintext editor.
In the <ColorCatalog section of a test MIF, a typical Pantone looks like:
<Color
<ColorTag `PANTONE 3308 CVC'>
<ColorCyan 99.998474>
<ColorMagenta 0.000000>
<ColorYellow 59.999084>
<ColorBlack 71.998596>
<ColorLibraryFamilyName `PANTONE\xa8 Coated'>
<ColorLibraryInkName `PANTONE 3308 CVC'>
> # end of Color
Now suppose we create what we think is the same CMYK color:
<Color
<ColorTag `CMYK-100-0-60-72'>
<ColorCyan 100.000000>
<ColorMagenta 0.000000>
<ColorYellow 60.000000>
<ColorBlack 72.000000>
> # end of Color
Notice two things:
No name. The print shop (or Pantone-aware print engine) has only the who-knows-what CMYK values to work with.
The initial CMYK values aren't even the same, although they look identical in the Color Definitions dialog. And they will be even more different in the PS and PDF on the Windows platform.
There could be easily be a more elegant way to fix this, but for a single file, a simple MIF hack would be:
Make sure the named Pantone color is in the Color Catalog.
Find, in the <ColorCatalog, each custom color that needs to be redefined.
Delete it, from and including <Color to and including > # end of Color.
Batch replace all other occurances of that custom color with the Pantone.
Using the examples above, change all
<FColor `CMYK-100-0-60-72'>
to
<FColor `PANTONE 3308 CVC'>
Repeat the above for each custom color.
Save the MIF and re-open in Frame.
Another way to get all your CMYK content under a measure of color control is to do ALL the color content as imported EPS. Mr.Bill's GDI shredder passes it through unscathed. This means no Frame art and color text only with great annoyance.

System colors definitely wrong

I bought a MacBook Pro yesterday (2.8 GHz, OS X 10.6 [why not 10.6.3? I guess Best Buy has old Mac in their warehouse: not nice]) and migrated my entire PowerBook G4 to it via Firewire. 61 gigs later, as I cast my undeserving eyes upon my beautiful new screen, I noticed that the colors and tones of my desktop picture were kind of different. Then I noticed that the un-visited links on webpages looked, not quite blue, but rather an intense darkish blue-purple. Then I noticed that some pages containing flash applications have rather intense, offish colors to them. I've been using Mac laptops since the first 180
Did I get a defective display?
Or is it that the migration assistant imported some settings belonging to the PowerBook G4 and it messed up the system colors in the MacBook Pro?
Any opinions would be appreciated.

Scott:
Thanks so very much for the help. I had attempted calibration, but not with expert mode. But now I did it and it definitely looks better now, though I think there's still some tweaking to do.
I lost a sentence in my original post: I have used color mac laptops since the 180c, and I do notice a big difference.
It might be that I'm not used to the brilliance of the new LCD, but I do know that the colors are wrong. And I do believe, after much thinking, that it had to do with the settings being messed up with Migration, since it copied my entire old PowerBook, settings included, to the MacBook Pro. Perhaps they should warn you about that when you migrate.
I'll mark the question as answered, since it seems to have had an effect, but I'm unhappy about Apple not letting you know that such things can go so wrong in Migration.
I'll keep trying to calibrate...
Thanks so very much for your help and time,
Saúl
PS: I couldn't figure out how to attach a pic here. Sorry.
S.

Photoshop CS6/Camera RAW 8.8 Inconsistent Color Edits

I just updated my Windows Photoshop CS6 to 13.01x64 and my Camera Raw to 8.8.0.397. My issue since updating is when I open a RAW file and edit it in that window, when I click 'Open Image' and it converts it into the Photoshop window (to further edit), the colour is very different than it was in the RAW window. Below is an example where I went extreme to show the issue. The left is the RAW window and the right is when it converted to after I clicked 'Open Image'. It's much more muted and the colours are quite different. You can see the difference especially in his face. I'm beginning to feel desperate. Can anyone help?

I'm not seeing it with CC 2014.2.2 and ACR 8.8, but then again it's a different PS version and different RAW.
Maybe something happen with color settings in Photoshop?

Inconsistent color values across CS3 apps

I am using CS3 on a 2.66 quad core Intel Mac running 10.5.8.
I am working with an InDesign file with many links. When I click the edit link button on the links palette in InDesign my image opens in Photoshop just as expected. I use the info panel in Photoshop to take a color reading and decide I need to edit. Any adjustment items (Levels/Curves) that I open cause the readout in the info palette to jump, both the before and After readings. I have a c:1, M:1, y:1 turn into a c:10, m:8, y:8.
If I open the file directly from the server or from my local desktop into Photoshop, This problem does not exist. The values stay the same until I actual make an adjustment.
I have restarted. Same problem. I have deleted all preferences for Photoshop, InDesign, & Bridge. Same Problem.
My admin logged in under their name and this problem disappeared.
Does anyone know what setting or preference I need to change/eliminate to stop this problem?
My biggest concern is that my final files will have some issues on press as a result of this.
Thanks

Urrrrrg.
Problem solved.
1. Go to the correct folder to get the image.
2. destroy attached profile.
3. rejoice over minor victory.

Inconsistent Color Prints on Epson R2400

Okay, I'm frustrated. I ran out of ink on my epson r2400, specifically light light black and light magenta. I changed cartridges and now the color is off. I haven't changed the profiles or settings and the image is the same (I was printing multiple copies of the same image when I ran out of ink). The prints are much more magenta now . The inks are epson inks, the paper is Costco paper, the profile I got directly from Costco. I ran a nozzle check, and it was fine. The combination worked very well until I ran out of ink.
I contacted Epson, to see if they could explain it or if they ever have ink inconsistencies. They assured me that their ink quality is perfectly consistent. Therefore, they said, the problem must be with the paper or my settings in Photoshop.
Has anyone experienced a color shift simply from changing cartridges before? Any suggestions on what might have happened within Photoshop to cause such a problem? Any suggestions at all?
Thanks,
Steve

Thanks for the latest tips, though the problem has been solved!!
I ran through the light magenta cartridge in question making a lot of color prints where the match wasn't critical. I replaced the cartridge with another epson light magenta and printed the same photo that initially caused my concern. Amazingly it is back to where it belongs, identical to the prints I printed before I made the last cartridge change.
Therefore, in my opinion, the cartridge was indeed the culprit. Surprising yes, disappointing yes, rare yes, but it really, truly did happen.
I've always been a fan of epson, but it sure is infuriating when a manufacturer places the blame on someone else and refuses to even consider that the fault could possibly be in their own quality control.
Though I will most likely stick with epson when I eventually search for another printer, I may now entertain other brands. Any suggestions?
Thanks,
Steve

Inconsistent color definitions

Similar Messages

Maybe you are looking for