[poppler] Annotation interoperability

Adam Reichold adamreichold at myopera.com
Wed Oct 3 23:11:16 PDT 2012

Hash: SHA1


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.

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?
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/


More information about the poppler mailing list