Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Jun 2019 21:48:25 +0000
From:      bugzilla-noreply@freebsd.org
To:        gecko@FreeBSD.org
Subject:   [Bug 238482] www/firefox: 67.0_3,1 print pre-formatting is HORRIBLE
Message-ID:  <bug-238482-21738-jh5zIiiqRs@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=3D238482

Ronald F. Guilmette <rfg-freebsd@tristatelogic.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Closed                      |Open
         Resolution|Works As Intended           |---

--- Comment #9 from Ronald F. Guilmette <rfg-freebsd@tristatelogic.com> ---
Why was this PR closed?  It is in no sense "fixed" and the print output sti=
ll
looks utterly awful as I have demonstrated, and as Jan Beich explicitly
confirmed by saying that bitmap fonts look bad except at low resolutions.

"Works as intended" ???

It is the maintainer's explicit and deliberate intention that print output =
from
Firefox should, by default, look like garbage??

Furthermore, I have done as suggested and run commands to determine various
things about the fonts on my system.  (See new attachement.)  There are no
fewer than 895 different possible font files listed in the output from "fc-=
list
:scalable=3Dfalse".  How am I supposed to know which ones I need to make pr=
int
output from Firefox look reasonable?

Apparently, Jan Beich knows how to get this working right, as he demonstrat=
ed
when he posted the following attachment to this PR:

https://bz-attachments.freebsd.org/attachment.cgi?id=3D204975

In that case the print preview looks excellent.

Now, if Jan Beich, or anyone else, can tell me how to make MY system produce
such excellent print output from Firefox, then I will at least be able to
work-around this self-evident bug for the time being.


As Jan Beich himself noted, it is not just me who has reported this
self-evident bug, so this isn't just one lone person who has made mention of
this issue:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225744

--=20
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238482-21738-jh5zIiiqRs>