- markup (52)
- xml (7)
- xslt (21)
- atom (8)
- overlapping markup (2)
- schema (9)
- creole (4)
- xforms (1)
- pipelines (7)
- coding (2)
- dtll (1)
- genealogy (3)
- gtd (1)
- hardware (1)
- legislation (1)
- ontologies (2)
- unicode (1)
- web (24)
- google (3)
- rdf (6)
- rest (3)
- wikis (1)
- work (1)
- xpath (1)
- xquery (1)
- xtech2008 (3)
- life (26)
- children (5)
- equality (6)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (7)
- xtech (6)
- blog (7)
- drupal (3)
Re: Processing CSS and pipelines with XSLT
Yes, I’m doing some CSS parsing, but it’s pretty straight-forward: all the CSS is generated from the WordprocessingML-to-XHTML stylesheet, so it’s very predictable, and I’m not doing all the things that I should be regarding ignoring the contents of string literals and so on. Also, the selectors that I’m dealing with are all very simple (just element names or class names with preceding
.) so working out how to apply declarations to individual elements isn’t as complicated as it would be in the general case.I agree with your observations about being able to isolate particular parts of a pipeline being incredibly useful for debugging.