Searching for "cannot add @xml:base to node set root element" reveals this thread:
https://lists.oasis-open.org/archives/docbook-apps/201305/msg00050.html Does that help? Peter On Tue, Sep 17, 2013 at 11:43 AM, Morgan Hayward <[email protected]> wrote: > Hi Peter, > > Thanks for replying. The source DocBook XML is not being changed during the > build process and yes, we have confirmed the XML is valid DocBook XML. The > source XML is also one large file at build time. > > One other clue I just stumbled upon is this. We always get the duplicate TOC > entries if we see this at the start of the build process: > > Note: namesp. cut : stripped namespace before processing > WARNING: cannot add @xml:base to node set root element. Relative paths may > not work. > Note: namesp. cut : processing stripped document > WARNING: cannot add @xml:base to node set root element. Relative paths may > not work. > > However, if we see this, the TOC comes out normally: > > WARNING: cannot add @xml:base to node set root element. Relative paths may > not work. > WARNING: cannot add @xml:base to node set root element. Relative paths may > not work. > > I hope that helps shed more light on this problem. If any more information > is needed, please let me know. > > Regards, > Morgan > > -----Original Message----- > From: Peter Desjardins [mailto:[email protected]] > Sent: September-17-13 10:26 AM > To: Morgan Hayward > Cc: [email protected] > Subject: Re: [docbook-apps] Duplicate TOC Enries with WebHelp DocBook > > Is the source DocBook XML changing between the random occurrences of this > error? Also, are you validating the source XML? > > I'm wondering why the stylesheets are trying to find the title of a code > element. It sounds like you might be trying to process invalid DocBook XML. > > Have you broken the source XML into separate files? If so, maybe something > unusual is happening you are resolving the separate files into a complete > document? > > Peter > > On Tue, Sep 17, 2013 at 10:08 AM, Morgan Hayward > <[email protected]> wrote: >> Hi all, >> >> >> >> I'm using the WebHelp stylesheets in DocBook v1.78.0 to output an HTML >> version of my manual and something strange is happening. >> Occasionally, maybe once every three or four times I build the manual, >> the links in the TOC will appear twice. For instance: >> >> >> >> * Preface >> >> * Introduction >> >> * Installing the Device >> >> * Communication Ports >> >> * Technical Specifications >> >> * Dimension Drawings >> >> * Certification >> >> * Preface >> >> * Introduction >> >> * Installing the Device >> >> * Communication Ports >> >> * Technical Specifications >> >> * Dimension Drawings >> >> * Certification >> >> >> >> This problem seems to only appear when I get the following messages >> from DocBook during the build process: >> >> >> >> No template for "/code" (or any of its leaves) exists in the context >> named "title" in the "en" localization. >> >> Request for title of element with no title: code >> >> Writing ./Alerts.html for section(Alerts) >> >> . >> >> . >> >> . >> >> Writing ./Mounting_Device.html for section(Mounting_Device) >> >> Warning: multiple "IDs" for constraint linkend: >> Installing_Removing_Power_Supplies. >> >> Warning: multiple "IDs" for constraint linkend: Connecting_AC_Power. >> >> Warning: multiple "IDs" for constraint linkend: Connecting_DC_Power. >> >> >> >> With respect to the first error message, I have no >> templates/variables/parameters in my customization layer named "code". >> Nor can I find this word in the DocBook stylesheets. The second error >> is unclear to me. None of my IDs are repeated in the source XML, nor >> am I including the same XML twice (which would cause an ID conflict). >> >> >> >> Has anyone seen messages like this before? Know what they mean or >> what causes them? Are these related to the problem with the TOC? Any >> assistance will be appreciated. Again, this appears to happen >> randomly. Perhaps it is related to resources available at the time...? >> >> >> >> Regards, >> >> Morgan >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
