Conference vaxuum::document_ft

    
    Yes, we are going to fix that. Meantime, you can use the
    \setlpdesign macro in any design file (some design files already
    have some settings for these). The default for \hoffset is 49pt, but this
    wasn't corrected when the driver was given a default starting
    position of 1inch from the left edge of the paper. 
    
    Here's a batch of changes I've been looking at:
    
    \global\def\setlpdesign{%
       \gutterwidth=0pt%          override LPCHARS default setting
       \hoffset=0pt 
       \hsize=32pc% decrease slightly
       \physicalpagewidth=\hsize% reset for new value
       \setblockindents{0pc}%
       \vsize=40pc
       \postsubheadonevskip=18pt% vertical skip following <subhead1>
    % Change font specs to use ragged right
       \def\normaltextfontspecs{\tenpoint\raggedrightspacing}%
       \def\tablefontspecs{\ninepointss\raggedrightspacing}%
       \pretolerance=10000% don't bother width hyphenation
     }
    
    
    These seem to work pretty well for the REPORT (aka GENERAL) style.
    I don't guarantee them for any others.

    You can move the page image to the left by specifying the
    /DEVICE_CONVERTER qualifier with the HORIZONTAL_OFFSET keyword and
    some value less than 72.  (This is specified in points, where 72
    points = 1 inch, and 72 points is the default currently known to
    the device converter.)
    
    For instance, 
    	$ DOCUMENT /DEVICE=(H=36) ...
    will move your page a half-inch to the left.
    
    This will NOT change the formatting of the page -- the line breaks
    will stay as they are.  The ultimate solution is to change the doctype,
    etc., as described in the previous note -- but this will allow you
    to position the existing text area at some place more to your liking.
    
    NOTE:  Some things make use of that left margin: I know that change
    bars and \WIDE structures use that space (but, of course, change
    bars don't yet exist in the monospaced output), so if you use something
    that falls into that space, you could push it right off the page.
    But for relatively simple documents, the HORIZONTAL_OFFSET keyword
    may give you satisfactory results until the *real* solution arrives.
    
    Mark

	I made the changes listed in .1 to the CUP$MEMO.DESIGN file, but
they seem to just move the page to the left. I'd also like to increase the total
width of the page, so that the right margin stays where it was. What parameter
should I tweak to do this?

To increase the total width of the page, increase the value of \hsize.

--Brian

    Why do both MAIL and LINE_PRINTER output start with a form feed?
    Since I frequently print these on my local printer, I don't like
    having a page wasted all the time.
    
    -pd

  > Why do both MAIL and LINE_PRINTER output start with a form feed?
    
    Fixed in V1.0.
    
    --Mark

    I taught one of our engineers how to use DOCUMENT, so he's
    been using it instead of RUNOFF. Now we have a problem. He
    wrote several design specs using the <display> tag. Up until
    now, he has processed all the specs with LN03 as the
    destination and has had no problems. Well, now he wants to
    put the spec in the notes file, and is using MAIL as the
    destination. He gets the following errors: 

 T e x t   F o r m a t t i n g ]...
%TEX-I-IDENT, V1.0
%TEX-I-LINETOOLONG, Line too long by 168.65462 points
-TEX-I-ONPAGE, on page [1] 

%TEX-I-LINETOOLONG, Line too long by 161.65463 points
-TEX-I-ONPAGE, on page [1] 

%TEX-I-LINETOOLONG, Line too long by 140.65466 points
-TEX-I-ONPAGE, on page [1] 


------------------------------------------------------------

    Here is the source file:


<head1>(Control Flow in the RECORD Subsystem for DECwindows Tests)
<p>
<display>

  --------------- "DTM's transport will monitor all client / X server I/O. 
  |    DTM's    | When it sees the termination character, it will send it
  | Specialized | to the record subsystem client, thus awakening it to
  | X Transport | process commands."
  ---------------
<enddisplay>


----------------------------------------------------------


    The MAIL destination cuts off several letters in each line. I
    tried using the /device=(h=36), but it didn't help. The only
    way I know of to work around this was to manually go in and
    change the files. 

    Is there some other way to process this so it will appear on
    the screen the way I want it to?  (Terminal doesn't work either.)

    
    The amount that the text is indented varies; some doctype/DESIGN
    files would look better than others. I processed the file as
    follows and the results were acceptable:
    
    $ DOCU file SOFT.SPEC TERM/DEVI=(H:0)
    
    H:0 puts all the text flush left, and looks fine on the screen (or
    would also be okay for MAIL.)