Conference 44.370::system_management

Does this include DOCUMENT V2.0 ???


If not, can we have this on FUTURS ?  PLEASE ???????

re .1;

Jane, "ask and thou shalt recieve"; I'll get Andrew to install Document V2.0
on FUTURS in the next couple of days.

Peter.

Thanks everso....

I keep using tags that get thrown out by 1.2....


I wish I still had my W/S...I miss so many tools :-(

First of all, thanks for the installation of DOCUMENT 2.0


There are problems with it though.....some I've found already:


Copyright page is now missing

<document_acknowledgement> tag is not recognized

<dec_logo> tag duffs-up in the tex-formatting stage

<mark><endmark> tags are just ignored

etc....


The 2.0 installation (ancillary files) on SBPEXE is correct, would it be
possible to compare the two and get FUTURS like SBPEXE ? 

what you actually wanted is the Document Writers Toolkit, which is only
available internally; we pulled the Document kit off the ConDist CD-ROM.

Isn't hindsight wonderful?

We'll sort it as soon as we can pull the kit over the pond...

Peter.

Ah well, but then I've been shoved back to being only a User and as such I
should be given the software I need not what I ask for...It's different when
you install it yourself... :-) 


Thanks anyway...

It includes 

    VAX DOCUMENT V2.0-1
    UTOX V3.0-1
    CUP Family Doctypes
    SPD Doctypes
    MANPAGE doctype/converter
 
And before anyone asks; Nope, you still can't do LN03 output - we only have
a license for it on CURRNT.

Peter.

To save someone else wasting time creating bookshelves, here's the
fix to the problem.

Ian.

           <<< MLTVAX::DISK$USER11:[NOTES$LIBRARY]DOCUMENT.NOTE;1 >>>
                    -< VAX DOCUMENT problems and questions >-
================================================================================
Note 3522.2  Destination BOOKREADER is invalid with ONLINE_SHELF error?   2 of 2
CSC32::R_WILLIAMS                                   124 lines  20-MAY-1991 17:32
                      -< Rough article draft with patch >-
--------------------------------------------------------------------------------
    Below is a rough draft of our customer article.  If you have any
    comments or feedback on this, please let me know.
    
    -Rick
    
    
    
TITLE:  DOCUMENT 2.0 Error Destination BOOKREADER Invalid With ONLINE.SHELF 

----------------------------------------------------------------------
COMPONENT:  VAX DOCUMENT                     OP/SYS:  VMS, Version 5.3
                                                          and later

LAST TECHNICAL REVIEW:  20-MAY-1991

SOURCE:  Customer Support Center/Colorado Springs  USA

\        Technical Contributors:
\             Rick Williams (130659) of LST

SYMPTOM:

In DOCUMENT 2.0, destination BOOKREADER is invalid with the ONLINE.SHELF
doctype.  The following errors will be generated with the command

    $ DOCUMENT/SYMBOLS=X_SYMBOLS X_SHELF ONLINE_BOOKSHELF BOOKREADER

    %DOC-I-IDENT, VAX DOCUMENT V2.0
    [ T a g    T r a n s l a t i o n ]...
    %TAG-I-DEFSLOADD, End of Loading of Tag Definitions
    %TAG-E-TAG_FAILS, The tag translator has detected a fatal error
    -TAG-F-INVLDDEST, tag <START_OF_PASS>, line 1, file
       DKA300:[DIRECTORY]X_SHELF.SDML
       Destination BOOKREADER is invalid with the ONLINE.SHELF doctype.
    %DOC-E-ERROR_TAG, Errors found by the tag translator


ANALYSIS:

VAX DOCUMENT 2.0 allows users to create .DECW$BOOKSHELF files by using
the ONLINE.SHELF doctype with the BOOKREADER destination.  The combination
of this doctype and destination does not work with the 2.0 kit that was
shipped.

Section 11.6 of the VAX DOCUMENT Producing Online and Printed Documentation
manual talks about building bookshelf files.


WORKAROUND:

There is no work-around for this.  Please apply the patch found under
"SOLUTION".

SOLUTION:

1)  Define DOC$PERSONAL_FORMATS to be some directory where the patch
    will exist:

    $ DEFINE DOC$PERSONAL_FORMATS mydisk:[my_dir.personal]

2)  In the file DOC$DESIGNS.DAT that is in the DOC$PERSONAL_FORMATS
    directory, add the following lines:

    name ONLINE_BOOKSHELF/definitions=TAG$O_FIXED_SHELF.GDX -
    /macros=TEX$O_SHELF/fonts=TEX$STANDARD_FONTS

3)  Create, in the same directory, the file TAG$O_FIXED_SHELF.GDX with 
    the contents:

<SET>(RETAIN_SPACING\FALSE)

<include>(doc$standard_formats:tag$o_shelf.stt)<eol>

<comment>****************************************************** 
*   _check_destination_string redefined to check for BOOKREADER
***************************************************<endcomment>
<string>(_check_destination_string\|<eol>
  <compare>(<string>(_destination)\BOOKREADER\\|<eol>
  <tag_diagnostic>(INVLDDEST\START_OF_PASS\<string>(_destination)
  \<string>(_doctype))&)<eol>
  &)<eol>

<copy_tag>(start_of_pass\shelf_fix_sop)

<define>(start_of_pass\|<eol>
<shelf_fix_sop>&\\\\\|<eol>
<shelf_fix_sop><string>(_check_destination_string)&)<eol>

<SET>(RETAIN_SPACING\TRUE)

4)  Use the following two .SDML files to test the patch: 

    a)  x_symbols.sdml file:

        <define_symbol>(reference_docs\LIBRARY)
        <define_book_name>(protocol\POLAR)
        <define_book_name>(test\testpolar)

    b)  x_shelf.sdml file:

        <shelf_create>(reference_docs\LIBRARY)
          <book_ref>(protocol\POLAR)
          <book_ref>(test\testpolar)
        <endshelf_create>

    c)  Use the following DOCUMENT command to test building a 
        .DECW$BOOKSHELF :

        $ DOCUMENT/SYMBOLS=X_SYMBOLS X_SHELF ONLINE_BOOKSHELF BOOKREADER


        By using the above .SDML files you will generate a file called 
        LIBRARY.DECW$BOOKSHELF that contains the following lines:

            BOOK\POLAR\POLAR
            BOOK\testpolar\testpolar




DIGITAL RESPONSE:

This should be fixed in a future release of VAX DOCUMENT.

If you talk nicely to Andy, he might make the corrections to the master
DOC$DESIGNS.DAT, it would save everyone having to do their own 
DOC$PERSONAL_FORMATS.

	Hi Peter, What version of ACMS are we going to go with on FUTURS
	V3.1 or V3.2 ?

	Wob

these are the versions already installed on ADGTST.

We'll need to install them ourselves after the BL1 installation, as they
became available too late for the BL1 kit itself...

They are pre-installed on the production CD-ROMs.

Peter.