#Birdfont add nodes pdf#
Such as the original PDF you pasted from. To figure-out what happened we would have to see all the documents. So somewhere in your process this got messed-up.
#Birdfont add nodes code#
Some applications like Word or LibreOffice (and perhaps ID too) have auto-correct entries which will replace the two ff characters (U+0066) with the one ligature code (U+FB00). If the font includes OpenType ligatures I have seen ID embed the code for both the ff characters, so when it is copied the new application can decide what to do with them. The Palatino that comes with macOS does not include OpenType ligatures for ff and ffi - but it does include the old legacy code points - ff (U+FB00), ffi (U+FB03).įor ligatures it uses the non-standard morx table, which is not supported in Affinity applications.īecause of the odd characters you are getting, I am guessing that the original PDF may have an issue with how they were embedded, and when you cut-and-pasted that came along with it.
If you would like to test this option, let me know. This would have the advantage of all current documents probably still working. I have seen in another forum that just changing the PostScript Name inside the font may work. This may be the best option with meeting your deadline. But sometimes if you have a lot of old Affinity docs that may be difficult - as you have to reassign the fonts to all the text. Renaming the fonts has been reported to work. Even if they were previously used in the document. There also does appear to be an issue with using these fonts in Affinity applications. Some are older fonts that were included with earlier versions of macOS or Apple apps." "These fonts are available only to documents that already use the font, or to apps that request the font by name. Variable fonts never remove the overlaps as they are required for correct interpolation.Īthelas is what Apple calls "Document-support fonts" that they have apparently stopped including - so they hide them.Ībout half way down the page you will see a heading which says: Document support fonts This is why the static fonts from the original Montserrat repo have no overlaps.Īffinity must fix this to be able to eventually support variable fonts. Static fonts in the original font developer repository usually remove the overlaps when they are generating the fonts from their font editor (they just check a box to remove the overlaps on export). Other desktop publishing applications handle this correctly. To support variable fonts, the application must handle this properly.Īlmost all browsers now handle this correctly.
Their position is that applications should handle this properly. When Google Fonts uses their tools to build the fonts, they leave these overlaps in. Those are the overlaps and looped corners used when creating fonts from multiple masters sources so the different styles interpolate properly. I encountered this problem when I was still using affinity designer V1 and it happened in V2 as well
#Birdfont add nodes plus#
This problem occurs only for some typfaces like Montserrat and Jakarta Plus Sans and some other fonts are still running normallyģ.
0 kommentar(er)
