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, but metadata content isn't valid everywhere, so that wouldn't be *quite* valid. (Might be valid *enough*.)
My backup suggestion was to have your pre-processor attach the content of the processing instructions as data-xyz attributes, either on their parent element or the element that follows them, whichever makes more sense for what you're doing. Not ideal at all, as they'll get relocated if they appear inside a large block of text, but...  http://www.w3.org/TR/html5/content-models.html#metadata-content Good luck, -- T.J. :-) On Apr 28, 2:15 pm, Walter Davis <wa...@wdstudio.com> wrote: > 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 if I can figure out another way to go. > > Walter > > On Apr 28, 2011, at 5:15 AM, T.J. Crowder wrote: > > > > > > > > > It isn't, strictly speaking *valid* because (for instance) you can't > > have a `script` element that's an immediate child of a `ul`. But > > firstly, that seems like an error in the spec (why not?), and > > secondly, the browsers don't seem to mind. -- 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 firstname.lastname@example.org. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.