Bug 2143869

Summary: dropping the dependency on google-droid-sans-fonts?
Product: [Fedora] Fedora Reporter: Jens Petersen <petersen>
Component: ghostscriptAssignee: Richard Lescak <rlescak>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: akhaitovich, mjg, mosvald, rlescak, zdohnal
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jens Petersen 2022-11-18 06:58:37 UTC
Description of problem:
libgs pulls in google-droid-sans-fonts (and also urw-base35-fonts).
I think it uses Droid Fallback as a fallback font.

Actually the Droid fonts are causing various problems via fontconfig
for other fonts in Fedora, so I am wondering if it is possible to consider
dropping the dependency on Droid or at least making a weak dependency?

If dropping is possible then the Droid fonts would no longer be installed
by default in Fedora Workstation.

Additional info:
Here is the list of open droid bugs in Fedora for reference:
https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&component=google-droid-fonts&list_id=13007869&product=Fedora

Ideally it would be nice to also not pull in urw-base35-fonts in libgs.

Actually ghostscript somehow treat this fonts are application fonts rather
than system fonts, then they would no longer interfere with selecting other
system fonts and that would solve the problem equally.

Droid is an old font by now: we are mostly using Noto for our core fonts today.

Comment 1 Jens Petersen 2022-11-18 07:05:18 UTC
Another simpler thing that could help maybe would be to subpackage DroidSansFallback.ttf
and then if it didn't have any font .conf, maybe that would be okay
and not interfere with other applications.

Comment 2 Michael J Gruber 2022-11-18 09:11:20 UTC
What is the problem with urw-base35-fonts?
Any compliant postscript renderer needs to "have" the standard ps fonts, one way or the other. If there are problems with their fontconfig then we should solve those.

As for droid: If that is still upstream's choice of fallback we'd have to work with upstream, or - again - fix any fontconfig (or harfbuzz) related problems. Alternatively, package the font just for the application, which is not exactly what we are supposed to do - other applications might have to do that, too.

Comment 3 Ben Cotton 2023-02-07 14:59:16 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.