As recently added to README at <https://github.com/googlei18n/noto-fonts>, Droid font has been absorbed into the Noto font, and "the Droid Sans Fallback font is superseded by Noto Sans CJK, available from noto-cjk."
The Noto fonts don't actually provide a direct replacement for DroidSansFallback. To get the equivalent involves using more than one, The best solution would be to use a TTC of the variants we want available, but that will mean quite a lot of work in our substitution code to support. As it is, DroidSansFallback works and is "fit for purpose", so marking this as "Enhancement" and maybe I'll get around to looking at it before Google's next change to direction on fonts......
Please read what I wrote - or actually quoted: Droid Sans Fallback is not superceded by the full Noto (super)family of fonts, but more narrowly by "Noto Sans Cjk" - which indeed is released as a Truetype Container (and in other forms as well).
(In reply to Jonas Smedegaard from comment #2) > Please read what I wrote - or actually quoted: Droid Sans Fallback is not > superceded by the full Noto (super)family of fonts, but more narrowly by > "Noto Sans Cjk" - which indeed is released as a Truetype Container (and in > other forms as well). DroidSansFallback is NOT superceded by Noto Sans Cjk, for our purposes at least. There are MANY glyphs present in DroidSansFallbackFull that are NOT in NotoSansCJK (arabic glyphs for example). To move to an "equivalent" fallback solution using the Noto fonts we'd need to have several fallback fonts (either separately or as a TTC). We are not doing that in the short term.