nerd-fonts
nerd-fonts copied to clipboard
JetBrainsMono Nerd Font on macOS caueses "multiple copies of this font are installed" warning
π― Subject of the issue
I installed the JetBrainsMono Nerd Font on my macOS machine by (1) installing JetBrainsMono.zip manually and (2) running brew install font-jetbrains-mono-nerd-font
.
Please note that I removed all the font files installed by step (1) before I continued with step (2).
In both cases, I get various "multiple copies of this font are installed" warnings in Font Book.
π§ Your Setup
- JetBrainsMono Nerd Font (see above)
- iterm2 Build 3.4.1
- macOS Catalina 10.15.7 (19H2)
β Optional
![Screen Shot 2020-11-20 at 20 34 50](https://user-images.githubusercontent.com/954561/99842586-65d93f80-2b70-11eb-8d56-46031845095c.png)
I'm also seeing this. Comparing the 3 fonts that are duplicated, the only collision that seems to make sense is that the "Postscript Name" is identical for the 3 fonts I've installed.
I'm seeing the same behavior with the 3 Italic fonts in the Mono versions.
Edit: I'm not sure how to fix this yet but I do plan to investigate and see if I can figure out how to manually rename the fonts (or ideally submit a PR for the patcher)
I was able to:
- Remove the "duplicate" copies of the font, leaving regular Italic installed
- ExtraBold Italic
- Medium Italic
- Download FontForge and open the 2 "duplicate" copies
- Modify the Font Name (Element -> Font Info in FontForge)
- I changed the fonts to MItalic (for Medium) and EBItalic (for Extra Bold) to differentiate the names
- I ignored this error (on macos) but it might be nice to "shorten" the names so they comply
- I retained the Unique ID when prompted (guessing this will prevent duplicates if I reinstall again
- Regenerate the fonts with File -> Generate Fonts
- Changed the type to True Type
- Ignored the warning about Em-Size (chose Yes)
- Ignored the errors warning (chose Generate)
- Installed my new fonts
So far everything looks OK but I need to do some more testing with the fonts. I think it would be better to fix the patcher, or for windows compatibility maybe choose a shorter name (JB instead of JetBrains?). I'm assuming ExtraBold and Medium got dropped to meet the 31 character naming warning.
@martinburger @jaydorsey This is not just a warning! Terminal emulator applications WezTerm are not able to recognize all the NERD fonts like the regular italic version of jetbrain mono you mention. I suspect it has to do something with this... Here's a workaround I did, it works well now...
I'm having the same problem with BlexMono. Font Book thinks the ExtraLight Italic, Italic, Light Italic, Medium Italic, Text Italic, Thin Italic, and SemiBold Italic faces are duplicates. Alacritty can recognise Italic, but it looks like none of the other faces are usable.
The Blex Mono font seems to have the same problem.
--- /tmp/original-list 2021-05-14 09:50:17.000000000 -0400
+++ /tmp/after-automatically-removal-by-font-book 2021-05-14 09:49:51.000000000 -0400
@@ -1,18 +1,12 @@
Blex Mono Bold Italic Nerd Font Complete.ttf
Blex Mono Bold Nerd Font Complete.ttf
-Blex Mono ExtraLight Italic Nerd Font Complete.ttf
Blex Mono ExtraLight Nerd Font Complete.ttf
Blex Mono Italic Nerd Font Complete.ttf
-Blex Mono Light Italic Nerd Font Complete.ttf
Blex Mono Light Nerd Font Complete.ttf
-Blex Mono Medium Italic Nerd Font Complete.ttf
Blex Mono Medium Nerd Font Complete.ttf
Blex Mono Nerd Font Complete.ttf
-Blex Mono SemiBold Italic Nerd Font Complete.ttf
Blex Mono SemiBold Nerd Font Complete.ttf
-Blex Mono Text Italic Nerd Font Complete.ttf
Blex Mono Text Nerd Font Complete.ttf
-Blex Mono Thin Italic Nerd Font Complete.ttf
Blex Mono Thin Nerd Font Complete.ttf
Same issue here with JetBrains
Same issue with Jetbrains, what's the best way to resolve?
The problem is the Family und SubFamily naming that is too simple to handle whole sets of fonts.
Would be fixed by #717.
Same issue with Hasklug:
Still seeing the issue with Blex Mono
In both cases, I get various "multiple copies of this font are installed" warnings in Font Book.
Version 2.2.2 seems to have this fixed. Thx!
Version 2.2.2 seems to have this fixed. Thx!
Great to hear that! Thanks for the feedback :green_heart: Normally ppl just complain and never say when something works ;-)
Aforementioned fix by #717 has been pulled indirectly by #723, but it is not active for any font but Caskaydia
.
You can utilize it when self patching with --makegroups
. That option will end up finally in the src/unpatched-fonts/*/config.cfg
files where appropriate.
Maybe the fix has been this PR less last minute commit: font-patcher: Correct Family for Mono Windows
Actually I'm astonished that the issue is gone :grinning:
The change with the families is planned for 3.0.0
, because it is kind of 'breaking' when names change.
Before that an update all the things version 2.3.0
.
2.2.0
was about fixing 'simple' stuff mainly.
VictorMono
has the same issue.
Iosevka
seems to have the same issue
Is one of you able/willing to try a VictorMono / Iosevka / ? font set (i.e. parallel installation of all of them that we have in the release zip), and try if they work as expected? I could generate the zips just for you to try, so maybe we can enable it then for v2.3.0.
Until now its only me who tested it (I assume), and then only on Linux :grimacing: But theoretically it must fix it ;-)
Reopening this, removing the font specific reference in the title, to collect more complains.
Is one of you able/willing to try a VictorMono / Iosevka / ? font set (i.e. parallel installation of all of them that we have in the release zip), and try if they work as expected? I could generate the zips just for you to try, so maybe we can enable it then for v2.3.0.
Until now its only me who tested it (I assume), and then only on Linux π¬ But theoretically it must fix it ;-)
Happy to test, but not sure what I have to do π Do you want me to test the v2.3.0-RC? Or you want to provide us a new zip?
Or you want to provide us a new zip?
I will generate a new Iosevka.zip for you tomorrow. :-)
Or you want to provide us a new zip?
I will generate a new Iosevka.zip for you tomorrow. :-)
@Finii Where can I find the zip file?
@noefroidevaux :exploding_head: Sorry forgotten. I build it right away, hold tight...
Edit:
It's running now, this will take an hour or so...
@noefroidevaux You can find the newly patched Iosevka here: https://github.com/ryanoasis/nerd-fonts/releases/download/v2.3.0-RC/Iosevka_makegroups.zip
The naming scheme changed with --makegroups
a bit.
Please remove all patched Iosevkas before installing from the new zip
.
@Finii Thank you! I removed the old font and installed the new one. And it seems all ok for me ππ
![image](https://user-images.githubusercontent.com/37739/199233732-d93ee164-a74c-45d1-b3f3-80405ff7d879.png)
![image](https://user-images.githubusercontent.com/37739/199233780-ec24dc39-3ffd-4859-b50f-4380aeeff6ec.png)
Great to hear! Thanks for testing!
Do you have this font book thingy? And it issues no warnings anymore?
@Finii I use the Font Book from macOS. But I'm on macOS Ventura (13, released last week). I don't see the warning with the old version of the font but, as you can see in the following screenshot, there was some problem (duplicates, some styles not activated) π
![image](https://user-images.githubusercontent.com/37739/199251061-b571d19b-22ef-4a22-9310-204e43e1d5a6.png)
Maybe someone who is always on macOS Monterey (12) can test? /cc @unikitty37 @PaulDoesDev @sizur
No joy when I install them all, I'm afraid⦠(This is on macOS 12.6 (21G115). I didn't have any version of Iosevka installed before.)
Removing the NF versions fixes the issue and removes the messages for the Nerd Font versions; I'm not sure what the two versions are, as no filenames have NF in them. Is that the Windows ones? If so, are they even supposed to be installed together? (It might be a better idea to have Windows and Not-Windows folders to stop people installing both at once, if soβ¦)
@unikitty37 Yes, I forgot to say that I only installed those that don't have "Windows Compatible" in the file name. Otherwise I also have the "NF" versions. /cc @Finii
Ah, in that case, it's fixed. But it's definitely a pain to pick them out in an alphabetical list:
Well, I would drop the Windows Compatible
fonts completely, they are only needed for e.g. IE9 or some old MS-Word-for-Mac (!!!). (see #891)
They should have different names, ... I will check that.
Thank you for testing :tada:
Edit: Add link to discussion
Thank you for testing π
Thank you to you!!!