Fabian Greffrath <fabian@debian.org> writes: > Hi Vasudev, > > Am Samstag, den 10.10.2015, 20:29 +0530 schrieb Vasudev Kamath: >> Any one knows what really happened here?. I never followed >> development >> of Android fonts and now I'm confused by these changes. > > me neither. My only guess is that Droid fonts have been absorbed into > Noto fonts and Roboto fonts have been split out into a separate > independent project (as you already pointed out). This particular commit confirms that part!. ¹ Where many of droid fonts but might not be all are deleted. Here their fonts xml is updated to point to noto fonts for serif and sans family ² Here is commit which confirms removal of Roboto font due to new upstream ³ All the fonts like roboto noto are present at ⁴ with external/ ¹ https://android.googlesource.com/platform/frameworks/base/+/a08f0f8f453bb192dd0c4cd25a5aeb05986805fc ² https://android.googlesource.com/platform/frameworks/base/+/8c1f9360ce12e43cb18e1569b59f6b1674e9ea86%5E!/#F0 ³ https://android.googlesource.com/platform/frameworks/base/+/5a5f1429dec06ee392c194d2a4250b9455a2cf94 ⁴ https://android.googlesource.com/platform/ > > But this is really just based on hear-say, maybe other have a better > educated point of view. So now what is next plan. Here is what I think 1. Put a NEWS file mentioning that Droid fonts are now merged into Noto fonts and recommend it?. (Better than depending I hope). 2. Probably Noto fonts puts a Provides? I'm just suggesting so I would love suggestions from fellow developers here. 3. Drop fonts-roboto binary package and clearly mention about this in NEWS file. 4. Package Roboto from new upstream (but this needs lot of tools packaging) Cheers,
Attachment:
signature.asc
Description: PGP signature