Christoph Moench-Tegeder writes:
> ## Andrea Venturoli (m...@netfence.it):
>
>> > Uh, define "illegible crap". Wrong glyphs? Bad rendering (blocky pixels,
>> > blurry?)?
>> More "something blocky, vaguely, *really* vaguely, resembling the
>> indended text": something you can read only if you alre
## Andrea Venturoli (m...@netfence.it):
> > Uh, define "illegible crap". Wrong glyphs? Bad rendering (blocky pixels,
> > blurry?)?
> More "something blocky, vaguely, *really* vaguely, resembling the
> indended text": something you can read only if you already know what
> it says.
That sounds fami
On 3/17/19 7:03 PM, Christoph Moench-Tegeder wrote:
Uh, define "illegible crap". Wrong glyphs? Bad rendering (blocky pixels,
blurry?)?
More "something blocky, vaguely, *really* vaguely, resembling the
indended text": something you can read only if you already know what it
says.
My bookm
## Andrea Venturoli (m...@netfence.it):
> Whenever I try printing from FireFox (mainly to PDF virtual printer, but
> also on paper), I get wrong headers fonts.
That sounds like fontconfig.
> I.e. most of the page gets printed properly, but [sub]titles (or any
> bigger text) are just illegible
On 3/13/19 12:47 PM, Robert Huff wrote:
Andrea Venturoli writes:
Sorry if my question is vague, but I'm lost at where to start looking.
May I suggest "gecko@", which I believe to be the list for
Mozilla-based ports?
Referentially,
Andrea Venturoli writes:
> Sorry if my question is vague, but I'm lost at where to start looking.
May I suggest "gecko@", which I believe to be the list for
Mozilla-based ports?
Referentially,
Robert Huff
___
Hello.
Whenever I try printing from FireFox (mainly to PDF virtual printer, but
also on paper), I get wrong headers fonts.
I.e. most of the page gets printed properly, but [sub]titles (or any
bigger text) are just illegible crap.
Of course I see the page correctly on screen, before printing.
