Inter: "Inter UI Bold" font problems in LibreOffice (Linux/Ubuntu 16.04.3, installed OTF version)

Created on 29 Dec 2017 · 8Comments · Source: rsms/inter

Hello, I would like to report a bug when installing the OTF version of Inter UI on my Linux Mint 18.3 (Ubuntu 16.04.3).

When I tested the font in LibreOffice Writer (a document processor software), the font names "Inter UI Bold" is separated from the bold weight of "Inter UI".

This means that the bold version of Inter UI is not selected when I type a bold text using the "Inter UI" font name. Here's a screenshot to describe the problem:

Font sample

bug

Source

reinhart1010

All 8 comments

Could you please try installing and testing LibreOffice with Noto Sans? https://www.google.com/get/noto/#sans-lgc

I suspect that there's a bug in LibreOffice that doesn't handle spaces in the family name of the font.

A font provides two important properties in its embedded metadata

family name ("Inter UI")
style ("Regular", "Italic", "Bold", "Bold Italic" ... etc)

Another possibility is that LibreOffice does a fragile hack where they instead use the "full name" property and try to parse its text content. There's currently a bug in the bold version of Inter UI for that field where "Bold" appears twice ("full name" = "Inter UI Bold Bold".) However, LibreOffice should really use the Family name and Style properties and show those to the user. If you find the issue, perhaps you could file a report with LibreOffice as well :)

I'll keep this issue open for now until we've figured this out.

rsms on 8 Jan 2018

Can you try this build (off of 4552fb970d17257ce043868e83eb78eed3134a33) and let me know if that fixes the issues for you @reinhart1010 ?

Inter-UI-2.3-4552fb970d.zip

rsms on 9 Jan 2018

Ping

rsms on 10 Jan 2018

Ok. I am currently not using the device where the bug is discovered; will check tomorrow.

reinhart1010 on 10 Jan 2018

👍1

That fixes the issue. Thanks.

reinhart1010 on 11 Jan 2018

👍1

You may want to file an issue with LibreOffice as they should display the family name and style properties of the font rather than perform brittle text parsing of the "full name" :–)

rsms on 14 Jan 2018

I didn't file this bug before with Aileron font.
After looking the font metadata in FontForge, it shown a conflict that the Family string differs between Windows and Mac (and I believe LibreOffice use the Windows one):