<RefEntry id="X25generate-legalnotice-linkX25">
<!-- This file is generated automatically from the DSSSL source. -->
<!-- Do not edit this file! -->
<?html-filename generate-legalnotice-link.html>

<RefMeta>
  <RefEntryTitle>%generate-legalnotice-link%</RefEntryTitle>
  <RefMiscInfo Role="file">dbparam.dsl</RefMiscInfo>
</RefMeta>

<RefNameDiv>
  <RefName>%generate-legalnotice-link%</RefName>
  <RefPurpose>Should legal notices be a link to a separate file?</RefPurpose>
</RefNameDiv>

<RefSynopsisDiv><Title>Synopsis</Title>
<Synopsis>
%generate-legalnotice-link%
</Synopsis>
</RefSynopsisDiv>

<RefSect1><Title>Description</Title>

<para>
If true, legal notices will be references to a separate file.
Note: the support for this handles the case where a single *INFO
node contains several distinct legal notices, but won't
handle multiple legal notices in different *INFO nodes.
(Each set will overwrite the previous.)  A more complex
approach could be implemented, but this is sufficient for
the current demand.  Let me know...</para>


</RefSect1>
<RefSect1><Title>Source Code</Title>

<ProgramListing>
(define %generate-legalnotice-link%
  ;; Should legal notices be a link to a separate file?
  #f)
</ProgramListing>
</RefSect1>

</RefEntry>
