From: Aditya Mahajan <adityam@umich.edu>
Subject: Different pagebreaks for component and whole document
Date: Sun, 2 Apr 2006 01:00:00 -0500 (EST) [thread overview]
Message-ID: <Pine.WNT.4.63.0604020041280.2816@nqvgln> (raw)
Hi,
I have run into a strange kind of a problem and I am not sure on how
to debug to figure out what is going wrong. Maybe someone with more
experience with context can help me here.
I have the following document structure
project: main.tex
environment:env_main.tex
products: assignments.tex
handouts.tex
project: assignments.tex
components:assignment-01.tex
assignment-02.tex
and so on
project: handouts.tex
component: handout-01.tex
handout-02.tex
and so on.
Each component starts with \title which does a page break. There are
no local setups in any component. I expected that each component will
be typed out in the same manner, whether I compile the a component,
a product or the entire project. It turns out this is not the case.
The first page of handout-01.tex is different when I compile the
project (main.tex). The pagebreak is set at a different place and I
get ugly page break at the end. If I compile handouts.tex or
handout-01.tex, the page breaks are same and there is no ugly
pagebreak at the end.
Is it possible that such a behaviour is due to the length of the
document. main.pdf is 105 pages long, while handout-01.pdf is 4 pages
and handouts.pdf is 14 pages. It seems that due to the large length of
main.pdf, context is not trying hard enough to get good page break.
Even a manual \page[disable] does not prevent the ugly pagebreak for
main.tex.
I am totally confused by this behaviour. Any explainations or
suggestions?
--
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008
next reply other threads:[~2006-04-02 6:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 6:00 Aditya Mahajan [this message]
2006-04-03 8:30 ` Taco Hoekwater
2006-04-05 6:54 ` Aditya Mahajan
2006-04-08 1:50 ` Mojca Miklavec
2006-04-08 7:07 ` Taco Hoekwater
2006-04-08 8:59 ` Hans Hagen
2006-04-03 9:01 ` Hans Hagen
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=Pine.WNT.4.63.0604020041280.2816@nqvgln \
--to=adityam@umich.edu \
--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).