From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/5278 Path: main.gmane.org!not-for-mail From: "Duncan Hothersall" Newsgroups: gmane.comp.tex.context Subject: Bad page breaking in enumerations Date: Wed, 15 Aug 2001 15:42:58 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035395876 32702 80.91.224.250 (23 Oct 2002 17:57:56 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:57:56 +0000 (UTC) Original-To: "ConTeXt mailing list" Xref: main.gmane.org gmane.comp.tex.context:5278 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:5278 Hi all. Have been having a very odd problem with some enumerations for a while. I have the following standard preamble (relevant excerpt only): --- %$Id: nubsmbabookbasic.tex,v 1.13 2001/08/08 11:02:19 dh Exp $ \setupoutput[pdftex] %new enumeration commands \defineenumeration[Activity] [text=Activity, before={\blank[2*big]}, after={\blank[2*big]}] \setupenumerations[Activity] [headstyle=\ss\tfa] \setupbackground [background=screen, corner=round, offset=6pt] \setupinmargin [align=right, style=\tfx\setupinterlinespace] --- And, for example, the following document fragment: --- This is a paragraph in running text. \startsubactivity% \margintext{\nohyphens\ss\bf This is the sidebar} \startbackground {\ss\sl This is the text of the activity telling you what to do ... }\stopbackground \stopsubactivity This is another paragraph in running text. --- I often get a page break between the "Activity X.X" title and the text of the activity, even if there is practically a whole page free and the content is no more than a few lines. I assume it's something to do with the background, but can anyone tell me how to phrase this better without the page breaking thing going on? Thanks a lot. Duncan PS I know there is some funny spacing in the input sample - that is because this stuff is generated from SGML/XML, and I wanted to give you exactly what was going in, in case it was the white space that could be causing the problem!