nixpkgs/pkgs/applications/misc/xpdf/ at 18.03-beta · pyrox.dev/nixpkgs · tangled

pyrox.dev / nixpkgs

lol

nixpkgs / pkgs / applications / misc / xpdf /

at 18.03-beta 5 files

cmake_version.patch

xpdf: fix build on darwin (still broken in runtime)

8 years ago

xpdf: specify paths to Qt plugins

8 years ago

Merge remote-tracking branch 'upstream/master' into hardened-stdenv

9 years ago

added libxpdf and pdf2xml

15 years ago

xpdf-3.02-protection.patch

This is a quote from http://www.johannes-bauer.com/xpdf/xpdf.php, any moral issues can be posted on the mailing list ;) "If you are the proud owner of a proprietary PDF-Creator like "Adobe Acrobat" you probably have noticed that it gives you the option to make the resulting PDF protected in a way that you cannot copy any text from it or that you cannot extract the pictures within. What a nice little feature. Now what this technically does is to set a flag in the PDF telling the reader program "Please don't let the mean user copy any content from me! ". However, the whole process relies on the reader progam (like "Adobe Acrobat Reader" or "xpdf", in our case) to obey the request of the PDF creator. Now at this point, xpdf really pissed me off. Because it really does obey the completely non-sensical request of the PDF creator. Probably because of some legal trouble which Adobe might give them if they did not obey it. But logically there is absolutely no reason to restrict the extraction of text of graphical images from a PDF file. Text I could read and type it in again. Pictures I could photograph off my PC screen. It's completely moronic. It's Adobe. Plus some people at my college think it's protecting their documents well. They seem to believe that content which is made for education should under no circumstances leak to the outside - somebody could maybe learn something! It would be a disaster! It is obvious they're morons. This patch just proves my point."

18 years ago