Date: Tue, 16 Jan 2024 04:09:17 +0000 From: bugzilla-noreply@freebsd.org To: desktop@FreeBSD.org Subject: [Bug 275758] x11-fonts/noto-basic and x11-fonts/fontconfig together enable ligatures in "monospace" font Message-ID: <bug-275758-39348-CzKAaH2qkJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275758-39348@https.bugs.freebsd.org/bugzilla/> References: <bug-275758-39348@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275758 --- Comment #7 from Stephen Hurd <shurd@FreeBSD.org> --- I care! But it really is the font itself at fault. It's saying "If you're displayi= ng these characters together, display them like this instead". Fontconfig is simply doing exactly what the font is telling it to. We can configure fontconfig to override what the font says, but a monospaced font should be monospaced in all cases, it should not be monospaced except = when 'f' is followed by a letter that looks better with different kerning when proportionally spaced. A "clever" program can just render each character separately, instead of rendering sequences. This usually makes things look worse, but in this cas= e, it "fixes" the problem. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275758-39348-CzKAaH2qkJ>