Pages to PDF/X-1 a:2001
1.8 Mhz G5 dual, 2 Ghz Duo MacMini, iPhone, Mac OS X (10.5.8)
1.8 Mhz G5 dual, 2 Ghz Duo MacMini, iPhone, Mac OS X (10.5.8)
Do I need Adobe Distiller?
Can I go through the normal PDF route via Pages?
I'm very new to this area of supplying a file for printing?
1. It does not have bleeds, crop marks or slugs
2. OSX does not support spot colors, except indirectly for imported postscript graphics.
3. OSX's ColorSync filters render any form of transparency at 72 dpi
4. The color management in OSX is opaque and has no usable method of verification that the .pdf is viable.
Henrik Holmegaard wrote:
1. It does not have bleeds, crop marks or slugs
Apple has the interface, but the interface does not do anything. Whether Apple should have the interface in the first place is another matter. Device dependent settings don't belong on the desktop, they belong as close as possible to the printing and binding process.
2. OSX does not support spot colors, except indirectly for imported postscript graphics.
The Apple ColorSync filter can be configured to preserve the names of non-process colourants (spot colours), and if memory serves to colour manage non-process colourants which is to say convert to the data space of some device using a source and destination ICC profile.
Presumably the names would be matched to CIEL a*b D50 2 degree standard observer measurements of double impressions e.g. of Pantone swatches on specified paper and at a specified frequency algorithm and specified tone value increase.
There is no information on what version of what spot colour library this would be done with. Chancing on the piece of UI is one thing, knowing what it does is another. Since there is no documentation, ...
3. OSX's ColorSync filters render any form of transparency at 72 dpi
A static condition, seemingly. Apple should not have said in advertisements that printing PDF provided for resolution-independent. Printing PDF does not provide for resolution-independent unless the destination device is able to accept PDF with transparency directly.
4. The color management in OSX is opaque and has no usable method of verification that the .pdf is viable.
IMO the blame is partly Apple's and partly Adobe's. Ever since Adobe had to advise the Securities and Exchange Commission in 2003 that Microsoft was preparing a competing document model, Adobe has been more concerned to complicate and diversify than to simplify and consolidate.
Just being able to label the output finish, whether it is a mixed ink, a laminate, varnish, metallic, diecut or whatever, is a start. Apple makes it almost impossible using its tools. Yes it can be in an imported .pdf/ai file but then you can't match the spot color within Pages.
I have no difficulty with a spot color being a solid or tint. Which is why it is so useful and why it works when so much of "Color Management" remains off-stage hokum.
I will repeat for the umpteenth time why I want and need spot colors:
1. Fine detail on uncoated stock.
2. Colors unmatchable by cmyk.
Henrik Holmegaard wrote:
I will repeat for the umpteenth time why I want and need spot colors:
For what it's worth, below ditto for why nobody needs the difficulties of working with non-process colours as more and more printing moves from sheetfed offset π.
1. Fine detail on uncoated stock.
Spots specified for PMS coated, solids only (no tints), last minute change to PMS uncoated, some solids changed to tints. Surprise, surprise, surprise, and page designer wonders why π.
2. Colors unmatchable by cmyk.
First, the colour spaces formed by process colourants are not necessarily static, and the larger the colour spaces the larger the number of spot colourants the device can reproduce directly.
Difficulty?
Pages to PDF/X-1 a:2001