| Context help - context id and generated html [message #274057] |
Thu, 14 October 2004 20:04  |
Eclipse User |
|
|
|
Originally posted by: greenj_nospam.nospam_ix.netcom.com
There's a nice xsl for DocBook for generating the TOC for Eclipse's
plug-in help system, which works great.
What seems to be missing is something for dealing with the fact that the
infopop help requires a context-id linked to a URL, but the URL may change
whenever the HTML is regenerated. (This is due to sections being added,
moved, etc.)
Has anybody built anything to deal with this? I'd hate to re-invent
something that's already been built.
|
|
|
| Re: Context help - context id and generated html [message #274058 is a reply to message #274057] |
Thu, 14 October 2004 21:04  |
| Eclipse User |
|
|
|
Originally posted by: greenj_nospam.nospam_ix.netcom.com
On Thu, 14 Oct 2004 17:04:42 -0700, John Green wrote:
> There's a nice xsl for DocBook for generating the TOC for Eclipse's
> plug-in help system, which works great.
>
> What seems to be missing is something for dealing with the fact that the
> infopop help requires a context-id linked to a URL, but the URL may
> change whenever the HTML is regenerated. (This is due to sections being
> added, moved, etc.)
>
> Has anybody built anything to deal with this? I'd hate to re-invent
> something that's already been built.
Never mind, I figured it out.
Use this:
<xsl:param name="use.id.as.filename" select="1"></xsl:param>
in your XSL. That forces the DocBook to HTML generation to use your XML
chapter and section IDs for the HTML filenames as well as for internal
anchors.
That way the URL is always static with the chapter/section ID that you
assigned in your xml, and you don't have to worry about keeping your
context IDs in sync with the URLs.
Hopefully this post will save someone else from struggling with the same
thing. :)
Regards,
John
|
|
|
Powered by
FUDForum. Page generated in 1.03559 seconds
Home