← Prev in month
← Prev in thread
sort-as Q1 [was: review of index* elements]
> -----Original Message----- > From: Chris Wong [mailto:] > Sent: Monday, 2006 September 25 15:40 > To: Grosso, Paul; > Subject: RE: [dita] review of index* elements [was: DITA 1.1 > Language Specification -- draft (ditaref-alpha.pdf) uploaded] > Concerning your other example: > > > <indexterm>$apple<index-sort-as>apple</index-sort-as></indexterm> > . . . > <indexterm>apple</indexterm> > > This should always result in separate entries: > > $apple, 3 > apple, 7 > > > This is because the operative phrase in index-sort-as is > "sort as". This > does not mean "index as": the processor is not being told to convert > "$apple" to "apple". If the author intended to have "apple" appear in > the first indexterm, he should not have typed "$apple" in the > indexterm. If this is what we decide and we document it that way, I can accept this. Note that what this potential decision is really saying is that we are really sorting by appending the actual indexterm value to the sort-as value. That is, you are really sorting the two indexterms above as "apple-$apple" and "apple-apple". Also note that if this is what the user really wanted, they could have done just that in the sort-as value themselves. paul > > -----Original Message----- > From: Grosso, Paul [mailto:] > Sent: Thursday, September 21, 2006 6:53 PM > To: > Subject: RE: [dita] review of index* elements [was: DITA 1.1 Language > Specification -- draft (ditaref-alpha.pdf) uploaded] > Suppose my document contains: > > <indexterm>$apple<index-sort-as>apple</index-sort-as></indexterm> > . . . > <indexterm>apple</indexterm> > > (where . . . represents several pages of content) such that the first > indexterm falls on page 3 and the second on page 7. > > Would my generated index look something like: > > apple, 3, 7 > > or > > $apple, 3, 7 > > or > > apple, 3 > $apple, 7 > > or something else?
← Prev in month
← Prev in thread