When a postscript file contains image data you may get an error during debug - Invalid token in line nnnn.
The FlateDecoded image data may contain characters that are considered invalid by the parser.
Viewing the file will work fine.
image
Gb"/Lkn"Fg+SU@a[MLW2XV#jRPC\/C3g1,!XXOK&<`,kl6^k`mC^'oS@@:&miQpiUm]V$Q@VbR(R!?
@@,%RC!'5t4FJ+d9JX^8RO2(4#5a1JFuD3]4.ccIeW,3Fj_iE1e].dJP>=YdZ@=4W&94iN4_oq`^Ym
g9T_SQN8kCQJKR#<2s[@JD02B[TUPf;_gtMq.[r4bp4-AACig;NL8$AH,@"o4TsC&LJ'&BUuD1/Wd'b
...
Syntax coloring will mark Gb" in black, /Lk in purple and continue in black until (R!>?...
For this kind of problems a solution (or rather a work-around) is already described in the Help Contents
(see section PostScript User Guide -> Tips and Tricks -> Raw Data):
When a postscript file contains image data you may get an error during debug - Invalid token in line nnnn. The FlateDecoded image data may contain characters that are considered invalid by the parser. Viewing the file will work fine.
Sample code: << /ImageType 1 /Width 538 /Height 250 /BitsPerComponent 8 /DataSource currentfile /ASCII85Decode filter /FlateDecode filter /MultipleDataSources false /ImageMatrix [538 0 0 -250 0 250] /Decode [0 255]