Bug 616112 - IDs not set on admonitions or varlistentry
Summary: IDs not set on admonitions or varlistentry
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 2.0
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Michael Hideo
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-19 17:23 UTC by Douglas Silas
Modified: 2010-11-24 03:59 UTC (History)
4 users (show)

Fixed In Version: publican-2.2-0.fc13
Clone Of:
Environment:
Last Closed: 2010-10-10 23:26:09 UTC
Embargoed:


Attachments (Terms of Use)

Description Douglas Silas 2010-07-19 17:23:01 UTC
Description of problem: setting the ID of an important admonition does not cause an anchor to be generated for that element, even if it is referenced via an xref. The xref does generate an href anchor that, however, is missing from the target. 

This is probably similar to bug 595564.


Version-Release number of selected component (if applicable):

version=2.1

How reproducible:

Steps to Reproduce:
1. xref to the ID of an important admonition
2. publican build (html-single in this case)
3. open document, click on link to admonition, no jump
  
Actual results:

nothing

Expected results:

jump to link

Additional info:

Generated link HTML is:

<a class="xref" href="#important-Smart_package_group_removal" title="Smart package group removal">Smart package group removal</a>

Generated target HTML is:

<h2>Smart package group removal</h2><a id="id4869860" class="indexterm"></a><a id="id4869872" class="indexterm"></a>

Comment 1 Douglas Silas 2010-07-19 17:42:36 UTC
Perhaps the creation of anchors for indexing overrides or affects the generated anchors?

Comment 2 Douglas Silas 2010-07-22 21:07:54 UTC
Note: this problem also occurs when linking to varlistentry elements.

Comment 3 Jeff Fearn 🐞 2010-08-04 06:04:14 UTC
Set IDs on admonitions & varlistentry

Fixed in Build: 2.1-0%{?dist}.t13

Comment 4 Ruediger Landmann 2010-08-06 04:26:53 UTC
Verified in 2.1.t20


Note You need to log in before you can comment on or make changes to this bug.