| With VAX DOCUMENT, the <REFERENCE> tag creates hotspots to cross refer
to other sections and to formal figures, tables, and examples.
The <REFERENCE> tag can only create a cross reference (or hotspot)
to a text element that can be assigned a symbolic name. For example,
<HEAD1>(Title Text\symbol-name). See the VAX DOCUMENT documentation
for more information about the <REFERENCE> tag, symbol names, and
tags that take symbol-name arguments.
In addition, the <ONLINE_POPUP> tag allows you to create popups
for text elements that cannot be assigned symbolic names; for
example, lists, paragraphs, informal tables, figures, and examples.
The syntax is:
<ONLINE_POPUP>(hotspot-text)
...stuff to go in popup...
<ENDONLINE_POPUP>
The VAX DOCUMENT documentation is available as listed in the note
below. The release notes contain specific information about coding and
building online books.
Mary
(If you are using DECwrite, you should inquire in QUEEN::DECWRITE
about its procedures for creating hotspots.)
<<< W7_:[NOTES$LIBRARY]DOCUMENT.NOTE;2 >>>
-< VAX DOCUMENT problems and questions >-
================================================================================
Note 2.13 VAX DOCUMENT Kits & Documentation 13 of 20
CLOSET::DEVRIES "By their notes ye shall know them" 87 lines 30-JAN-1990 14:52
-< V1.2-B kits & docs & PAKs; also, installation tips >-
--------------------------------------------------------------------------------
Digital Internal Use only
DISTRIBUTION POINTS
===================
SOFTWARE KITS AND DOCUMENTATION ARE AVAILABLE FROM THESE SITES:
Home base (ZKO, Nashua, NH):
CLOSET::KITS_:[DOCUMENT.V12B.SOFTWARE]
CLOSET::KITS_:[DOCUMENT.V12B.BOOKS]
Greater Maynard (MLO):
NEWS::CUP$KITS:[DOCUMENT.V12B.SOFTWARE]
NEWS::CUP$KITS:[DOCUMENT.V12B.BOOKS]
Europe (UTO):
IJSAPL::KIT_:[DOCUMENT.V12B.SOFTWARE]
IJSAPL::KIT_:[DOCUMENT.V12B.BOOKS]
Please copy from the site most accessible to you. Use FTSV to copy files, if
possible. Copy after business hours at the kit site, if you can.
Since this kit combines several previous kits, it has grown considerably.
To install all components of VAX DOCUMENT at one time, you may need up to 23,900
free blocks on your system disk (during installation) and also up to 23,900 free
blocks on the target disk (if different from the system disk). RAGS and UTOX
will be installed on your system disk.
The savesets are
DOCWTK010.A required for *any* installation
.B, .C, .D, .E for VAX DOCUMENT
.F for UTOX
.G, .H for RAGS
If you don't want to install all three products at once, you may copy only the
savesets you need. To make that easier, the [...SOFTWARE] directory on each
distribution node contains a command file, DOCWTK-COPY.COM, which you may run to
specify which components you want. This will set up and submit a job that will
copy (with FTSV, if available) the savesets you need.
See the conference CLOSET::DOCUMENT, note #2737, for a description of
DOCWTK-COPY.COM and other installation matters.
INSTALLING THE SOFTWARE
=======================
Installation instructions are part of the Internal Notes manual. There are no
longer separate guides for installing and using the internal enhancements. This
guide is available in the [...BOOKS] directory as DOC_V12B_INTERNAL_NOTES (in
several output forms).
This kit incorporates tools that have had various means of installation and
support in the past. Some of the logical names that supported older versions
may interfere with IVP and use of these tools. IF YOUR ACCOUNT EXECUTES
PROCEDURES THAT REDEFINE THE FOLLOWING LOGICALS TO LOCAL DIRECTORIES, YOU MAY
NEED TO DEASSIGN THEM BEFORE INSTALLING AND USING VAX DOCUMENT V1.2-B:
doc$bookr_fonts, doc$bookr_tools, dvc$bookrshr, doc$message,
tag$translateshr
If you have LSE installed on your system and wish to install LSE support for VAX
DOCUMENT, you must also have a license installed for LSE!
VAX DOCUMENT REQUIRES A LICENSE
===============================
In order to run VAX DOCUMENT (including the IVP) you must load a valid Product
Authorization Key (PAK). If you don't already have this PAK (which is the same
one used for V1.2/V1.2-A), follow one of these procedures:
Users in the U.S.: type VTX PAK at the DCL prompt;
Users in Europe: type VTX ISPAK at the DCL prompt;
Users in GIA: send request via e-mail to AKOV11::HAMEL_WHITE.
See topic 13.* in CLOSET::DOCUMENT for information about PAKs.
MAINTAINING MULTIPLE BASELEVELS ON SAME SYSTEM
==============================================
In the [...SOFTWARE] directory is a DCL command file, BASELEVEL.COM. This is a
DCL command file you can use (with appropriate local modifications) to switch
between two or more versions of VAX DOCUMENT. The file contains the
description, instructions, and warnings on how you might use it. Please
approach this function cautiously -- but be heartened by the fact that there are
several sites that have used this program successfully.
BASELEVEL.COM has not changed since the V1.2/V1.2-A release in mid-1989.
|
|
Here is the reply I posted in the DECwrite conference.
<<< QUEEN::QUEEN$DUA1:[PUBLIC.NOTES]DECWRITE.NOTE;1 >>>
-< You can't go wrong with DECwrite >-
================================================================================
Note 646.1 Hotspots 1 of 1
EPIK::DONOHUE 24 lines 21-FEB-1991 09:37
-< Use cross reference IDs >-
--------------------------------------------------------------------------------
Pi,
For text elements DECwrite automatically creates a hotspot of
every cross-reference you use. The way you do this is to create
your titles and assign a cross reference Reference ID (Do C S)
to each of them. For example, if you assigned a cross reference
ID to the section 2-1, Using Foobar when you use the reference ID,
a reference to that title's text (Using Foobar), label (2-1), or
page number becomes a hotspot in the Bookreader file when you Export
to Bookreader.
The above is also true for the label of a list item to which
you've assigned a cross reference ID.
When DECwrite V2.0 IFT becomes available (soon?) you'll be able to
hotspot any rectangular portion of any arbitrary graphic. By any
arbitrary graphic I mean a DECwrite drawing, scanned images, or images
created by a paint (DECpaint) program. If Bookreader supported
PostScript the same would be true of those images. I'll post a
separate note describing how to create graphic hotspots with a pointer
as a reply to this note.
Jack
|