OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [docbook-apps] Indexterm start and end of range produces incorrect punctuation and transform error


Hi Dave
Use something else besides informalfigure, eg. inf.001.
When manually generating code for indexterm IDs I use the pattern I given you above.
Maybe you already have. Your code is correct.
IDs should begin with a letter as per your example.
Hope this is helpful.


On Tue, Mar 13, 2012 at 6:14 AM, Xmplar <info@xmplar.biz> wrote:

My fo transformation setup is 1.76.1 ns, Saxon 6.5.5. I’m experimenting with basic autoindexing and have specified start and end ranges in markup:

<para><indexterm class="startofrange" xml:id="informalfigure">
       
<primary>informalfigure element</primary>
       
<secondary>attributes of</secondary>
     
</indexterm>This paragraph contains…

<para><indexterm class="endofrange" startref="informalfigure">
       
<primary>informalfigure element</primary>
     
</indexterm>

 

I get a transformation error:

  (flow [41]
        [error] no entries for index key 'informalfigure element'
      )

And the result puts a comma after the index term where it should not (attached).

This behaviour is not consistent with how other terms are generated (where page ranges are not specified). Is this a bug?


--
Dave Gardiner



---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]