--- Comment #5 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
is a dead end evolution-wise.
Sure, you can continue using it, but it’s an orphaned no-upstream thing. So, at
some point, it will need switching out.
Also note that the coverage of the chromeos version, is less than the coverage
of the new upstream (granted, the github project is missing precomposed T WITH
CEDILLA; don’t know if this precomposition is a requirement in modern unicode).
And a lot of the other differences are trutype instructions missing in the
It looks like the ChromeOS version of the font files forked from an earlier
state of the project. Or, used the same design masters, but processed with
earlier 2013 font tools, a lot less complete than the ones available today.
Certainly, it seems to be missing a lot of things present in the github
(like all Google font projects the new project forgets to remove Regular from
fullname; that hints at using common tooling with all the other Google fonts;
given the extent of Google font nowadays, I’d expect the result to be
significantly more robust than whatever ChromeOS used in 2013).
You are receiving this mail because:
You are on the CC list for the bug.