From: SourceForge.net <no...@so...> - 2011-11-25 06:14:24
|
Bugs item #3325153, was opened at 2011-06-23 05:27 Message generated for change (Comment added) made by bobstayton You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=3325153&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: XSL Group: output: HTML Status: Open Resolution: None Priority: 5 Private: No Submitted By: John Maddock (johnmaddock) Assigned to: Nobody/Anonymous (nobody) Summary: Link to bridgehead causes spurious error messages Initial Comment: If I link to a bridgehead which contains any XML child elements at all, I see two error messages per link: Request for title of element with no title: link Request for title of element with no title: link Replace "link" in the above with the name of the first child element in the bridgehead. Here's the test case: <?xml version="1.0"?> <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> <article xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" id="math_toolkit" rev:last-revision="$Date: 2011/06/23 10:13:51 $"> <title>Math Toolkit</title> <section> <anchor id="math_toolkit.policy.pol_ref.policy_defaults.boost_math_assert_undefined_policy"/> <para> Determines how discrete quantiles return their results: either as an integer, or as a real value, can be set to one of the enumerated values: <computeroutput xmlns:xi="http://www.w3.org/2001/XInclude"><phrase role="identifier">real</phrase></computeroutput>, <computeroutput xmlns:xi="http://www.w3.org/2001/XInclude"><phrase role="identifier">integer_round_outwards</phrase></computeroutput>, <computeroutput xmlns:xi="http://www.w3.org/2001/XInclude"><phrase role="identifier">integer_round_inwards</phrase></computeroutput>, <computeroutput xmlns:xi="http://www.w3.org/2001/XInclude"><phrase role="identifier">integer_round_down</phrase></computeroutput>, <computeroutput xmlns:xi="http://www.w3.org/2001/XInclude"><phrase role="identifier">integer_round_up</phrase></computeroutput>, <computeroutput xmlns:xi="http://www.w3.org/2001/XInclude"><phrase role="identifier">integer_round_nearest</phrase></computeroutput>. Defaults to <computeroutput xmlns:xi="http://www.w3.org/2001/XInclude"><phrase role="identifier">integer_round_outwards</phrase></computeroutput>. </para> <bridgehead renderas="sect5" id="math_toolkit.policy.pol_ref.policy_defaults.boost_math_assert_undefined_policy-heading"> <link linkend="math_toolkit.policy.pol_ref.policy_defaults.boost_math_assert_undefined_policy">BOOST_MATH_ASSERT_UNDEFINED_POLICY</link> </bridgehead> <para> <link linkend="math_toolkit.policy.pol_ref.policy_defaults.boost_math_assert_undefined_policy-heading">Determines</link> whether functions that are mathematically undefined for a specific distribution compile or raise a static (i.e. compile-time) assertion. Defaults to <computeroutput xmlns:xi="http://www.w3.org/2001/XInclude"><phrase role="keyword">true</phrase></computeroutput>: meaning that any mathematically undefined function will not compile. When set to <computeroutput xmlns:xi="http://www.w3.org/2001/XInclude"><phrase role="keyword">false</phrase></computeroutput> then the function will compile but return the result of a domain error: this can be useful for some generic code, that needs to work with all distributions and determine at runtime whether or not a particular property is well defined. </para> </section> </article> If I remove the link to the bridgehead then the errors go away. If I remove the child elements from the bridgehead then the errors also go away. Please note that the code generating these messages is generated automatically, and there are potentially hundreds of such links with all the associated messages, so this is a big issue for me. The XSL processor is xsltproc BTW. John Maddock. ---------------------------------------------------------------------- >Comment By: Robert Stayton (bobstayton) Date: 2011-11-24 22:14 Message: Two questions: 1. Are you using olinks, and running with the param collect.xref.targets set to 'yes'? 2. Do you see anything wrong with your output? ---------------------------------------------------------------------- Comment By: John Maddock (johnmaddock) Date: 2011-09-12 10:22 Message: I've worked around the issue in my code for now, so I no longer have a test case other than the one given above.... so if it does the right thing in that case, then that's good enough for me ;-) ---------------------------------------------------------------------- Comment By: Mauritz Jeanson (mzjn) Date: 2011-09-12 08:22 Message: It appears that the following is needed: <xsl:template match="link" mode="title.markup"> <xsl:apply-templates mode="title.markup"/> </xsl:template> Can you please test this? If the fix is added to the stock stylesheets, it should go into common/titles.xsl. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=3325153&group_id=21935 |