🚀 go-pugleaf

Darren,

Most colour printing is done via composite PDFs (i.e. a single PDF
that is in CMYK colour space) and the separations are done in the RIP.
Pre-separated workflows are going the way of the dodo.

The problem with FM on the Windows platform is that it relies on
Microsoft's graphical device interface (GDI) to create postscript. The
GDI only works in RGB colourspace, so all FM defined colours get
converted to RGB, except for colours defined in EPS files (these
simply get passed through to the postscript file untouched).

To get the correct CMYK in your final PDF, you must either intercede
at the postscript stage and convert the colours back from RGB to CMYK
or do this in the PDF. 

A tool to do this before it gets to the PDF is ColourChameleon
available at http://www.grafikhuset.dk/ColourChameleon.html 

Alternatively, to correct the PDFs themselves, you can use PitStop Pro
from Enfocus at http://www/enfocus.com or Quite-a-Box-of-Tricks from
Quite Software at http://www.quite.com

If you think that pre-separated sounds like a better route, be aware
that these separations themselves are RGB. So if you don't properly
inform your print shop, they may not set the parameters on the RIP
properly and it will then separate the "separations" - you can do the
math as to how many pieces of film that you could be on the hook
for...

Not to completely scare you off, you can create colour print jobs from
FM Windows (I do it all of the time), but you need to be fully aware
of these limitations. There simply is no direct way for FM on Windows
platforms to directly produce proper composite PDF for press work
without the aid of third-party tools. However, if you can create the
final FM output on a Mac or unix platform, then you can avoid these
issues.

I do heartily endorse what Bill said - talk to your printer about what
they expect/want from you in the PDF.

I hope this helps.