[ docbook-Bugs-2102592 ] Don't know what gentext to create for xref to: "indexterm"

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Bugs item #2102592, was opened at 2008-09-09 22:14
Message generated for change (Comment added) made by mzjn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373747&aid=2102592&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: Sam Steingold (sds)
Assigned to: Nobody/Anonymous (nobody)
Summary: Don't know what gentext to create for xref to: "indexterm"

Initial Comment:
I just updated the xsl stylesheets from 
rsync -av --port=5873 docbook.xml-doc.org::xsl docbook-xsl
and now I get the errors

Don't know what gentext to create for xref to: "indexterm", ("mop-class-mo")

code:

<para>A <firstterm>class metaobject
  <indexterm id="mop-class-mo" significance="preferred">
   <primary>metaobject</primary><secondary>class</secondary>
 </indexterm></firstterm>

it used to work

----------------------------------------------------------------------

>Comment By: Mauritz Jeanson (mzjn)
Date: 2008-09-15 22:28

Message:
I'm sorry, I don't see any errors.

BTW, I had to adjust the test document a bit, since it is not valid:

* there is a dot after "DOCTYPE book"
* the "PUBLIC" keyword is missing
* a "]" character is missing after the entity declaration

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2008-09-15 22:08

Message:
maybe you need to use entities:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book . "-//OASIS//DTD DocBook XML V4.5//EN"
          "./docbook-dtd/docbookx.dtd" [
 <!ENTITY c-mo '<link linkend="mop-class-mo">class metaobject</link>'>
 >
<book><title>b</title>
<chapter><title>c</title>
<section><title>s</title>
<para>A <firstterm>class metaobject
<indexterm id="mop-class-mo" significance="preferred">
<primary>metaobject</primary><secondary>class</secondary>
</indexterm></firstterm></para>
</section>
<section><title>s</title>
<para>&c-mo;</para>
</section>
</chapter>
<index/>
</book>

if this does not produce the error, you might have to put the entity
definition in a separate file...

I am not using snapshots for production, just for testing.
alas, some bugs are only fixed in snapshots.

----------------------------------------------------------------------

Comment By: Mauritz Jeanson (mzjn)
Date: 2008-09-15 21:51

Message:
I can't reproduce the error. I have run your test document through both
DocBook-XSL 1.74.0 [1] and snapshot release r8126 [2], using xsltproc [3].

Saying that something worked "last fall" is still very vague. Please do
not rely on unofficial snapshots for production releases of your
documentation.

---
[1]
http://sourceforge.net/project/showfiles.php?group_id=21935&package_id=16608

[2] http://docbook.sourceforge.net/snapshots/

[3] Using libxml 20632, libxslt 10123 and libexslt 813
xsltproc was compiled against libxml 20632, libxslt 10123 and libexslt
813
libxslt 10123 was compiled against libxml 20632
libexslt 813 was compiled against libxml 20632

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2008-09-15 20:55

Message:
VERSION file reports this:
<xsl:param name="DistroName">docbook-xsl</xsl:param>
<xsl:param name="PreviousRelease">1.74.0</xsl:param>
<xsl:param name="PreviousReleaseRevision">8034</xsl:param>
<xsl:param name="Revision">$Revision: 8051 $</xsl:param>

the previous version which worked was from the last fall, I did not do
rsync for a long time.

a small, self contained &c &c &c is hard to produce, clisp manual being
very large.
since clisp is one of the largest users of your stylesheets, 
it makes perfect sense for you to add it to your regression tests:

cvs -d:pserver:ano...@cl...:/cvsroot/clisp login
cvs -z3 -d:pserver:ano...@cl...:/cvsroot/clisp co
-P clisp
cd clisp/doc
make html

I know this suggestion sounds outrageous, but given our history 
(the many bugs I have reported over the last 5+ years)
I think it is a good idea.

at any rate, I think this is what you are asking for:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book . "-//OASIS//DTD DocBook XML V4.5//EN"
          "./docbook-dtd/docbookx.dtd" >
<book><title>b</title>
<chapter><title>c</title>
<section><title>s</title>
<para>A <firstterm>class metaobject
<indexterm id="mop-class-mo" significance="preferred">
<primary>metaobject</primary><secondary>class</secondary>
</indexterm></firstterm></para>
</section>
<section><title>s</title>
<para><link linkend="mop-class-mo">class metaobject</link></para>
</section>
</chapter>
<index/>
</book>

----------------------------------------------------------------------

Comment By: Mauritz Jeanson (mzjn)
Date: 2008-09-15 20:12

Message:
The "code" snippet is not a well-formed document. Please provide a small,
complete, valid, self-contained test document that can be used to reproduce
the error. 

You downloaded something using rsync a few days ago, but that is rather
vague, I'm afraid. Does this correspond to a specific snapshot version?
What is the latest version (snapshot or official release) of DocBook-XSL
that does not exhibit the error? 

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2008-09-11 20:11

Message:
see also
https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&group_id=21935

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2008-09-10 18:31

Message:
just for clarity:
1. the text which generates this error is
<link linkend="mop-class-mo">class metaobject</link>
(_NOT_ an <xref> as might be inferred from the error message)

2. instead of <a ...>class metaobject</a>, the output contains <a
...>???</a>

3. I do NOT have any <xref> references to <indexterm>s

4. I don't see why "class metaobject" or, at the very least, "metaobject
class" cannot be inferred from the code above.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373747&aid=2102592&group_id=21935