I've seen some stuff about this previously but can't seem to relocate it on
"you do not have permission to extract text"
"you did not close the PDF document"
errors when running the filter-media script.
I seem to recall something about changing permissions or security settings
on the pdf files themselves, but I already have hundreds of these things in
the repository - how exactly do I change the permissions on these files (or
is there another workaround/patch?). I'd hate to have to do this all
manually, especially on an ongoing basis.
Thanks in advance for any advice.
Library IT Services
University of Sydney
ph: 61-2-9351 5946
From: Mark H. Wood <mwood@IUPUI.Edu> - 2006-06-26 15:18:33
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, 23 Jun 2006, Gary Browne wrote:
> I seem to recall something about changing permissions or security settings
> on the pdf files themselves, but I already have hundreds of these things in
> the repository - how exactly do I change the permissions on these files (or
> is there another workaround/patch?). I'd hate to have to do this all
> manually, especially on an ongoing basis.
Is it convenient to make checking the security settings part of the
workflow? Recent Adobe Reader versions make it fairly easy to see these
settings. xpdf (http://www.foolabs.com/xpdf/) comes with a commandline
'pdfinfo' tool that shows some of them too. Then at least you can avoid
archiving any more of the locked documents. Plus you need to get word out
to your contributors about making sure they submit usable documents in the
I wonder how hard it would be to add an automagical check for extraction
permission at submission time, when a bitstream is marked as PDF.
seems to take care of making the actual determination.
Mark H. Wood, Lead System Programmer mwood@...
Typically when a software vendor says that a product is "intuitive" he
means the exact opposite.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: pgpenvelope 2.10.2 - http://pgpenvelope.sourceforge.net/
-----END PGP SIGNATURE-----