- Affinity photo font glyphs stylistic alternatives pdf#
- Affinity photo font glyphs stylistic alternatives pro#
- Affinity photo font glyphs stylistic alternatives windows#
Affinity photo font glyphs stylistic alternatives pdf#
Something that I have not yet tested is what happens if one has an alternate glyph for a single letter and one produces a PDF document.įor example, a swash e at the end of a line of the text of a poem. It means that one can publish a PDF document of a poem and have ligatures in the display, yet the poem can be copied from the PDF document and the underlying text pasted into another document, such as in, say, WordPad. The ligature must not be mapped as well though. The issue is that the underlying text is displayed, not blanks where some or all of the ligatures appear. Not in the same font, but that is not the issue. Suppose that one now copies the text from the PDF document and pastes it into WordPad. Suppose that one produces a PDF document (for publication on the web) where the text of the document is displayed using a font that has OpenType ligature capability. This feature is really top class quality.
Affinity photo font glyphs stylistic alternatives pro#
But that being said, I'm using Font Explorer X Pro and it has been working fine for me so far.I have found a fantastic feature in Affinity Publisher. Lastly I don't imagine the actual choice of your Font Manager is vital to these problems – as far as I see they all (under the hood) work in a similar way when it comes to how fonts are activated or not. Currently it's certainly a pain in the a** to change/substitute an extensively used font in Publisher when you didn't consistently assign text formats in your document.
So far, however, only old PS Type 1 fonts seem to have been concerned and maybe it's actually wise to use newer OTF fonts whenever possible and to check PDF export in an early stage anyway. (Way back in InDesign and with an older macOs the KnockOut font had worked just fine, however.) I didn't find any way to fix this except swapping the font (family) to another similar one. When in the Export dialogue you could see the ”Estimated File Size" check wouldn't be completed and no PDF would actually be produced. The font in question (ITC Conduit, PS Type 1) actually exported to PDF without any problems, but Publisher’s Glyph Browser did look exactly as empty as it did with ITC Korinna in Lagarto’s screenshot.Īs you mention it: I did have problems with exporting to PDF once with another (old) PS Type 1 Font Family (HTF KnockOut, if I remember correctly). Because Type 1s do render at times in PDF, this does not appear to be a problem with PDF Library but with Affinity apps.
Affinity photo font glyphs stylistic alternatives windows#
This same font (well, the same library but different physical files, as Type 1s are on Windows and macOS) shows ok in the Glyphs panel of Publisher Windows version, and also exports to PDF. This font exports to PDF but if I remember correctly, there can be problems when exporting multiple members of the same family at the same time. UPDATE: Just tested this on macOS (Big Sur 11.4), with ITC Korinna (also from Adobe Font Folio 8): The PDF export also fails to render the font at all, but it exports ok to bitmaps. Yes, this happens oftenoccasionally with Type 1 fonts, especially symbol fonts like Zapf Dingbats (this is from Adobe Font Folio 8, and it works with other apps without problems): It's not a vital problem as I've changed the font later but I'm curious nevertheless if anybody else might have noticed something like this as well or even knows what specifically might be an explanation of this behaviour.
0 kommentar(er)
