Conference vaxuum::document_ft

884.0. "INPUTBAD error - cannot find source" by CUPOLA::HAKKARAINEN (Days of Mackerel and Flounder) Tue Sep 08 1987 14:32

    The .lis file following the formfeed shows Document falling over
    during the very last part of the device conversion stage. This file
    processed fine under bl7. I welcome any suggestions.
    
    The index, when processed alone, looks fine. 
    
    kh
    
%DOC-I-IDENT, VAX DOCUMENT V1.0
[ T a g   T r a n s l a t i o n ]...
%TAG-I-TAG_IDENT, V1.0
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-FMTDEVICE, Tag <PAGE> produces device-specific output.
%TAG-I-ENDPASS_1, End of first pass over the input
%TAG-I-FILEWRTOK, File LSP_FRONTMAT.TEX written
%TAG-I-FILEWRTOK, File LSP_CH1.TEX written
%TAG-I-FILEWRTOK, File LSP_CH2.TEX written
%TAG-I-FILEWRTOK, File LSP_CH3.TEX written
%TAG-I-FILEWRTOK, File LSP_CH4.TEX written
%TAG-I-FILEWRTOK, File LSP_CH5.TEX written
%TAG-I-FILEWRTOK, File LSP_CH6.TEX written
%TAG-I-FILEWRTOK, File LSP_CH7.TEX written
%TAG-I-FILEWRTOK, File LSP_CH8.TEX written
%TAG-I-FILEWRTOK, File LSP_AXA.TEX written
%TAG-I-FILEWRTOK, File LSP_AXB.TEX written
[ T e x t   F o r m a t t i n g ]...
%TEX-I-IDENT, V1.0
%TEX-I-INFO, loading CUP fonts, SET1, for ln03 output - on page [1]
%TEX-I-INFO, Possible table paging problem. - on page [xii]
%TEX-I-LINETOOLONG, Line too long by 19.17008 points
-TEX-I-ONPAGE, on page [7-2] 


%TEX-I-LINETOOLONG, Line too long by 28.58688 points
-TEX-I-ONPAGE, on page [7-2] 


%TEX-I-LINETOOLONG, Line too long by 9.40864 points
-TEX-I-ONPAGE, on page [7-2] 


%TEX-I-LINETOOLONG, Line too long by 18.0 points
-TEX-I-ONPAGE, on page [7-2] 


%TEX-I-LINETOOLONG, Line too long by 43.22904 points
-TEX-I-ONPAGE, on page [7-3] 


%TEX-I-LINETOOLONG, Line too long by 4.33188 points
-TEX-I-ONPAGE, on page [7-4] 


%TEX-I-LINETOOLONG, Line too long by 4.33188 points
-TEX-I-ONPAGE, on page [7-4] 


%TEX-I-LINETOOLONG, Line too long by 1.4309 points
-TEX-I-ONPAGE, on page [B-2] 


%TEX-I-INFO, Possible table paging problem. - on page [B-13]
%TEX-I-LINETOOLONG, Line too long by 9.23012 points
-TEX-I-ONPAGE, on page [B-28] 


%TEX-I-INFO, Possible table paging problem. - on page [B-29]
%TEX-I-INFO, Possible table paging problem. - on page [B-30]
%TEX-I-LINETOOLONG, Line too long by 6.5080 points
-TEX-I-ONPAGE, on page [B-35] 


%TEX-I-LINETOOLONG, Line too long by 6.5080 points
-TEX-I-ONPAGE, on page [B-35] 


%TEX-I-LINETOOLONG, Line too long by 6.5080 points
-TEX-I-ONPAGE, on page [B-35] 


%TEX-I-INFO, <PAGE> ignored in floating figure. - on page [B-35]
%TEX-I-INFO, Figure is too large for a single page. - on page [B-35]
%TEX-I-LINETOOLONG, Line too long by 25.22904 points
-TEX-I-ONPAGE, on page [B-37] 


