TonyB

This will be a graphics card related issue. Can you post your MacBook Pro specs and what version of macOS you are running please.

The betas of Designer and Photo 1.7 updates should start in a couple of weeks.

Hyperlinks are on our internal roadmap, unfortunately like most of the other great suggestions we just don't have a date for when it will be implemented.

If you pick one the the Prepress PDF standards like PDF/X-1a:2003 then and RGB images will be converted to CMYK for you. We do need to add preflight check for other items in the future but source image colourspace shouldn't be one of them.

The cost of Publisher would have to be close to the cost of Quark. We would also need to rewrite the whole PDF pipeline causing a delay of probably a year.

Embedded font support will be added for PDFs.

There isn't any reason we couldn't be better the Infix. The only problem is being as good as Adobe.

Thanks for the Quark 2018 info. I believe they started with Adobe tech then used Jaws and now look like they have changed again. The problems for Affinity are still the same though. I believe the best way forward is to improve our PDF rendering and therefore our editing.

Implementing pdf-passthrough has two problems. The first is we still need to draw something so we read and render the PDF exactly the same way as we edit them. The second is the pdf-passthrough usually fails because the PDF is not a press-ready PDF with the exact spec version, colour space, transparency flattening, compression, bleed etc. as the destination PDF. The only way to correct these is to read the PDF file and interpret the contents the exact way we do to edit them. Adobe do the same but are just better at it than us as they created the spec and even sell the tech. You can even licence the tech from Adobe but the cost per copy would be n-times the cost of Publisher. I believe Quark licensed from Adobe but also use another RIP with varied results.

I think this should be viewed as a bug.

Support for hyperlinks will be added to Affinity but unfortunately we don't have a timescale yet.

The ability to output as pages and not just spreads will be added soon.

I think we have received all the feedback we need for PagePlus import. I will end this thread by saying that if we did produce an importer we would wait until Affinity Publisher supports enough features that the importer would be better than our current PDF import. Sorry but that's best we can say at this time.

We will be able to import InDesign IDML files but not .indd files. The feature is being written but we don't have a timescale yet.

The option is currently on the "More" button. I think we should move it to the main panel though.

Yes, this feature will be added. Thanks for the feedback.

When you place a PDF then you can choose the page shown on the context toolbar at the top. If you want multiple pages then you should load(File Open) the PDF into Publisher and choose the pages you want. We don't currently have a insert PDF/Affinity document that will merge multiple pages yet but we might add it later.

The ability to import .docx files is on our internal roadmap. Implementing .doc files is much, much harder so we can't commit to doing that work at the moment but we will continue to track its importance.

We also agree and page columns are on our roadmap for all the Affinity Apps.

This capability is on our roadmap. Like other long document features, we will release them when have have them working well.

Your description is basically what we plan to do so just be a bit patient and give us feedback when we have a working version. Other long document features will come over time.

This feature isn't on the roadmap so we can't commit it do it but it's something we are looking into for a future version. You can already produce good colour accuracy but just not with the profiles from CCP.

This should hopefully make the 1.7 update This should hopefully make the 1.7 update later this year.

If you feel this way then you are possible using the wrong Application.

All vector applications including Ai have traditionally produced raster data in the same way. It does look like Ai now does edge anti-aliasing differently. I'm not sure how recent the change in Ai was but I also noticed the quality of their anti-aliasing is now not as good. We can visit this again in the future but at the moment this is how we and all other vector applications render edges for off pixel boundaries. We will have to experiment but it does look like we will lose some quality though.