OK, then suppose you store the attributes in the X-expressions for the purposes of your internal Pollen processing. You can always strip out those private attributes before the `doc` is injected into the HTML template. Does that work?
You're right that the X-expression closely models HTML output (which makes it a convenient choice for Pollen). But it's also a vanilla Racket list structure, so you can manipulate it with the usual list functions (with the `txexpr` module sugaring over some small annoyances) > On Apr 12, 2019, at 9:02 AM, dsockw...@gmail.com wrote: > > 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.
