[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: DOCBOOK: Re: Extra Spaces Caused by <indexterm>s
If it makes sense to attach the indexterms to an element with an id (rather than just a specific position in mixed content), you can have your indexterms out-of-line. For each indexterm, refer to appropriate target elements via the zone attribute, like this: <indexterm zone="some-id another-id"> <primary>Some term</primary> <secondary>what I meant was</secondary> <tertiary>to be precise</tertiary> </indexterm> It might actually be easier to maintain you index this way. In my case, the index is maintained by another person than the authors. The DocBook xml or sgml doesn't even have to be the primary storage or exchange format. Kind regards, Peter Ring -----Original Message----- From: David Cramer [mailto:dcramer@broadjump.com] Sent: 4. april 2002 22:14 To: Norman Walsh; Jeffrey Oldham Cc: docbook@lists.oasis-open.org Subject: RE: DOCBOOK: Re: Extra Spaces Caused by <indexterm>s I'm sure there's something flawed about this idea, but what if there were an <indextermset> element in the DTD that you could use to wrap a series of indexterm inside a para? Then when you process the para for presentation, you could strip out that entire <indextermset> and any spaces between its children. David > -----Original Message----- > From: Norman Walsh [mailto:ndw@nwalsh.com] > Sent: Tuesday, March 05, 2002 10:52 AM > To: Jeffrey Oldham > Cc: docbook@lists.oasis-open.org > Subject: DOCBOOK: Re: Extra Spaces Caused by <indexterm>s > > Unfortunately, the only way to avoid this problem is either to put the > indexterms between paragraphs (which is logically wrong) or to make > sure that you don't introduce extra spaces with your index terms: >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC