Issues with Iowan Old Style Font (purchased version)

All Macs used to include the Iowan Old Style font family. This font has now been deprecated and is only in the support folders, where old documents can use the font, but not new ones. Even then, support for this feature is spotty as not all programs even allow it when opening older documents. Regardless, I love this font and now have HUNDREDS of files that rely on it to display properly. (Music engraving)


Knowing that this font will no longer be offered for free on Macs, I went to the type foundry (ParaType) and purchased a new, full license for the entire font family, under my own name.


The old bundled Mac version was .ttf, the new version which I purchased from the foundry is .otf and was updated in 2017. Regardless, I cannot get programs to show me the new font that I PURCHASED because of some settings buried in MacOS. There's some .plist or xml file that is preventing me from using my font, because the computer thinks it's the same as the deprecated version that is no longer bundled with macOS.


How do I prevent this from happening and gain access to my font? I just paid $120 for a font that my computer will not let me use(!), and I'm not a happy camper. Any help would be much appreciated.

Posted on Jan 17, 2024 10:53 AM

Reply
Question marked as Top-ranking reply

Posted on Jan 17, 2024 11:32 AM

The OS can't display it because your purchased font conflicts with the OS installed copy. Or said another way, it has the same internal names, so the OS hides it the same way it does the included copy.


Despite the fact you can't see the OS copy listed in your apps, that doesn't mean it isn't active. They're all active, but those not meant for your region or language are hidden. Some apps purposely ignore this division, like all of the Adobe apps, the SoftMaker Office suite and Master PDF Editor. But most have incorporated Apple's API to hide the same fonts the OS and Apple's supplied apps do. Such as the Affinity suite.


You cannot remove or disable the OS installed version. Your only option is to change the internal names of the font you purchased. But doing that would likely fall under a copyright violation (modifying the font without permission).


Here's what you'd be looking for. This shot is from FontLab 8. While this is the Roman (normal) font in the OS supplied copy, it's pretty much a given your purchased copy has the same internal names.



There are seven faces in the set, so they'd all have to be changed.


One way would be to use the free, open source font editor, FontForge. But again, you'd very likely be running afoul of copyright law. Better would be to contact the owner of the font and see if they'd be willing to send you an updated version with new internal names.

5 replies
Question marked as Top-ranking reply

Jan 17, 2024 11:32 AM in response to Romanos401

The OS can't display it because your purchased font conflicts with the OS installed copy. Or said another way, it has the same internal names, so the OS hides it the same way it does the included copy.


Despite the fact you can't see the OS copy listed in your apps, that doesn't mean it isn't active. They're all active, but those not meant for your region or language are hidden. Some apps purposely ignore this division, like all of the Adobe apps, the SoftMaker Office suite and Master PDF Editor. But most have incorporated Apple's API to hide the same fonts the OS and Apple's supplied apps do. Such as the Affinity suite.


You cannot remove or disable the OS installed version. Your only option is to change the internal names of the font you purchased. But doing that would likely fall under a copyright violation (modifying the font without permission).


Here's what you'd be looking for. This shot is from FontLab 8. While this is the Roman (normal) font in the OS supplied copy, it's pretty much a given your purchased copy has the same internal names.



There are seven faces in the set, so they'd all have to be changed.


One way would be to use the free, open source font editor, FontForge. But again, you'd very likely be running afoul of copyright law. Better would be to contact the owner of the font and see if they'd be willing to send you an updated version with new internal names.

Jan 17, 2024 12:07 PM in response to Romanos401

I'm just surprised the system cannot tell the difference between font files that were installed at a later date.

Font type or age has no bearing on what the system sees. It's all, and only, based on the internal names. You can have an old Type 1 PostScript font, and a brand new OpenType font that was given the same internal names as the T1 PS font, and you'll have the exact same problem.

Jan 17, 2024 11:52 AM in response to Romanos401

While I get the idea behind Apple's decision (this started back in El Capitan), it's also as major disruption for advertising agencies and publishing. You can't get at fonts you need to work on a project, and now since Ventura, you can't even disable conflicting fonts installed with the OS.


I'd guess it's the entire reason Adobe won't implement the API. You see all of the OS fonts in their lists. Including ones you'd rather not have to constantly scroll past, like the 100+ Noto Sans fonts.

Jan 17, 2024 11:41 AM in response to Kurt Lang

Thank you for your help. I have messaged the type foundry to ask how I should proceed.


I suspected what you mentioned was indeed the culprit, and I presumed (incorrectly, apparently) that the commercial version would have come with separate IDs so this wouldn't happen. I would have thought that by now they would be aware of the issue, as it's been about 2 years now that this font has been hidden.

Jan 17, 2024 12:01 PM in response to Kurt Lang

yea... it's been a real pain.


In the case of the current font, I think it was axed because the typeface designer who updated the font with Cyrillic characters is Russia based, and I suspect there was a little bit of subtle liberal grandstanding going on.


I'm just surprised the system cannot tell the difference between font files that were installed at a later date. It would be one thing if I was just dragging font files from one folder to another, but the files I installed earlier had different metadata markers. You'd think that would be sufficient.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Issues with Iowan Old Style Font (purchased version)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.