El Martes, 5 de Julio de 2005 08:39, Alexander E. Patrakov escribió: > I think that the biggest trouble is that xpointer expressions include > some meaningless offset numbers like para[2] instead of assigning a > meaningful name to the exact text to be copied to another page.
The more simplest way is using ID attributes: ----parent.xml--- <para id="some-ID">Text to be xincluded.</para> -------- --child.xml-- <xi:include href="parent.xml" xpointer="id('some-ID')"/> -------- The problem: by definition, each ID must be unique into each full book. Then, after do the Xinclude processing the sources will not validate due duplicated IDs. Another way is using a different common DocBook attribute, like "role", if there is no conflicts with its other current uses in the XSL templates. ----parent.xml--- <para role="some-unique-string">Text to be xincluded.</para> -------- --child.xml-- <xi:include href="parent.xml" xpointer="xpointer(//[EMAIL PROTECTED]'some-unique-string'])"/> -------- Now the problem is, what police should we to use to define in an standardized way that some-unique-strings? Solving that (and the possible conflicts with the stylesheets) it could fix both issues: to be sure that the proper block is always the one that we are importing, and to know beforehand that some block is exported to other file(s). -- Manuel Canales Esparcia Usuario de LFS nº2886: http://www.linuxfromscratch.org LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.com TLDP-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page