From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to avoid a page break?
Date: Tue, 4 Nov 2008 23:25:17 +0100 [thread overview]
Message-ID: <6011F4E6-7CCD-48B1-BC6B-8084B8BAAD29@gmail.com> (raw)
In-Reply-To: <20081104213908.GE2264@atos.labs.wmid.amu.edu.pl>
Am 04.11.2008 um 22:39 schrieb Marcin Borkowski:
> Dnia Tue, Nov 04, 2008 at 10:17:51PM +0100, Wolfgang Schuster
> napisał(a):
>>
>> Am 04.11.2008 um 21:21 schrieb Marcin Borkowski:
>>
>>> Hi,
>>>
>>> I have the following in my code:
>>>
>>> \def\doPutTitle#1{%
>>> \startalignment[middle]
>>> \bfb
>>> \page[bigpreference]
>>> \blank[2*big]
>>> #1%
>>> \page[no]%
>>> \blank[big]%
>>> \page[no]%
>>> \stopalignment
>>> \page[no]%
>>> }%
>>>
>>> Why is it still possible that I have a page break after, say,
>>> \doPutTitle{some title} (in MkII, in MkIV page breaks fall in
>>> different
>>> places). Which percentage signs and \page[no]'s are unnecessary
>>> here?
>>
>> \def\doPutTitle#1%
>> {\page[bigpreference]
>> \vbox\bgroup
>> \raggedcenter
>> #1%
>> \egroup
>> \nobreak\blank[big]}
>
> OK, though this looks rather low-level. I was thinking about
> something
> more user-friendly;).
>
> This raises a philosophical question: is it the "ConTeXt way" to use
> low-level constructs in environments and high-level in documents?
> Or is
> it better to avoid low level whenever possible? Also, your code mixes
> low-level commands (\vbox, which is a TeX prmitive, \raggedcenter,
> which
> is a ConTeXt low-level command, I guess) and high-level ones (\blank).
> I understand that this ensures a uniform vertical spacing (\blank[big]
> is obviously better than \vskip 10pt;)), but I thought that it is
> against ConTeXt philosophy to use low-level stuff unless something
> really non-standard is needed.
Here is a better method, there is nothing wrong with low level but
you should know what you do.
\defineblankmethod [nobreak] {\nobreak}
\def\doPutTitle#1%
{\framed[frame=offwidth=\textwidth,align=middle]{#1}%
\blank[nobreak,line]}
Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-11-04 22:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 20:21 Marcin Borkowski
2008-11-04 21:17 ` Wolfgang Schuster
2008-11-04 21:39 ` Marcin Borkowski
2008-11-04 22:25 ` Wolfgang Schuster [this message]
2008-11-04 22:42 ` Marcin Borkowski
2008-11-04 22:49 ` Wolfgang Schuster
2008-11-05 7:39 ` luigi scarso
2008-11-05 9:57 ` Marcin Borkowski
2008-11-05 10:13 ` Wolfgang Schuster
2008-11-05 10:22 ` Marcin Borkowski
2008-11-05 10:05 ` Marcin Borkowski
2008-11-05 10:14 ` Wolfgang Schuster
2008-11-05 10:50 ` Marcin Borkowski
2008-11-05 11:12 ` Wolfgang Schuster
2008-11-05 12:13 ` Marcin Borkowski
2008-11-05 12:25 ` Wolfgang Schuster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6011F4E6-7CCD-48B1-BC6B-8084B8BAAD29@gmail.com \
--to=schuster.wolfgang@googlemail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).