https://bugzilla.redhat.com/show_bug.cgi?id=1823984
--- Comment #9 from Nicolas Mailhot ---
qt is probably confused by all the broken metadata in Cantarell
$ fc-scan -f
"%{family};%{style};%{fullname[0]};%{width};%{weight};%{slant};%{fontversion};%{file}\n"
/usr/share/fonts/cantarell | sort -
https://bugzilla.redhat.com/show_bug.cgi?id=1823984
--- Comment #10 from Nikolaus Waxweiler ---
I don't understand your metadata criticism. The "Cantarell Extra Bold Regular"
thing is a concatenation of name id 1 and 2 and the spec recommends that you
pretend to be a RIBBI font in them. It make
https://bugzilla.redhat.com/show_bug.cgi?id=1823984
--- Comment #11 from Nicolas Mailhot ---
The OpenType spec states, when defining fullname (Name ID 4)
https://docs.microsoft.com/en-us/typography/opentype/spec/name#nid4
> name ID 4 would typically be a combination of name IDs 16 and 17
You’
https://bugzilla.redhat.com/show_bug.cgi?id=1823984
--- Comment #12 from Nicolas Mailhot ---
See also
https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/185
https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/208
https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues
https://bugzilla.redhat.com/show_bug.cgi?id=1823984
--- Comment #13 from Nikolaus Waxweiler ---
Regarding ID 4, the spec uses wording like "would generally be omitted" and
"would typically be a combination of name IDs 16 and 17", so "non-conformance"
sounds like hyperbole to me.
I don't know i
https://bugzilla.redhat.com/show_bug.cgi?id=1823984
--- Comment #14 from Nicolas Mailhot ---
The OpenType spec is quite hard to read because its authors do not use
IETF-style unambiguous MUST SHOULD etc but plain human text (sometimes,
repeating the same point multiple times with various levels
https://bugzilla.redhat.com/show_bug.cgi?id=1823525
--- Comment #2 from Charalampos Stratakis ---
Thank you!
--
You are receiving this mail because:
You are on the CC list for the bug.
___
fonts-bugs mailing list -- fonts-bugs@lists.fedoraproject.o
https://bugzilla.redhat.com/show_bug.cgi?id=1823984
--- Comment #15 from Nikolaus Waxweiler ---
I agree that a better written specification would be highly appreciated, but I
think you're fighting a losing battle here. OpenType is 40 years of accumulated
cruft and vendors and applications doing
https://bugzilla.redhat.com/show_bug.cgi?id=1823637
--- Comment #3 from Akira TAGOH ---
Think of 3) as a solution/workaround for SB specific, we could assume that
caches having 0 timestamp is always the latest because updates of all the
files under /usr won't appear without reboot on SB and /u
