[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

519.0. "Finding LINETOOLONG's" by DELNI::TURBETT () Wed Jun 17 1987 12:02

    I'm getting a lot of "Line too long" error messages.  I'd love to
    fix the offending tables, but the .lis file gives me no indication
    of the location of the offenders within my document.
    
    Any hints on how to locate these?
T.RTitleUserPersonal
Name		DateLines
519.1me too...CHAPLN::ROSENTHALI REALLY need a vacation!Wed Jun 17 1987 13:385
    
    
    I'm looking for this info, too...
519.2Beauty in the eye of the documenterCOOKIE::JOHNSTONWed Jun 17 1987 15:0916
Re: .0 and .1


The line-too-longs are only too long if they are *visibly* too long in your 
final output.  TeX is complaining about what *it* thinks is aesthetically
displeasing.  Per earlier replies to similar messages, note that there are
72 points to an inch, so if TeX complains that a line is too long by 7 points, 
chances are it isn't noticeable.

Study your .LN03 (or whatever) output; if there is nothing visually 
displeasing, you can ignore the errors.

In BL8, TeX even complains about "too short" lines!


Rose
519.3A thorn grows in NashuaWRONGO::PARMENTERVenusian or Venerean?Wed Jun 17 1987 15:2826
    There is a small class of TeX errors which can be kind of frustrating,
    because there isn't neccesarily anything *wrong* with your tex file.
    These are essentially the following: LINETOOLONG, LINETOOSHORT,
    PAGETOOLONG, PAGETOOSHORT, TOOMANYLINES, TOOFEWLINES, WIDESPACING,
    and TIGHTSPACING.  In all of these cases, TeX is indeed complaining
    about things which it finds "aesthetically displeasing".  Sometimes
    there are logical explanations, for these errors, and sometimes
    not.  Common culprits are forced page breaks, or misuse of tags
    which fool around with things that affect the whole page, or weird
    tables (syntactically correct from the tag translator's point of
    view, but troublesome from TeX's point of view.  The other COMMON
    culprit is trying to run something for the line printer which was
    originally coded with the LN03 in mind (we advertise generic coding,
    but monospaced-ness is really unforgiving alas.)
    
    This is definitely a thorn in our side which we can't do much about
    for V1.0 .  One problem is that we don't really want to encourage
    poking about in the TeX file, but that is just what we do with the
    8 errors listed above.  As .2 ably points out, your best bet is
    to inspect your output.
    
    David Parmenter
519.4Post V1.0 suggestionBUNSUP::LITTLETodd Little NJCD SWS 323-4475Thu Jun 18 1987 02:009
    I don't remember if this has been suggested before but it would
    certainly be a nice post V1.0 addition.  TeX normally dumps the
    offending line(s) to the log file or terminal for these types of
    warnings.  Could those lines be included in the .LIS file?  Right
    now it seems that the .LIS doesn't provide a whole lot of extra
    information that one is accustomed to with listing files.
    
    -tl
519.5suggestion notedWRONGO::PARMENTERVenusian or Venerean?Thu Jun 18 1987 10:2616
    We are definitely going to upgrade TeX's diagnostic capabilities
    post V1.0 .  This will include some sort of map of the input files
    as they are read, and presumably an option to do something along
    the lines of .4 .  As more users come on line as capable doctype
    designers, we will have to suspend our previous wish to discourage
    users from poking about in the teX file.
    
                                            
    David Parmenter