public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Alan W. Irwin" <irwin@beluga.phys.uvic.ca>
To: Peter Toft <pto@sslug.dk>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: Limit for docbook
Date: Tue, 30 Oct 2001 07:12:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.40.0110300651370.11508-100000@starling.mylan.home> (raw)
In-Reply-To: <Pine.LNX.4.33.0110300049510.1701-100000@k6.sslug>

Check my posts to this list over the last 12 months, and you will see a
detailed description of how to extend your (la)tex resources.  Beyond that,
you may have to experiment a little about which resource to increase, but
there is always the brute force method; double everything as a first
approximation. Whatever your changes to the resources, you should be able to
see the effects of the changes in the (la)tex log file which summarizes the
total resources and the actual resources used.  By correlating the log file
changes with the actual resources you specified you can quickly narrow down
which resource has to be increased.  Usually, (as appears to be your case as
well) it is one of the resources having to do with strings.

Alan W. Irwin

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6
__________________________

Linux-powered astrophysics
__________________________

On Tue, 30 Oct 2001, Peter Toft wrote:

> Hi
> I am still using Red Hat 6.2 docbook 3.1 since it works
> (some people say that RH7.2 also works - good news).
>
> I have a problem with a collection of 11 books in a
> set, which is kinda biiiig :)
>
> When I do db2pdf I get
>
> Underfull \vbox (badness 10000) detected at line 303790
> [855.0.21] [856.0.21] [857.0.21] [858.0.21] [859.0.21]
> [860.0.21] [861.0.21]
> [862.0.21] [863.0.21] [864.0.21] [865.0.21] [866.0.21]
> [867.0.21] [868.0.21]
> [869.0.21] [870.0.21] [871.0.21] [872.0.21] [873.0.21]
> [874.0.21] [875.0.21]
> [876.0.21] [877.0.21] [878.0.21] [879.0.21] [880.0.21]
> [881.0.21] [882.0.21]
> [883.0.21]
> ! TeX capacity exceeded, sorry [number of
> strings=55456].
> \IfFileExists #1#2#3->\openin \@inputcheck #1
>                                               \ifeof
> \@inputcheck \ifx \inpu...
> l.311823 {1}}
>
>
> I understand that this is one of the TeX limits I have
> to hack - but I really don't know which one, since I
> can easily make a 500 page book - but not this one ...
>
>
> Best
>
> --
> Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto
>
> "...... Those who want to get at the real guts of their machines
> have already begun turning to Linux."
> (IHT 29 oct 98)
>
>

      reply	other threads:[~2001-10-30  7:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29 15:52 Peter Toft
2001-10-30  7:12 ` Alan W. Irwin [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=Pine.LNX.4.40.0110300651370.11508-100000@starling.mylan.home \
    --to=irwin@beluga.phys.uvic.ca \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=pto@sslug.dk \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).