https://bugzilla.redhat.com/show_bug.cgi?id=1532523
--- Comment #11 from David Kaspar [Dee'Kej] dkaspar@redhat.com --- (In reply to Nicolas Mailhot from comment #9)
@Jens: we should pick the latest version of each component of Droid from all the various android trees. Google has always been terrible at publishing this font, they probably have a master version somewhere internal, we only see the bits they deem suitable and they vary from Android release to release depending on the other fonts in each release and the markets they wish to target (it may even be that some droid bits are only in specific vendor branches).
The font is very nice but locating its parts is a lot of work.
From what I've seen/deduced from looking at the git repository logs, the Google Droid is no longer used as primary fonts for CJK-based glyphs. From what I've been told, people hated those fonts.
Google is switching to different fonts in Android because of it. IIRC they are using Noto fonts for it as a replacement. IMHO it might make sense to start dropping support of Google Droid Fonts in favor of Google Noto, since Google Noto is still receiving updates...
For what I need from the fonts right now is just update of Google Droid Fallback font. It seems outdated (in regards of timestamps & sizes) compared to version that Ghostscript needs/is using.
If we can't get the update for the Droid Fallback, then I would have to bundle the same font in Ghostscript package (so it functions as we need), which would be also against Fedora Packaging Guidelines (I would like to avoid that).
NOTE: Ghostscript is using the Google Droid Fallback for displaying of CJK glyphs in case the CJK-based documents do not contain embedded fonts for the glyphs (or the necessary fonts are not installed on the system).