I received an answer to this question from the developer. It turned out to be a bug in the way pdftk
handled a /DecodeParms [null]
line.
If the decode parameters are null, a writer could just omit the /DecodeParms
line, but a compliant reader should understand it either way. I tried out the new version of pdftk
and the problem seems to be solved.