Bug 735063 - HTML output omits certain xrefs
Summary: HTML output omits certain xrefs
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: Documentation (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Thomas Schraitle
QA Contact: Karl Eichwalder
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-06 12:37 UTC by Tanja Roth
Modified: 2012-07-12 13:50 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
HA Guide (PDF Output) (4.27 MB, application/pdf)
2011-12-06 12:40 UTC, Tanja Roth
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tanja Roth 2011-12-06 12:37:26 UTC
The current HTML output of our doc sources omits xrefs completely if they contain xrefstyle="select:nopage".

Berhard stumbled across this in 
http://docserv.suse.de/generated/books/SLE-HA/SLE-ha-guide_sd_remarks_comments/cha.ha.configuration.hawk.html#sec.ha.config.hawk.templates:

5. Specify the resource template as you would specify a primitive. 
Follow , starting with Step 4.b. 
     ^^^^^^
    missing xref

Source code:
<step>
 <para>
  Specify the resource template as you would specify a primitive. Follow
  <xref linkend="pro.ha.config.hawk.primitives" xrefstyle="select:nopage"/>,
  starting with <xref linkend="step.ha.config.hawk.primitives.start" 
  xrefstyle="select:label"/>.
 </para>
</step>


The PDF output gets it right, see attachment.
Comment 1 Tanja Roth 2011-12-06 12:40:04 UTC
Created attachment 466071 [details]
HA Guide (PDF Output) 

PDF, see 6.3.4 Using Resource Templates, Step 5 (p. 120)
Comment 2 Thomas Schraitle 2012-07-12 13:50:19 UTC
The current build doesn't have this error anymore:

http://docserv.suse.de/documents/SLE-HA/SLE-ha-guide/htmlsingle/#sec.ha.config.hawk.templates

I also did a short test with xrefstyle="select:label" and it works as expected.

Setting this bug to resolved for now. Feel free to reopen it if necessary.