OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [docbook-apps] XInclude with xpointer and ID


Thanks Eduard and Eric!

The processing with xsltproc->fop works just fine.
Although the file references in the resulting fo file (for media objects at least) are relative to the xml processed file (input) so i would have to descend to the dir containing it in order to issue the fop command, but that is a minor issue

Anyways, it would be nice if I could get rid of it by using the namespace definition in fop as suggested by Eric
But, Im not familiar with namespaces and schemas...
in order to do so i'm almost sure I need

1) A line with the following content, probably in the opening of the tag article (or section)

xmlns:xs="http://www.w3.org/2001/XMLSchema"

2) Another line like this one or similar, but I can't figure out where to put it

<xs:attribute name="xml:id" type="xs:ID"/>

could you please help with that?

My apologies for a possibly trivial question
Thanks in advance,

Cristóbal



2013/2/7 Eric Johnson <ejohnson@redhat.com>
IIRC Xalan requires that you include the schema definition in the document's header for xml:id resolution to work.




On 02/07/2013 08:01 AM, Eduard Tibet wrote:
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:crvio@antica.cl]
Sent: Thursday, February 07, 2013 7:03 AM
To: Dew, Simon
Cc: docbook-apps@lists.oasis-open.org
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="">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 <Simon.Dew@sbdinc.com>


        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.
       
        Simon.Dew@SBDInc.com | +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="">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: docbook-apps-unsubscribe@lists.oasis-open.org
        For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
       
       



---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org



---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]