FS#38036 - [ttf-droid] various issues with PKGBUILD and sources

Attached to Project: Community Packages
Opened by Pablo Lezaeta (Jristz) - Friday, 06 December 2013, 08:28 GMT
Last edited by Balló György (City-busz) - Wednesday, 24 January 2018, 05:24 GMT
Task Type Support Request
Category Packages
Status Closed
Assigned To Jelle van der Waa (jelly)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
Actually the PKGBUILD is pointing to the wrong upstream url [1]
And the fonts are taken from a tarball hosted in Arch server, but they have an upstream source [2], so I suggest fix the upstream url and take the fonts from upstream rather than package them in a tarball and download from Arch servers...

And apparently DroidFonts have a version different to a date....

Corrects URL:
[1] Upstream: http://www.droidfonts.com/
[2] Directory with the Droid font from upstream: https://github.com/android/platform_frameworks_base/tree/master/data/fonts
This task depends upon

Closed by  Balló György (City-busz)
Wednesday, 24 January 2018, 05:24 GMT
Reason for closing:  Not a bug
Comment by Daniel Micay (thestinger) - Monday, 28 April 2014, 22:26 GMT
I fixed the URL (not pushed as a new version yet), but not the sources. Is there really no proper stable release for these?
Comment by Pablo Lezaeta (Jristz) - Monday, 28 April 2014, 22:47 GMT
Look like they have a version of 1.03 until they drop using versions...
maybe unless the fonts change, the version is same as first android version with the cnaged font

but I personally prefer keep the actual version unless the font have some info build-in.
Comment by Jelle van der Waa (jelly) - Sunday, 17 August 2014, 11:30 GMT
There really isn't any sane source for these fonts (ofcourse), so I am not really feeling much for "fixing" the source=() to just become a list of long and cumbersome urls.
Comment by Pablo Lezaeta (Jristz) - Monday, 18 August 2014, 03:26 GMT
I thing the more uptodate source it the Android one I post, so I think is better use that.
As it the uptream project source and not a tarball that could be modiffied by the host for.
Comment by Jelle van der Waa (jelly) - Tuesday, 29 March 2016, 19:18 GMT
Seems the source might be here now https://github.com/google/fonts
Comment by Daniel Micay (thestinger) - Wednesday, 30 March 2016, 04:13 GMT
That's not the origin though, they just pull it in to that web fonts repository.
Comment by Samantha McVey (samcv) - Thursday, 09 June 2016, 19:15 GMT
From my looking https://github.com/google/fonts/tree/master/apache this appears to be a repository made by the actual Google Fonts team itself, and the droid fonts are not available in other repositories I can see. I am thinking this android source (https://android.googlesource.com/platform/frameworks/base.git/+/master/data/fonts/)is downstream from whatever the *ultimate* internal source of these files which could be google internal. The android source also doesn't contain all the droid language files either. What do you guys think?
Comment by Daniel Micay (thestinger) - Thursday, 09 June 2016, 22:15 GMT
The Droid fonts were deprecated in Android in favour of Roboto and Noto. It's not a good place to obtain the fonts.

It's likely that there isn't a proper internal source for these either, since it's really a dead project now.
Comment by Samantha McVey (samcv) - Thursday, 09 June 2016, 22:48 GMT
Yes exactly what I was saying, Android would not be a good place to find them. Checking again, there seems to be some language files not in this source:
https://github.com/google/fonts/tree/master/apache
The Hebrew Droid Sans files are missing and so are the fallback ones (not sure what these are). I ran fc-scan and compared the output on the DroidSans Monospace between our version and the one on the google github, and the github version actually had one language removed, whatever language "mo" is, not sure what this is, but in any case it does not seem there are any good places to obtain these fonts that are any "better" or "newer" than the tarball that we are hosting ourselves. Not sure what the resolution of this should be.
Comment by Pablo Lezaeta (Jristz) - Monday, 13 June 2016, 20:39 GMT
That deppend but this this point if both sources differ in a few files we can either add the ones that the other is missing to the finall package.

They has moved to roboto/noto so our option is just merge the work of both to bring the last shipped product or just drop droid to aur and package instead roboto/noto as a replacement with the apropiate provide fonts-family for chromium fonts needings.
Comment by Daniel Micay (thestinger) - Tuesday, 14 June 2016, 02:51 GMT
There's really no reason to worry about web pages. They'll already use @font-face to serve fonts to people without them for cases like the Droid fonts where many people will not (most Windows, OSX/iOS and Linux users).
Comment by Balló György (City-busz) - Wednesday, 24 January 2018, 05:23 GMT
The Droid Fonts were removed from the Google Fonts repository:
https://github.com/google/fonts/pull/1275

I'm closing this task as upstream is dead.

Loading...