| 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 | 
        I am just beginning to learn DOCUMENT and want to use it
        first to make some overheads.  The basic overhead is pretty
        easy and I love the results, but I am stuck trying to use
        a figure.
        
        I think what I want is:
        
        <SLIDE>
        <TOPIC>(FOOBAR Conceptual Diagram)
        <FIGURE>
        
        +-------------------------------------------------------+
        |                                                       |
        | nifty diagram done with hyphens and vertical bars and |
        | plus signs, etc. on terminal screen.                  |
        |                                                       |
        +-------------------------------------------------------+
        <ENDFIGURE>
        
        but I get lots of LINE_TO_LONG warnings,(which I have already
        read about in a previous note), and finally an error.
        
        The portion of the .LIS file is listed below.
        
        Thanks for any help you can provide.
        
        mark
%TEX-E-TEXERROR, Error found by TeX
%TEX-I-ONPAGE, on page  [1]
%TEX-I-OUTFILENAME, 'disk$dragon3:[mhyde.document]X.DVI_LN3'
.
<to be read again> 
                   {
\variablewindow #1#2->{
                       \par \MACdimenA =\pagegoal \advance \MACdimenA by -\p...
\startfigure ...w {\MACdimenB }{\backuppagebreak }
                                                   \fi \vskip \prefigurevski...
l.35              {}
                    %if fig is not floatable, window value
A number should have been here; I inserted `0'.
(If you can't figure out why I needed to see a number,
look up `weird error' in the index to The TeXbook.)
%TEX-E-TEXERROR, Error found by TeX
%TEX-I-ONPAGE, on page  [1]
%TEX-I-OUTFILENAME, 'disk$dragon3:[mhyde.document]X.DVI_LN3'
pt inserted).
<to be read again> 
                   {
\variablewindow #1#2->{
                       \par \MACdimenA =\pagegoal \advance \MACdimenA by -\p...
\startfigure ...w {\MACdimenB }{\backuppagebreak }
                                                   \fi \vskip \prefigurevski...
l.35              {}
                    %if fig is not floatable, window value
Dimensions can be in units of em, ex, in, pt, pc,
cm, mm, dd, cc, bp, or sp; but yours is a new one!
I'll assume that you meant to say pt, for printers' points.
To recover gracefully from this error, it's best to
delete the erroneous units; e.g., type `2' to delete
two letters. (See Chapter 27 of The TeXbook.)
) [1]
%TEX-I-PAGESOUT, 1 page written.
%TEX-I-OUTFILENAME, 'disk$dragon3:[mhyde.document]X.DVI_LN3'
        
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 226.1 | You can see what I've done | COOKIE::JOHNSTON | Thu Apr 09 1987 12:04 | 12 | |
| I've done figures in overheads with very nice results, including sixels, 
picmode, and plain old line art.  You're welcome to copy the relevant 
files and to examine what I have done, from :
COOKIE::DISK$FIG_4:[JOHNSTON.CLASS.SLIDES]FIGURES.GNC
                                          EXAMPLE.SIX
                                          KEYBOARD.TEX
Rose
 | |||||
| 226.2 | OASS::M_HYDE | From the laboratory of Dr. Jekyll | Thu Apr 09 1987 12:12 | 5 | |
|         Thanks much!  A quick look at FIGURES.GNC and I think
        I see what I have to do.
        
        thanks again,
        mark
 | |||||
| 226.3 | looks like you need LINEART tags | ATLAST::BOUKNIGHT | Everything has an outline | Thu Apr 09 1987 13:38 | 3 | 
|     What did you do to fix it?
    
    jack
 | |||||
| 226.4 | needed <line_art> | CLOSET::ANKLAM | Thu Apr 09 1987 15:21 | 18 | |
|     
    I suspect that the fix was in adding text element tags around the
    line art, ie.
    
    <figure>
    <line_art>
       ...
    
    <endline_art>
    <endfigure>
    
    This is in the category of a  figure that has no elements (where
    the <figure> tags expect only tags of a certain type). I was going
    to make that a W-level message, but if this is a common type of
    problem, perhaps I should make it an E ?
    
    patti
    
 | |||||
| 226.5 | yup | OASS::M_HYDE | From the laboratory of Dr. Jekyll | Thu Apr 09 1987 23:07 | 12 | 
|         Yes, the line art tags took care of it.  I suppose I just
        didn't completely understand the documentation.  It appeared
        that <figure> <endfigure> would just take whatever was between
        and give it to you literally.
        
        Anyway, problem solved.  I'm getting more time to read the
        manuals.  I've never used anything like this before and so
        far, with the manuals handy, I think I'm catching on pretty
        well.
        
        regards,
        mark
 | |||||
| 226.6 | another question | OASS::M_HYDE | From the laboratory of Dr. Jekyll | Fri Apr 10 1987 16:39 | 23 | 
|         How do I force spacing into the text of a paragraph?
        I'm still doing overheads :-) and now I want to print on
        the slide an ACL:
        <SLIDE>
        <TITLE>(Accessing Conference Files)
        <TOPIC>(ACL to allow direct access to conference file)        
                
        TRUCK.NOTE;1  [HYDE]       (RWE,RWE,RWE,RWE)
        	(IDENTIFIER=[NOTES$SERVER],ACCESS=READ+WRITE+EXECUTE)
	        (IDENTIFIER=[HYDE],ACCESS=READ+WRITE+EXECUTE+CONTROL)
	        (IDENTIFIER=[DECNET],ACCESS=NONE)
	        (IDENTIFIER=NETWORK,ACCESS=NONE)
        And I would like it to be offset as above.  If I use <P>,
        it gets all wrapped into a paragraph.  If I use <CODE_EXAMPLE>
        it works but it comes out in regular size text, not overhead
        size.   I've experimented with making it a list, but that
        hasn't been very successful.  I try not to ask until I've
        given it a thorough try on my own, and I can't seem to get
        this to happen.
 | |||||
| 226.7 | <line> and <line>(indent) | COOKIE::JOHNSTON | Fri Apr 10 1987 17:27 | 7 | |
| Use <LINE> and <LINE>(INDENT). Try <LINE>(INDENT) first without a numeric argument; the default should probably be satisfactory. Rose | |||||
| 226.8 | New font, too | VAXUUM::SEGAL | Tue Apr 14 1987 10:15 | 5 | |
|     New LN03 monospace font will be available in the update.
    Code examples in overheads will print in a larger point size then.
    
    Lee
    
 | |||||
| 226.9 | but I want a space here! | OASS::M_HYDE | From the laboratory of Dr. Jekyll | Sat Apr 18 1987 14:32 | 12 | 
|         It's got to be simple, which is probably why I can't figure
        it out.  How do I get a line to retain it's vertical spacing?
        Suppose I really want the line to be:
        
        
        Text here and then                a truly large gap.
        
        How do I keep document from mashing it all together?
        
        Thanks again for all the help.
        
        mark
 | |||||
| 226.10 | horizontal or vertical? | CLOSET::ANKLAM | Mon Apr 20 1987 08:22 | 7 | |
|     
    you can use <align_char> or <align_after> to force horizontal
    space (which is what your example shows) in normal text. Both
    horizontal and vertical space are preserved in monospaced
    examples (<code_example>, <line_art>....)
    
    
 | |||||