[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: Marcus Carr <mrc@xxxxxxxxxxxxxx>, FrameSGML@xxxxxxxxxxx
Subject: Re: [FrameSGML] Re: What's new in 6.0
From: Dan Emory <danemory@xxxxxxxxxxxx>
Date: Mon, 13 Mar 2000 20:16:26 -0700 (MST)
Cc: "Framers@xxxxxxxxx" <framers@xxxxxxxxx>
Sender: owner-framers@xxxxxxxxx
At 12:32 PM 3/14/00 +1100, Marcus Carr wrote: > >Dan Emory wrote: > >> I don't care whether it's called XSL FU or cascading style sheets or >> whatever, as long as it's W3C-compliant. > >Are you suggesting that the CSS that is currently being created is not compliant? >Can you elaborate? > >> What I want to see is style >> information that's derived from the EDD's format rules without the >> restrictions that currently apply in V5.5.6. Those restrictions are so >> limiting that the resulting style information is useless. > >Details, Dan! How do expect anyone to comment based on that paragraph? ============================================================== Here is a direct quote from the Download FrameMaker+SGML 5.5.6 XMLcss Plug-In: "When you export a structured document to XML use FrameMaker+SGML 5.5.6, both an XML document and a CSS document are produced. The information in the CSS document is based on the formatting information in the paragraph catalog and in the font catalog. If the element names in your FrameMaker+SGML document do not correspond with the paragraph tags and the charactertags used to format these elements, the formatting may be inadequate. The XMLcss plug-in examines the actual formatting used in the FrameMaker+SGML document and produces a CSS that ties element names to the actual formatting of these elements. Context-based formatting fules are handled correctly too." What this means is the every paragraph-type container element in the EDD must specify a specific paragraph tag in every possible context. Formatting in format change lists, as well as specifying individual format parameters within format rules are not picked up in the CSS document. The same goes for text range elements--Each such element must specify a particular character tag for each context. Only an EDD that conforms to the above constraints can produce a non-anomalous CSS document. But that type of EDD is extremely cumbersome, and flies in the face of good design practice. ==================== | 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. **