#OPEN OFFICE FONTFORGE FONT SUBSTITUTION LIGATURE MAC#

#OPEN OFFICE FONTFORGE FONT SUBSTITUTION LIGATURE MAC#

So in the font there are Mac metrics, Windows metrics, and the newer Typo metrics. Those vertical metrics settings are often (usually) different for the Mac vs. It means to use the vertical metrics (leading) intrinsic in the font. The 'default' leading setting in APub is not a default vertical leading (as you would expect). If I change this on the Mac from 12pt to 15pt it presents exactly the same as on the HP, 15pt on Windows computer and 12pt on Mac for the same. I seem to have traced the problem, but only after purchasing a Windows computer (HP) and a new Windows version of Affinity Publisher! By opening and comparing the same file on both computers, it appears that the View/Studio/Paragraph/Spacing/Leading spacing is not carried through as a part of the file - it was presenting as different on the two computers, e.g. If you are not using MacOS, please provide more info. But I do know for sure - it may be possible that MacOS can properly figure-out the PS curves.

I am assuming you got the single static font from Cufon which is v1.001 and has no overlaps. So the GF position is Apple needs to fix it (which they did in 11+). MacOS 10.xx does not handle the overlaps correctly. So some static fonts may still have overlaps. When static fonts are created from a variable source, the overlaps may or may not be removed (it is not required). Those are the overlaps used in variable masters (the source files) and required in the variable fonts for them to interpolate properly. Is this an issue with fonts how they are handled by the AD or simply the error of the font maker? If I select stroke order: Draw Stroke Behind it looks ok but when I expand that stroke it is still this weird stroke that doesn't seem to be on its place. I'm having a weird strokes for some of my fonts, like Petrona. Need some people who know the applications better to test. This could be an Affinity issue - because I can see the overlaps and looped corners after converting the GF fonts Bold font to curves (in ADesigner on Win 10).

The issue could be MacOS, or it could be Xara causing your overlap issues. The issue could be MacOS, or it could be are you using MacOS 10.xx? Or? I would still like to know if the OP is using MacOS 10.xx. So the repo/Cufon fonts may have had some bugs fixed in the GF fonts. It appears that GF cleaned-up some empty glyphs and other stuff, and regenerated the fonts.īecause the glyph count and character count are different than the fonts above. The fonts from Google Fonts (also v2.001, but created ~2 hours later) still have the overlaps.

So that is why the outlines look correct. The Cufon fonts (v2.001) appear to be the same as the static fonts in the source repository.

Open office fontforge font substitution ligature