forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin" <ga...@16degrees.com.au>
Subject generate-id and @id (skins)
Date Mon, 11 May 2009 00:43:40 GMT
HI All,

Just wondering on the implementation of generate-id when @id are already
present.

Example, in sample.xml we have 

<section id="link-class">

which gives us a generated file with

<a name="N102CC"></a><a name="link-class"></a>

Now, I don't see the generated-id as being referenced anywhere, whereas
'link-class' is referenced from the toc.

This seems to be the situation for all <section id="..."> , they all get a
generated id also.

In document-to-html.xsl we have :-

  <xsl:template match="section">
<!-- count the number of section in the ancestor-or-self axis to compute
         the title element name later on -->
    <xsl:variable name="sectiondepth"
select="count(ancestor-or-self::section)"/><a name="{generate-id()}"/>
    <xsl:apply-templates select="@id"/>
...

which causes the above behaviour.

So, just wanted to query, should we use the given id and not use generate-id
unless an id is not given? (as 'id' is not a required attribute of section)
? That way we have one named anchor or the other, not both.

Gav...


Mime
View raw message