I use a simple set of macros in nxml mode that make things very easy.

Once nice thing, which may have been discussed before, would be if the 
stylesheets could somehow avoid inserting extra spaces in the text in the 
places where index terms are included. I've ended up only putting index terms 
at the beginning or end of paragraphs or immediately after titles to avoid that 
problem. It would be nice to be able to put them exactly where the term is in 
the text, so that if there's a break in the middle of a paragraph, the index 
entry still points to the right place.

Dick Hamilton
On Mar 8, 2012, at 11:25 AM, Bob Stayton wrote:

> My experience is that a good index is made by an iterative process. The first 
> pass of adding entries will have small inconsistencies in vocabulary, 
> groupings, see, and see also. The index person has to be able to process the 
> entries, review the index, and make adjustments in the indexterms.
> 
> For adding indexterms, a macro or two in your XML editor can speed things up 
> quite a bit.
> 
> Bob Stayton
> Sagehill Enterprises
> [email protected]
> 
> 
> ----- Original Message ----- From: Xmplar
> To: [email protected]
> Sent: Thursday, March 01, 2012 9:13 PM
> Subject: [docbook-apps] Embedding indexterms for fo and html
> 
> 
> I'm just starting to experiment with the automatic index generation, 
> following the procedure in The Complete Guide, and wondered if anyone would 
> like to comment on how they approached the procedure to generate indexes for 
> PDF and HTML output. Are there any shortcuts to specifying the indexterms? 
> Did you do any post-generation editing for the HTML index? It'd be great to 
> get some insight.
> Thanks,
> 
> -- 
> Dave Gardiner 
> 
> ---------------------------------------------------------------------
> 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