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