Nate… My thoughts on this… ( in order )
1. The documentation is wrong…
2. The feature is broke…
3. The syntax so convoluted nobody's worked it out…
Indesign has more preferences than Illustrator has all in… and it all works too…
Thanks Muppet Mark,
So far you have confirmed my suspicion that it just does not work and has not worked for years.
I do need to use illustrator though for the project I am working on that tiles multiple PDF's up with user defined bleed and gutters. Die lines, marks and registration marks are also built. Sometimes custom dies are placed and need to be edited which Indesign will have a problem with. A final PDF is created at our multitude of substrate sizes. The die and registration marks are seperated to a seperate file that is opened in cutting software to route, cut or score final pieces. Everything works great except for placing the PDF's.
If I ever do find a way to properly read the crop boxes of a PDF upon placing into illustrator as a link, I will post it.... but it seems most likely broken. Plus I do want to get working on the multisize, copies and intelligent scatter functions.
You can after placing just change the bounds of the first path of the group this will be the main PDF mask ( artBox )… Unfortuantely and very annoying there appears to be f**k all you can do about page to place…
I don't think there's options for placing PDFs, the options are for opening PDFs, and yes, they don't work, hahaha
you could, if your workflow allows it, place a dummy pdf (manually) with the settings you want (MediaBox), then Relink it with the real PDF via Scripting.
The AppleScript Dictionary says the same as the OMV and Jongs helper… CropToBox for placing & pageToOpen for opening… For me a misleading doc mistake… And forgiven for the fact that it should dammed well be there in the first place…
Property Type Access Description pDFCropToBox PDFBoxType:
r/w What box should be used when placing a multipage document (default: PDF media box) pageToOpen int r/w What page should be used when opening a multipage document (default: 1) parent Object readonly The object's container. typename string readonly The class name of the object.
Isn't it cool that those can just be C&P into here… Thanks Jong…
obvious mistake, right before that properties box, there's a sentence that adds to the confusion
Options for opening a PDF file, used with the open method. All properties are optional.
My point 3 was those get & put methods for app prefs… I wasn't 100% that there wasn't an underling way to change something behind the place but I couldn't work it out…