This bug applies to publican 2.3, at least for the html-single format (others not tested) Description of problem: A footnote in an element within a <biblioentry> causes the footnote to appear twice. This is the causing DocBook fragment: <biblioentry id="Unicode"> <indexterm><primary>Unicode</primary></indexterm> <title>The Unicode Standard<footnote><para>No version is given here, as this standard evolves over time. At the time of writing, the latest version was 6.0</para></footnote></title> <publisher><publishername>The Unicode Consortium</publishername></publisher> <biblioid class="uri">http://www.unicode.org</biblioid> </biblioentry>
Hi, I can't duplicate this behaviour on F14, can you tell us what version of the DocBook DTD and styles you are using?
Created attachment 462841 [details] Screenshot showing the effect
Created attachment 462843 [details] XSL style sheets that came with Publican 2.3
I don't see any CVS version tags or similar in the style sheets, so I simply attached them to this bug report. I am using DocBook 4.5. As I am using Ubuntu, I downloaded Publican from the repository of the upcoming 11.04 version ("natty"), as the current release for Unbuntu 10.10 is still 1.6.3. The version tag is "2.3-1ubuntu1", whatever this means. I also attached a small screenshot, depicting the problem. I am using my own branding (still not perfect), but should not have any effect on the structure of the HTML file as far as I understand the whole system. The problem does not occur with the multi-page ("html") format, by the way. The document that causes the problem is not that secret, but I don't want to make it public via Bugzilla. So if I had an e-mail address, I could supply the document if need be.
I can reproduce this on F19, but not in html-single; only in multi-page HTML. Updating subject accordingly.
HSS-QE has reviewed and declined this request. QE for this bug will be handled by IED.
To ssh://git.fedorahosted.org/git/publican.git f493597..4654b5a HEAD -> devel
footnote appears once in all formats verified with publican-3.1.5-0.fc19.t62.noarch
The fix for this bug has been shipped in publican 3.2.0