There seems to be a bug in the font manager within the editor:
When I import a font from Google (I tried it with “Inter” and another one), the different font styles are created multiple times. In the media manager, sometimes only 4-5 uploaded fonts appear. When I reopen the editor, the font manager has lost the connection to the fonts.
When I look at the fonts in the “old” font manager (Bricks Settings), the text “The Fox jumps…” also contains only Unicode characters. If I delete the font styles there and re-upload them, everything is as it was in older Bricks-Versions when uploading fonts.
1 Like
Hi Louie,
Thanks so much for your report!
I can replicate the problem (with Inter) and have added it to the internal bug tracker. We will update this thread as soon as it is fixed.
Best regards,
timmse
1 Like
@timmse Is this a bug though? Each entry has a different unicode range, which means only the woff2 files that are actually needed to render the text are downloaded. Seems like a performance optimisation if anything.
I thought it was a bug. I used this feature. I saw a whole bunch of files and deleted them all. I uploaded them manually. It’s more peaceful that way.
Basically, it’s correct—but it can quickly lead to confusion (take a look at a font like Noto Sans JP). See this thread on Facebook for more some details:
I think it would be sufficient to display a note that it can get pretty “wild” depending on the font. However, what we definitely need to take care of is the “old” custom font manager… which is a mess, due to the unicode ranges 
By peaceful I assume you mean fewer files (one file per style/weight) but that isn’t as efficient and performant as a file per unicode range, since the browser will be downloading one large file instead of only the files that it needs to render the text on the page.
It would be useful though, if you could choose which ranges you need like “latin-ext” because right now there’s no easy way to tell what those ranges actually translate to in Bricks, Google Fonts or any of the font downloader services I found.
The only bug that I think I discovered in this area is that I was left with the “italic” version of the font files even after I’d deleted them from the font manager.
If Bricks supported variable fonts, there would potentially be fewer font files required depending on how many styles and weights you use.