Re: FM+SGML --> read/write rules

[Dan Emory <danemory@xxxxxxxxxxxx>]

At 05:09 PM 6/14/00 -0700, Douglas Wade wrote:
>To the list:
>
>Using FM+SGML read/write rules. At the top of many of them are #include
>statements. What is the order they are read and those values set.
>
>Are the includes values set when FM+SGML first sees the include file or is
>it read in on the bottom of the existing file it is reading.
>
>What value is set, the first or last occurrence?
======================================
To quote from Appendix F of the Developer's Guid:
"Remember that FM+SGML uses the first rule in a rules file that applies to 
a particular situation."
Thus, If you have the #include isoall.rw statement in your read/write 
rules, and you want to
add a special read/write rule for one of those ISO entities, the special 
rule must
precede the #include isoall.rw line.
====================
| Nullius in Verba |
====================
Dan Emory, Dan Emory & Associates
FrameMaker/FrameMaker+SGML Document Design & Database Publishing
Voice/Fax: 949-722-8971 E-Mail: danemory@primenet.com
10044 Adams Ave. #208, Huntington Beach, CA 92646
---Subscribe to the "Free Framers" list by sending a message to
majordomo@omsys.com with "subscribe framers" (no quotes) in the body.



** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **