Thanks Mary ... I could follow you all the way to almost the end. The xhtml document is not text (I can query it). It is in the right namespace. I did NOT have the xhtml processing enabled so I enabled it. But no docbook output.
Your last paragraph " Do you have the XHTML processing attached to your domain? (vs. just the HTML processing?) I believe the DocBook pipeline as shipped responds to XHTML only in the structured-xhtml state. If you want to skip the XHTML post-processing, you'll need to have a version of the DocBook pipeline that has the appropriate state transition. See what state your XHTML document is in." How do I determine what "state" my XHTML document is in ? and how would I change that state to trigger the docbook conversion ? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mary Holstege Sent: Monday, November 30, 2009 11:30 AM To: General Mark Logic Developer Discussion Subject: Re: [MarkLogic Dev General] Docbook Conversion from .xhtml - "OK" butno results On Thu, 26 Nov 2009 14:49:39 -0800, Lee, David <[email protected]> wrote: > I'm experimenting with the HTML -> XHTML -> Docbook conversions. > > I've enabled the Content Processing framework. > When I drop PDF file into the directory all goes well, I get an .xhtml > file and a .xml file (docbook format). > > > But when I drop a plain .html file I get a .xhtml file but no .xml ... > > Manually in CQ I tried this command > > import module namespace dbk = "http://marklogic.com/cpf/docbook"; at > "/MarkLogic/conversion/docbook.xqy"; > > let $options := <options xmlns="dbk:convert"> > <wrap-text>false</wrap-text> <preserve-styles>true</preserve-styles> > </options> > > return dbk:convert(fn:doc("/PDF/cat_html.xhtml"), $options) > > And the result is simply > > <status>ok</status> > > But no docbook content. > > Changing the command to use the .xhtml file produced by the PDF > conversion and I get the docbook contents. > > Any ideas on where to look for what went wrong ? > > Thanks. Check that the XHTML document (a) exists, (b) is XML, not text (i.e. that fn:exists(doc("your.xhtml")/*)), and (c) is in the http://www.w3.org/1999/xhtml namespace. If it came out of the XHTML conversion pipeline, all this should be true, but it is worth checking. Do you have the XHTML processing attached to your domain? (vs. just the HTML processing?) I believe the DocBook pipeline as shipped responds to XHTML only in the structured-xhtml state. If you want to skip the XHTML post-processing, you'll need to have a version of the DocBook pipeline that has the appropriate state transition. See what state your XHTML document is in. //Mary _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
