[Date Prev][Date Next] [Thread Prev][Thread Next]
[Date Index] [Thread Index] [New search]

RE: Getting rid of Doctype declaration header?



Sorry, I mispoke. It's not in the SGML fragment file, but when the fragment
is imported into an FM+SGML document, it gets wrapped in the SGMLFragment
element.
At 08:51 AM 8/3/99 -0700, Hogan, John (Tempe) wrote:
>---------------Snip
>
>3. As you mention, on import of the SGML fragment as a text inset into
>the
>larger FM+SGML document, it retains the SGMLFragment element, which, in
>this
>case, is not a highest-level element. 
>
><deleted>
>************************************************************
>
>But the SGML fragment would not contain an element named <SGMLFragment>.
>That element is a FrameMaker+SGML construct and is defined only in the
>EDD. If you used 'SGMLFragment' from within Frame to create an SGML
>fragment as Lynne suggested, the EDD element 'SGMLFragment' would have
>been stripped by Frame on export to SGML. Then, when you import the
>fragment as a text inset into a structurally valid location, it does not
>insert the 'SGMLFragment' element (you must make sure that your fragment
>will be valid where inserted).
>
>I don't argue with your other cautions. I see the technique as having
>more value for creating structured FM+SGML fragments for reuse in
>standardized documents.
>
>
     ====================
     | 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.   **