Conference vaxuum::document_ft

    I have run a few tests using PostScript output, with very pleasing
    results. I also ran some experiments including RENDER output and
    PostScript bitmapped images as figures. 
    
    --Andrew

I've been running with output to POSTSCRIPT, with no particular problems.
Since it works just as advertised, I haven't complained about it!

					I

    Works great on the LN03R, particularly with GRED pictures as boith
    figures and icons.
    
    jack

    I'll add my voice too.  We're using PostScript and, for the most
    part, everything is going well.  We're using the sixel-to-PostScript
    bitmap translator written by Andrew Gent to do our screens, and
    GRED for all our figures.  Those tools are working great.
    
    Where we are having trouble is trying to include PostScript files
    created on other systems (VALID for example).  We also need a
    PostScript version of the Digital logo, and a few other things our
    system manager is working on.
    
    By the way, all you PostScript users might want to start checking
    out the new generation of PostScript high resolution "plain paper 
    typesetters".  Agfa makes one (sold by Compugraphic) that outputs
    400dpi @ 18ppm - $30,000, and Varityper just announced their 600dpi 
    machine that outputs @ 10ppm - $18,750.  I've seen output from the 
    Varityper machine, and it looks quite good, not quite phototype 
    quality, but good.
    
    -- Craig
    

    I've already reported a problem in this notes file concerning use
    of certain <MATH_CHAR>s in PostScript output.  In particular, the
    <MATH_CHAR>(DELTA) appeared as a blob of ink, although it worked
    ok on LN03 output.  Also, a lowercase "a", used as a variable inside
    a <MATH> string, was printed as a blob in PostScript, although it
    worked fine on the LN03.
    
    Another problem I've noticed is that the PostScript uses smaller
    text, and more of it per page, than LN03 output.  I think the LN03
    output is easier to read.
    
    By the way, I'm printing both the PostScript and LN03 output on
    an LPS40, using the ANSI option for the LN03.
    
    -pd

    Thanks for the votes of confidence (.1-.4).  
    
    Re .5: Peter, let me see if I understand your problem correctly.
    The problem looks like;
    
    DOCUMENT <MATH_CHAR>(DELTA) and "a" --> ANSI(aka LN03) --> .PS 
       prints OK on LPS40, but
    DOCUMENT <MATH_CHAR(DELTA) and "a"  --> .DVI --> .PS  
       does not print OK on the same LPS40 (and furthermore with smaller
    text).
    
    Looks to me like the glitch is in the .dvi-to-.ps translator of
    document, since the same source works good through the ansi-to-.ps
    translator and prints OK through the PostScript interpreter in the
    LPS40.  Same thing about the smaller text; looks like the .dvi
    translator is calling for a smaller scalefont than the ansi translator.
    
    
      John

    Re/ .6:
    
    	What are you saying?  That it's not a PostScript problem?  I
    	never thought it was.  I assumed it was a problem in the device
    	conversion part of DOCUMENT.  That's why I reported it here.

    I agree with .5, however, that the LN03 output for most document
    styles is easier to read that the PostScript output.  Except for
    the type size, PostScript would win easily over LN03 for readability.
    
    I expecially like the look of code_examples in Post Script.

    The DIGITAL logo under doctype MEMO and postscript comes out with
    black letters in a white background, the reverse of the LN03.
    
    I (and others) prefer the latter.
    

    The logo is different on PostScript because we don't currently have
    the reverse typeface. You'll also notice that PS callouts aren't
    what you've seen printing via the LN0x printers (same reason).
    The monospace typeface is COURIER. It's also the LN03 monospace
    that will be shipped with V1.0.
    
    Lee 
    

    I have a problem with both the postscript and the LN03 printers.
    Sounds like a cockpit setup problem but don't know what it can be.
    When I submit a job to the postscript printer either from the document
    command line or by PRI/QUE=....doc.ps, I get the postscript code
    printed instead of the document.  With the LN03 I get blank space
    in the doc where it should not be; i.e. near the bottom of the page
    the printer will form feed and continue printing at the correct
    column and line thus leaving lots of white space.  I've setup the
    printer per the installation guide but alas...
    
    Any ideas here ??
    -fred

    re. 11:
    
    >When I submit a job to the postscript printer either from the document
    >command line or by PRI/QUE=....doc.ps, I get the postscript code
    >printed instead of the document.  
    
    The default input type on the PostScript print queues is ANSI. 
    If you want your output executed as a PostScript program (and you
    do), queue it to a PostScript generic queue (if you have one)
    or add this qualifier to your PRINT statement:
    
    		/PARAM=DATA=POST
    
    >With the LN03 I get blank space
    >in the doc where it should not be; i.e. near the bottom of the page
    >the printer will form feed and continue printing at the correct
    >column and line thus leaving lots of white space.  
    
    I'm not sure I understand the symptoms, but I will suggest this:
    Are you using /NOFEED/PASSALL on your PRINT command to the LN03?
    Are you using a document design intended for paper longer than
    11 inches? (Probably not.)  Does this occur on pages that are
    text-only, or are you talking about pages with included sixel figures?
    (These may have white space that makes them longer than they appear.)
    
    Mark

    re .12  THANKS !!
    The /NOFEED/PASSALL seemed to fix the LN03 problem.
    
    Someone had commented out the LPS$STARTUP.COM line in the systartup
    command file.
    
    tks,
    -f