https://bugzilla.redhat.com/show_bug.cgi?id=1820166
--- Comment #11 from Akira TAGOH <tagoh(a)redhat.com> ---
Sorry for late response, I missed the notification mail from bugzilla.
(In reply to Nicolas Mailhot from comment #10)
> So I'm wondering why you did push your packages only even
though you know you break it.
First, this change did not break any Fedora package or config. It broke one
*user* configuration.
As I said in the previous comment, this is irrelevant to users configuration.
this issue can be reproduced without custom configuration once you install both
google-droid-sans-fonts and google-noto-sans-cjk-*-fonts.
And second, I’ve been telling fontconfig upstream for years the
syntax in
fontconfig was not clean and robust enough for today’s needs (today as in
the today of 12 years ago, yes the reports have been going that long). At
one point, I bowed to your expertise and pushed stuff with the existing
syntax.
I'm sorry but I don't understand why you started to talk about the syntax
here...
We are talking about the issue we are facing *NOW* which is actually a
regression.
BTW I'm seeing another problem about font family unification. but it is
off-topic for this. I'll bring it up on the list shortly.
--
You are receiving this mail because:
You are on the CC list for the bug.