Description of problem: Assigning a bridgehead an ID, for example: <bridgehead id="eels">Eels</bridgehead> and then linking to it using an xref: <xref linkend="eels"/> produces a correct link in the html, but when clicked, it does not take you to the actual bridgehead.
Modified template anchor to match bridgehead better. Committed revision 1788.
wow this fix shipped ages ago!
~]$ rpm -q publican publican-2.8-1.fc15.noarch Linking to a bridgehead still doesn't work. Re-opening.
hmm must have been reverted at some time... Reapplied patch to trunk. Committed revision 2022.
The referencing works, but the produced link has the anchor of the format: Section x.y, "Eels". where x.y is the section (which has a different title) that contains that particular bridgehead. This may be confusing to users as you are saying it's section x.y and yet the name of that section is not Eels. Hope this makes sense. I think the produced html link should just says "Eels" and the author will be responsible for ensuring it makes sense grammatically. Moving back to ASSIGNED. Thanks!
(In reply to comment #5) > I think the produced html link should just says "Eels" and the author will be > responsible for ensuring it makes sense grammatically. Unfortunately removing the title makes it impossible for translators to make sense grammatically. We've debated this on numerous occasions and we've always come back to having the label in the xref as the default. Brands can override this if they choose to do so. FWIW the label used 'Section' it set in the DocBook translation XSL, so a bug would need to be lodged upstream if a different label was sought for bridgeheads.
(In reply to comment #0) > Description of problem: > > Assigning a bridgehead an ID, for example: > > <bridgehead id="eels">Eels</bridgehead> > > and then linking to it using an xref: > > <xref linkend="eels"/> > > produces a correct link in the html, but when clicked, it does not take you > to the actual bridgehead. execute the above
Linking works as expected. Moving to VERIFIED.