Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 23 |
Nodes: | 6 (0 / 6) |
Uptime: | 49:45:07 |
Calls: | 583 |
Files: | 1,138 |
Messages: | 111,301 |
Syntax Error (3868069): Missing 'endstream' or incorrect stream length Syntax Error (3557294): Missing 'endstream' or incorrect stream length
[multiple repetitions of those 2 lines
Syntax Error (3556857): Bad FCHECK in flate stream
Syntax Error (3868069): Missing 'endstream' or incorrect stream length Syntax Error (3866517): Bad FCHECK in flate stream
I tried "pdfseparate -f 116 -l 116 TFP2021.pdf dianostic.pdf" and got
Syntax Error (3868069): Missing 'endstream' or incorrect stream length
Syntax Error (3557294): Missing 'endstream' or incorrect stream length
[multiple repetitions of those 2 lines
Syntax Error (3556857): Bad FCHECK in flate stream
Syntax Error (3868069): Missing 'endstream' or incorrect stream length
Syntax Error (3866517): Bad FCHECK in flate stream
I'm running Debian 12.8.
I have a 100+ page PDF document.
I wish to extract 2 of those pages, each to their own PDF file for later editing.
I'm focusing on poppler-utils as it appears to offer tools for current
and future goals.
Doing "pdftotext -layout -f 116 -l 116 TFP2021.pdf jul24-a.txt" comes
very close to what I want.
Having been surrounded by TECO-buffs in the 70's, comparing the output
of "pdftotext -f 116 -l 116 TFP2021.pdf jul24-b.txt" to the above
suggests an approach to resolving.
It involves being able to edit a *SINGLE* rather than all 100+ companion pages.
I tried "pdfseparate -f 116 -l 116 TFP2021.pdf dianostic.pdf" and got
Syntax Error (3868069): Missing 'endstream' or incorrect stream length Syntax Error (3557294): Missing 'endstream' or incorrect stream length
[multiple repetitions of those 2 lines
Syntax Error (3556857): Bad FCHECK in flate stream
Syntax Error (3868069): Missing 'endstream' or incorrect stream length Syntax Error (3866517): Bad FCHECK in flate stream
How/where do I find interpretation of those?
TIA
*A postscript
I had originally composed this message before discovering "pdfseparate"
had created output files that that appear to be what I intended.
I'm still interested in the meaning of the error messages as it may hint
as why ""pdftotext" wasn't *exactly* what I hoped for.
Richard Owlett <rowlett@access.net> writes:
I tried "pdfseparate -f 116 -l 116 TFP2021.pdf dianostic.pdf" and got
Syntax Error (3868069): Missing 'endstream' or incorrect stream length
Syntax Error (3557294): Missing 'endstream' or incorrect stream length
[multiple repetitions of those 2 lines
Syntax Error (3556857): Bad FCHECK in flate stream
Syntax Error (3868069): Missing 'endstream' or incorrect stream length
Syntax Error (3866517): Bad FCHECK in flate stream
I think the PDF is malformed, although not necessarily fatally so.
https://superuser.com/questions/1383547/when-i-am-trying-extract-text-from-pdf-using-pdftotext-command-in-linux-i-got
Why not use pdfseparate to extract the two pages you want, and then use pdftotext on each of the two pages?
On 2025-07-24, Richard Owlett <rowlett@access.net> wrote:
I'm running Debian 12.8.
I have a 100+ page PDF document.
I wish to extract 2 of those pages, each to their own PDF file for later
editing.
I'm focusing on poppler-utils as it appears to offer tools for current
and future goals.
Doing "pdftotext -layout -f 116 -l 116 TFP2021.pdf jul24-a.txt" comes
very close to what I want.
Having been surrounded by TECO-buffs in the 70's, comparing the output
of "pdftotext -f 116 -l 116 TFP2021.pdf jul24-b.txt" to the above
suggests an approach to resolving.
It involves being able to edit a *SINGLE* rather than all 100+ companion
pages.
I tried "pdfseparate -f 116 -l 116 TFP2021.pdf dianostic.pdf" and got
Syntax Error (3868069): Missing 'endstream' or incorrect stream length
Syntax Error (3557294): Missing 'endstream' or incorrect stream length
[multiple repetitions of those 2 lines
Syntax Error (3556857): Bad FCHECK in flate stream
Syntax Error (3868069): Missing 'endstream' or incorrect stream length
Syntax Error (3866517): Bad FCHECK in flate stream
How/where do I find interpretation of those?
TIA
*A postscript
I had originally composed this message before discovering "pdfseparate"
had created output files that that appear to be what I intended.
I'm still interested in the meaning of the error messages as it may hint
as why ""pdftotext" wasn't *exactly* what I hoped for.
On 7/24/25 3:55 PM, Richard Kettlewell wrote:
Richard Owlett <rowlett@access.net> writes:
I tried "pdfseparate -f 116 -l 116 TFP2021.pdf dianostic.pdf" and got>>>> Syntax Error (3868069): Missing 'endstream' or incorrect stream length
Syntax Error (3557294): Missing 'endstream' or incorrect stream length >>>> -a-a-a-a [multiple repetitions of those 2 lines
Syntax Error (3556857): Bad FCHECK in flate stream
Syntax Error (3868069): Missing 'endstream' or incorrect stream length >>>> Syntax Error (3866517): Bad FCHECK in flate stream
I think the PDF is malformed, although not necessarily fatally so.
https://superuser.com/questions/1383547/when-i-am-trying-extract-text-from-pdf-using-pdftotext-command-in-linux-i-got
Interesting read as is manpage for mutool {just installed}.
I have no control of the source document[1] as it a USDA publication.
Is there an independent site, which when given a URL will evaluate structural correctness [esp one whose evaluation would be worth
reporting to USDA]?
[1]https://fns-prod.azureedge.us/sites/default/files/resource-files/TFP2021.pdf
On 7/25/25 8:30 AM, Richard Owlett wrote:
On 7/24/25 3:55 PM, Richard Kettlewell wrote:
Richard Owlett <rowlett@access.net> writes:
I tried "pdfseparate -f 116 -l 116 TFP2021.pdf dianostic.pdf" and got >>>>> Syntax Error (3868069): Missing 'endstream' or incorrect stream length >>>>> Syntax Error (3557294): Missing 'endstream' or incorrect stream length >>>>> -a-a-a-a [multiple repetitions of those 2 lines
Syntax Error (3556857): Bad FCHECK in flate stream
Syntax Error (3868069): Missing 'endstream' or incorrect stream length >>>>> Syntax Error (3866517): Bad FCHECK in flate stream
I think the PDF is malformed, although not necessarily fatally so.