<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - "Syntax Error (202): Command token too long"" href="https://bugs.freedesktop.org/show_bug.cgi?id=58966#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - "Syntax Error (202): Command token too long"" href="https://bugs.freedesktop.org/show_bug.cgi?id=58966">bug 58966</a> from <a class="email" href="mailto:robertmuil@gmail.com" title="Robert Muil <robertmuil@gmail.com>"> Robert Muil</a> <pre>I did indeed mean pdftotext, sorry. That was amazingly fast! Chapeau! (In reply to <a href="show_bug.cgi?id=58966#c1">comment #1</a>) > (In reply to <a href="show_bug.cgi?id=58966#c0">comment #0</a>) > > I've attached a file that generates the error. To recreate, simply run: > > > > `pdftotex stimulus_category_influence_on_ratings_videos_emoman.pdf` > > I assume you mean 'pdftotext'. I can reproduce the error with pdftotext, > pdftoppm, and pdftocairo. Ghostscript and acroread open the file without > errors or warnings. > > I had a look at where the error is coming from and it turns out it is in the > check for linearized files in Linearization::Linearization. This function > checks if the first object in the file after the header is a Linearization > dictionary. The problem is this function has disabled the 'allow streams' > flag. As a result when opening a PDF file where the first object is a stream > results in the error due to trying to parse the stream as if it were not a > stream.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>