Well, I see your point, however, since L<>'s are user created, it would
make sense that the user should know what they are pointing to. I don't
think that improving the name references to be unique in such cases
actually causes a major problem.
However, I can see that it might make things beyond plain old and maybe
that isn't preferred.
I guess that's why I have the source!
Do you know of any of the pod2<what>'s that handle this problem?
--bob w.
On Thu, Nov 13, 2003 at 08:54:12AM +0100, [EMAIL PROTECTED] wrote:
> Hello Bob,
>
> I understand your reasononing, but there's a problem: What
> if other PODs refer to such a subtopic with
> L<yourpod/"podsubtopic 1">
> Where should this link to? The one in podtopic i or ii?
> The (limited) syntax of L<> currently does not support
> such hierarchies. On the other hand, you may want to link
> to these POD->HTML pages from elsewhere, and there you might
> be able to specify the exact location, but beware - when
> the formatter (POD->HTML) changes, the <a name>'s might be
> different, and then you're lost.
> I'm afraid that the only viable way is to link to the
> "podtopic i" and "podtopic ii", and not their (ambiguous)
> subtopics.
>
> Cheers,
>
> Marek
>
>
> > I would like to be able to create pod files with
> > redundant =head elements which end up being unique in the the
> > outputted TOC links in the html
> > from pod2html. So, essentially I'd like pod2html to keep
> > track if head
> > elements are redundant and make unique "<a name="ref_id">"
> > name reference
> > tags if they are.
> > Is this in the works, or already available? Or do you have a
> > recommendation on how to make this happen easily? Or maybe
> > pod2fm or another tool takes care of it somehow?
> >
> > Thanks!
> >
> > --bob w.
> >
> > So, for instance, if I made a pod block like this...
> >
> > =pod
> >
> > =head1 podtopic i
> >
> > =head3 podsubtopic 1
> >
> > =head3 podsubtopic 2
> >
> > =head3 podsubtopic 3
> >
> > =cut
> >
> > And then later in the document I made
> >
> > =pod
> >
> > =head1 podtopic ii
> >
> > =head3 podsubtopic 1
> >
> > =head3 podsubtopic 2
> >
> > =head3 podsubtopic 3
> >
> > =cut
> >
> > I would like the outputted HTML to contain something like this...
> >
> > <a href="podtopic i">podtopic i</a>
> > .
> > .
> > .
> >
> > <a name="podtopic i"></a>
> > <h1>podtopic i</h1>
> > <a name="podsubtopic 1"></a>
> > <h3>podsubtopic 1</h3>
> > <a name="podsubtopic 2"></a>
> > <h3>podsubtopic 2</h3>
> > <a name="podsubtopic 3"></a>
> > <h3>podsubtopic 3</h3>
> >
> > .
> > .
> > .
> >
> > <a name="podtopic ii"></a>
> > <h1>podtopic ii</h1>
> > <a name="podtopic_ii_podsubtopic 1"></a>
> > <h3>podsubtopic 1</h3>
> > <a name="podtopic_ii_podsubtopic 2"></a>
> > <h3>podsubtopic 2</h3>
> > <a name="podtopic_ii_podsubtopic 3"></a>
> > <h3>podsubtopic 3</h3>
--
Robert Waldrop Motorola Personal Communications Sector
[EMAIL PROTECTED] Urbana-Champaign Design Center
voice 217-384-8719 1800 South Oak Street
Champaign IL 61820
[X] Motorola General Business Information
[ ] Motorola Internal Use Only
[ ] Motorola Confidential Proprietary
