Re: [PATCH] build with t1lib for type3 support

[Vincent Noel <vincent noel gmail com>]

Actually this PDF renders fine for me, see
http://members.cox.net/vnoel/screenshots/Screenshot-Andantino.png
Or am I missing rendering artefacts somewhere ?
I'm confused, because I, just like you, thought that evince did not
render Type 3 fonts correctly. However, it looks like it does. Which
is good, but surprising.
Any confirmation by some wise coder ?
Cheers
Vincent

On Wed, 16 Feb 2005 14:02:02 -0500, Jeff Muizelaar <jrmuizel nit ca> wrote:
> On Wed, Feb 16, 2005 at 01:10:12PM -0500, Vincent Noel wrote:
> > Which PDF are you referring to in bug 112506 ?
> > As weird as it sounds, I can open fine the first PDF (attachment
> > 16336) with evince CVS.
> > See the screenshot at
> > http://members.cox.net/vnoel/Screenshot.png
> > left is acrobat reader, right evince. Evince actually renders better
> > than acroread.
> > Was some work done on Type 3 fonts while I was not looking ???
> > Cheers
> > Vincent
> 
> So yeah, it turns out evince has no problem with that document. However
> linking with t1lib does fix the rendering of
> http://www.mutopiaproject.org/ftp/SorF/O2/sor_op2_3/sor_op2_3-a4.pdf
> , which I found from a evince or gpdf bug (that I can't seem to find
> anymore).
> 
> I had assumed that type 3 fonts didn't work at all. But it looks like
> they just don't work sometimes, which makes some sense but not lots.
> When I was looking at the problem evince certainly tried to draw the
> glyphs for the document above, but it seems they just never made it
> out.
> 
> -Jeff
> 
>