Bug? Font Limitation in Rhino?

Hi,
I’m trying to use OpenType fonts in Rhino, but it seems like Rhino doesn’t recognize font families properly. Is that expected behavior?

I’m working with a corporate font and need access to different styles beyond just Regular and Bold (such as Light, Medium, etc.).
Is there a way to use these additional font styles in Rhino?

Thanks in advance for any help!
Best,
Pip

SystemInfo.txt (5.0 KB)


Hi Pip -

No, not necessarily. Please post or upload the font so that we can take a look.
-wim

Hi Wim,

Thanks for taking a look at it.

Unfortunately, I can’t share a commercially licensed font family with 14 cuts.

However, the issue also appears with some classic, freely licensed Google Fonts.
Fonts.zip (791.7 KB)

It seems I’m not the only one experiencing this:

I don’t necessarily wish to implement variable fonts, which are the latest technology in fonts. Even though it would be good in the long term to be up to date on this.
What would be great would be to be able to just use standard Opentype font families. For the moment, it doesn’t seem possible to use them. Only a regular weight.

The Bold and Italic buttons aren’t truly meaningful from a type design perspective, as fonts are individually drawn in specific weights and styles.

Thanks,
Pip

1 Like

that is a known but wildly ignored ghosted issue since v6 with the same developer coming forth and claiming its not repeatable even when given numerous easy to follow steps to which he never responded to again. this issue is not just open type its many known font types across the board.

this is a serious bug that breaks ones leg entirely in some instances and it goes beyond anything i can grasp or imagine why this is not getting any progressive attention what so ever. after pro actively battling for it for years i manged to get a tiny picture that indicates that it is in fact a known issue but no official wholesome statement was ever admitted,

i can collect some links for you where this was discussed later i am not on my computer right now.

so, here a link to one of the oldest topics regarding this issue, the topic alone is already 5 years and still has not been acknowledged, the bug is in there quite a bit longer i guess.