search

MonoLisaFont / feedback

Send us your feedback regarding the MonoLisa font
84 stars 2 forks source link

[Bug]: Variable black regular font name error #227

Closed xqdoo00o closed 8 months ago

xqdoo00o commented 10 months ago

Edition

Complete (Pro)

What version are you using?

2.010

What type of weights are you using?

Variable (customized)

Operating system

Windows 10 21H1

Program

VSCode

Display resolution

1920*1080

What happened?

Open folder C:\Windows\Fonts, check the MonoLisa Variable font, found that there are two MonoLisa Variable Regular, missing the MonoLisa Variable Black. image

And after check the static MonoLisa font, there is no such error.

okonet commented 10 months ago

I’m not entirely sure how you arrived at this state since variable font shouldn’t have separate weights exposed. Have you downloaded the variable version or static one on the customization form?

xqdoo00o commented 10 months ago

I’m not entirely sure how you arrived at this state since variable font shouldn’t have separate weights exposed. Have you downloaded the variable version or static one on the customization form?

Just open folder C:\Windows\Fonts, double click monolisa variable font the same result, two variable regular, static font no such error. image

xqdoo00o commented 10 months ago

Looks like version 2.009 has no such error, so 2.010 cause this error

bebraw commented 10 months ago

There was a name table related change in 2.010 (some Glyphs update) that may have caused this. Interestingly enough it's not visible on MacOS as all of the variable instances are visible there. It might be something specific to Windows.

mekkablue commented 9 months ago

I don’t understand. What exactly is the issue? Is the Black weight not showing up in the font menu? In which app? Does it persist after uninstalling, cleaning the caches, restarting, and reinstalling?

That the Windows 10 file system interface struggles with variable fonts, may be cosmetic or a caching issue. Most of the other weights are misrepresented as well in the screenshot.

Some Windows apps are known to exclusively use the info in the STAT table to build the menu, so the Regular may show up twice (once for its representation on the axes, once for style linking).

mekkablue commented 9 months ago

Hold on, after some digging, I indeed found a bug. Working on a fix.

MarcusSterz commented 9 months ago

This problem should solved with the upcoming version 2.011 – stay tuned!

bebraw commented 9 months ago

There's an initial prerelease available now. Could you download the prerelease version and check? Note that you have to select the following at the download to get it.

Screenshot 2023-10-04 at 15 07 13

To verify you have the right version, it should register itself as 2.011 on your system (visible through a font metadata viewer).

xqdoo00o commented 9 months ago

There's an initial prerelease available now. Could you download the prerelease version and check? Note that you have to select the following at the download to get it.

Screenshot 2023-10-04 at 15 07 13

To verify you have the right version, it should register itself as 2.011 on your system (visible through a font metadata viewer).

It's now shows fine using prerelease version

bebraw commented 8 months ago

Included to newly released 2.011.