[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

CSS processing (was Re: Re: Can XLink be fixed?)

• To: xml-dev@l...
• Subject: CSS processing (was Re: Re: Can XLink be fixed?)
• From: "Simon St.Laurent" <simonstl@s...>
• Date: Thu, 15 Aug 2002 16:04:09 -0400
• In-reply-to: <Pine.LNX.4.44.0208151445200.24890-100000@t...>

David Eisenberg writes:
> I think this is the same kind of problem I found when I was trying to 
> convert some XHTML strict to XSL-FO.  The post is at
> 
>   http://groups.yahoo.com/group/XSL-FO/message/2139
> 
> (essentially, how do I map <p class="important warning">...</p> to an 
> equivalent XSL-FO without parsing a stylesheet, or equally ugly, the
> class attribute.) 

I was planning to write a series of programs that would parse the CSS,
then apply the properties from that CSS (per the selectors) to the XML
structures I've built in MOE.  (MOE lets you add any annotations you
like to any node of a document.)

Initially I was thinking of creating a class representing CSS properties
as annotations separate from the XML, but I think I'll take that a step
further and create a namespace-based mechanism for representing the
properties as attributes.

Once I've gotten that far, it should just be an XSLT transformation to
XSL-FO.

Selector processing is the hardest-looking part of it, and I suspect
I'll start with just a subset.

Just need to find time!
-- 
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com

• References:
  • Re: Re: Can XLink be fixed?
    • From: "J. David Eisenberg" <catcode@c...>

• Prev by Date: Re: Re: Can XLink be fixed?
• Next by Date: Re: Re: Can XLink be fixed?
• Previous by thread: Re: Re: Can XLink be fixed?
• Next by thread: Re: Re: Can XLink be fixed?
• Index(es):
  • Date
  • Thread