Thanks, the error logs were my final salvation. The .xhtml file was crashing out with some unresolvable CSS references ... why that caused a docbook conversion failure I cant comprehend, but its clearly logged. Storing a "clean" .xhtml file and I get docbook !
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Geert Josten Sent: Monday, November 30, 2009 3:59 PM To: General Mark Logic Developer Discussion Subject: RE: [MarkLogic Dev General] Docbook Conversion from .xhtml -"OK"butno results Hi David, You can find the CPF processing status and state among the document properties. Have you tried running your steps from a clean setup? Create a new triggers database, a new documents database, connect the triggers database to the documents, install CPF with conversion option, make sure PDF, HTML, XHTML and DocBook pipelines are active in the default domain, and drop in a PDF and an HTML (using webdav or whatever). You can also enable trace events to get log entries that can help you understand what happens in the background. Details can be found in chapter 8.3 of http://developer.marklogic.com/pubs/4.1/books/cpf.pdf.. Kind regards, Geert > Drs. G.P.H. Josten Consultant http://www.daidalos.nl/ Daidalos BV Source of Innovation Hoekeindsehof 1-4 2665 JZ Bleiswijk Tel.: +31 (0) 10 850 1200 Fax: +31 (0) 10 850 1199 http://www.daidalos.nl/ KvK 27164984 De informatie - verzonden in of met dit emailbericht - is afkomstig van Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden ontleend. > From: [email protected] > [mailto:[email protected]] On Behalf Of > Lee, David > Sent: maandag 30 november 2009 21:16 > To: General Mark Logic Developer Discussion > Subject: RE: [MarkLogic Dev General] Docbook Conversion from > .xhtml - "OK" butno results > > 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 _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
