On Sat, Oct 31, 2026 at 03:30:29PM +0100, Matijs van Zuijlen wrote: > Package: fonts-materialdesignicons-legacy > Version: 5.9.55+6.9.96+dfsg-4 > Severity: normal > > With the latest version of fonts-materialdesignicons-legacy, on some web > pages, monospace text, typically in code blocks, only shows uppercase > and special characters.
Hi Matijs, Oh, that's not good. The big change I made that might have caused this is to remove the WOFF2 versions of the fonts from /usr/share/fonts, following lintian's report that they should not be in that directory: W: woff-font-in-wrong-dir N: N: This package contains a WOFF or WOFF2 font (Web Open Font Format) that is N: installed outside of /usr/share/fonts-fontname/woff/ or N: /usr/share/fonts-fontname/woff2/. N: N: WOFF and WOFF2 fonts must not be installed to /usr/share/fonts/ as this N: causes problems with fontconfig. N: N: Please refer to https://wiki.debian.org/Fonts/PackagingPolicy for details. N: N: Visibility: warning N: Show-Always: no N: Check: fonts But I put the WOFF2 fonts in /usr/share/fonts-materialdesignicons-webfont/fonts/ rather than /usr/share/fonts-materialdesignicons-webfont/woff2/- maybe that's my error? I've just uploaded a version -5 with this fix - does that solve the problem? > For example, the code on the following pages is broken: > > - > https://stackoverflow.com/questions/14894941/how-to-reset-css-fonts-cache/40311591 > - > https://github.com/publify/publify/pull/1340/changes/e9d70fd09fdade581efb59177f06478a93d67ca1 > > Whereas this page looks fine: > > - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1150394 I can't see the problem you're referring to on these pages - are you able to share a screenshot and point out where the problem is? Also, which version of Firefox are you using? > When I check the actual fonts used, in the broken examples, Firefox > states that it uses Liberation Mono and Material Design Icons version 6, > while in the working example, it says it just uses Liberation Mono. > > Since things were fine yesterday, I'm assuming this has something to do > with the fix for bug #1150394. Best wishes, Julian
