Conference vaxuum::document_ft

    
    Did you rename the CUP$DESIGNS.DAT file in DOC$ROOT:[LOCAL.FORMATS]
    as described in the installation guide?
    
    

    Isn't this the same thing that was missed in note 3.5? I made the
    same mistake.
    
    It is not explicitly stated in the Installation Guide to rename
    CUP$DESIGNS.DAT to DOC$DESIGNS.DAT.
    
    There is only a reference  to Chapter 4 of the Release Notes. It 
    tells you to do it there, but the reference (Administrators should 
    review...) could be a little more emphatic in the Install guide. 
    

	We've already done that and it still isn't giving what we
	expect.  So what do we expect, the old format (logo placement
	optional), something like:

		I N T E R O F F I C E  M E M O R A N D O M

	To: Patti Anklam		From: William K. Volkman
					Dept: LCG Training and Consulting
					EXT:  DTN 548 - 4241 
	CC: George Clinard		MS:   CXO3-2/B4
					ENET: TYFYS::VOLKMAN
+-------------+
|D|i|g|i|t|a|l|
+-------------+

	SUBJ:  This is the format that we are looking for...

	I was able to do this with LaTeX with very little work, so
	it should be possible to do this with DOCUMENT (I hope).

	Regards,
	Bill V.

The way to get the old DIGITAL MEMO working is to 

1. Make MEMO active by renaming CUP$DESIGNS.DAT to DOC$DESIGNS.DAT.

2. In your .GNC file, use the old MEMO tags, like <TO> and <FROM>.
   Do *not* use the new "MEMO template\LETTER doctype" tags, such as
   <MEMO_TO> and <MEMO_HEADER>. These tags are not recognized in DIGITAL
   memos (not on my system anyway).

3. Use the MEMO doctype, not the LETTER doctype.

When this is straightened out, you will notice that your memos are practically
falling off the right side of the page. So do this (or have your system
administrator do it):

4. Edit DOC$LOCAL_FORMATS:CUP$MEMO.DTP.

5. Change the following line from:

   \hoffset=1in

   to:

   \hoffset=1pc


--------------------------------
Patti: This seems to have given many people a lot of trouble. Perhaps
       MEMO should be able to process or throw away all those <MEMO_...>
       tags. Was this kind of doctype-modification something you
       intended the system administrators to do?
   
       Also, I guess LSE support for internal memos disappears. 


Marty

    
    Guess I went too far trying to preserve the old way of doing things...
    will look into fixing (at least getting CUP$MEMO to do the correct
    thing with the new MEMO tags.)
    
    

    RE: .4
    	Your solution does just what we wanted.
    
    Thanx,
    Bill V.

    \hoffset=0in % also works
    
    I find that <DISTLIST> DOES not maintain input spacing as advertised
    (did I overlook a release note?). The .TEX file includes
    \spacingasis, but it doesn't print that way. In a two column list
    of names, the first columns lines up vertically with and without
    leading spaces, but some names in the second column are shifted
    right two or three characters. (Fixed with yet another LYX doctype.)
    
    Joe

Two-column distlists are not supported. You actually are getting "spacing 
as is" to the extent that spaces and line breaks are not ignored; 
however, the fact that the font is proportionally-spaced means that
the width of the first column will vary, which accounts for the differing
vertical alignment in the second column.

