[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] role and xml:id
Hi Jacques, On Freitag, 2. November 2007, Jacques Foucry wrote: > On 2 nov. 07, at 23:35, Thomas Schraitle wrote: > > 1. Did you validate your files? How? > > My files are validate with saxon with a oXygenXML scenario. > > > 2. Do you use XIncludes or external entities? > > I use XInclude, enabled in oXygenXML, and it works, all the texts are > présent in my PDF. > > > 3. Which tools do you use? > > I use oXygen as editor and saxon6.5.5 and XEP. > All of the above seems ok to me. > > 4. Do you use profiling? > > Yes. I use the role os=leopard. In my oXygen scenario with > profile.os="leopard". I think here is the problem. Probably you allow other values in your os attribute. When you profile it with this value, the section with os="leopard" disappears. Just to show you what I mean, I wrote a small test file, similar to your example: -------[ article.xml ]------------ <article xmlns="http://docbook.org/ns/docbook" version="5.0"> <title>Small test</title> <section os="leopard" xml:id="anID"> <info> <title>Leopard</title> </info> <para>blah</para> </section> <section xml:id="other"> <info> <title>Another Section</title> </info> <para>Please refer to <xref linkend="anID"/></para> </section> <section os="foo"> <info> <title>The Foo Section</title> </info> <para>...</para> </section> </article> ---------------------------------- Then I run it with the following line ($DB contains the path to the DocBook XSL stylesheets): $ xsltproc --output article-foo.xml \ --stringparam profile.os "foo" \ $DB/profiling/profile.xsl article.xml In this case, the section with xml:id="anID" disappears and therefor you get a validation error. > > I may be wrong, but perhaps you forgot to xinclude the respective > > file? Or > > you filtered out some sections with profiling? > > The section are in the result PDF, the only things missing are the > links and the title refs. A solution could be to insert the parent para with an os="leopard" like this: <para os="leopard">Please refer to <xref linkend="anID"/>.</para> Did you tried this? Hope that helps, Tom -- Thomas Schraitle
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]