Eric,
I did not even think we needed an XHTML serializer, as I wasn't aware of those pseudo-XML-that-is-kind-of-compatible-with-HTML guidelines ;-)
I think the poster meant at the time that he was using the XML serializer, and just configuring it to set the correct DOCTYPE, etc.
Maybe simple text-based post-processing of the output of the XML converter (configured correctly for DOCTYPE, encoding, etc.) would suffice to implement and/or validate those guidelines?
-Erik
PS: The reason we now have XML / HTML / Text is that those are three three serialization methods defined by the XSLT spec. Those are actually now split into combinations of converters and Text serializer.
Eric van der Vlist wrote:
Hi,
It looks like a XHTML serializer has already been implemented in the past (http://mail.orbeon.com/pipermail/oxf-test/2004-August/000422.html)
Has it been published somewhere? If not, are they any plan to write another? Or should I write one by myself?
Thanks,
Eric
PS: by XHTML serializer, I mean a serializer that would implement the compatibility guidelines (http://www.w3.org/TR/xhtml1/#guidelines).
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
