[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: Dan Emory <danemory@xxxxxxxxxxxx>, Free Framers <framers@xxxxxxxxx>, "nasser.silakhori@xxxxxxxxxxx" <nasser.silakhori@xxxxxxxxxxx>
Subject: Re: Getting rid of Doctype declaration header?
From: "Lynne A. Price" <lprice@xxxxxxxxxxxx>
Date: Wed, 04 Aug 1999 13:13:37 -0700
In-Reply-To: <2.2.16.19990802235358.33470d0c@pop.primenet.com>
Sender: owner-framers@xxxxxxxxx
At 11:55 PM 8/2/99 -0700, Dan Emory wrote: >At 04:33 PM 8/2/99 -0700, Lynne A. Price wrote: >> One shortcoming you did not mention is that there is no provision >>for inherited exceptions on import. >===================================================== >How about an example of what you mean by "inherited exceptions"? >=============================================================== "Exception" is an SGML term that (pun intended) includes both inclusions and exclusions. So if you have, say, a Chapter element with a general rule like Title, Para+, Section* and an inclusion of IndexTerm, then any Section in a Chapter can include IndexTerm elements. However, when FrameMaker+SGML processes a fragment consisting of a Section, it has no way of knowing that that Section is intended for use within a Chapter and hence does not permit IndexTerms. If you have this situation, you can: 1) Change the EDD to specify explicitly in general rules where the "inclusions" are permitted 2) Avoid using fragments --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. **