On Mon, 2 May 2011, Hartmut Henkel wrote:
On Mon, 2 May 2011, Reviczky, Adam wrote:
Right, I have a feeling that this is MetaPost related, hence the random problems with different styles.
I can reproduce this now without simpleslides too, using only metapost.
Here's a minimal example:
Get logo_ignite.mp from: http://pastebin.com/raw.php?i=VqvcWniu
% slides.tex \startreusableMPgraphic{ignite} input logo_ignite; \stopreusableMPgraphic \starttext \reuseMPgraphic{ignite} \stoptext
%handout.tex \setuppapersize [A4][A4] % or [A4,landscape][A4,landscape] \setuplayout [header=0pt,footer=1cm,backspace=1cm,topspace=1cm,width=middle,height=middle] \setupfootertexts [presentation---\currentdate\space---\space\pagenumber] \starttext \combinepages[slides][nx=2,ny=3,frame=on] \stoptext
context slides.tex && context handout.tex && qpdf --linearize handout.pdf out.pdf
results in: object stream 21 (object 31 0, file position 1547): unknown token while reading object (nullnullnullnull)
ConTeXt ver: 2011.05.01 12:50 MKIV fmt: 2011.5.2 int: english/english mkiv lua stats > luatex banner - this is luatex, version beta-0.71.0-2011050213 (rev 4233)
seems to be a bug in luatex beta-0.71.0-2011050213 (rev 4233). Checking...
found it: There were 4 null objects in an ObjStm in handout.pdf, stored now compress: "nullnullnullnull" (not yet so in 0.70.x). Each null object has a correct pointer to its begin (the 'n'), so one should suppose that an object ends at the character ('l') just before the start ('n') of the next null object. Like in the TeX string pool. But qpdf gives an error about a "nullnullnullnull" object (fully ignoring the start of the 2nd null object!), and also Adobe Reader 9 quits with an error. Interestingly xpdf displays the file handout.pdf without any problem. The problem is fixed by adding a space at to the end of each object within an ObjStm, so there is now "null null null null", see SVN 4242. No comment in the PDF Ref. on this. Looks like a flaw in qpdf and the Reader? Regards, Hartmut