Will PDF-Robot work with our Agfa Apogee CTP Workflow?

Hi, I work in a pre-press studio which runs a pdf workflow. We use an Agfa CTP system (Apogee Series 3) where we postscript straight from Quark into a Apogee Normaliser which flightchecks the postscript files, adds any actions (we have programmed some master actions ie.-knockout white etc,) and creates the pdf's for us to impose etc. This system works ok but it struggles with DCS2.0 files, we are not able to send composite files down which in turn would create a composite pdf, so we have to create separated pdf's which visually only show the last plate (no good for proofing to the customer) and also it creates images on any blank colour spaces.

I have also updated to OSX Panther and running Quark 6.5 and any spot colour vignette in quark converts to CMYK through our current system. Could we create hi-res pdf's to use in our current Agfa workflow using PDF-X-Robot, and would PDF-X-Robot solve the problems I have mentioned above? Do you know of . . .
.
Click Title Above for Additional Info. .

PDF Viewer with pluPDF Viewer with plugin support (other than adobe acrobat)

PDF Viewer with plugin support (other than adobe acrobat)

Hi, I am looking for some pdf viewer which supports customized plug-ins (to extract metadata from PDF doc) other than acrobat. I have modified the text annotation by changing the sub-type name from 'text' to my custom name.

In the title of this annotation I store my metadata (e.g. the row id of some table in oracle). I have written a plugin to handle this custom annotation, to extract this metadata and pass it to the calling application (actually, acrobat is embedded in this calling application).

I need a PDF viewer which can support my plug-in. also, let me know if there are available viewers which can provide plug-ins to do a similar work.
.
Click Title Above for Additional Info. .

Font Types and Why So Many, dFonts, OpenType, TrueType

I would like to see Adobe embrace the dFont format. i am so weary of all these font types with OS X, and it's getting worse by the day. Why does Adobe have to try and screw up font management again. First they came up with that damn type 1 font that required two separate font components IN SAME FOLDER. Did they ever consider engineering that to be a single file? No, they created a monster for us to deal with for years and years.

For years Adobe was making sure that Mac OS True Type fonts were not going to work right in Adobe Rips. True Type was always a better model for sure in that it DID NOT require two separate font components to work (Like screen AND printer font). Now we are over ten years down the road and every modern font model DOES NOT require two font components like Adobe's type 1 fonts do. Wht can't they just sell their damn fonts under dFont and make our lives easier. . . Like we all need ANOTHER font format out here to deal with.
.
Click Title Above for Additional Info. .