From: Gerhard Kugler <praxis@psychotherapie-kugler.de>
Subject: Re: Elevated text blocks
Date: Thu, 28 Dec 2006 21:25:02 +0100 [thread overview]
Message-ID: <20061228202502.GA4352@grohe.our-isp.org> (raw)
In-Reply-To: <alpine.WNT.0.81.0612281450400.2984@nqvgln>
On Thu, Dec 28, 2006 at 03:03:35PM -0500, Aditya Mahajan wrote:
> If choosing page size is an option, and there are only a few that are
> larger than a page, things may be much easier. Keep all of them in one
> page, and typeset. Note the ones that are larger than a page, and mark
> them using a differnt environment. That is, you decide which exercises
> should break and which should not.
This seems a good clarification.
> > > 3. Or a more drastic case, when the current page has only two lines
> > > and the text block is exactly one page long. Should the text split or
> > > not.
> >
> > No.
>
> This seems inconsistent with case 1. There the text was less than one
> page, but you want it to be split. In this case, the text is exactly
> one page, but you do not want it to be split?
I'm no longer so sure.
> Is something like this acceptable:
>
> if length < 1 page
> keep the whole thing together, even if it means ending the current
> page with lots of empty space.
>
> if length > 1 page
> split whereever you want
>
o.k.
> That would means, do a trial typesetting to find the length of the
> block, if length is less than one page put in a framedtext (which is
> just a highly customizable vbox) if length > 1 page, don't do anything
> and let it break pages anywhere. Just one more bit of information is
> needed. Do your exercises contain display math?
>
No.
Gerhard
--
Gerhard Kugler
Psychotherapeut
http://www.psychotherapie-kugler.de
prev parent reply other threads:[~2006-12-28 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 21:25 Gerhard Kugler
2006-12-28 12:58 ` Wolfgang Schuster
2006-12-28 19:34 ` Gerhard Kugler
2006-12-29 9:12 ` Wolfgang Schuster
2006-12-28 16:48 ` Aditya Mahajan
2006-12-28 19:26 ` Gerhard Kugler
2006-12-28 20:03 ` Aditya Mahajan
2006-12-28 20:25 ` Gerhard Kugler [this message]
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=20061228202502.GA4352@grohe.our-isp.org \
--to=praxis@psychotherapie-kugler.de \
--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).