Conference vaxuum::online_bookbuilding

249.0. "Error in \special" by UTROFF::OOSTENDE () Thu Jan 04 1990 07:06

Hello,

I'm a first-time user of the BOOKREADER application. I'm having an
SDML source file with a score of .FSE and two .DECW$BOOKFIG graphic 
files included. The bookbuild goes OK, except for the .DECW$BOOKFIG 
files. I get the following error messages:

DVC-W-SPECIALERROR, error in \special
   voila: plotfile  zk-9279.decw$bookfig
-DVC-W-FIGNOTFND, cannot find figure image in figure file
-DVC-I-INPUTFILE, input file is:
   USER4:[OOSTENDE.BKRDR_TEST]5176_STYLEFILES.DVI_BOOKREADER;
-DVC-I-ONPAGE, on page [16]

%DVC-W-SPECIALERROR, error in \special
   voila: plotfile  zk-9274.decw$bookfig
-DVC-W-FIGNOTFND, cannot find figure image in figure file
-DVC-I-INPUTFILE, input file is:
   USER4:[OOSTENDE.BKRDR_TEST]5176_STYLEFILES.DVI_BOOKREADER;
-DVC-I-ONPAGE, on page [16]
 
Both files are printed correctly on an LPS40 PostScript printer.
They are in the same directory as the other files used in the
bookbuild, and they have the same protection. 

What can be wrong with them? You can have a look at the files in
UTES01::USER4:[OOSTENDE.BKRDR_TEST]. The source file is called
5176_STYLEFILES.SDML. File 5176_STYLEFILES.LIS can be viewed as 
well. (BTW: the above-mentioned error messages are not part of
the .LIS file. These are DVC messages, and DOCUMENT only puts 
tag translation and text formatting messages in the .LIS file.
Isn't that strange?) 

DOCUMENT version: 1.1
Doctype: ONLINE.HAND
Online bookbuilding tools, 20-MAR-89 baselevel


Thanks,
Martin

    Martin,
    
    The error message you're getting means the DVC can't find any image
    data that it knows about in the named file.
    
    I only checked one of the .decw$bookfig files but as I suspected
    it's a postscript file and we don't do postscript in the bookreader.
    
    At the baselevel you're running the device converter isn't really part
    of Document and doesn't communicate with it so no messages are passed
    back to it. Run the build  /batch and the DVC messages will be in the
    .log file. 
    
    
    
    MIke

Hello, 

We have solved the problem. It proved that we had defined some 
incorrect coordinates when creating the files with MOPS. I guess that's
why they remained postscript files. After 
reprocessing everything went OK.

Thank you,
Martin