https://bugzilla.redhat.com/show_bug.cgi?id=1820166
--- Comment #4 from Akira TAGOH <tagoh(a)redhat.com> ---
Why? Noto is effectively Droid v2. It is the same design, produced by
the same people, for the same use cases. There are some metric differences, but mostly, it
is an evolution of the same family. The only reason it is not called Droid still is that
Google realized the Droid naming was a mistake (for trademark reasons, and due to how they
contracted out Droid to Ascender in the first place).
If looking at Latin glyphs only, that may be true. that's not what I'm talking
about. my concern is about Droid blahblahblah unified as *Droid*. those had
never been considered to be worth changing default fonts for certain languages
despite that other Noto families did for some. if you don't want to drop those
lines, those poor quality fonts should be dropped from unified Droid. those
aren't worth a fallback font as *unified Noto*.
Is there an ETA for this? Droid has been unified in Fedora for a
decade+. Noto upstream formally requested Noto unification. I don’t see how you can argue
in this issue tracker, that unification is a challenge, while arguing in the fontconfig
issue tracker, that the existing fontconfig syntax needs no changes and serves font
deployment needs well.
On your efforts, new fonts packaging guidelines has taken effect. thank you for
that. all the fonts packagers are encouraged to follow on it in f33 IMHO.
probably good to have Change proposal for that? dunno.
Forgive me but this has been going on for 10+ years. The “at least
until it is done” card expired long ago. Do you have a more definite forward plan than
that?
It's for you right. but not for most of people, because there were no strong
reasons to do so and is really new in guidelines.
Anyway, this has been reported to *f32*. I don't think we had enough time to
work on it. seeing packages followed by new guidelines was really nice and is
really helpful to understand how we need to do. but having changes breaking
other packages and pushing it without taking care of them are not a good idea,
particularly for an upcoming stable release.
--
You are receiving this mail because:
You are on the CC list for the bug.