As a follow-up to my initial reply (and sorry for the typo in your name), the XHTML document should be in the XHTML namespace (which my initial example did not do). E.g.:
<html xmlns="http://www.w3.org/1999/xhtml"> ... </html>
As a side note, it is also possible and actually recommended by the XHTML 1.1 spec to set application/xhtml+xml as as content-type. IE unfortunately does not appear to be able to display documents with that content-type, but Mozilla works like a charm.
I attach the modified example with those changes.
-Erik
Erik Bruchez wrote:
> Juston, > > You have to use the XML Serializer (uri="oxf/processor/xml-serializer"). > This will ensure the serializer outputs XML, not HTML. You can set the > correct public and system doctypes in the serializer configuration, as > documented here: > > http://www.orbeon.com/oxf/doc/processors-serializers > > I attach a small example of pipeline that you can try out, for example > by adding the following in your controller.xml: > > <page path-info="/examples/test" model="../test/xhtml.xpl"/> > > This will generate the strict doctype: > > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> > > -Erik > > Justin Makeig wrote: > > > I still don't understand how to generate XHTML 1.0 Strict. I thought > one of > > the new features of v2.0 was an easily configurable HTML serializer. > Do I > > really have to write my own? > > > > - Justin Makeig >
xhtml.xpl
Description: audio/scpls_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
