Conference vaxuum::document_ft

    This problem is decribed in the release notes (they are the file
    DOC010.RELEASE_NOTES in the documenation copy area).
    
    Sorry if my earlier note seemed inaccurate:the problem is that the
    font dictionary in the LPS40 is running out of room, whether this
    is DOCUMENT's problem for trying to shove too much in, or the LPS40's
    for not having enough of that sort of memory is a discussion I'll
    leave to someone with a more philosophical bent than I.  
    
    In any case, if you print the the User manuals using the broken
    up versions as described in the file A.read_me_first, you should
    have no problems,
    
    -randy

    Splitting vol 1 into two pieces is great as far as you went, but
    the second piece is not yet small enough. Can you resplit it more
    equally, or in three pieces? 
    
    Are we always going to have this sort of problem with large
    documents??? We are going to have a lot of large documents, 
    and hopefully we won't have to split them up. 
                                         
    I have not printed the second half of vol 2 yet, but it is smaller,
    so it should work.
    
    Did you guys actually try printing this stuff before you announced
    it? 8-)
    
    Ken Serack
    DECwest Engineering

    Vol 2 doesn't print either! However, it produces a different error.
    	LPS-W-UNDEF, undefined: Name not known - offending command
    		is turySchlbk-Bold-DOCPSE
    
    Can you please fix both vol 1 and 2.
    
    Ken

    A follow up note to .2 and .3  I AM using the split up version of
    both Vol 1 and Vol 2.
    
    Ken

    We *did* test print everything before we copied it into that area---it
    all printed fine on our LPS40.  Where (approx page-number) did your
    print job of the User Manual volume 1, second file die?  This info
    can tell me where to place the next split.
    
    The different error you got from printing the second half of the
    user manual volume 2 does not effect your printing of that file---you
    should have gotten all of that book.  What happened was that because
    we use so darn many fonts, we underestimated how long our comment
    line would be at the end of the .POST file--the error message you
    got was caused by a comment about the fonts overflowing the comment
    area and getting into the output stream.  Sorry about that, but
    it *is* safe to ignore it.
    
    -randy

    Vol 1 printed all pages  up to and including D-14.
    Vol 2 printed all pages  up to and including Index-6.
    
    Thanks
    Ken
    
    Don't take my complaining TOO seriously. Didn't you see the Smiley
    Face? 8-)

    I am really curious how you printed the complete file on your LPS40.
    Or did you print all of the elements separatly? Why does putting
    it in a public directory make it not print?
    
    Ken

    Thanks for the page info Ken, looks like you got all that was there.
    (unfortunately the User manual vol 1 didn't include an index in
    that file...I'll be putting its index in the copy area on VAXUUM
    and on NEWDOC shortly).
    
    I never did get a complete printing of the entire .POST file on
    our LPS40, but I posted the file  just the same in case it was only a local
    problem.
                                     
    I did see you smiley face Ken, it was just that at that point I
    was having particularly unpleasant thoughts about .POST files...
    
    again, thanks for the info,
    
    -Randy

    Thanks for the quick response to this problem. Apparently vol 2
    printed completely. I got an error message and assumed that the
    last pages of the file were lost. The index does indeed end with
    V. Vol 1 did not have an index so I though it was missing. Everything
    is ok now.
    
    Thanks
    Ken

    The index you mention is part of the User Manual Vol 1 .LN03 file
    but is absent in the .POST file.  Its there now (both on VAXUUM::
    and on NEWDOC::) as V1_USER_MAN_VOL_1_INDEX.POST.
    
    By the way, any general questions about the docset or kit should
    be done as replies to note 1 where everything gets announced.
    
    -randy

I got both volumes of the User's Manual to print without dividing them up.
I did it by editing the PostScript file. For each manual, the first line
of the PostScript file that doesn't begin with a comment character (%)
includes the command "200 dict def".  As the error message had indicated
that there wasn't enough room in the dictionary, I changed the 200
to 500.  Then manual then printed with no problem.
    
Kathy

    Re: .1: Please don't malign the LPS40, when in fact the problem is with
    the PostScript output. As Kathy points out in .-1, the dictionary that
    is full is not some built-in LPS40 dictionary, but your own dictionary.
    Simply increasing its size as Kathy did will make life easier for your
    customers, although it won't truly fix the problem, since it can still
    overflow. The real fix will be to track how many fonts you have defined
    and cut them back when you reach a certain limit.
    
    (BTW, another fix that will slow the filling of your dictionary
    would be to modify the definitions of DNF and DF in your prolog
    to add only one name to the dictionary, rather than two.)

    I apologize if I  cast aspersions on the LPS40. Re .11 and .12,
    you are quite correct, the printing failure is a fault in the 
    PostScript file DOCUMENT  creates, not in the LPS40 that processes
    it--I was unfamiliar with the error message and misread its meaning.
    
    Thanks for the suggested fixes,
    
    -Randy

>    I apologize if I  cast aspersions on the LPS40.
    
    Yes, aspersions, if cast, must be cast on the VAX DOCUMENT PostScript
    converter developer, the VDPSCD.  :-)
    
    --Mark DeVries,
      VDPSCD

    I changed "dict def" to 600 and 500, respectively for User's Manual
    Vol 1 and Vol 2, and both appear to have printed OK. However, both
    terminated with an error status. I didn't capture the error message
    for Vol 2, but the Vol 1 error message follows:
    
    %LPS-W-UNDEF, undefined: Name not known - offending command is ammi10
    %LPS-E-FLUSHING, Rest of Job (to EOJ) will be ignored
    %LPS-I-JOBFINISH, Job 1719 Finish

    This is just for "somebody's" information; again, the books appear
    to be complete.
    
    Joe

    Reply .5 and others make some reference to this problem, in which
    the whole book prints and then you get an "undefined" message with
    all or part of a font name listed as the offender.
    
    Here is the explanation:  Near the end of the .POST file is a comment 
    (%%DocumentFonts) which lists the fonts used.  The list was so long that
    the device converter split it in two, which made the PostScript
    interpreter think the continuation was a bogus instruction.
    
    The document prints okay, but the error message is disconcerting.
    We will change these files for the benefit of those who copy them
    in the future, and we apologize for the inconvenience and uncertainty
    this has caused many of you to date.  (And, of course, we'll fix
    the device converter in the next go-round, too.)
    
    --Mark

    The two user manual files V1_USER_MANUAL_VOL_1.POST and 
    V1_USER_MANUAL_VOL_2.POST in VAXUUM::[sdml.v10] have been fixed and
    should print without error.  We'll be copying them over to
    NEWDOC::[SDML.V10] shortly...
    
    -randy