From: SourceForge.net <no...@so...> - 2008-06-06 15:55:05
|
Bugs item #1986587, was opened at 2008-06-06 11:31 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&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: links generated by indexterm Initial Comment: Consider this text: <firstterm>foo <indexterm id="my-foo" significance="preferred"> <primary>foo</primary></indexterm></firstterm> this generates an index entry for foo, but the reference from the index entry goes NOT to the anchor __<a id="my-foo" class="indexterm"></a>__ created next to "foo", but to the enclosing section. in fact, there are no pointers to the id "my-foo". (note that when I omit id="my-foo" from <indexterm>, a generated anchor is created: ___<a id="id12345" class="indexterm"></a>"___ and still there are no references to this anchor) I think this is a bug. The correct behavior would be to refer to the supplied (or generated) id of indexterm, OR __NOT__ to generate the ID which is never used. (However, I like that the name of the enclosing section is used as the label). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&group_id=21935 |
From: SourceForge.net <no...@so...> - 2008-06-30 16:56:29
|
Bugs item #1986587, was opened at 2008-06-06 17:31 Message generated for change (Comment added) made by mzjn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&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: links generated by indexterm Initial Comment: Consider this text: <firstterm>foo <indexterm id="my-foo" significance="preferred"> <primary>foo</primary></indexterm></firstterm> this generates an index entry for foo, but the reference from the index entry goes NOT to the anchor __<a id="my-foo" class="indexterm"></a>__ created next to "foo", but to the enclosing section. in fact, there are no pointers to the id "my-foo". (note that when I omit id="my-foo" from <indexterm>, a generated anchor is created: ___<a id="id12345" class="indexterm"></a>"___ and still there are no references to this anchor) I think this is a bug. The correct behavior would be to refer to the supplied (or generated) id of indexterm, OR __NOT__ to generate the ID which is never used. (However, I like that the name of the enclosing section is used as the label). ---------------------------------------------------------------------- >Comment By: Mauritz Jeanson (mzjn) Date: 2008-06-30 18:56 Message: Logged In: YES user_id=582041 Originator: NO I would say that this is more of a feature request (and an interesting topic for discussion) than an obvious bug. There are different views on what the correct behaviour is. See this thread on docbook-apps (from March 2008): http://lists.oasis-open.org/archives/docbook-apps/200803/msg00077.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&group_id=21935 |
From: SourceForge.net <no...@so...> - 2008-06-30 17:02:01
|
Bugs item #1986587, was opened at 2008-06-06 11:31 Message generated for change (Comment added) made by sds You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&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: links generated by indexterm Initial Comment: Consider this text: <firstterm>foo <indexterm id="my-foo" significance="preferred"> <primary>foo</primary></indexterm></firstterm> this generates an index entry for foo, but the reference from the index entry goes NOT to the anchor __<a id="my-foo" class="indexterm"></a>__ created next to "foo", but to the enclosing section. in fact, there are no pointers to the id "my-foo". (note that when I omit id="my-foo" from <indexterm>, a generated anchor is created: ___<a id="id12345" class="indexterm"></a>"___ and still there are no references to this anchor) I think this is a bug. The correct behavior would be to refer to the supplied (or generated) id of indexterm, OR __NOT__ to generate the ID which is never used. (However, I like that the name of the enclosing section is used as the label). ---------------------------------------------------------------------- >Comment By: Sam Steingold (sds) Date: 2008-06-30 13:01 Message: Logged In: YES user_id=5735 Originator: YES creating unused gensym anchors is certainly a bug. the thread you mention appears to deal mostly with text, not links. ---------------------------------------------------------------------- Comment By: Mauritz Jeanson (mzjn) Date: 2008-06-30 12:56 Message: Logged In: YES user_id=582041 Originator: NO I would say that this is more of a feature request (and an interesting topic for discussion) than an obvious bug. There are different views on what the correct behaviour is. See this thread on docbook-apps (from March 2008): http://lists.oasis-open.org/archives/docbook-apps/200803/msg00077.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&group_id=21935 |
From: SourceForge.net <no...@so...> - 2008-09-11 18:12:25
|
Bugs item #1986587, was opened at 2008-06-06 11:31 Message generated for change (Comment added) made by sds You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&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: links generated by indexterm Initial Comment: Consider this text: <firstterm>foo <indexterm id="my-foo" significance="preferred"> <primary>foo</primary></indexterm></firstterm> this generates an index entry for foo, but the reference from the index entry goes NOT to the anchor __<a id="my-foo" class="indexterm"></a>__ created next to "foo", but to the enclosing section. in fact, there are no pointers to the id "my-foo". (note that when I omit id="my-foo" from <indexterm>, a generated anchor is created: ___<a id="id12345" class="indexterm"></a>"___ and still there are no references to this anchor) I think this is a bug. The correct behavior would be to refer to the supplied (or generated) id of indexterm, OR __NOT__ to generate the ID which is never used. (However, I like that the name of the enclosing section is used as the label). ---------------------------------------------------------------------- >Comment By: Sam Steingold (sds) Date: 2008-09-11 14:12 Message: see also https://sourceforge.net/tracker/index.php?func=detail&aid=2102592&group_id=21935&atid=373747 ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-06-30 13:01 Message: Logged In: YES user_id=5735 Originator: YES creating unused gensym anchors is certainly a bug. the thread you mention appears to deal mostly with text, not links. ---------------------------------------------------------------------- Comment By: Mauritz Jeanson (mzjn) Date: 2008-06-30 12:56 Message: Logged In: YES user_id=582041 Originator: NO I would say that this is more of a feature request (and an interesting topic for discussion) than an obvious bug. There are different views on what the correct behaviour is. See this thread on docbook-apps (from March 2008): http://lists.oasis-open.org/archives/docbook-apps/200803/msg00077.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&group_id=21935 |
From: SourceForge.net <no...@so...> - 2009-03-15 19:14:09
|
Bugs item #1986587, was opened at 2008-06-06 08:31 Message generated for change (Comment added) made by bobstayton You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&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: Pending >Resolution: Fixed Priority: 5 Private: No Submitted By: Sam Steingold (sds) >Assigned to: Robert Stayton (bobstayton) Summary: links generated by indexterm Initial Comment: Consider this text: <firstterm>foo <indexterm id="my-foo" significance="preferred"> <primary>foo</primary></indexterm></firstterm> this generates an index entry for foo, but the reference from the index entry goes NOT to the anchor __<a id="my-foo" class="indexterm"></a>__ created next to "foo", but to the enclosing section. in fact, there are no pointers to the id "my-foo". (note that when I omit id="my-foo" from <indexterm>, a generated anchor is created: ___<a id="id12345" class="indexterm"></a>"___ and still there are no references to this anchor) I think this is a bug. The correct behavior would be to refer to the supplied (or generated) id of indexterm, OR __NOT__ to generate the ID which is never used. (However, I like that the name of the enclosing section is used as the label). ---------------------------------------------------------------------- >Comment By: Robert Stayton (bobstayton) Date: 2009-03-15 12:14 Message: I added a new param 'index.links.to.section', which when set to zero will cause index entries in HTML output to link directly to the anchor associated with its indexterm. This has been a long standing feature request. Any duplicate entries will produce duplicate titles in the index, however, because they each have different destinations. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-09-11 11:12 Message: see also https://sourceforge.net/tracker/index.php?func=detail&aid=2102592&group_id=21935&atid=373747 ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-06-30 10:01 Message: Logged In: YES user_id=5735 Originator: YES creating unused gensym anchors is certainly a bug. the thread you mention appears to deal mostly with text, not links. ---------------------------------------------------------------------- Comment By: Mauritz Jeanson (mzjn) Date: 2008-06-30 09:56 Message: Logged In: YES user_id=582041 Originator: NO I would say that this is more of a feature request (and an interesting topic for discussion) than an obvious bug. There are different views on what the correct behaviour is. See this thread on docbook-apps (from March 2008): http://lists.oasis-open.org/archives/docbook-apps/200803/msg00077.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&group_id=21935 |
From: SourceForge.net <no...@so...> - 2009-03-16 16:40:28
|
Bugs item #1986587, was opened at 2008-06-06 11:31 Message generated for change (Comment added) made by sds You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&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: links generated by indexterm Initial Comment: Consider this text: <firstterm>foo <indexterm id="my-foo" significance="preferred"> <primary>foo</primary></indexterm></firstterm> this generates an index entry for foo, but the reference from the index entry goes NOT to the anchor __<a id="my-foo" class="indexterm"></a>__ created next to "foo", but to the enclosing section. in fact, there are no pointers to the id "my-foo". (note that when I omit id="my-foo" from <indexterm>, a generated anchor is created: ___<a id="id12345" class="indexterm"></a>"___ and still there are no references to this anchor) I think this is a bug. The correct behavior would be to refer to the supplied (or generated) id of indexterm, OR __NOT__ to generate the ID which is never used. (However, I like that the name of the enclosing section is used as the label). ---------------------------------------------------------------------- >Comment By: Sam Steingold (sds) Date: 2009-03-16 12:39 Message: what is the default value? xhtml-1_1/param.xsl appears to be setting it to 0, but I still observe the same behavior, see https://sourceforge.net/tracker2/index.php?func=detail&aid=747703&group_id=21935&atid=373750 ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2009-03-15 15:14 Message: I added a new param 'index.links.to.section', which when set to zero will cause index entries in HTML output to link directly to the anchor associated with its indexterm. This has been a long standing feature request. Any duplicate entries will produce duplicate titles in the index, however, because they each have different destinations. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-09-11 14:12 Message: see also https://sourceforge.net/tracker/index.php?func=detail&aid=2102592&group_id=21935&atid=373747 ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-06-30 13:01 Message: Logged In: YES user_id=5735 Originator: YES creating unused gensym anchors is certainly a bug. the thread you mention appears to deal mostly with text, not links. ---------------------------------------------------------------------- Comment By: Mauritz Jeanson (mzjn) Date: 2008-06-30 12:56 Message: Logged In: YES user_id=582041 Originator: NO I would say that this is more of a feature request (and an interesting topic for discussion) than an obvious bug. There are different views on what the correct behaviour is. See this thread on docbook-apps (from March 2008): http://lists.oasis-open.org/archives/docbook-apps/200803/msg00077.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&group_id=21935 |
From: SourceForge.net <no...@so...> - 2009-03-16 17:31:05
|
Bugs item #1986587, was opened at 2008-06-06 08:31 Message generated for change (Comment added) made by bobstayton You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&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: links generated by indexterm Initial Comment: Consider this text: <firstterm>foo <indexterm id="my-foo" significance="preferred"> <primary>foo</primary></indexterm></firstterm> this generates an index entry for foo, but the reference from the index entry goes NOT to the anchor __<a id="my-foo" class="indexterm"></a>__ created next to "foo", but to the enclosing section. in fact, there are no pointers to the id "my-foo". (note that when I omit id="my-foo" from <indexterm>, a generated anchor is created: ___<a id="id12345" class="indexterm"></a>"___ and still there are no references to this anchor) I think this is a bug. The correct behavior would be to refer to the supplied (or generated) id of indexterm, OR __NOT__ to generate the ID which is never used. (However, I like that the name of the enclosing section is used as the label). ---------------------------------------------------------------------- >Comment By: Robert Stayton (bobstayton) Date: 2009-03-16 10:30 Message: That snapshot works for me. When I cut and paste your example from feature request 747703 into my document, the indexterm location in the section has this anchor: <em class="firstterm">no-prim;<a class="indexterm" name="no-prim"></a></em> the index entry shows this link: <a class="indexterm" href="achap.html#no-prim">My section</a> That is, it links to the exact location of the indexterm anchor within the chunk. Can you please double check your setup, or test without your customization layer? Regarding the default value of the param, I meant to set that to 1 to retain the existing behavior. I'll change that in the source. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2009-03-16 09:39 Message: what is the default value? xhtml-1_1/param.xsl appears to be setting it to 0, but I still observe the same behavior, see https://sourceforge.net/tracker2/index.php?func=detail&aid=747703&group_id=21935&atid=373750 ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2009-03-15 12:14 Message: I added a new param 'index.links.to.section', which when set to zero will cause index entries in HTML output to link directly to the anchor associated with its indexterm. This has been a long standing feature request. Any duplicate entries will produce duplicate titles in the index, however, because they each have different destinations. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-09-11 11:12 Message: see also https://sourceforge.net/tracker/index.php?func=detail&aid=2102592&group_id=21935&atid=373747 ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-06-30 10:01 Message: Logged In: YES user_id=5735 Originator: YES creating unused gensym anchors is certainly a bug. the thread you mention appears to deal mostly with text, not links. ---------------------------------------------------------------------- Comment By: Mauritz Jeanson (mzjn) Date: 2008-06-30 09:56 Message: Logged In: YES user_id=582041 Originator: NO I would say that this is more of a feature request (and an interesting topic for discussion) than an obvious bug. There are different views on what the correct behaviour is. See this thread on docbook-apps (from March 2008): http://lists.oasis-open.org/archives/docbook-apps/200803/msg00077.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&group_id=21935 |
From: SourceForge.net <no...@so...> - 2009-03-16 19:27:20
|
Bugs item #1986587, was opened at 2008-06-06 11:31 Message generated for change (Comment added) made by sds You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&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: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Sam Steingold (sds) Assigned to: Robert Stayton (bobstayton) Summary: links generated by indexterm Initial Comment: Consider this text: <firstterm>foo <indexterm id="my-foo" significance="preferred"> <primary>foo</primary></indexterm></firstterm> this generates an index entry for foo, but the reference from the index entry goes NOT to the anchor __<a id="my-foo" class="indexterm"></a>__ created next to "foo", but to the enclosing section. in fact, there are no pointers to the id "my-foo". (note that when I omit id="my-foo" from <indexterm>, a generated anchor is created: ___<a id="id12345" class="indexterm"></a>"___ and still there are no references to this anchor) I think this is a bug. The correct behavior would be to refer to the supplied (or generated) id of indexterm, OR __NOT__ to generate the ID which is never used. (However, I like that the name of the enclosing section is used as the label). ---------------------------------------------------------------------- >Comment By: Sam Steingold (sds) Date: 2009-03-16 15:25 Message: wfm too. sorry. ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2009-03-16 13:30 Message: That snapshot works for me. When I cut and paste your example from feature request 747703 into my document, the indexterm location in the section has this anchor: <em class="firstterm">no-prim;<a class="indexterm" name="no-prim"></a></em> the index entry shows this link: <a class="indexterm" href="achap.html#no-prim">My section</a> That is, it links to the exact location of the indexterm anchor within the chunk. Can you please double check your setup, or test without your customization layer? Regarding the default value of the param, I meant to set that to 1 to retain the existing behavior. I'll change that in the source. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2009-03-16 12:39 Message: what is the default value? xhtml-1_1/param.xsl appears to be setting it to 0, but I still observe the same behavior, see https://sourceforge.net/tracker2/index.php?func=detail&aid=747703&group_id=21935&atid=373750 ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2009-03-15 15:14 Message: I added a new param 'index.links.to.section', which when set to zero will cause index entries in HTML output to link directly to the anchor associated with its indexterm. This has been a long standing feature request. Any duplicate entries will produce duplicate titles in the index, however, because they each have different destinations. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-09-11 14:12 Message: see also https://sourceforge.net/tracker/index.php?func=detail&aid=2102592&group_id=21935&atid=373747 ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2008-06-30 13:01 Message: Logged In: YES user_id=5735 Originator: YES creating unused gensym anchors is certainly a bug. the thread you mention appears to deal mostly with text, not links. ---------------------------------------------------------------------- Comment By: Mauritz Jeanson (mzjn) Date: 2008-06-30 12:56 Message: Logged In: YES user_id=582041 Originator: NO I would say that this is more of a feature request (and an interesting topic for discussion) than an obvious bug. There are different views on what the correct behaviour is. See this thread on docbook-apps (from March 2008): http://lists.oasis-open.org/archives/docbook-apps/200803/msg00077.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1986587&group_id=21935 |