--Brian

    I did all of what was in this note and I get the digital logo and
    inter... stuff just below the FROM: in destination ln03.  Am I doing
    something wrong?
    
    Jerry

    
    did you use the memo template tags from MEMO.GNC in 
    DOC$ROOT:[LOCAL.TEMPLATES] ?
    

    We've just started looking into the MEMO doctype and managed to
    come up with a couple of minor irritants... (what else is new?!)
    
    1. Using doctype MEMO resulted in <memo_from> and <memo_to> being
       unrecognised. They are, however, recognised in LETTER which seems
       a bit strange.
    
    2. Using <memo_line>(Warning\This is a warning) results in the colon
       overwriting the first T in the text.
    
    3. There is no blank line between the "To" and "From" lines which
       makes it less than clear.
    
    4. <memo_to> supresses or ignores text. Using (blah\blah\01234
       Townname\France\) results in output of:
    
              blah
              blah1234 Townname
              France
    
       Since at least nine areas in France have leading zeroes in the
       postcode and DEC has offices in at least two of them, this is
       inconvenient....
    
    5. The CC list butts right up under the body of the memo. It ought
       to go at the bottom, no?
    
    Gavin 

You have to use the BL06 MEMO tags with the BL07 MEMO doctype.

See item 2 in note 39.4.


Rose

re: 39.11

>    4. <memo_to> supresses or ignores text. Using (blah\blah\01234
>       Townname\France\) results in output of:
>    
>              blah
>              blah1234 Townname
>              France
>    
>       Since at least nine areas in France have leading zeroes in the
>       postcode and DEC has offices in at least two of them, this is
>       inconvenient....

Also you want the codes to line up in some cases.

    
    There is a bug in this doctype and and some others in that arguments
    to tags that begin with 0's are getting mixed up in TeX. I am fixing
    these for the field test update. If time allows this week, I'll
    try to put together a patch to the CUP$MEMO doctype for the current
    base level.
    
    patti anklam
    

    Re: .12
    
    Nice to know you have to use BL6 and BL7 mixed to get the results
    desired... Where is *that* documented?  ;-)
    
    Will this situation continue with the next release? 
    
    Gavin

    
    No, you do not *need* base level 6. What .12 meant was that the
    tags for doing Digital interoffice memoranda did not change from
    bl6 to bl7. The file DOC$ROOT:[LOCAL.TEMPLATES]MEMO.GNC contains
    a template of the tags that work for Digital memos. These are
    tied to the TeX macros that get the Digital logo in the correct
    position, etc. That was what didn't change.
    
    sorry for the confusion. 
    
    patti
    

    Now that BL8 is out, I'm still having problems with MEMO.  Can you
    help me out please.  Here's what I get:
    
Hitech>>document/noprint/nobatch status_870515 memo ln03
%DOC-I-IDENT, VAX DOCUMENT T1.0-008
[ T a g	T r a n s l a t i o n ]...
%TAG-I-TAG_IDENT, T1.0-002 
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-ENDPASS_1, End of first pass over the input
%TAG-I-CPU_USAGE, Pass	1:	10.7	Pass	2:	2.5	Total:	13.2 seconds
[ T e x t	F o r m a t t i n g ]...
%TEX-I-IDENT, T1.0-005 %TEX-W-UNDEFINEDCS, Undefined control sequence
%TEX-I-SHOWCONTEXT, '...hbox to \hsize {\declogo '
%TEX-I-SHOWCONTEXT, '	\hskip	48pt\raise	5.2pt\hbo...'
%TEX-I-LINE, Error occurred on or around line number:	5
%TEX-I-SHOWCONTEXT, '\individualto{Someone}'
%TEX-I-SHOWCONTEXT, '	'
%TEX-I-FILENAME, 'status_870515'
-TEX-I-ONPAGE, on page [1] %TEX-I-PAGESOUT,	3 pages written. 
-TEX-I-OUTFILENAME, 'usr$:[peterson.decstart]STATUS_870515.DVI_LN03' 
%DOC-E-ERROR_FORMATTER, Errors found by the Text Formatter. 
Hitech>>
    
    I really need to get this out and would really appreciate some help.
    I am using almost exactly (body text changed) as the one I used
    in BL6.  CUP$DESIGNS.DAT was properly renamed and everything.
    
    Help...?
    
    Rick

    SET FACE/COLOR=RED
    
    Patti fixed the problem.  It turns out that I forgot to define
    DOC$LOCAL_ELEMENTS to point at
    DOC$ROOT:[LOCAL.FORMATS]CUP$LOCAL_ELEMENTS.TEX.
    
    All works fine now.  I wish they were all this easy...
    
    Regards,  Rick

I'm glad this works for other people, but I still seem to have problems.

I have DOC$LOCAL_ELEMENTS defined to point to CUP$LOCAL_ELEMENTS.TEX.
I've renamed CUP$DESIGNS.DAT to DOC$DESIGNS.DAT.
I'm using the MEMO.SDML file from DOC$LOCAL_TEMPLATES.

And it still blows up. Can anybody point out what I'm doing wrom (this is with
BL8, installed today).

--------------------------------------------------------------------------------
$ show log doc$local_elements
   "DOC$LOCAL_ELEMENTS" = "DOC$LOCAL_FORMATS:CUP$LOCAL_ELEMENTS.TEX" (LNM$SYSTEM_TABLE)
$ show log doc$local_formats
   "DOC$LOCAL_FORMATS" = "DOC$ROOT:[LOCAL.FORMATS]" (LNM$SYSTEM_TABLE)
$ dir doc$local_formats:doc$designs.dat,doc$local_elements

Directory DOC$ROOT:[LOCAL.FORMATS]

DOC$DESIGNS.DAT;1   CUP$LOCAL_ELEMENTS.TEX;1                

Total of 2 files.
$ copy doc$local_templates:memo.sdml []
$ docu memo memo post
%DOC-I-IDENT, VAX DOCUMENT T1.0-008
[ T a g   T r a n s l a t i o n ]...
%TAG-I-TAG_IDENT, T1.0-002
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-ENDPASS_1, End of first pass over the input
%TAG-I-CPU_USAGE, Pass 1: 11.2  Pass 2: 1.7  Total: 12.9 seconds
[ T e x t   F o r m a t t i n g ]...
%TEX-I-IDENT, T1.0-005













%TEX-W-UNDEFINEDCS, Undefined control sequence
%TEX-I-SHOWCONTEXT, '...pt\hbox {\kern 4pt\sixpointcc '
%TEX-I-SHOWCONTEXT, '                                          {TM}} \fi '
%TEX-I-SHOWCONTEXT, '...hbox to \hsize {\declogo '
%TEX-I-SHOWCONTEXT, '                                          \hskip 48pt\raise 5.2pt\hbo...'
%TEX-I-LINE, Error occurred on or around line number: 5
%TEX-I-SHOWCONTEXT, '\individualto{Receiver}'
%TEX-I-SHOWCONTEXT, '                       '
%TEX-I-FILENAME, 'memo'
-TEX-I-ONPAGE, on page [1]




%TEX-I-PAGESOUT, 1 page written.
-TEX-I-OUTFILENAME, 'dua1:[hetrick.ipse.mem]MEMO.DVI_POST'
%DOC-E-ERROR_FORMATTER, Errors found by the Text Formatter.

	It does work for me with destination LINE.

    
    While I continue to look for a previous NOTE on this:
    
    -there is a bug in CUP$LOCAL_ELEMENTS in the dec logo for POSTSCRIPT
    (only POSTSCRIPT). You can copy the corrected version from
    CLOSET::KITS_:[DOCUMENT]CUP$LOCAL_ELEMENTS.TEX.
    
    -pa
    

    I am having a little problem with Digital logo using MEMO and POSTSCRIPT.
We just installed V1.0 last night. I process the same source twice, once as
LN03 and once as POSTSCRIPT. The LN03 file came out fine but when I printed
the POSTSCRIPT file the Digital logo came out as a negative image. Is this
what should happen? Did I do something wrong? Did Digital change the logo and
not tell us?                    What too do.....

    You didn't do anything incorrectly. The POSTSCRIPT font with reverse
    print for the logo is not available for this release, so the
    logo is constructed with a macro and regular (black on white) typeface.
    
    Lee