Hi Cristobal!

Please, note, that FOP is mostly XSL:FO processor (.fo > .pdf or .fo > .ps) - 
not an XSLT processor (.xml > .fo). Of course, it has XML-XSLT generation 
capabilities (as a nice bonus), but rather than do a transformation by itself 
it relies on Xalan that is supplied with FOP (look at /lib catalog of FOP 
distro). So, you question is more concerns XSLT-processor (Xalan), but not FOP 
itself. Please, try to search in Xalan docs for capabilities you required. Or 
you can use double step transform: get .fo file by xsltproc and .pdf (or other 
print related formats) by FOP.

--
Best regards, 
 Eduard

-----Original Message-----
From: Cristobal Vio [mailto:[email protected]] 
Sent: Thursday, February 07, 2013 7:03 AM
To: Dew, Simon
Cc: [email protected]
Subject: Re: [docbook-apps] XInclude with xpointer and ID

Hi Simon!

That worked perfect with xsltproc, but fop keeps on complaining...

"Include operation failed, reverting to fallback. Resource error reading file 
as XML (href='../../.../antica_admin.xml'). Reason: XPointer resolution 
unsuccessful.2"

at least version 1.0

i'll try to install the newest version and try again

thanks a lot for your reply


2013/2/6 Dew, Simon <[email protected]>


        Hi Cristobal
        
        Instead of <section id="reqs">, try <section xml:id="reqs">
        --
        Simon Dew
        
        Technical Author | Stanley Security Solutions
        1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K.
        
        [email protected] | +44 (0) 161 406 3400
        www.stanleysecuritysolutions.co.uk
        
        Registered Office: Stanley House, Bramble Road, Swindon
        Registered in England and Wales No. 181585 VAT No. 232 2446 95
        

        On 06/02/13 19:41, Cristobal Vio wrote:
        
        > Hi all,
        >
        > I was trying to make a modular document with XIncludes using xpointer.
        > I would like to use them with the ID that tags are assigned. Like so
        >
        > some doc:
        > ...
        > <section id="reqs">
        >      <title>Requerimentos</title>
        > ...
        > </section>
        > ...
        >
        > some other doc:
        >
        > ...
        > <xi:include 
href="../../antica/antica-iwrs-procs-admin/antica_admin.xml"
        >                  xpointer="element(reqs)"/>
        > ...
        >
        > But this scheme is not working for me. Not in xsltproc neither in fop.
        >
        > if I use xpointer="element(/1/6)" , for example, it does work
        >
        > but that means that i cannot add an element (say a paragraph) before 
the
        > included elements, because that would mean that the numbering changes
        >
        > what is wrong with my scheme?
        >
        > i've searched lots of sites but i haven't found a similar problem,
        > besides some people that wasn't defining their DTD right
        >
        > btw, I'm using docbook version 5 and my docbook headers look like this
        >
        > <?xml version="1.0" encoding="UTF-8"?>
        > <!DOCTYPE article [
        > <!ENTITY % HashEnts SYSTEM "urn:xml-antica:llaves.ent">
        > %HashEnts;
        > ]>
        > <article version="5.0" xml:lang="es" 
xmlns="http://docbook.org/ns/docbook";
        >        xmlns:xlink="http://www.w3.org/1999/xlink";
        >        xmlns:xi="http://www.w3.org/2001/XInclude";
        >        xmlns:svg="http://www.w3.org/2000/svg";
        >        xmlns:m="http://www.w3.org/1998/Math/MathML";
        >        xmlns:html="http://www.w3.org/1999/xhtml";
        >        xmlns:db="http://docbook.org/ns/docbook";>
        >
        > where i add a DOCTYPE element because I need to use some entities file
        > defined somewhere else
        > of course the ones belonging to the included parts are of type 
section :)
        >
        > If someone of you could tell me the mistake im committing if any, it
        > would be very useful
        >
        > Thanks a lot!
        >
        >
        >
        
        
        ---------------------------------------------------------------------
        To unsubscribe, e-mail: [email protected]
        For additional commands, e-mail: [email protected]
        
        



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to