Bug 2267629 - liberation-mono-fonts breaks default font for Hebrew
Summary: liberation-mono-fonts breaks default font for Hebrew
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: google-noto-fonts
Version: 42
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-04 08:51 UTC by Akira TAGOH
Modified: 2025-07-11 09:57 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-07-11 09:57:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-1131 0 None None None 2024-03-04 09:01:45 UTC

Description Akira TAGOH 2024-03-04 08:51:04 UTC
google-noto-sans-hebrew-vf-fonts is supposed to be a default monospace font for Hebrew though, liberation-mono-fonts is picked up as the default monospace font when it is installed.

This happens because liberation use 59 as the priority number although google-noto-sans-hebrew-vf-fonts use 66.

The priority number needs to be updated.

Reproducible: Always

Comment 1 Akira TAGOH 2024-03-08 10:03:33 UTC
We have two options to address this:

1) Add the generic alias rule for monospace in google-noto-sans-hebrew-vf-fonts. Though Noto Sans Hebrew is a sans-serif font.

2) Accept liberation-mono-fonts as a default monospace font for Hebrew

Comment 2 Akira TAGOH 2025-03-03 07:20:27 UTC
need some feedback about the above question. postponing to the future release so far. moving to 42.

Comment 3 Akira TAGOH 2025-07-11 09:57:47 UTC
This seems not happens now:

$ rpm -q liberation-mono-fonts google-noto-sans-hebrew-vf-fonts fontconfig
liberation-mono-fonts-2.1.5-13.fc42.noarch
google-noto-sans-hebrew-vf-fonts-20250701-1.fc43.noarch
fontconfig-2.17.0-2.fc43.x86_64
$ fc-match monospace:lang=he                 
NotoSansHebrew[wght].ttf: "Noto Sans Hebrew" "Light"


Note You need to log in before you can comment on or make changes to this bug.