Conference vaxuum::document_ft

Is it desirable to set up some new bl8-related keywords for this 
conference?  Perhaps add a set of new keywords, same as the "old" ones, 
but preceded or succeded (sp?) by _BL8_ ?  Or some other nomenclature?


Rose

    What's the difference between this version (T1.0) and the version
    I'm already running, that was available a month ago (T1.0)?
    
    Does this have additional bug fixed, yet is not the SDC product?
    Should I install it, or wait for the SDC version?

    
    It is principally bug fixes, though the enhancements for multinational
    character support are very important for European sites. You
    can copy/read the release notes file to see whether any of the bug
    fixes, etc. are important. If not, you can wait for the SDC version.
    
    patti
    

    
    I have just been informed that DOC010.B in KITS_:[DOCUMENT] was
    truncated. I have place a new version there.
    
    -pa

Bizarre as it sounds, there are still a few BL06 files hanging around 
here.  Are there any problems updating from BL06 to BL08?  Is 
DOC$CONVERT in BL08, or should we convert all files before installing 
BL08?

Also, are there any more updates planned between now and FRS?


Thanx

Rose

    The converter will translate Bl6 to Bl8.
    
    The new version (V1.7) translates to an .SDML file
    (which gets rid of the renaming problems).  It also
    has some bug fixes and reports the number of definitions
    deleted.
    

    There are still a lot of BL6 files around here, also. There shouldn't
    be any problem going from BL6 to BL8. BL8 is the last update before
    we go to the SDC. 
        
    The latest version of the converter (1.7, which uses SDML for the
    output filetype) was not in the BL08 kit. It can be copied from
    
    CLOSET::KITS_:[DOCUMENT]DOC$CONVERT_06_FILES.EXE
    
    It has the following bug fixes:

Version 1.7 

o   Translates <NOHELP> to <BOOK_ONLY>

o   Translates <KEYPHRASE> to <KEYWORD>

o   Prints the number of definitions deleted at the end
	of processing and lists each one of the deleted
	definitions in the list file.  Many people are
	disturbed to find these definitions deleted so
	this action calls attention to the deletion and
	provides information about which definitions
	deleted.

o   Encloses the following tags in a comment:

		<DOCUMENT_TITLE>(full-name))
		<WRITER>(writer-name[\...])
		<EDITOR>(editor-name[\...])
		<DPN>(discrete-project-number)
		<ORDER_NUMBER>(order-number)
		<STATUS>(document-status)
		<PRODUCTION_INFORMATION>
		<ENDPRODUCTION_INFORMATION>
		<HISTORY>(previous-version)
		<ENDHISTORY>(previous-version)
		<TITLE>(element-title)
		<TEXT_TYPE>(type)
		<SPECIAL_INFORMATION>
		<ENDSPECIAL_INFORMATION>
		<HAS_FIGURE>(<name-in-text>\etc.)
	    

    We would prefer that people copy the documentation from NEWDOC::[sdml.bl8]
    instead of CLOSET::USE3$:[sdml.bl8]. Also, if people could copy
    the kit during off-peak hours, that would be appreciated.
    
    Because of the number of processes using network access (about 30
    right now), users may be getting the "insufficient resources at
    remote node" trying to copy files or otherwise access CLOSET/VAXUUM.
    
    Mike    

    
    How does this documentation differ from the User's Guide, Parts
    1 and 2 for Fields Test Draft?
    
    Should bl6 users be given this new set rather than the fields test
    draft volumes?  Is conversion from 6 to 8 addressed here, or should
    bl6 users use bl7 and bl8 documentation to navigate through the
    changes?
    
    Thanks,
    Fern
    

    
    It consists up updates and corrections made to the documents, many
    of which were made as a result of comments we received. If you
    haven't used bl7, there is no reason to use it; the copious
    release notes from base level 6 should be used as a guide to tag
    name changes, etc. (I also recommend reading the notes in this
    conference about conversion) 
    
    patti
    

    How much difference is there really?
    
    I mean, we have at least 75 people using Document, and we just finished
    copying 75 complete BL07 docsets ...  I really don't look forward to doing
    another 100.
           
    Ken

The files are available along with some of the documentation at:

{TIPPLE,IMBIBE,OBIWAN}""::DISK$USER04:[KITS.DOCUMENT]

Those nodes are in area 32 in the New York/New Jersey Area.  Please
feel free to copy the files from there if so desired.  Lastly our
preference would be that you copy them off hours.

