[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | Online Bookbuilding |
| Notice: | This conference is write-locked: see note 1.3. |
| Moderator: | VAXUUM::UTT |
|
| Created: | Fri Aug 12 1988 |
| Last Modified: | Mon Jul 15 1991 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 440 |
| Total number of notes: | 2134 |
138.0. "another runaway argument (T1.2)" by AITG::WARNER (Ross Warner) Mon May 22 1989 14:33
When using DOCUMENT T1.2 to process for ONLINE.REFERENCE, I get a runaway
argument. I never had this problem with V1.1. DOCUMENT's message doesn't help
me find the problem.
Can someone shed some light on this?
Here's the relevant portion of the LOG file:
%DOC-I-IDENT, VAX Document T1.2 6-MAR-1989 14:28:26.99
.
.
.
[ T e x t F o r m a t t i n g ]...
%TEX-I-INFO, loading online doctype design file, TEX$O_REFERENCE - on page [1]
.
.
.
%TEX-W-RUNAWAY, Runaway 'argument'
%TEX-I-SHOWTOKEN, '{'
%TEX-E-NOROOM, Exceeded memory capacity:
-TEX-I-MEMORYSIZE, Main memory size = 131072 words
%TEX-I-SHOWCONTEXT, '->\getmark 4{B'
%TEX-I-SHOWCONTEXT, ' }'
%TEX-I-SHOWCONTEXT, '...alse \fi \gettblubotmark '
%TEX-I-SHOWCONTEXT, ' \edef \tempcsA {\withintblM...'
%TEX-I-SHOWCONTEXT, '...ar =\endgraf \setMarkFlags '
%TEX-I-SHOWCONTEXT, ' \setpageclass \shipout \vbo...'
%TEX-I-SHOWCONTEXT, '...ax }\fi \fi \else \sdmloutput '
%TEX-I-SHOWCONTEXT, ' \fi }'
%TEX-I-SHOWCONTEXT, '->\penalty -\@M '
%TEX-I-SHOWCONTEXT, ' '
%TEX-I-SHOWCONTEXT, '...\fi \else \vfil \eject '
%TEX-I-SHOWCONTEXT, ' \fi \ifdim \pagetotal =0pt ...'
%TEX-I-SHOWCONTEXT, '...s \vfill \superejectpage '
%TEX-I-SHOWCONTEXT, ' \pagepoprevisions '
%TEX-I-SHOWCONTEXT, '... script file. \SDMLpageject '
%TEX-I-SHOWCONTEXT, ' \topichunk {continuetopic}{...'
%TEX-I-SHOWCONTEXT, '...1,\kern 1em\turnaround #2'
%TEX-I-SHOWCONTEXT, ' \ifx 0#3\else \newline #3\f...'
%TEX-I-LINE, Error occurred on or around line number: 2700
%TEX-I-SHOWCONTEXT, '{0}'
%TEX-I-SHOWCONTEXT, ' %'
%TEX-I-FILENAME, 'PROLOGW$:[STAPLES.V1_REF]S1034AB.TEX;32'
-TEX-I-ONPAGE, on page [848]
%TEX-I-PAGESOUT, 847 pages written.
-TEX-I-OUTFILENAME, 'PROLOGW$:[STAPLES.V1_REF]S1034PRO.DVI_BOOKREADER'
%DOC-E-ERROR_FORMATTER, Errors found by the text formatter
WARNER job terminated at 19-MAY-1989 10:04:21.72
Accounting information:
Buffered I/O count: 1605 Peak working set size: 7502
Direct I/O count: 3500 Peak page file size: 15168
Page faults: 11709 Mounted volumes: 0
Charged CPU time: 0 00:20:37.77 Elapsed time: 0 00:23:17.21
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 138.1 | | VAXUUM::UTT | | Mon May 22 1989 17:28 | 14 |
| The problem is that TeX ran out of memory processing the file. This
most commonly occurs because of a very large 'chunk' of information,
such as a very long informal table or example, or even just a very,
very long segment of text in a long book. The fix to these problems is
generally to make the long example or table formal, or to use the
<online_chunk> tag to break the long chunk into separate chunks.
(The output will look the same on the screen but TeX will be a
lot happier with the smaller chunks.) If these suggestions do not
help, please let me know. I will probably want to take a look at
S1034AB.SDML.
Thanks,
Mary
|
| 138.2 | <online chunk> doesn't help | AITG::WARNER | Ross Warner | Wed May 24 1989 07:37 | 4 |
| This appendix is for Error Messages, so it is composed of sort chunks
already. I tried adding three <online_chunk> tags anyway, spaced
through the 1000 lines or so, but I got a similar error. Instead of
runaway argument, I got "runaway 'text'".
|
| 138.3 | Mary's fix | AITG::WARNER | Ross Warner | Fri May 26 1989 16:33 | 17 |
| From: CLOSET::UTT "Mary Utt" 24-MAY-1989 13:29:53.32
To: AITG::WARNER
CC:
Subj: RE: I found a coding error...
This is a known problem and is easily fixed. The files TEX$O_REFERENCE.DESIGN
and CUP$O_DECWINDOWS_HAND.DESIGN in DOC$LOCAL_FORMATS need to be edited.
Open the files and find \def\begintoc. About 5 lines into the macro
is the line \vsize=50in -- change the 50 to 25 and you'll be all set.
This will be fixed in the next baselevel.
Sorry,
Mary
|
| 138.4 | | VAXUUM::UTT | | Fri May 26 1989 17:55 | 12 |
| I should note that the fix to Ross' original problem (.0) was a
coding change; he later had a problem with tex running out of
memory on the table of contents. The fix Ross posted in .3 is
for *that* problem. Unless tex is running out of memory on
table of contents formatting I do not recommend that you edit
the design file. (It's too easy to introduce errors and then things
are broken for everyone.)
(The design files will be updated in the next baselevel of the
online bookbuilding tools.)
Mary
|
| 138.5 | further note... | AITG::WARNER | Ross Warner | Wed May 31 1989 09:59 | 22 |
| That's true; my original problem was the following:
We had an Error Message appendix that was missing the closing parenthesis for
the argument to a <msg> tag. DOCUMENT V1.1 did not complain about this, and
because the argument is not bold in LPAHAND PostScript output, we never saw
any ill effects in our printed copies that went through SDC before I started
work on the Bookreader.
In the Bookreader, however, the msg is boldface, so I got the runaway argument
and pages of bold text.
When I inserted the missing parenthesis, I got a message about the problem of
TEX running out of memory. This problem did not occur with DOCUMENT V1.1 and
the 20-MAR bookbuilding tools.
Changing the design file (which was easy for me since I was already using an
edited file, but which is NOT recommended practice as Mary noted) solved that
problem. I also preferred the smaller chunks it created, because this gave
shorter ranges in the TOC for both the Glossary and Error Messages appendix.
Previously, each range had five or six pages to scroll through, now each is only
two to two-� pages. Also, it's easy to find information with the shorter
ranges. I think the shorter ranges are better.
|