Recommended package, `fonts-droid-fallback` is missing many common glyphs making it useless as a fallback font.

[Piyush Kancharlawar]

Ghostscripts dependency on fonts-droid-fallback is flawed since the newest version of the package is no longer suitable as a fallback font due to missing so many glyphs.

Context:

The ghostscript ubuntu package strips out the vendored file and adds a symlink that is compatible with the fonts-droid-fallback package. Likely because the font is large enough to have a convenient way of opting out, esp. since the font is already available via the fonts-droid-fallback pacakage. https://git.launchpad.net/ubuntu/+source/ghostscript/tree/debian/rules?h=ubuntu/focal-updates#n138

In 2014, as a way of saving space, the fallback font removed common glyphs https://android.googlesource.com/platform/frameworks/base/+/034b20c102ee2e7ec1da09e2b080f35be4a5cf54

At some point fonts-droid-fallback pulled in that upstream change, and now when you install ghostscript alongside fonts-droid-fallback, the fallback font is actually missing those characters.

Credit to <email address hidden> for figuring this out.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.