Specifying A Search Path For Including Files In Rules Documents - Adobe 65030365 - FrameMaker - PC Developer's Manual

7
A p p l i c a t i o n d e f i n i t i o n f i l e
An Entities element can contain only one EntitySearchPaths element. The software
assumes the EntitySearchPaths element ends this way:
EntitySearchPaths
. . .
N: $SRCDIR
Thus, if there is no EntitySearchPaths element, the software assumes all markup files
are in the same directory.
Example
Assume the Defaults element is defined as follows:
Defaults
Entity locations:
FilenamePattern: $(System).sgm
FilenamePattern: $(System).$(Notation)
EntitySearchPaths
and the markup document contains:
<!ENTITY intro SYSTEM "introduction.xml">
<!ENTITY chips SYSTEM "chipsfile" NDATA cgm>
. . .
&intro;
. . .
<graphic entity=chips>
When processing the reference to intro, the software looks for the files:
$HOME/introduction.xml
$SRCDIR/introduction.xml
until it finds one of those files. When processing the graphic element, the software
searches in order for:
$HOME/chipsfile.cgm
$SRCDIR/chipsfile.cgm

Specifying a search path for including files in rules documents

The RulesSearchPaths element is analogous to the EntitySearchPaths element, but
it pertains to additional files you include in a read/write rules document rather than to
Working with Special Files
1: $HOME
2: $SRCDIR
64