benwiggy

Test this PDF, made in Aff Publisher. It contains Non-lining figures in several different Adobe / Monotype fonts. -- Caslon, Garamond, Baskerville, Bembo, etc. They are all outlined in Illustrator, because they are alternate glyphs that can't be mapped back. If you claim that these fonts are 'wrong', then almost every font is wrong and we can't use any of them. Or, the application should work with fonts as they are. That is what Illustrator does, by outlining the glyphs. That is what Affinity should be doing. Instead, Affinity imports this PDF and switches in the default glyphs. Figures.pdf

It's not the font's fault.

Affinity cannot handle the fi and fl ligatures in this PDF. Untitled Project 1.pdf Also: create a PDF in Affinity Publisher that contains Small Caps, Non-lining numerals, Swash Italics, and other OTF variants. Then import the PDF back in. Results can vary form font to font, but even using Adobe / Monotype fonts, e.g. Minion, Kepler, Garamond, there are problems. These have been reported many times.

There are still several issues relating to fonts/glyphs in imported PDFs, particularly related to ligatures, OpenType alternates, and PUA Unicode ranges.

Here's a page ("Good PDF.pdf") exported as PDF from Dorico, music notation software. It uses the Qt framework for its PDF generation. Designer imports it almost reliably (let's forget about ligatures for the moment). However, if I re-save the PDF in Preview (or other PDFKit processes), the import goes completely crazy. ("Bad PDF.pdf") Interestingly, an EPS of the Bad PDF (still with embedded fonts) imports perfectly, as outlines. Converting the EPS back to PDF yields the same crazy results. Bad PDF.eps Bad PDF.pdf Good PDF.pdf

Can I ask what does "Import now allows creation of Art Text if 'Group lines of Text into Text Frames' is switched off" mean? Does that mean all text gets turned into Artistic Text?

Hopefully, everything has stayed as vector data, so resolution should be irrelevant. But if there are any bitmap images in the PDF, then yes, 300 dpi should hold.

The Affinity suite 'doesn't support import of PDFs with embedded fonts'. Sadly, you can expect problems of this sort. The workarounds are: outline the text to curves in the PDF before importing; convert to EPS, whose embedded fonts for some reason Affinity can import.

As said, there are still a number of problems with Affinity's 'correct interpreting' of imported PDFs. You can't rely on it, and you need to double-check everything. I'm still on MacOS Mojave so that I can use Creative Suite 6, and when Affinity finally imports PDFs accurately, I'll be able to forsake Adobe.

Bingo. Thanks.

I have a triangle with one of the corners as a curved point, and the two sides are bowing out; but I want them to be concave. No amount of moving the little things seems to help. I presume there's a 'flip' button somewhere. I tried "Reverse Curves", but that doesn't do anything. Thanks

If you're looking for PDF Viewer, Affinity isn't it. Yet. It will 'convert' a PDF into a DTP document, but it can't be trusted to represent font data 100% accurately. If you need a viewer, then there's Acrobat Reader, or Foxit Reader. For Editors, Master PDF Editor is quite good and on all platforms. On Mac there's PDFPen Pro. There are plenty of others. If you want post-processing of PDFs, then really you have to go the command line route of things like GhostScript, Coherent PDF, or python scripts.

Dear MEB This is really something that should be in the FAQs, because it comes up all the time, and Serif really need to set out their 'direction' on this.

It's been well-observed that the Affinity Suite 'doesn't support' the import of PDFs with embedded fonts, and attempting to do so causes a variety of issues. However, Designer imports EPS and PostScript files with embedded fonts perfectly accurately, because it outlines all the embedded font data. It would solve a great many problems if Designer offered the option to outline the embedded font data, as for EPS files, in the PDF import dialog. I'm presuming that this would be a 'relatively easy fix', as Designer can already outline EPS at import, (and it can outline font data in PDFs when exporting).

I don't have PDFLib in /usr/local or my User home. Yes, if you transported a Mac Type 1 font over a Windows file system, it may well have lost the resource fork that contains the substance of the file.