Comment 10 for bug 254849
Revision history for this message
| Alex Valavanis (valavanisalex) wrote | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I agree that this seems like a bad situation... does anyone have an idea about whether a switch to public Poppler API would be painful to implement? I'd be willing to look into it, but first...
* Are we doing anything that *needs* non-public poppler API or are we just using it for legacy reasons?
* Is the public API actually more stable than the private stuff or will we still be stuck with assorted build failures and conditional builds whenever there is a new Poppler release?