%TEX-I-PAGESOUT, 177 pages written.
-TEX-I-OUTFILENAME, 'swdoc1:[library.vaxlab.lsp]LSPPROFILE.DVI_LN03'
[ C o n t e n t s   G e n e r a t i o n ]...
[ T e x t   F o r m a t t i n g   C o n t e n t s ]...
%TEX-I-IDENT, V1.0
%TEX-I-INFO, loading CUP fonts, SET1, for ln03 output - on page [1]
%TEX-I-PAGESOUT, 6 pages written.
-TEX-I-OUTFILENAME, 'swdoc1:[library.vaxlab.lsp]LSPPROFILE_CONTENTS.DVI_LN03'
[ I n d e x   G e n e r a t i o n ]...
%INX-I-IDENT,  V1.0
%INX-I-ENDPASS_1, End of first pass over the input.
%INX-S-ENDPASS_2, End of second pass over the input.
%INX-S-CREATED, 'SWDOC1:[LIBRARY.VAXLAB.LSP]LSPPROFILE_INDEX.TEX;1' created
[ T e x t   F o r m a t t i n g   I n d e x ]...
%TEX-I-IDENT, V1.0
%TEX-I-INFO, loading CUP fonts, SET1, for ln03 output - on page [1]
%TEX-I-PAGETOOSHORT, Page too short - on page [INDEX-3]
%TEX-I-PAGESOUT, 3 pages written.
-TEX-I-OUTFILENAME, 'swdoc1:[library.vaxlab.lsp]LSPPROFILE_INDEX.DVI_LN03'
[ D e v i c e   C o n v e r s i o n ]...
%DVC-I-IDENT, DVC$LN03 V1.0ti
%DVC-I-INCLUDING, including input file: 

   SWDOC1:[LIBRARY.VAXLAB.LSP]LSPPROFILE_CONTENTS.DVI_LN03;
%DVC-I-INCLUDING, including input file: 

   SWDOC1:[LIBRARY.VAXLAB.LSP]LSPPROFILE_INDEX.DVI_LN03;
%DVC-E-INPUTBAD, bad input file -- aborting run
-DVC-I-INPUTFILE, input file is: 

   SWDOC1:[LIBRARY.VAXLAB.LSP]LSPPROFILE.DVI_LN03
-DVC-I-ONPAGE, on page [INDEX-3] 

 


DOCUMENT  LSPPROFILE S.H LN03/CONT/INDEX/LIST
Date/Time:  8-SEP-1987 13:17:58.71
CPU time: 2313.42 secs.
    

    The release notes describe a similar case of a large document with
    an included index that fails after the last page of the index.
    
    I don't know why such a document fails (it has to do with splitting
    up font loads, at least in our case), but the workaround should
    be DOCUMENT/DEVICE_CONVERTER=(ENDING_PAGE=INDEX-3) or whatever
    your last page happens to be.
    
    --Mark

    Thanks. The /device=etc. fixed the problem. Interesting that this
    shows up in V1.0; the book runs fine under bl8.
    
    I'm trying the same book with the postscript destination. Will report
    any interesting results.

    Dunno if it's related, but the same job chokes when run under
    Postscript. It processes, but the LPS40 aborts with an name not
    known error for dOblique-DOCPSE.
    
    It appears that a wicked long line is created, longer than 256
    characters. It breaks, leaving the Oblique item as a fragment.

    RE: failure in PostScript
    
    Chances are this is the same thing that was reported in printing
    the VAX DOCUMENT user's guide (or one of those) -- the file
    prints fine, but at the next-to-the-last line the file contains a
    comment that lists the fonts used in the document.  When this comment
    line reaches a certain length, the device converter output routine
    blindly throws out a newline and continues.  Since the continuation
    is NOT marked as a comment, the PostScript interpreter tries to
    execute it.  So your analysis of the problem is correct.
    
    As a workaround, you can edit the .POST file.  Move to the end of
    the file, then go up a couple of lines to the broken line, which
    follows the line starting with 
    
    		%%DocumentFonts: ...
    
    Insert these three characters at the start of the broken line: 
    
    		%%+
    
    (Actually, all you need is one percent sign, but putting in the
    three symbols corresponds to what the device converter will do when
    we fix the problem.)
    
    (And, for your information, the trouble you get in your PostScript
    output is unrelated to the trouble you get in your LN03 processing.
    It just happens that you have a large, font-rich document that 
    triggered both errors.  Can I have your DVI files to test the fixes,
    once we've done them?)
    
    Thanks,
    Mark

    Re -1:
>                           Can I have your DVI files to test the fixes,
>   once we've done them?)
    
    Well, if you really need them ...
    

    RE:  		-< Font rich and output poor >-
    
    
    Given the workarounds, I'd modify that to read
    
    			-< Font rich and output clumsy >-