Thanks for the nudge. Declaring the default namespace (as db) and prefixing
all the selectors with db: seems to be what I should have done.
OTOH, still get the error message, so now using xsltproc and passing the FO
it writes along to XEP to format.
Not, in fact, using the DocBook XSLs. I get Pandoc to convert Markdown to
DocBook 5 XML to get some semantic markup, and then my own XSL for the FO.
(Haven’t been doing enough typesetting in recent years to warrant keeping
DocBook in my stack.)
If anyone’s interested, attached sample XML, XSL, FO and PDF.
Stephen Taylor | Librarian | *Kx* | +44 7713 400852 | stephen@kx.com
On 3 May 2018 at 19:23, <xep-support-request@renderx.com> wrote:
> Date: Thu, 3 May 2018 11:23:44 -0700
> From: "Kevin Brown" <kevin@renderx.com>
> To: "'RenderX Community Support List'" <xep-support@renderx.com>
> Subject: [xep-support] Re: line 1: Incorrect top element - should be
> 'root'
> Message-ID: <01a201d3e30b$df378720$9da69560$@renderx.com>
> Content-Type: text/plain; charset="utf-8"
>
> After reading up a bit on Docbook, I have been away for a bit ? it leads
> me to the question:
>
>
>
> Which Docbook XSLs are you using to process the input? Are you using the
> v5 Docbook XSLs?
>
>
>
> In reading the Docbook 5 documentation, it appears that the input is now
> in a default namespace and that is xmlns=http://docbook.org/ns/docbook.
>
> So the v5 Docbook XSLs should account for this.
>
> Which XSLs are you using?
>
>
>
> Kevin
>
_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
ww.renderx.com/terms-of-service.html
This archive was generated by hypermail 2.1.8 : Mon May 21 2018 - 08:34:16 PDT