>It's not useful on a normal system since it's for debugging
Depends on point of view. :)
*As long as* everything is still working fine, there is no need for that tool. But once evince goes all wonky with a certain PDF, it's the best tool to use and NOT (as most users do) put the entire blame on evince itself. But evince is merely the "executive power", while highly dependent on the API it accesses under the hood.
>Do you know if what binary fedora includes the binary?
Sure, but you will get the information only because you've explicitly asked for it. :) So here goes...
>It's not useful on a normal system since it's for debugging
Depends on point of view. :)
*As long as* everything is still working fine, there is no need for that tool. But once evince goes all wonky with a certain PDF, it's the best tool to use and NOT (as most users do) put the entire blame on evince itself. But evince is merely the "executive power", while highly dependent on the API it accesses under the hood.
>Do you know if what binary fedora includes the binary?
Sure, but you will get the information only because you've explicitly asked for it. :) So here goes...
Originally, it was in poppler-utils, cf. https:/ /bugzilla. redhat. com/show_ bug.cgi? id=872338
Later, Marek moved it to its own subpackage 'poppler-demos'. arm.koji. fedoraproject. org/koji/ rpminfo? rpmID=1912994
Version 0.40 is now in the wild out there:
http://