-tl

    
    Documentation differences are really not major; the missing chapter
    1 of the UG is now in place, as is the missing <preface> tag. For
    the rest, it's  the usual miscellaneous insertions/corrections you
    normally get during field test review. In short, no new functionality
    is documented in BL8 that wasn't present in BL7.
    
    patti
    

    If I have installed BL8, and am NOT interested in maintaining any
    BL7 compatability, can I just delete everything under [DOCTOOLS...]?
    I'd really like to free up the disk space.
    
    Also, in the installation procedure, the default answer to the question
    "Do you want to supply another destination and queue name?" is "YES".
    Why is that?  I would assume that most people would only use one
    destination/queue for each device type.  Inadvertently typing <CR>
    at this point can make the installation unpleasant.
    
    Finally, I asked for a POSTSCRIPT destination for the IVP.  The
    messages said everything queued ok, but nothing printed.
    
    -pd

    
    Yes, you can remove the old [DOCTOOLS...] once you're satisfied
    that BL8 is working properly. (We didn't want to throw out a system
    from under people who are on tight production schedules.)
    
    

    re: .14, I did the same thing accidentally accepting the YES default
    for another round on the queue queries.  Me thinks the NO default
    is definitely the safer and more friendly setting.
    
    jack

    If there is still a need for any one to copy the kit I have put
    it on system :: 
    
    		CADDLE""::DISK$BEARS:[SDML.BL8]

                
    And yes you can get it during normal working hours.


    dave               

    I thought a lot about the YES or NO default on the question
    about whether you want to supply another destination/queue name.
                                                     
    Here is the reasoning:
    
    If you are in the habit of hitting RETURNs to take the defaults,
    and the default is NO, then it will be too late to input any more 
    destination/queue name entries for this device type.  So, I
    regard the YES default as a "fail safe" for people who have
    more than one of a given device type.
    
    However, as you have noted, the default leaves you back at the position
    of inputting another destination name.  MOST users will have
    only one destination, so they will say "Uh, oh! What do I do now?"
    
    Well, they MIGHT look in the Installation Guide.  It tells you what
    to do.  (It says, "If you make a mistake and press RETURN you will
    be prompted for a new destination and queue name.  You can supply
    any values, and then when you are asked to confirm the values,
    just reply NO.")
    
    For the final kit I see I need to add more for users who don't
    have/read the Installation Guide.  The second time around on the
    query for destination name it provides no default value.  But at
    the moment it requires that you enter something. I will make it
    possible to enter nothing (just press RETURN) and it will jump ahead
    to the question about "supplying another destination..."  I'll
    also put a more elaborate help message in for those who type "?".
    
    Thanks for the comments.
    

    As a veteran VMSINSTALler, I seldom, if ever, read the installation
    guide.  Sometimes I don't even read the prompts.
    
    I still vote for making "NO" the default.

    After all, you've made it much easier to now change/add destination
    definitions and assignements, so missing the change at installation
    time is no longer such a big deal.
    
    jack

    I think I will remove the default -- that way you have to 
    consciously (well, more or less consciously) type SOMETHING
    to go in either direction.   And if you just press RETURN
    it just repeats the same prompt.

    A copy of the kit is now available at MRO in:
    
     KIWI::DOCUMENT$KIT:
    
    It's available (save a catastrophe!) 24 hours a day...
    
    Regards

  For the European side:

     the entire installation kits with LN03 documentation files can also
     be copied from

       IJSAPL::$1$DJA19:[KIT.DOC]*.*

     (BL 8).

Theo

(IJSAPL is the SWAS VAX 8650 at Digital's HQ in the Netherlands)

A copy of the kit is available as:

bm1gsg::shelf$disk:[doc010] (savesets, installation, and release documents)
bm1gsg::shelf$disk:[doc010.doc] (remaining documents)
bm1gsg::shelf$disk:[doc010.design_samples] (how to's)
bm1gsg::shelf$disk:[doc010int] (savesets for internal use materials)
bm1gsg::shelf$disk:[docln03010] (savesets for internal use LN03)

Regards, Ira Grollman (GSG Systems Engineering)

!  < Note 379.7 by CLOSET::ANKLAM >
!                    -< You need to get the latest version >-
!
!        
!    The latest version of the converter (1.7, which uses SDML for the
!    output filetype) was not in the BL08 kit. It can be copied from
!    
!    CLOSET::KITS_:[DOCUMENT]DOC$CONVERT_06_FILES.EXE


    Before I install BL08, are there more patches on the BL08 Kit ??



   Eric Hofland    

    
    A few files (all in CLOSET::KITS_:[DOCUMENT])
    
    - CUP$LOCAL_ELEMENTS.TEX should replace the one in DOC$LOCAL_FORMATS.
      This has a correction for the declogo for POSTSCRIPT output.
    
    - TEX$REPORT.DESIGN corrects a typo in the table of contents format.
    
    - AUTODEST.EXE is an updated version of Autodest.
    
    patti