no, because you don’t need it for the output from InDesign. Same with linked files in Illustrator.
Can you elaborate a little on why it's not necessary? If I'm packaging the files to send to the printer and they need to open the packaged "BaseImage.psd" link, they'll then see that "LinkedImage1.psd" and "LinkedImage2.psd" are missing. If a link is missing from an InDesign it will print lo-res, so I'm assuming the same would apply in this situation. Also, if I place an InDesign file within an InDesign and then package, it will collect the linked InDesign file and all of the images placed in that file -- so I don't quite understand why or how it's OK that the same does not work for Photoshop and Illustrator files.
LImked INDDs are different they are needed.
AS long as AI or PSD files are not opened they contain the full information for output. There is no need to open them and the printer should never do it, not with AI, not with PSD files. Hands off.
WHy are you not sendinn PDF files.
That makes total sense... I can't think of any reason why the printer would need to open a linked PSD or AI file -- and I certainly never want them to, but someone above me at my agency is going to ask the question when I propose the solution I'm working on so I want to make sure I can explain why it's OK.
We send hi-res PDFs to the printer for sure, but always send the fully packaged files. I can't give a better answer as to why we send it all other than it's the way my company rolls. Most of the agencies I've worked for are still sending packaged files. Sadly enough, I'm not exactly sure what the printer does with the files we send because it's kind of "above my pay grade," which is another issue in and of itself... I've heard that they take what we send and rebuild them in their own application, which I'm trusting is fine, but could just be an antiquated way to do things because they're not ready to get on board with something new/different.
I can't think of any reason why the printer would need to open a linked PSD or AI file -- and I certainly never want them to, but someone above me at my agency is going to ask the question when I propose the solution I'm working on so I want to make sure I can explain why it's OK. ...
We send hi-res PDFs to the printer for sure, but always send the fully packaged files.
The only rational for sending a package along with a press ready PDF would be to give the printer the ability to edit the job. If you really never want them to edit then why send a package?
I can't give a better answer as to why we send it all other than it's the way my company rolls
There is a difference between Photoshop's Placed Embedded... and Placed Linked... If you Place Linked and don't include the linked file the printer would have to rasterize the placed smart object in order to edit, which it seems would defeat the purpose of a placed smart object. If you want the printer to have full access, then including the placed files would be a good idea. If you use Place Embedded... you would not have to include the original—double-clicking the smart object opens the placed image.
I understand what you're saying, Rob, but sending the package is our process, which I'm not currently in a position to try and change. Also, there's a unique aspect to the work I'm doing that requires a few extra/different steps on our printer's end.
I also understand the difference between placing an embedded image and linked image.
Thanks for the help!
Is there a way when packaging my InDesign file it will not only collect the "BaseImage.psd," but also collect the linked images within that PSD?
To your original question you probably could gather Photoshop or Illustrator links—or embed them—via scripting. I don't see a way to do it via the built-in packaging.
Yup... I wish InDesign would know to collect link items in AI and PSD -- it seems like an obvious glitch? But per Willi's comment, and a little test run I did with my printer yesterday, I'm thinking it's OK so long as the PSD isn't opened. I know you can package the PSDs now like you can an INDD, but I'd like to avoid an added step -- again, I'm not really in a position to try and change our process for doing things on that end. That's also the reason I'm not sure using a script would be an acceptable option for my company at this time. It's difficult being one designer working on one specific type of work within a large agency with set processes.
That's also the reason I'm not sure using a script would be an acceptable option for my company at this time
Is there a reason embedding or Convert to Smart Object isn't acceptable? I guess you'd still have to worry about someone inadvertently linking.