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.
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.
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.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.