From: SourceForge.net <no...@so...> - 2006-12-14 05:05:37
|
Bugs item #1614469, was opened at 2006-12-12 19:29 Message generated for change (Comment added) made by bobstayton You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1614469&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: Fixed Priority: 5 Private: No Submitted By: Sam Steingold (sds) Assigned to: Robert Stayton (bobstayton) Summary: ERROR: xref linking to has no generated link text. Initial Comment: fc6: $ xsltproc --version Using libxml 20627, libxslt 10119 and libexslt 813 xsltproc was compiled against libxml 20627, libxslt 10119 and libexslt 813 libxslt 10119 was compiled against libxml 20627 libexslt 813 was compiled against libxml 20627 $ libxslt-1.1.19-1.fc6 libxml2-2.6.27-1.FC6 docbook-style-xsl-1.69.1-5.1 $ XML_CATALOG_FILES="catalog.xml " xsltproc --timing --stringparam target.database.document "olink-pile.xml" --stringparam current.docid "impnotes" -o impnotes.html pile.xsl impnotes.xml Parsing stylesheet pile.xsl took 0 ms Parsing document impnotes.xml took 825 ms ERROR: xref linking to has no generated link text. ERROR: xref linking to has no generated link text. ERROR: xref linking to has no generated link text. ERROR: xref linking to has no generated link text. ERROR: xref linking to has no generated link text. ERROR: xref linking to has no generated link text. ERROR: xref linking to has no generated link text. ERROR: xref linking to has no generated link text. ERROR: xref linking to has no generated link text. ERROR: xref linking to has no generated link text. ERROR: xref linking to has no generated link text. ERROR: xref linking to has no generated link text. ERROR: xref linking to has no generated link text. https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1593909&group_id=21935 >Comment By: Michael(tm) Smith (xmldoc) Date: 2006-12-13 12:23 The error messages about "xref linking to has no generated link text." seem to be caused by a bug in handling of instances of "<citation><link linkend="ansi-cl">ANSI CL standard</link></citation>" in your source. If you can open a new bug about it, I'll make sure to follow up with Bob. He made some significant changes to the code for xref handling recently. Those changes seem to have introduced the problem you're seeing. ---------------------------------------------------------------------- >Comment By: Robert Stayton (bobstayton) Date: 2006-12-13 21:05 Message: Logged In: YES user_id=193218 Originator: NO File Added: citation-bug.xml ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-12-13 19:25 Message: Logged In: YES user_id=5735 Originator: YES different error this time: XML_CATALOG_FILES="catalog.xml " xsltproc --timing --stringparam target.database.document "olink-pile.xml" --stringparam current.docid "impnotes" -o impnotes.html pile.xsl impnotes.xml Parsing stylesheet pile.xsl took 0 ms Parsing document impnotes.xml took 998 ms Request for title of element with no title: biblioentry (id="amop") Request for title of element with no title: biblioentry (id="amop") Request for title of element with no title: biblioentry (id="amop") Request for title of element with no title: biblioentry (id="amop") Request for title of element with no title: biblioentry (id="amop") Request for title of element with no title: biblioentry (id="amop") Request for title of element with no title: biblioentry (id="amop") Running stylesheet and saving result took 373704 ms ---------------------------------------------------------------------- Comment By: Michael(tm) Smith (xmldoc) Date: 2006-12-13 01:30 Message: Logged In: YES user_id=118135 Originator: NO Sam, I tested Bob's change with your clisp.xml built from your latest CVS, and it seems to fix the "xref linking to has no generated link text" problem. Can you please test with the lastest snapshot and confirm? ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2006-12-13 01:23 Message: Logged In: YES user_id=193218 Originator: NO I checked in fixes for html and fo inline.xsl to handle citations that link to biblioentry based on abbrev element matching. I simplified it to not call the xref template since that is not needed in this case. ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2006-12-13 01:23 Message: Logged In: YES user_id=193218 Originator: NO A fix for this issue has been added to the current codebase. Please test the fix with the latest snapshot from: http://docbook.sourceforge.net/snapshots/ ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2006-12-13 00:02 Message: Logged In: YES user_id=193218 Originator: NO I'm also not able to duplicate the error with the given sample document. Was a customization involved? Also, the bug report mentions version 1.69.1 of the stylesheets, but that error message was not introduced until after 1.71.1, so I presume we are talking about the snapshot release, right? ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2006-12-13 00:01 Message: Logged In: YES user_id=193218 Originator: NO I'm also not able to duplicate the error with the given sample document. Was a customization involved? Also, the bug report mentions version 1.69.1 of the stylesheets, but that error message was not introduced until after 1.71.1, so I presume we are talking about the snapshot release, right? ---------------------------------------------------------------------- Comment By: Michael(tm) Smith (xmldoc) Date: 2006-12-12 21:32 Message: Logged In: YES user_id=118135 Originator: NO hmm, I now don't seem to be able to reproduce this with the minimal test instance I put together. I guess I made it too minimal. I'm now not sure that the issue of it having multiple Abbrew instances is actually a problem or not. ---------------------------------------------------------------------- Comment By: Michael(tm) Smith (xmldoc) Date: 2006-12-12 21:31 Message: Logged In: YES user_id=118135 Originator: NO @linkend and @xlink:href are both valid on Citation in DocBook 5, but not in DocBook 4. So if want to validate against DocBook 5 instead of DocBook 4, you could move the @linkend to the citation. Anyway, we still have a bug in the stylesheets that we need to get fixed. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-12-12 21:12 Message: Logged In: YES user_id=5735 Originator: YES http://docbook.org/tdg/en/html/citation.html does not list @linkend or @xlink:href attribute on the citation element. are they allowed? if so, I can just replace "<citation><link linkend="ansi-cl">ANSI CL standard</link></citation>" with "<citation linkend="ansi-cl">ANSI CL standard</citation>" ---------------------------------------------------------------------- Comment By: Michael(tm) Smith (xmldoc) Date: 2006-12-12 20:29 Message: Logged In: YES user_id=118135 Originator: NO Problem seems to be the fact that the Biblioentry in the test document has multiple Abbrev elements: <abbrev>ANSI CL</abbrev><abbrev>ANSI CL standard</abbrev> Not sure why it does or what the expected behavior should be when it does, but it is valid to have multiple Abbrev instances there, so it seems like we should be handling it. And along with that, there is still the issue of the error message not looking for the linkend ID on the correct element (it's looking for it on the Citation, but should be looking for it on the Link). ---------------------------------------------------------------------- Comment By: Michael(tm) Smith (xmldoc) Date: 2006-12-12 20:21 Message: Logged In: YES user_id=118135 Originator: NO Pasted in here and also uploaded/attached is a minimal test case that demonstrates the problem. <refentry> <refnamediv> <refname>clisp</refname> <refpurpose>ANSI Common Lisp compiler, interpreter and debugger.</refpurpose> </refnamediv> <refsect1> <title>Citation link test</title> <simpara>See <citation ><link linkend="ansi-cl">ANSI CL standard</link></citation></simpara> <bibliolist> <biblioentry id="ansi-cl"> <abbrev>ANSI CL</abbrev><abbrev>ANSI CL standard</abbrev> <title>ANSI Common Lisp standard X3.226-1994</title> </biblioentry> </bibliolist> </refsect1> </refentry> File Added: citation-bug.xml ---------------------------------------------------------------------- Comment By: Michael(tm) Smith (xmldoc) Date: 2006-12-12 19:55 Message: Logged In: YES user_id=118135 Originator: NO The root problem appears to be that the xref (named template) code is looking for a @linkend or @xlink:href attribute on the citation element, but in this case the linkend attribute is actually on a link element that's a child of the citation. I'll try to upload a minimal test case that demonstrates the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1614469&group_id=21935 |