[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

731.0. "Where's the wizard ????" by RDGE00::CRESSWELL (Julie Cresswell) Thu Jul 30 1987 10:15

    I am new to Document and have a large 250+ page guide which I have
    been trying to Document. The error message below occurred after
    I added some <head1> tags and so I have been trying to cut the length
    of these arguments down, but it still does not work. 
    Am I looking in the right area ? and if so what is the limit for
    a <head> tag length ?
    I will be leaving DEC tomorrow, Friday,and so would appreciate a
    quick reply,
    
    Thanks,
    
    Julie

    PS  I used software.guide for line_printer

%TEX-I-OUTFILENAME, 'disk$dev005:[cresswell.tas_doc]TAS_PROG_GUIDE.DVI_LPR'
[2-257] [2-258] [2-259] [2-260] [2-261] [2-262] [2-263] [2-264]
%TEX-E-TEXERROR, Error found by TeX

%TEX-I-ONPAGE, on page [2-265]

%TEX-I-OUTFILENAME, 'disk$dev005:[cresswell.tas_doc]TAS_PROG_GUIDE.DVI_LPR'
pool size=22174]
.
\markstring ...\marktoksviii ][::\the \markcounti 
                                                  ][\the \markcountii ][\the...

\makemark ... \origmark \expandafter {\markstring 
                                                  }
\headermark ...\let \noexpand =\nxnxnx \markA {#1}
                                                  }\ifdim \CHKlastskip =0pt\...
l.10450 ...pand\_DATE\noexpand\_LOV\noexpand\_GRP}
                                                  
If you really absolutely need more capacity,
you can ask a wizard to enlarge me.


%TEX-I-PAGESOUT, 267 pages written.

%TEX-I-OUTFILENAME, 'disk$dev005:[cresswell.tas_doc]TAS_PROG_GUIDE.DVI_LPR'

                                              
T.RTitleUserPersonal
Name
DateLines
731.1Likely a missing "}" or Tag Translator error?IJSAPL::KLERKTheo de KlerkFri Jul 31 1987 08:1512
 That is the sort of message TeX normally generates if a lot of commands
 are nested and TeX is running out of allocated memory for this purpose.
 More often it occurs because some argument is not closed properly, and
 hence TeX keeps looking for the closing } , thereby exhausting its
 memory.

 If you haven't made an error in matching < > and ( ) in the SDML file
 (which ought to have been reported by the Tag Translator), then the
 error is probably caused by an error in the Tag Translator itself.
 Which means that the Translator must be corrected...

Theo
731.2premature diagnosis?VAXUUM::KOHLBRENNERFri Jul 31 1987 09:534
    If the tag translator is broken, I'll be the first to admit it
    and the first to fix it, but so far there isn't any evidence
    to that effect.     :-)          bill
    
731.3BL7's the problem, methinks...WRONGO::PARMENTERVenusian or Venerean?Fri Jul 31 1987 11:3931
    
    As Theo rightly points out, there *may* be some sort of missing delimiter
    in the TeX file which is causing the problem.  However, I doubt
    that this is the case.  .0 did not state this, but this book was
    processed on BL7 which had significantly less memory than does V10, 
    or BL8 for that matter.  If possible, the book should be processed
    for BL8 or V10, where I believe it would go straight through.
    
    If for some reason this is not a possiblity, then perhaps the book
    could be split into two parts.  It is unfortunate that the memory
    sizes for BL7 were not adequate, but we fixed this the only way
    possible:  on the next baselevel.
    
    The idea that there might be a missing delimiter which the
    and the tag-translator and then the TeX macros failed to catch is
    fairly far-fetched, because usually when this sort of thing happens,
    all sorts of terrible things occur at every point.  In this case
    the user quietly ran out of string room and nothing else happened.
    
    David 
    
    P.S.  BL8 and V10 are so vastly superior to BL7, that I strongly
    urge everyone to convert as soon as possible.