[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: FrameSGML@xxxxxxxxxxx, Douglas Wade <dwade@xxxxxxxxxxxx>, "FrameSGML List" <FrameSGML@xxxxxxxxxxx>, "Free Framers" <framers@xxxxxxxxx>
Subject: Re: [FrameSGML] Re: FM+SGML --> read/write rules
From: "Lynne A. Price" <lprice@xxxxxxxxxxxx>
Date: Sun, 18 Jun 2000 10:29:16 -0700
In-Reply-To: <4.2.0.58.20000614212115.0098d5c0@pop.primenet.com>
References: <LYRIS-25280-21697-2000.06.14-17.09.33--danemory#primenet.c om@lists.frameusers.com>
Sender: owner-framers@xxxxxxxxx
At 09:25 PM 6/14/00 -0700, Dan Emory wrote: >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. Dan, You are correct that the include directives are processed in the order encountered, and that when multiple rules apply, the first one is supposed to be used. This precedence applies, for example, when there are multiple element rules for a single GI. However, you pointed out to me just a few weeks ago that it doesn't seem to be predictable which rule will be used when there are multiple rules for a single character entity. --Lynne Lynne A. Price Text Structure Consulting, Inc. lprice@txstruct.com http://www.txstruct.com ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **