[poppler] Annotation interoperability
Albert Astals Cid
aacid at kde.org
Fri Oct 5 11:58:34 PDT 2012
El Divendres, 5 d'octubre de 2012, a les 20:42:36, Adam Reichold va escriure:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 05.10.2012 20:17, Albert Astals Cid wrote:
> > El Dijous, 4 d'octubre de 2012, a les 08:11:16, Adam Reichold va
> > escriure: Hello,
> > On 04.10.2012 01:00, Fabio D'Urso wrote:
> >>>>> Maybe it is sensible to enforce one way of cropping in the
> >>>>> Qt4 frontend of Poppler? Not sure about this though.
> >>>> It seems to me that it's poppler rendering it incorrectly:
> >>>> 1) The attached document is rendered in a completely
> >>>> different way
> >>>> than in acroread: we show the icon bottom-left, acroread
> >>>> shows it
> >>>> top-left.
> >>>> 2) Also, in acroread the icon always has the same size, while
> >>>> in poppler it scales according to the current zoom level.
> >>>> I guess fixing #1 should be fairly straightforward and I'll
> >>>> work on it tomorrow, about #2 there's some extra work to do.
> > I think, at least for me, changing #2 would break application
> > behaviour: I currently try to avoid the problem by cropping the
> > boundary selected by the user to 24x24 at 72dpi and transform it in
> > the same way as the page itself so that it matches the icon size.
> > (Which I thought was implied by giving it in normalized
> > coordinates.)
> > If Poppler decides to (not) scale it like acroread, the effective
> > boundary at any scale factor and hence the transformation to be
> > applied would become different and also specific to fixed-size
> > icon-like annotations.
> > Not that is isn't possible, it would just introduce new behaviour
> > and hence necessarily new code on the application level.
> >> Sure, but the thing is, if the current behaviour is wrong, it has
> >> to be fixed and apps adapted, we can't live forever with
> >> workarounds in the wrong place.
> Yes, I agree. As I understand it, the way I currently do it may be
> correct for the implementation but not for the standard. So the
> implementation has to change and hence my application's dependent
> It would be nice if Poppler's behaviour changed only at some
> well-defined point in time like the release of version 0.22.
> So I'll probably start to respect the FixedSize and FixedRotation
> flags beginning with Poppler 0.22? (Meaning text annotations will
> really be 24px times 24px from the top left corner of the boundary no
> matter what resolution I pass to Poppler::Page::renderToImage?)
I guess Fabio can confim your question.
About the Poppler 0.22 that is why i suggested merging the patch only to
> Best regards, Adam.
> >> Cheers, Albert
> > Best regards, Adam.
> > P.S.: Obviously, I am not respecting the FixedSize or
> > FixedRotation flags. Does Poppler? Maybe those could be use to
> > convey the scaling that is done internally?
> >> _______________________________________________ poppler mailing
> >> list poppler at lists.freedesktop.org
> >> http://lists.freedesktop.org/mailman/listinfo/poppler
> > _______________________________________________ poppler mailing
> > list poppler at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/poppler
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
> -----END PGP SIGNATURE-----
> poppler mailing list
> poppler at lists.freedesktop.org
More information about the poppler