Date: Sat, 15 Jun 2019 04:22:24 +0000
From: bugzilla-noreply@freebsd.org
To: gecko@FreeBSD.org
Subject: [Bug 238482] x11-fonts/fontconfig: Firefox print pre-formatting is HORRIBLE ("bitmap font by default")
Message-ID: <bug-238482-21738-vrxs6vmFHk@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-238482-21738@https.bugs.freebsd.org/bugzilla/>
References: <bug-238482-21738@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=238482 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|www/firefox: 67.0_3,1 print |x11-fonts/fontconfig: |pre-formatting is HORRIBLE |Firefox print | |pre-formatting is HORRIBLE | |("bitmap font by default") Flags|maintainer-feedback+ |maintainer-feedback?(gnome@ | |FreeBSD.org) CC| |gnome@FreeBSD.org --- Comment #14 from Kubilay Kocak <koobs@FreeBSD.org> --- Analysis of actual underlying issues: - Unclear to users that program font rendering relies on fontconfig - Unclear to users what their options are for customising font rendering for their needs - Bitmap fonts or not by default, affects different user classes for different cases (see bug 225744) - To at least me: Unclear whether application specific font rendering defaults is possible currently, or possible at all The primary question we should be asking (on behalf of our users), is: In what ways can we improve their out of the box, and/or customisation, and/or initial learning experience for font rendering, considering that 'one size does not fit all' nature of font selection and program requirement diversity, with particular consideration given to ways to improve the port/package, if possible -- 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-238482-21738-vrxs6vmFHk>