If you use entities, you have to declare them in the DTD/internal subset. Another strategy is to have a preprocessing xsl step that replaces a marker of some sort with another piece of the document. This requires customization of the DTD and writing an xsl:
<para id="foo" is_shared="yes">My example text.</para> ... <share_para sharer_id="foo"/> Where <share_para> is replaced with <para id="foo"> (and the id is omitted in the copy). Note that if the para being shared contains elements that have ids, you'd need to strip or munge them and you need to watch for recursion. We've got a system like this set up by which we share content within and between documents. We call it 'holmanization' because the inspiration for it came from a conversation with Ken Holman <http://www.cranesoftwrights.com/>. The 'is_shared' attribute on the sharing para is just a little flag to remind you that changing this text affects other parts of the doc. David > -----Original Message----- > From: Christopher J. Graham [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 20, 2002 3:36 PM > To: Camille Bégnis > Cc: [EMAIL PROTECTED] > Subject: Re: DOCBOOK-APPS: same text in different areas > > > a bit uncertain... is it possible to do that in line? > Otherwise I would have > lots of ENTITY elemets in my header. > > <para><!ENTITY test-a "my example text">&test-a;</para> > ... > <para>&test-a;</para> > > > on 3/20/2002 3:22 PM, Camille Bégnis at > [EMAIL PROTECTED] wrote: > > > "Christopher J. Graham" a écrit : > >> > >> Hello all: > >> > >> Is it possible to have the same <para> (or any other > element) content in two > >> locations? I am trying to make sure that if it is edited > in one location, > >> then the other is also updated. > > > > Simply define an entity: > > http://docbook.org/tdg/en/html/ch01.html#s-entities > > > > Camille. > > > >> For instance, > >> > >> <para>text-a</para> > >> . > >> . > >> . > >> <para>text-a</para> > >> > >> Regards > >> > >> > -------------------------------------------------------------- > ---------- > >> Christopher Graham > >> [EMAIL PROTECTED] > >> > >> PGP Fingerprint: F765 CCB5 B9CF 1285 7E3E 8CB0 0B1B 8454 9D66 D411 > > > -------------------------------------------------------------- > ---------- > Christopher Graham > [EMAIL PROTECTED] > > PGP Fingerprint: F765 CCB5 B9CF 1285 7E3E 8CB0 0B1B 8454 9D66 D411 > >