https://bugzilla.redhat.com/show_bug.cgi?id=1569943
--- Comment #2 from Nicolas Mailhot <[email protected]> --- Yes, that's not specific to liberation at all, that's old and well-known broken fontconfig/harfbuzz integration in Firefox, it does not properly invalidate its font cache when fonts are updated. You have to close it to force it to parse the new font file metadata otherwise it seems to try reading glyphs as their location in the old font file even though the new font file has them moved somewhere else (with metadata that correctly indicates where this somewhere else is). The bug should be reassigned -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ fonts-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
