The easiest method would be simply disabling the conflicting styles of the non-Apple version using FontBook. But as this is a Type 1 font, modern Adobe apps no longer support it, and Affinity apps are helpless in differentiating these fonts. Adobe apps might have been able to handle these conflicts without problems because they read those additional names to identify and group the fonts correctly. Many apps only read this information and accordingly would get confused font menus when enumerating available fonts. ![]() As you can see both fonts use identical family name and style group with identical sub style. If I try to install this font using Font Book, it warns about a duplicate being in process of installation. This illustrates a situation that you might have:Ī) Internal macOS version (part of TrueType collection):ī) Legacy Type 1 font, this one is from Adobe FontFolio 8 (which still can be installed on most recent macOS): Or consider changing to one of the many free or less expensive options available now. Being a much more modern font family it does not have the old numbered font naming issues, or the R/I/B/BI style groups naming issues. If you have something like TransType, you can rename the fonts to work properly (if you know what you are doing). The Std or Pro or WG1 versions have different family names which will not conflict with the macOS versions. One thing is for sure is you need to get rid of the broken non-macOS Helvetica fonts. They may appear to work and then you may have the wrong font(s) get embedded in a PDF. ![]() Same with Helvetica Neue LT Pro.īUT, both of those font families are configured with multiple R/I/B/BI style groups (2), and Affinity apps do not handle multiple R/I/B/BI style groups well. Helvetica Neue LT Std (which is easy to find as it is in the old Adobe Font Folio 11) has a different family name so there will be no name conflicts like you have now. Apple did this on purpose to prevent others from using their fonts. It may work in Apple applications and most of Adopey apps, but it will never work properly in Word, LibreOffice, and apps like Affinity. There are no "HelveticaNeue" (no space) official fonts. The versions you have were probably found thru a web search - and most of those are broken with name conflicts like this. I don't know what the original source is. Mine are a little bit mixed up between the two sets. It looks from your screenshot that your Apple and Adobe versions are in the same list but fortunately sorted out. The Font Book is probably good enough tool to do this task, as it allows just deactivating conflicting fonts without needing to uninstall them. If name editing is not an option, you could try if just removing the exactly conflicting fonts from the non-Apple family would make it possible to use all sub styles of these fonts, even if from mixed families. As mentioned, the problem is often app-specific, depending on whether an app uses multiple name fields to deduce how individual fonts should be grouped and identified. I do not think that it is possible to resolve the issue unless the family name of one of the conflicting font is changed and sub names thereafter rebuilt. on PostScript body (the first part of the name), name conflicts would happen and all kinds of issues related to this problem. PostScript name seems to be built based on Family name (spaces removed and style name appended by other parameters), it may be that at least certain fonts that have close to identical family names, end up having fully identical secondary names (like PostScript name). Yes, the both Helvetica Neue versions on your computer seem to have same or close to same family names (perhaps a space character is not enough to separate the names, unless the app can make a difference when enumerating the fonts).įont editors typically use the FamilyName as a base, and then other parameters to build several other names to create a unique set of font names to avoid name conflicts. I think the same thing will happen in that the Apple Version will display alongside the bought version. Of course I could delete my other source and buy a new set from Font Shop (£165). Font Book alerts that there are multiple copies. Both my sources appear in Publisher so maybe I just need to take more care selecting and then check fonts when packaging for output. I can't deactivate the Apple resident fonts so they have to appear. The source of the other typeface might be someone who I worked with who artwork a publication and then packaged the job so I could check it. I've left now and the laptop was taken back and the account closed. I used to work at a University where the Adobe license and typefaces were taken care of. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |