Conference vaxuum::document_ft

    Please add the keywords, VMS and RTL.

Also please add WISHLIST.  

BTW, is it possible to make this notes file prompt for a keyword when a note is
entered, including replies?  I'm doing my best to remember to add a keyword
after I've entered a note.  I've noticed that many of the notes have no
keywords, as many of my searches on different topics come up empty, yet I
*know* I've read a note about such and such somewhere before. 

Keywords aside, it would also help if people really think about the titles they
give their notes and replies, making them informative and being careful 
not to enter titles like "A question or two", when "Table Spacing and Figure
Captions", for example is so much more helpful.

I'm not guiltless of this myself, but I'm getting better.


Thanx

Rose

Keywords added.  Changing NOTES to prompt for keywords, however, is not
 our department . . .
  <_Jym_>

    A question regarding installation: Do I arrange for installation
    of version 1.0 on my cluster, or should I point my system manager
    toward the task?
    
    If the system manager installs DOCUMENT 1.0, will the user documentation
    be available through him? 
    
    Thanks in advance for your assistance...I'm having a blast using
    the package you all created.
    
    Regards,
    John Kelly
          

    
    You should copy and print the documentation, including the installation
    guide. Give the installation guide to your system manager (DOCUMENT
    does require that someone with system privileges perform the
    installation.) If you are installing the current (T1.0) version,
    be sure to tell your system manager that it is very important to
    read the installation guide, as there are some restrictions in this
    release.
    
    patti anklam
    

    Given that the conference title points us to 1.1 for installation
    info, perhaps 1.1 should be updated. In particular, the pointers
    to the documentation set use the bl7 locations. 

DOCUMENT Version T1.0, Field Test Update version, is now available. The
installation guide, release notes, and the kit are available from:

 - CLOSET::KITS_:[DOCUMENT]          (Nashua, NH)
 - CADDLE""::DISK$BEARS:[SDML.BL8]   (Andover, MA)
 - KIWI::DOCUMENT$KIT:               (Marlboro, MA)
 - IJSAPL::$1$DJA19:[KIT.DOC]        (the Netherlands)

1. Files you will need:

   - DOC010.A through DOC010.D (savesets for installation via VMSINSTAL,
                                including line printer and PostScript
                                support)

   - DOCLN03010.A and .B       (savesets for installing LN03 fonts)

   - DOCINT010.A through DOCINT010.C (internal Digital designs and optional
                                      LN01 support)

   - DOCT10_INSTALL.LN03, .LN01, .POST, .LINE (Installation Guide)

   - DOCT10_RELEASE.LN03, .LN01, .POST, .LINE (Release notes)

2. The NOTES file for questions and problems is:

   VAXUUM::NOTES$LIBRARY:DOCUMENT_FT

   Use the keyword KIT to locate information pertaining to installation
   of the kit. Also, check the NOTES file before copying files from
   CLOSET. There may be a site closer to you geographically that has
   made a copy of the kit available.

3. Documentation on DOCUMENT Version T1.0 can be copied from any of
   the following:

   NEWDOC::[SDML.BL8]
   CLOSET::USE3$:[SDML.BL8]
   CADDLE""::DISK$BEARS:[SDML.BL8]

   The file A.READ_ME_FIRST lists the available documentation in those
   directories.

Using our usual nomenclature, this version will be known as
Base Level 8 (BL8), for reference purposes.

    Is there a SDC version of the documentation available yet?  I'm
    getting tired of hauling this binder of single sided out-dated
    DOCUMENT documentation around.  Can someone give me the part numbers
    for the SDC version?
    
    					Sieg

    We should have copies of whats going to the SDC available in a public
    copy area by the end of this week. That will include the User manual
    volume 1 and 2, the doctype designers manual, the step-by-step writing
    book, the design samples book, and the installation guides and release
    notes.
    
    We'll announce that area in the notes file when everything is set to go.
    
    -randy

With Randy's permission, here's information that Jon Patt sent to me. I 
think that Jon is the product manager for DOCUMENT; I'm not sure.  If 
anyone has different, more current, or additional information, please
post it here. 

AA-JT85A-TE 	Step-by-Step -  Writing with VAX Document
AA-JT84A-TE	Document User Manual, Vol. 1                      
AA-JT86A-TE     Document User Manual, Vol. 2                      
AA-JT88A-TE     Document Design Samples                           
AA-JT89A-TE     Document Doctype Designer's Guide                    
AA-JT87A-TE	Document Installation Guide
AA-KP75A-TE     Document LN03 Fonts Installation Guide
AV-KQ99A-TE     Read Before Installing coverletter                
AV-KQ98A-TE     Divider set


I do not know if the SDC is accepting early orders.

I do not know the costs.

Jon was not able to confirm it for me, but I have information from (I 
think) the small buffer notes file that the kit number is QLZE7-GZ; I 
make no promises that it is correct.

Question: is the divider set the binder and tabs, or just the tabs?  In 
the past, it hasn't been possible to order separate documents 
without sacrificing the binders and spines; binders are included with a
kit, but not for separate documents.  This has been my experience,
anyway.  At the very least, it would be nice if binders and spines were
offered separately. 

Note everyone needs an installation guide.  And a doctype designer's 
guide could be dangerous in the hands of the wrong users! (I have 
nightmares about my doc$tools directory getting corrupted by some 
well-meaning-or-not-so-well-meaning midnite hacker who has privs!)

Rose

    I talked to the SDC today!!  They stated that the numbers are as
    -.1 stated.  However, I think you want to order by the Q number,
    and anyway:
    
    IT AIN'T RELEASED AND WON'T BE UNTIL AT LEAST MID SEPTEMBER!!
    
    At least thats what they told me.
    
    BTW: Are you telling me in -.? that the current documentation I have,
    which has AAnnnnn part numbers on the title pages ISN'T THE REAL STUFF?
    I just sent out a 5 inch stack of this stuff to a printer to have
    copies made so we have enough for our use!   AAAAAAARRRRGGGGGGHHHHHHHH!!!

    Dave P

I'm not sure what you're asking.  The Bl8 doc'n I have shows the same numbers
cited in .11.  If you're having Bl8 copied, then I assume you simply won't have 
the most up-to-date version of the doc'n because Bl9 will supercede it.

Randy Otte or Barbara or another doc person, step in and correct me if I'm 
wrong.

Rose

    Will whatever changes occur in the documentation due out later this
    week be of importance?  Is it worth the trouble of halting the process
    of having copies made, bringing the new version over the network,
    printing a set, and sending these out to the printer?
    
    Dave P

    Re: .14, it depends upon what you judge to be important. 
    The books that will be made available later this week are cleaner 
    and more complete than are the previous versions. 
    In particular, the user manual volume 1 is a lot more complete (no
    missing chapters).  There are very few technical changes however.
    
    Re: .12, as to whether these docs are "real" or not, they are as real as
    any pre-release documentation---you might have noticed the notation
    "field test update draft" or something similar below the order number
    on the various title pages indicating this fact.
    
    The books posted later this week will be 99.99% of the SDC version of the
    docs--currently these book are undergoing a final-clean up and
    proofreading process.
    
    Hope that helps you make your decision,
    
    -Randy

RE < Note 1.11 by COOKIE::JOHNSTON >

> I think that Jon is the product manager for DOCUMENT; I'm not sure.  

Jon Patt is the documentation supervisor for DOCUMENT (he used to be
my supervisor, in fact [he supervises writers on other projects besides
DOCUMENT]).  The product manager is Linda Storm, who lives at DSSDEV::STORM.

							-- Nina

    The pre-SDC documentation for VAX DOCUMENT V1.0 is now available.
    These books can be found in both .Ln03 and .POST formats in 
    VAXUUM::USE3$:[SDML.V10].
    
    The file A.read_me_first in this directory lays out the file names
    and the books that correspond to them.
    
    By the way, for those of you used to talking in terms of DOCUMENT
    baselevels, I guess this is officially bl9 documentation.
    
    -randy
    

    One of the folks trying to print these files found out that some
    PostScript devices run out of memory printing the file for the User
    Manual Volumes 1 and 2.  
    I've now provided those books in two separate chunks in the directory
    VAXUUM::Use3$:[SDML.V10].  
               
    Please read the A.READ_ME_FIRST file for more information.
    This file also contains the SDC order numbers for the documentation
    kit.                           
    
    -Randy

             Version 1.0 of VAX DOCUMENT is now available for Digital Internal
             Use Only. Kits in CLOSET::KITS_:[DOCUMENT.V10] consist of:

                The SDC version of DOCUMENT (DOC010.*)
                The Field Test Update version of the LN03 fonts (DOCLN03010.*)
                The internal doctypes and designs (DOCINT010.*)

             These should be installed in the order shown.

             THE IVP SHOULD NOT BE EXECUTED UNTIL AFTER THE DEC INTERNAL KIT IS
             INSTALLED.

             If you are running DOCUMENT Base Level 8 (Field Test Update
             Version) you do not need to re-install the LN03 fonts, but please
             do not run the IVP until after installing DOCINT010. Since the
             SDC will not begin shipping the VAX DOCUMENT LN03 Font Kit before
             September, 1987, you will be allowed to use the field test version
             of the fonts through December 31, 1987.

             Installation and User Information specific to the Internal files
             supplied in the DOCINT kit are in:

              o  DOC_V10_INTERNAL_INSTALL.LN03 (.POST,.LN01,.LINE)

                Contains installation and post-installation information. If you
                are not the installer of VAX DOCUMENT on your system, please be
                sure that the installer receives this information!

              o  DOC_V10_INTERNAL_NOTES.LN03 (.POST,.LN01,.LINE)

                Describes the additional doctypes available in the DEC internal
                kit and the templates available (project plans, specifications,
                and so on).

             Available documentation files are listed in

                CLOSET::USE3$:[SDML.V10]A.READ_ME_FIRST

             Please consult the NOTES file DOCUMENT on node VAXUUM if you have
             any questions concerning the installation.




                                                                              1

    If you must copy the documentation during the day, PLEASE copy it
    from:
    
    	NEWDOC::[sdml.v10] instead of CLOSET::USE3$:[sdml.v10]
    
    The files are the same. As Randy and Brian pointed out, refer to the file
    A.READ_ME_FIRST for further information on the documentation.
    

    Also, please continue to send any questions/comments on the
    documentation to the account VAXUUM::CLOSET::DOCDOC. By sending
    mail to that account, the correct writer(s) will be sure to get
    your comments and will answer any questions as soon as feasible.
    This includes any comments on the Version 1.0 docset, as well as
    Baselevel 8.
    
    Here's hoping you find the latest documentation a breeze to use!
    -Barbara

    The index to the .POST version of the User Manual Vol 1 is now in
    USE3$:[SDML.V10]V1_USER_MAN_VOL_1_INDEX.POST.  Those of you who
    already printed what you (and I) thought was the whole book may
    want to print this file as well.
    
    -randy

Please DO NOT copy the VAX DOCUMENT V1.0 savesets or documentation from
CLOSET:: or VAXUUM:: between the hours of 9AM and 5PM EDT Monday--Friday.

At this moment, all of our normally available network links 
are being used by people either copying or installing the kit 
over the net, and our development team is finding itself unable
to communicate with other machines.

Thank you in advance for your cooperation.

--Brian

    Please note that there will be a general power shutdown in
    the Spitbrook facility this Saturday, so don't waste your 
    time trying to initiate copies over the net from VAXUUM/CLOSET
    on Saturday, July 25.  THe cluster will have gone fishing.
    
    The power is SUPPOSED to come back on at 5PM, and the systems
    are SUPPOSED to be rebooted after that, and so the kits SHOULD
    be available Saturday evening (ha!) or Sunday (probably).
    
    Those are Nashua, NH times.
      
    bill

    Is there going to be a system adminitrators manual, or does the
    doctype designers guide take its place?
    
    Ken

    The Doctype Designer's book is as much as we could pull together
    in the way of a system administrator's book for V1.0.  We'll probably
    be internally releasing something like a system administrators guide
    in the future, but as to when I couldn't say=---we're just beginning
    to plan what to do next.  It is on our list of things to do however...
    
    -randy

  For the European areas, it may be easier to copy the document sets
  of V1 from  IJSAPL::$1$DJA19:[KIT.DOC]*.*
  This contains the SDC kit, the internal kit, the LN03 kit, the
  EDUOVER set (though now integrated in internal kit), the V1*.LN03
  documentation (no Postscript or other printer support).

  Since the Netherlands is 8 hours ahead of the USA, this may allow
  European evening copying while the US is getting up for work...
  We're supposed to be open 24 hours a day, 7 days a week...

Theo

I couldn't find this mentioned anyplace else...

Is DOCUMENT (specifically the documentation) going to be shipped to the 
field via ADS (the Automatic Distribution System)?

If so, who and/or what ADS class will be getting it?

Thanks,

	Kathy

ps.  The reason I'm asking is to find out if folks will be getting it 
automatically or if it will need to be ordered - and, yes, I do know it 
won't be available until mid-September...

Yes, it is. It is in a class by itself (ain't it the truth)!

The group code is Electronic Publishing (EP).

--Brian

    HELP!!!!!!!!
    
    After installation V1.0 I run a SDML testfile and this came out.
    Is there anybody who can help me on this???????

    
    
    ---->>>> error listing <<<<----
        
%DOC-I-IDENT, VAX DOCUMENT V1.0
%CLI-W-BUFOVF, command buffer overflow - shorten expression or command line
%CLI-E-INVROUT, invalid routine specified in command tables - check .CLD file
[ T a g   T r a n s l a t i o n ]...
%TAG-I-TAG_IDENT, V1.0
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-ENDPASS_1, End of first pass over the input
%SYSTEM-F-ACCVIO, access violation, reason mask=05, virtual address=02405B24, PC=0036C4B9, PSL=03C00004

  Improperly handled condition, image exit forced.

	Signal arguments	      Stack contents

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=7FEF8600, PC=80018322, PSL=03C00004

  Improperly handled condition, image exit forced.

	Signal arguments	      Stack contents

	Number = 00000005		 8001831B
	Name   = 0000000C		 8001825F
		 00000000		 FFFFFFFC
		 7FEF8600		 003FE288
		 80018322		 00080101
		 03C00004		 003FE248
					 00457FA0
					 00000000
					 00441500
					 00000020

	Register dump

	R0 = 00000000  R1 = 8001819C  R2 = 000000FC  R3 = 7FEF84EC
	R4 = 00000000  R5 = 00000004  R6 = 7FEF85EC  R7 = 7FEF846D
	R8 = 7FEF8600  R9 = 7FEF8454  R10= 7FEF84EC  R11= 7FEF84A8
	AP = 7FEF83CC  FP = 7FEF838C  SP = 7FEF8408  PC = 80018322
	PSL= 03C00004

   ---->>>> end of error listing <<<<---- 

    Can I add my voice to the cry for help?

    I also get the %CLI message, but the file processes as normal.
    Except when using the new <DEC_LOGO> tag.
    
    Here's a log of an attempt to process a file that contains ONLY
    the <DEC_LOGO> tag:
    
    $ document declogo.gnc report ln03
    %DOC-I-IDENT, VAX DOCUMENT V1.0
    %CLI-W-BUFOVF, command buffer overflow - shorten expression or command line
    %CLI-E-INVROUT, invalid routine specified in command tables - check .CLD file
    [ T a g   T r a n s l a t i o n ]...
    %TAG-I-TAG_IDENT, V1.0
    %TAG-I-DEFSLOADD, End of Loading of Tag Definitions
    %TAG-I-ENDPASS_1, End of first pass over the input
    [ T e x t   F o r m a t t i n g ]...
    %TEX-I-IDENT, V1.0
    %TEX-W-UNDEFINEDCS, Undefined control sequence
    %TEX-I-LINE, Error occurred on or around line number: 5
    %TEX-I-SHOWCONTEXT, '\declogo'
    %TEX-I-SHOWCONTEXT, '        {}'
    %TEX-I-FILENAME, 'declogo'
    -TEX-I-ONPAGE, on page [1] 
    %TEX-I-PAGESOUT, 0 pages written.
    -TEX-I-OUTFILENAME, 'disk$ipg02:[walters]DECLOGO.DVI_LN03'
    %DOC-E-ERROR_FORMATTER, Errors found by the Text Formatter.
    

    Colin
  

         
         Re: .31,.32
         
         PLEASE, PLEASE, PLEASE, do not add problems to the reply
         of note #1, this is for installation information ONLY.
         
         If you have a problem, and do not see an already existing
         note for this problem execute the notes command WRITE,
         and enter your problem as a new topic!.
         
         As it is the command buffer overflow problem has been
         discussed and a workaround is posted in note 467.*.
         
         Re: .31
         
         I am not sure why you are getting a system access violation
         I am suspicious of the command buffer problem.  Please
         see not 467 and try to fix your problem in the 
         DOC$STANDARD_FORMATS:DOC$DESTINATIONS.DAT file, be very
         careful not to add extraneous characters into the file,
         especially after the continuation characters!
         
         If you still have the problem, please enter it as another
         topic.  I will not discuss it further in this note.
         
         Chris
         
         

    A system manager pointed out to me that the Document kits are not
    included in the public kits listing, AIMHI""::SYS$PUBLIC:KITSDIR.DOC.
    
    The Easynet_Kits conference is temporarily unavailable, but I suspect
    that Document is not mentioned there. 
    
    It would be helpful to have 1.20 posted in Easynet_Kits. Most system
    managers not familiar with Document first check the above-mentioned
    file or conference for kit info. 
    

'Twill be done.   --Brian