On Thu, 23 Aug 2001, Rev Lebaredian wrote:
> Sean M. Burke wrote:
>
> > At 21:41 2001-08-21 -0700, Patty wrote:
> >
> >> Can anyone tell me more about the X<index> command?
> >
> >
> > Example from the book I'm working on:
> >
> >
> > =head2 The URI class, and Absolutizing Relative URLs
> >
> > X<URI.pm (class for URLs)>X<relative URLs,
> > absolutizing>X<absolutizing relative URLs>The URI class
> > (which is actually, behind the scenes, a whole class hierarchy)
> > does a lot of things, one of which is specifically most useful here:
> > URI.pm provides a way to absolutize URLs. [...]
> >
>
> Many indexes I've seen often have two levels. For example looking at
> page 644 in "Programming Perl" I see :
>
> ....
> tokens, 44, 139-140
> parsing text into, 510
> top-of-form processing, 123, 210, 242
> ...
>
> Since we are trying to nail down the POD spec, how do you guys suggest
> we represent this sort of indexing? I suggest using "/". For example
> the previous index could be generated with the following tags appearing
> in the document :
>
> X<tokens> # Shows up in pages 44, 139, and 140
> X<tokens/parsing text into> # Shows up in 510
> X<top-of-form procssing> # Shows up in 123, 210, and 242
>
>
> What do you guys think?
>
I agree that X<> is underspecified and would welcome a way of specifying
nesting (this maps nicely to latex - I have to deal with the issue in
Pod::LaTeX).
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
