That's a very cool idea, certainly do-able with about 2 lines of Ruby
code in my pre-processor! Thanks for the suggestion.
Walter
On Apr 28, 2011, at 5:15 AM, T.J. Crowder wrote:
Walter,
Unfortunately, I think you're out of luck, because I don't think
browsers retain processing
Aha, I just read further, and it appears this won't work for what I'm
doing, which is in part creating a valid XHTML branch to build epub
documents, PrinceXML PDF documents, etc. from. I could certainly strip
these out when building those iterations, but I guess I'll keep
looking and see
Hi,
Yeah, I don't think there's any valid way to do this in XHTML without
a lot of work. You could turn them into namespaced non-HTML XML
elements as discussed here[1], but metadata content isn't valid
everywhere, so that wouldn't be *quite* valid. (Might be valid
*enough*.)
My backup suggestion
Template evaluate returns a string. What is the best way to go from string
to Element?
--
You received this message because you are subscribed to the Google Groups
Prototype script.aculo.us group.
To post to this group, send email to prototype-scriptaculous@googlegroups.com.
To unsubscribe
You can insert it, and it will be instantiated into the element you
desire, assuming that it is valid HTML after it's been evaluated, and
you're inserting it into a spot in the DOM where that makes sense. For
example, a TR inside a TBODY or THEAD, a SPAN inside a P...
If you want to make
