Am 10.06.2012 um 12:19 schrieb Sido Jensma:

This is the first time I am posting here. I am not really sure what a typical bug report should look like.

I had posted a question on stack-exchange and it was suggested to post a bug report here. I’m not sure if this is a bug, but it was unexpected behavior to me.

The original question was posted here: http://tex.stackexchange.com/questions/59134/strange-problem-with-frames-con...

And a ‘not-so-minimal’ example of what is happening is attached (see the last page).

I have tested this with extreme tables and don’t get the same behavior.

When you use a table environment which is broken across pages together with the same environment in header settings can sometimes mix. In your case it’s best to use \framed in the header which does the same and is also faster but even then one problem remains. By default \framed uses \linewidth for “rulethickness” and natural tables assign a different value to this length, this results in wrong rules in the header when you don’t change the value (see example below). Here is a better version for the header of your document. \startsetups[header] \setupframed[width=0.2\textwidth,height=\headerheight,align=middle,offset=2mm,rulethickness=0.4pt] \dontleavehmode \startframed Rev \stopframed \startframed[width=0.6\textwidth,foregroundstyle=\ssbfa] \getvariable{document}{projectname}\\ \getvariable{document}{documenttitle} \stopframed \startframed some text \stopframed \stopsetups BTW: Please use next time the normal mailing list for such problems and not the developer list. Wolfgang