commit 57347e732fd186b907726dd9a27fc2011390e145
from: Sven M. Hallberg <pesco@khjk.org>
date: Fri Aug 12 17:02:59 2022 UTC

remove misplaced TT_ObjStm case from kcontentstream

Similar to kbyteostream, kcontentstream is a specialized version of
kstream that replaces the generic switch on /Type for the data parser.

This version uses either p_textstream (the parser for content streams)
or p_objstm__m. I think the latter case must have been the result of
some confusion. Object streams are something completely different than
content streams and cannot appear in place of one.

That leaves kcontentstream identical to kbyteostream except that it uses
p_textstream (parsing the stream data directly) instead of p_bytes
(leaving the stream data to be parsed in parse_pagenode)...

commit - a091668f694a14e7da6415d8056c770d72993198
commit + 57347e732fd186b907726dd9a27fc2011390e145
blob - ec84c6ef47cf4155338902214bcea5f70a826315
blob + 42adbaf179426ca995afc290db450170511ad12b
--- pdf.c
+++ pdf.c
@@ -3860,8 +3860,6 @@ kcontentstream(HAllocator *mm__, const HParsedToken *x
 	v = dictentry(dict, "Type");
 	if (v == NULL)	// XXX -> custom type
 		spec->parser = p_textstream;
-	else if ( (v->token_type == TT_BYTES) && bytes_eq(v->bytes, "ObjStm") )
-		spec->parser = p_objstm__m(mm__, dict);
 	else {
 		fprintf(stdout, "kcontentstream: Not a text or object stream!\n");
 		return p_fail;