Jump to content
You must now use your email address to sign in [click for more info] ×


  • Posts

  • Joined

  • Last visited

Profile Information

  • Location

Recent Profile Visitors

998 profile views
  1. Is there a way to change or replace a created contour and fill style for all instances after it has been applied to many objects?
  2. Yes, thank you for pointing that out. I am aware of this. If a Type1 font is displayed and usable by Affinity, I expect full support, not half support (see kerning).
  3. Hello Sean, Oh yes, the font has been damaged in the ZIP archive. Probably because old Mac Type1 fonts usually don't have a suffix but a resource and data fork. I have therefore packed the FontSuitcase type FFIL and the associated outline printer fonts type LWFN into a DMG image. Good luck with testing. UniversBQ.dmg
  4. The key for me is whether Serif is willing to address this problem. Otherwise, the APu is not an option for me. I would like an answer from the developers. Is it possible to contact them directly?
  5. Under Mac OS Mojave with Adobe CS6, PS Type1 kerning still works perfectly. I have avoided later versions because of the subscription. With QuarkXpress it works perfectly up to the current version 2020. As already described by Old Bruce Adobe wants to discontinue support from 2021 to 2023.
  6. Thank you for your detailed answer. The "No Kerning" problem certainly exists with all Type1 fonts in Mac OS. I use Mojave and the fonts are in the user folder. The behaviour in AP on Windows doesn't seem to be correct either, as your example with the AV and VA pairs shows. With Fontexproler you can see the kerning of the pairs. These are identical with -95 units, see screenshots. I share your assessment of the product philosophy of the Affinity apps and would welcome it for the older generation of users and switchers if better Type 1 support were realised.
  7. I would like to have this statement directly from the Serif developers. I still have a large Type1 font library for print and upgrading to Opentyp would cost many times more than a publishing program. When Adobe dupes its customers, Serif doesn't have to follow suit. It is also not to understand that Typ1 is half supported.
  8. I have a similar problem with old original Mac Postscript Type1 fonts. The problem: glyph pairs like "To" lose automatic kerning in AP. These font metrics are usually stored in the Mac Font Suitcase file "FFIL" and not in the printer fonts "LWFN". It seems that AP ignores these font metrics. If this were so - an embarrassing programming error for a publishing tool! Attached is a screenshot. Above the Postscript Type1 fonts and below the same as OpenTyp Font.
  9. Hi Sean, try the glyph pairs "LT" of the UniversBQ Mac PostScript (Type1) font. As an example for the correct metric kerning, I made a screenshot of FontExplorer X Pro and have attached it too. best explore! Jens UniversBQ.zip
  10. Publisher has problems using the integrated kerning pairs of Postscript Type1 fonts. It ignores them! I noticed this with extreme pairs like LT. In new OpenType fonts this works correctly. Not so with Postscript Type1 – no matter if the AFM files or only the font suitcases are included.
  11. As an old FreeHand User I miss an input field for the origin of a transformation and one for the number of copies too for a value input. Greetings from bielefeld, Germany
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.