Conference vaxuum::online_bookbuilding

    
    I was trying to do a '$dir currnc::sys$doc:[wjohnson.bklib]' where
    I encountered 'privilege violation' problem.
    
    Any pointers appreciated.
    Thanxs.
    
    
    Pi.

    RE: .1

    The problems fixed, please try again.  I thought giving the files world
    read access would be sufficient, but it seems that they must also have
    world execute access as well.  Sorry.

    /Wes

Is it still available? ...

%DIRECT-E-OPENIN, error opening CURRNC::SYS$DOC:[WJOHNSON.BKLIB]ONLINE_BUILD*.P
S;* as input
-RMS-F-DEV, error in device name or inappropriate device type for operation

My NCP node database says CURRNC is 38.579.

Thanks,
John.

    RE: .3

    John,

    No wildcard (*) characters are allowed in the filespec.  Enter the file
    specifications exactly as I have written them in the base note.  Also,
    you cannot do a directory listing of the entire directory.  

    If you still cannot copy the files, contact me directly.

    Thanks,

    /Wes

Because of a project change, the files for the ONLINE_BUILD_HOWTO_GUIDE
have been moved to my MRED::USER4:[WJOHNSON.BKLIB] account.  To copy a
file, enter the exact file specification.  No wildcard (*) characters are
allowed.

    MRED::USER4:[WJOHNSON.BKLIB]ONLINE_BUILD_HOWTO_GUIDE.PS
    MRED::USER4:[WJOHNSON.BKLIB]ONLINE_BUILD_HOWTO_GUIDE.DECW$BOOK
    MRED::USER4:[WJOHNSON.BKLIB]ONLINE_BUILD_HOWTO_GUIDE.DECW$BOOKSHELF

/Wes

    It should be noted that the document referred to in .5 documents V1.2
    online bookbuilding only.
    
    Some changes for VAX DOCUMENT V2.0, and some other comments:
    
    1. <contents_file> is *not* required. All of the contents generation
       work is done automatically, without the writer having to supply
       either the <contents_file> tag or the /contents qualifier on the
       command line.
    
    2. <lmf_info> replaces the need for <reference> in the <title> tag.
    
    3. The symbol generator can be used to put the required symbol
       arguments in <chapter>, <headn>, etc. tags.
    
    4. <footnote> can be used as usual in online docs: but be careful
       to use them only as specified in the VAX DOCUMENT documentation.
       
    5. Your note about "the default Bookreader window is fairly narrow"
       is confusing. I'm not sure what you mean by 'default window'.
    
       The text window *is* fairly narrow, but the size is only changed 
       if the user resizes it: Bookreader never resizes the text window.
    
       *Formal* figures, tables, and examples pop up in a separate,
       'formal', window, which *is* sized for the dimensions of the element
       being displayed.
    
    6. The requirement for <delayed> within <gterm>, <msg> has been
       lifted. (It was a restriction for both hardcopy and online, not
       an online-only restriction.)
    
    7. The use of a backslash at the end of a line in a <headn> tag
       is now permitted.
    
    8. The reason for putting FSE bitmap graphics files on the CD is
       because they (usually) display faster than RAGS metafiles. 
    
       VAX DOCUMENT processing time is not affected by which type of
       graphics file you use.
    
       In addition, V2.0 allows you to specify DDIF graphics files (also
       bitmaps).
    
    9. CLOSET::KITS_:[DOCUMENT.V12]WRITER_GUIDELINES.* is no longer
       accessible, having been superseded by VAX DOCUMENT V2.0 documents
       (and previously by the V1.2B Writer's Toolkit release notes).
    
    10.The V2.0 online doctypes are SOFTWARE.ONLINE, MANUAL.ONLINE
       and MILSPEC.ONLINE.
    
    

>    8. The reason for putting FSE bitmap graphics files on the CD is
>       because they (usually) display faster than RAGS metafiles. 
>    
>       VAX DOCUMENT processing time is not affected by which type of
>       graphics file you use.
>    
>       In addition, V2.0 allows you to specify DDIF graphics files (also
>       bitmaps).

Does this mean you can specify DDIF object-oriented graphics files, and also
DDIF image (bitmap) files?

Or does it mean that the only kind of DDIF graphics you can specify are
images which, like FSE files, are also bitmaps?

If the former, this ought to be #1, not #8!

Mark

>>Or does it mean that the only kind of DDIF graphics you can specify are
>>images which, like FSE files, are also bitmaps?
    
    Yes.

    RE: .6

    Thanks for the V2.0 info Mary, I'll incorporate it into the guide when
    I can find some time.  I started on a new project a few weeks ago and
    haven't had much time for notes.  Nor have I tried processing any files
    using the new V2.0, although it is installed on the SPICES cluster that
    I now work on.

>   5. Your note about "the default Bookreader window is fairly narrow"
>      is confusing. I'm not sure what you mean by 'default window'.

    In this statement I was referring to informal entities, which can be
    wider than the standard window in which they are displayed.  Perhaps I
    didn't make that clear enough.

    Regards,

    /Wes