Errors in PDF version 1.1

[mlbraga82]

Hi, I have some PDF files in versions 1.1 and 1.4. The script that I wrote work perfectly in 1.4 files, but not in 1.1 versions. When I open 1.1 file in a PDF viewer (PDF XChange Viewer) and "Save As..." the new file is 1.4 version and works in the python script.

Can anybody help me?

Lib version: pdfplumber 0.5.28

Code:

import re
import pdfplumber
import sys
file = sys.argv[1]
pdffile = open(file,'rb')
(...)
pdf=pdfplumber.open(pdffile)
(...)

Errors:

Traceback (most recent call last):
  File "H:\test\extraitexto.py", line 50, in <module>
    pdf=pdfplumber.open(pdffile)
  File "C:\Users\limab\AppData\Local\Programs\Python\Python38-32\lib\site-packages\pdfplumber\pdf.py", line 60, in open
    return cls(path_or_fp, **kwargs)
  File "C:\Users\limab\AppData\Local\Programs\Python\Python38-32\lib\site-packages\pdfplumber\pdf.py", line 33, in __init__
    self.doc = PDFDocument(PDFParser(stream), password=password)
  File "C:\Users\limab\AppData\Local\Programs\Python\Python38-32\lib\site-packages\pdfminer\pdfdocument.py", line 554, in __init__
    xref.load(parser)
  File "C:\Users\limab\AppData\Local\Programs\Python\Python38-32\lib\site-packages\pdfminer\pdfdocument.py", line 177, in load
    (_, obj) = parser.nextobject()
  File "C:\Users\limab\AppData\Local\Programs\Python\Python38-32\lib\site-packages\pdfminer\psparser.py", line 567, in nextobject
    (pos, token) = self.nexttoken()
  File "C:\Users\limab\AppData\Local\Programs\Python\Python38-32\lib\site-packages\pdfminer\psparser.py", line 494, in nexttoken
    self.charpos = self._parse1(self.buf, self.charpos)
  File "C:\Users\limab\AppData\Local\Programs\Python\Python38-32\lib\site-packages\pdfminer\psparser.py", line 452, in _parse_string_1
    self._curtoken += bytes((int(self.oct, 8),))
ValueError: bytes must be in range(0, 256)

[jsvine]

Judging by the stacktrace, the exception is raised from this library's main dependency, pdfminer.six. And my hunch is that the exception is caused by malformed PDFs, rather than a bug in pdfminer.six. If you haven't already, it's worth trying to repair your PDF using Ghostscript. To do so, run gs -o repaired.pdf -sDEVICE=pdfwrite original.pdf, replacing original.pdf with your PDF's actual filename.