[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

224.0. "Quirks with LPR output" by SARAH::P_DAVIS (Peter Davis, X-NYer) Wed Apr 08 1987 15:54

    I know it's hard to believe, but there are still uses for line printer
    output from DOCUMENT.  I've been using this a little recently, and
    have a couple of nits to pick.
    
     -	Why doesn't LPR output look like DSR output?  DSR manages to
    	do margin justification, etc. even with monospaced text.  I
    	would like to see DOCUMENT do that
    
     -	<SUBHEAD2> becomes unreadable, at least with the GENERAL doctype,
    	in LPR output.  For LN03 (or PostScript) output, the subhead
    	title is distinguished by a bolder typeface.  Without that luxury,
    	putting the subhead title on the same line as the text makes
    	it unreadable.
    
     -	The <NEWTERM> and <EMPHASIS> tags seem to map onto underlining
    	for line printer output.  I have no problem with that, but I
    	do have a suggestion about the way it's implemented.  Currently,
    	it looks like the underlining is done by outputting a sequence
    	like:
    
    	text of line containing the __________ _____.<CR>
    	                            underlined words
    
    	This means that if you type the file to the terminal screen,
    	all you see is:
    
    	                            underlined words.
    
    	How about outputting the horizontal spacing and the underlining
    	first, followed by <CR> and the full text of the line.  I think
    	DSR made this fix somewhere along the line to improve readability.
    
     -	My GNC file contains a sequence like <MATH>(<FRACTION>(1\72)).
    	This prints correctly in LN03 output, but is totally unreadable
    	in line printer output.  Instead of getting "1/72", I get an
    	underlined "72", with the "2" overstriking a "1".
T.RTitleUserPersonal
Name		DateLines
224.1SARAH::P_DAVISPeter Davis, X-NYerWed Apr 08 1987 16:185
    And another thing:
    
     -	Why can't I get a table of contents in my LPR file?  I used
    	the same procedure which worked for LN03 output, but the table
    	just isn't there.
224.2CommentsVAXUUM::DYERI Park at Mrs. Nelson&#039;s Candy HouseThu Apr 09 1987 12:5113
I believe margin justification for monospaced text is not provided because
 it's real ugly.

As for the underlined words, perhaps it would be better if it were done this
 way:

	_^Hu_^Hn_^Hd_^He_^Hr_^Hl_^Hi_^Hn_^He_^Hd _^Hw_^Ho_^Hr_^Hd_^Hs

(that's how the Unix "roff" programs do it, sorta).  If you want to type the
 file to the terminal, though, you're better off using the TERMINAL destination
  (same DVI converter as the line printer, so you can use the .DVI_LPR file
   and run it /NOTAG/NOTEXT).
    <_Jym_>
224.3CLOSET::ANKLAMThu Apr 09 1987 16:187
    
    The inclusion of table of contents and index files is not available
    in line printer output. This was noted in the release notes.
    
    Will add your comments on line printer output to the list...
    
    patti
224.4SARAH::P_DAVISPeter Davis, X-NYerFri Apr 10 1987 12:3022
    Re/ .2:
    
    I don't find right justified monospaced text particularly ugly.
    Obviously it doesn't compare with proportional text, but people
    have been using DSR for years and have obtained satisfactory results.
    
    There is a great need to be able to MAIL to TYPE documents which
    are LPR formatted.  I don't believe it should be necessary to create
    separate TERMINAL, MAIL, and LPR copies of every document you want
    to distribute.  DSR handles all three adaquately.  I think DOCUMENT
    should too.
    
    Re/ .3:
    
    Is there any reason why tables of contents are not available?  I'm
    sorry I don't have a copy of the release notes.
    
    I really like DOCUMENT, but if you want to capture the internal
    DEC users market, then LINE_PRINTER output should be at least equal
    to DSR, including tables of contents, etc.
224.5release note comment only.VAXUUM::KOHLBRENNERFri Apr 10 1987 13:025
    Peter, for the relase notes, you should be able to queue a copy
    of SYS$HELP:DOC010.RELEASE_NOTES  (on a line printer :-) ).
    
    bill
224.6More possibilities than you knowCOOKIE::JOHNSTONFri Apr 10 1987 13:555
You can also create in terminal and mail it; you just have to forwarn people to 
do an extract tt and make sure there's a <ff> preceding the text.


Rose
224.7CUPOLA::HAKKARAINENAlbatross!Mon Apr 13 1987 15:2210
    DSR gave us troubles when we tried to mail those .mem files (those
    blessed crlfs). Since mail took away the ability to include video
    attributes, we've needed differing versions for terminal and mail.
    (DSRplus also gave us versions for different output devices.)
    
    All of the display features from DSR[plus] are in the monospaced output
    options in Document. Unfortunately, we still have the same devices
    with the same limitations, requiring differing solutions.
    
    kh