Jump to content


  • Content Count

  • Joined

About A_B_C

  • Rank
    Dedicated User

Profile Information

  • Gender
  • Location

Recent Profile Visitors

3,993 profile views
  1. I’d probably separate the PDF to single pages in an external application. There are plenty of free or inexpensive options available for doing this on Windows. Then you can use File > Place …, select all your single-page PDFs in the dialogue, and you’ll get the useful Place Images panel that allows you to simply add one PDF after another. 😀 (If you have single-page PDFs, still another option would be data merge, I guess. Unfortunately, I didn’t have the time to test it with documents so far, but it should work.)
  2. Yes! PDF Passthrough is getting useful! Thank you so much … 😀
  3. The Resource Manager with linked resources is a very welcome addition, Matt! Awesome work with the 1.9 series so far! 😀
  4. That’s a great real-life example! 😀 And I’d support your conclusion. Also not meant as mere criticism in any way, but hopefully received as some sort of constructive feedback! 😊
  5. I absolutely agree with the point you made earlier in this thread, Jens! 🙂 I just meant to provide an example that can explain why it is essential to have the non-interpreted version of a placed PDF displayed in Affinity Publisher. In my example, I exported a PDF with Erica One from Publisher, disabled the font, and placed the PDF back in a different Publisher document. Now, what can you do with the placed file, when the typeface is replaced by Lucida Grande? There is no way to create a consistent design context in which the placed PDF could play a role. You simply don’t see what you get. I fear the current approach will be met with strong reservations, should it find its way to the release version. I must also confess, I didn’t understand completely what Adam said in his earlier reply. As far as I understand, the development team would like to stick to the idea that the PDF interpreter is responsible for displaying the placed PDF on screen. And to achieve WYSIWYG, they are planning to improve the PDF interpreter up to the point where the interpreted PDF is visually identical to the source PDF, in particular by finding a solution for embedded fonts. Of course, if that’s achievable, it would be a satisfactory solution. But I think it’s clear that PDF passthrough, in its current state, would cover a rather limited range of use cases in real-world contexts.
  6. Strictly out of curiosity: MacBook Pro 13" Late 2011 2,4 GHz Intel Core i5 16 GB 1333 MHz DDR3 Intel HD Graphics 3000 512 MB macOS Sierra 10.12.16 Sorry, this is hard to read, but that’s the way the benchmark panel looks on Sierra:
  7. Configuration: MacBook Pro 16" 2019 — Base Model 2.6 GHz Intel 6-Core i7 16 GB 2667 MHz DDR 4 Intel UHD Graphics 630 AMD Radeon Pro 5300M macOS Catalina 10.15.6 Get slightly different numbers when running the test several times, as probably to be expected. Anyway, here are some. 😉
  8. I do as well. Absolutely. There is a essential difference between just placing a PDF in a Publisher document and embedding a PDF into the design context of a Publisher document. If we were talking about placing PDFs in the first sense only, the current implementation would surely be sufficient. But as soon as you have to refer to the visual contents of the placed PDF by any kind of design elements, you are lost. As for a hypothetical example, suppose you are asked to add some explanatory texts to a design specimen of a new typeface without having access to the typeface itself yet. Then Publisher will replace the typeface by Lucida Grande (see below). So, how are you going to complete your task on the basis of the current implementation? How could you possibly determine the correct position of the blue line that serves as a pointer in my example? Seems difficult, right? 😉
  9. Adam, I’m excited about PDF passthrough! But why do you display the interpreted preview in the Affinity document, and not the actual output? That is thoroughly confusing. Is there a technical constraint that motivates this aspect of the implementation? 🙂
  10. Other that that: there are some fantastic new features in this. 😊
  11. Have to agree. If auto-updating presets was an option, I definitely wouldn’t use it … 😊 (Oh, and while you’re at it: what about an option of locking the workspace? That is, when the workspace is locked, it’s impossible to resize or tear off panels.)
  12. I see. That’s fine. I was afraid the devs would change the setting globally, such that it would affect the other tools too. 😉
  13. To make myself more clear, when you’re doing pixel-perfect stuff, you will always have Force Pixel Alignment enabled, but only sometimes enable a set of additional snapping options. For this scenario, I believe the current solution is just perfect. 😀
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.