> > You could preserve the semantic information inside a `class` attribute, or > custom attribute. These would also be reachable through CSS selectors, if > you're into that. >
True, and I considered that. (Something like '(define book (default-tag-function 'li #:class "book"))` would do the trick nicely). But note that that's not quite what I was asking about: that preserves the semantic info all the way through to the generated HTML. As you mentioned, that could be good if I wanted to apply CSS based on the semantics. But it wouldn't do what I was asking about: keep the semantics in the X-expression without keeping them in the HTML. Based on your answer, I'm assuming that there isn't a simple way to do what I was asking. Based on that (and rereading some of the docs), I've concluded that I was thinking of the generated X-expression all wrong. I was thinking of the X-expression as basically still a source file, albeit one that has been processed. But I it seems like it's very nearly an output file—it's pseudo-HTML (or pseudo-text, or pseudo-LaTex, or whatever the final output format is). From that point of view, it makes perfect sense that it'd have a structure that's limited to the semantics of HTML/text/LaTex. -- You received this message because you are subscribed to the Google Groups "Pollen" group. To unsubscribe from this group and stop receiving emails from it, send an email to pollenpub+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
