Jump to content
You must now use your email address to sign in [click for more info] ×

Vex

Members
  • Posts

    85
  • Joined

  • Last visited

Everything posted by Vex

  1. I disagree entirely. The two features output different results. One embeds (or links to) the PSD, allowing editing of the PSD separately from the Publisher document. The other adds the PSD's layers to the layers of the Publisher document, allowing editing of the document as a separate file from the original PSD.
  2. Well, I think I figured out my "problem", which is more of a UX issue than a functionality issue. Seeing only the rasterized version of each PSD in Publisher via data merge (placing the PSD rather than importing), I assumed an exported PDF would likewise use the rasterized version. It apparently does not - I'm able to select all the text in the exported PDF, which I think means I should be able to use the PDF for the next phase of this project. This wasn't clear in the Publisher UI, but I'm glad it's doing what I need it to do.
  3. Well, that wouldn't be a problem if I were only working with one or two files, but again, this is going to be a total of nearly 700 files - which is why I'm automating it. If Publisher just can't accommodate what I'm trying to do, that's ok (and I might post feedback suggesting an improvement to the existing features). (ETA: I have an alternative route, which I was already working on when I discovered Publisher's ability to import PSD text layers as actual text, so it's not the end of the world if I just have to do what I was originally planning on doing)
  4. I made a new preset with the page size, DPI, and image placement settings I wanted, but when I do a data merge, I'm still getting placed PSDs, which means no real text layers in my Publisher document. Is there a way to automate/script Publisher from the command line to import individual files, ignore warnings (there are lots of text layer warnings that are irrelevant), and combine into a new file?
  5. Unfortunately, no - I'm working with copyrighted material for a client. I think I'm just doing something wrong in trying to set the document to default to embed instead of link for imported images. How do I set that properly?
  6. I tried setting the doc to embed rather than link, but when I merged the data, it was still linked. How do I properly set up my template page (that the data is merged into) for embedding? Sorry - I'm very new to Affinity apps.
  7. Right, and that works if I import a PSD. However, per the details of the 1.9 update, placing a PSD rasterizes the text.
  8. I do. I noticed, though, that in the 1.9 release, placing PSDs rasterizes all text now. Is there a way to disable that? I haven't found one yet.
  9. Thanks for the tip - does this allow me to insert the PSDs and preserve the text layers as text? I figured out how to get it working with my data, but it's using image placement with rasterized text instead. I need the text conversion.
  10. I'm working on a project that involves my source content as PSDs (with real text layers). Affinity Publisher's ability to import PSDs with text preservation is pretty sweet and looks like the only app that does this, but I don't see a way to do this in bulk. I'm working with about 700 individual files, so I definitely need to be able to automate this. Is this possible? Thanks!
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.