https://bugzilla.redhat.com/show_bug.cgi?id=1902881
Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(nicolas.mailhot@l |
|aposte.net) |
--- Comment #15 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
Well that just shows the danger of not addressing problems in the fontconfig
core, expecting users to deploy more and more elaborate fixup rules to keep
things working. In the end the fixups take a life of their own.
2. is clearly not acceptable, that’s just upping on the breakage.
A clean 3. is
https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/200
Let me state once again than the more verbose and low level the syntax
fontconfig imposes on its users, the more likely such issues are to creep in.
It’s not a matter of writing a config generator. A good syntax lets users
express basic functional intent, and nothing more that can have side effects
for years.
I will revisit the dejavu rules to see if fullname matching can be removed. In
theory that should be possible, to many apps do not read fullname at all for it
to be mandatory. However IIRC it could not be done in the past due to various
bugs in the way fontconfig handled variable instance names.
Also, it will probably be stuck like the rest of the new font macros. No one
wanted to be involved in their merging when I had time to work on the subject
and fix bugs, and right now IRL issues mean I can’t look at it properly right
now.
--
You are receiving this mail because:
You are on the CC list for the bug.