Pit Stop Server l l JACo W Pit

Pit. Stop Server l l JACo. W Pit. Stop Server automates pre-flight and correction procedures. PDF files are dropped into a hot folder and are automatically processed. Emails can be sent to one address to notify success, errors or warnings. The server uses PDFProfiles and Action Lists for the processing. Pit. Stop Server, Team Meeting, Frascati, 2005, J. Poole 1

Pre-flight JACo. W Features which may interest us: l Check the number of pages l Check and correct PDF version l Check and correct media box l Detect graphics overlapping margins (but no correction) l Check, Substitute and embed fonts l Detect and remove bookmarks Pit. Stop Server, Team Meeting, Frascati, 2005, J. Poole 2

Action Lists l JACo. W Currently we use the JACo. W-Media. Box action list by hand this: o Selects all o Resizes media box to 210 x 279 mm (595 x 792 pt) o Removes crop box l The final stage (Remove crop box) cannot be done with a PDFprofile. Pit. Stop Server, Team Meeting, Frascati, 2005, J. Poole 3

What could be done for more automation ? l l l JACo. W Author uploads Post. Script to a Distiller-watched folder Distiller produces PDF in a Pit. Stop. Server-watched folder Pit. Stop Server o checks the number of pages, checks/removes blank pages o checks the file, fixes the page size and removes the crop box. o checks for graphics in the margins and sends email to editor if there are problems. l Error log files are produced and these could be fed back to the author but this would probably require manual intervention ? Pit. Stop Server, Team Meeting, Frascati, 2005, J. Poole 4

What are the drawbacks ? l l JACo. W There a large number of papers where we don’t get Post. Script. Detection of graphics in the margins is a bit flakey. Font checking is not quantified (a bad font may have negligible impact). If you get a message telling you that there is a bad font, it may not be easy to find. We still need an editor to verify performance. Pit. Stop Server, Team Meeting, Frascati, 2005, J. Poole 5

Conclusion l JACo. W Complete automisation would not be very effective because of the number of bad or missing Post. Script files. o Unless we really forced the authors to submit them l Maybe we could improve on reliability if editors dropped the Post. Script into a Distiller-watched folder which was connected to Pit. Stop Server via another watched folder o the PDF would just need checking for graphics, fonts and performance – the Action List would be guaranteed to be done. Pit. Stop Server, Team Meeting, Frascati, 2005, J. Poole 6