Skip to main content
October 13, 2010
Question

FM 9 save-as-PDF does not respect tints of cmyk color defs?

  • October 13, 2010
  • 3 replies
  • 1261 views

Using FMp237 and Acrobat 7. I am an experienced user, but new to FM9.


The color defs in my file consist of spot CMYK Pantone colors that use an ink from one of  the built-in Pantone libraries and custom colors that consist of tints of the spot colors. For example, I have a Pantone Cool Gray 10 as a spot color and a Contents Table Gray custom color that is  a tint set at 10% of the base color Pantone Cool Gray 10.

I create the PDF by using the Save-As feature and de-selecting Convert CMYK Colors to RGB so that the resulting PDF has only CMYK colors (we do 4-color printing).

In the resulting PDF, none of the tint colors come out right. They are all 100% of their base colors. For example, Contents Table Gray looks exactly like its base color, Pantone Cool Gray 10, but it's supposed to be only a 10% tint of it. It prints that way, too.

What can I do about this?

If tints just don't work with Save-As, how do I figure out what CMYK values will get me that tint?

I know that the FM 9 Save-As feature uses its own Postscript generator when you de-select Convert CMYK Colors to RGB--could that be the root of the problem?

Any help will be much appreciated--I have to debug this pronto as some print dates are approaching.

    This topic has been closed for replies.

    3 replies

    October 14, 2010

    Thank you, Jeff and Bernd.

    The fix for the table screens is great, thanks so much for the info.

    A question: RE the self-defined spot colors that don't work: Someone posted on this forum a supposed fix for this, he said you could just save as Mif and enter the missing values and then save, and the spot colors would work. for example:

    <ColorLibraryFamilyName `Hypertext Blue>

    <ColorLibraryInkName `Hypertext Blue Light>

    Does this fix work?

    Be.eM
    Inspiring
    October 14, 2010

    becky a. edmondson wrote:

    A question: RE the self-defined spot colors that don't work: Someone posted on this forum a supposed fix for this, he said you could just save as Mif and enter the missing values and then save, and the spot colors would work. for example:

    <ColorLibraryFamilyName `Hypertext Blue>

    <ColorLibraryInkName `Hypertext Blue Light>

    Does this fix work?

    Well, that somebody was me, and yes, it works

    When I published the original results of my color tests, I've created an additional test PDF using a manually edited MIF file. You can download the PDF created from this MIF, as well as the MIF file for inspection.

    Bernd

    Be.eM
    Inspiring
    October 13, 2010

    becky a. edmondson wrote:

    I create the PDF by using the Save-As feature and de-selecting Convert CMYK Colors to RGB so that the resulting PDF has only CMYK colors (we do 4-color printing).

    In the resulting PDF, none of the tint colors come out right. They are all 100% of their base colors. For example, Contents Table Gray looks exactly like its base color, Pantone Cool Gray 10, but it's supposed to be only a 10% tint of it. It prints that way, too.

    Becky,

    you're doing it in the correct way, which should work. Should, but doesn't. And while Jeff's tips are both reasonable and you should follow them, neither of them will solve this problem. Actually, there are two different bugs which lead to the result you get (you didn't encounter the third one yet). I created a test PDF some time ago, which shows (and confirms) your results:

    1. In tables, colors defined as tints of other colors always appear @ 100%

    This is still a fact (not fixed, although known for quite some time now). The only way to get a small selection of tints that work: Assign the choosen color in its original definition (the 100% spot color or a process color) and use the available tint settings within the table definition. This is a limited selection, but these definitions work.

    2. For all other FM elements, colors defined as tint (within the color definition dialog) appear in the PDF @ 100%

    I'm not sure if this is an Acrobat or an FM bug, or if two half bugs which make one when both meet. The PDF display is correct once Overprint or Output preview is enabled. It's wrong with these options disabled. This is true for all color usage but for tables, as mentioned above.

    3. Self-defined Spot colors don't work at all, because these miss the required entries

    <ColorLibraryFamilyName `Whatever color'>

    <ColorLibraryInkName `Whatever color bright'>

    (the names are just an example, as they appear in the corresponding MIF files). You won't have to bother with this bug, as long as you're using Spot colors from theFM libraries, these have the required names.

    Bernd

    Jeff_Coatsworth
    Community Expert
    Community Expert
    October 14, 2010

    Thanks Bernd for chiming in - I knew someone out there would know better than me when dealing with colour-stuff ;>)

    Be.eM
    Inspiring
    October 14, 2010

    Jeff_Coatsworth wrote:

    Thanks Bernd for chiming in - I knew someone out there would know better than me when dealing with colour-stuff ;>)

    You're welcome

    But actually I wish it wouldn't be necessary to know weird and funky stuff like this one

    Bernd

    Jeff_Coatsworth
    Community Expert
    Community Expert
    October 13, 2010

    Make sure that you've updated to p255 & check if you need to load the MS XP hotfix for Postscript printing (there's a mention in the Adobe Tech Comm blogs of the location)