From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: Different pagebreaks for component and whole document
Date: Wed, 5 Apr 2006 02:54:33 -0400 (EDT) [thread overview]
Message-ID: <Pine.WNT.4.63.0604050252440.460@nqvgln> (raw)
In-Reply-To: <4430DD30.60605@elvenkind.com>
On Mon, 3 Apr 2006, Taco Hoekwater wrote:
>
>
> Aditya Mahajan wrote:
>>
>> 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.
>
> The fact that the page breaks are different indicates an
> imperfection somewhere in the internal macro definitions
> for \startproject c.s., and is definately not related to
> the length of your document.
>
> But, since you are not really supposed to compile the project
> file in the first place, fixing this will be very low on the
> list of to-be-fixed problems, I wager. The manual is not as
> clear on that as it could be (I suppose), but you are definately
> not expected to be compiling project definition files.
Thanks. I will only compile the products and join then using
--pdfcombine. Each product has separate pagenumbering, so this will
work for my project as of now.
Hans, I will try to make a minimum example to illustrate the problem.
Thanks,
Aditya
--
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008
next prev parent reply other threads:[~2006-04-05 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 6:00 Aditya Mahajan
2006-04-03 8:30 ` Taco Hoekwater
2006-04-05 6:54 ` Aditya Mahajan [this message]
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.0604050252440.460@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).