[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: `High-level' format specifications with XSL?
>>>>> "Kent Fitch" <kent.fitch@xxxxxxxxxxxx> writes: > <rule> > <target-element type="projecttitle"/> > > <H1> > <children/> > </H1> > </rule> Hm. In a previous message I wrote that I had tried something similar. Here's an excerpt from that message: I think I tried the obvious (to me) approach: I wrote rules like the following: ,----- | <rule> | <target-element type="projecttitle"> | </target-element> | <H1> | <children/> | </H1> | </rule> `----- This didn't work, though. It produced errors like this: ,----- | xslj:project.xsl:29:7:E: element "H1" undefined | xslj:project.xsl:29:4:W: unknown flow-object spec or macro | xslj:project.xsl:35:8:E: end tag for "rule" which is not finished `----- Obviously, my rule was pretty much the same as yours, and xslj choked on it, whereas MSXSL seems to be happy with it. Therefore the question is: which of the two implementations (if any) behave conforming to the standard-to-be? If MSXSL is correct, maybe one should send a bug report to the author of xslj. kai -- You ate somebody? -- Just a leg. -- That's terrible! -- Not with mustard. (Terry Pratchett: Interesting Times) XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|