[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Clarification of implications of index-see-also
I agree that Paul and Bruce's interpretation is (should be) the correct one. So I think this goes on the "clarrify in the corrigendum" list. Thanks, E. On 4/12/11 9:22 AM, "Grosso, Paul" <pgrosso@ptc.com> wrote: > I believe I wrote (at least the basis for) this wording, and I'm > afraid I agree that it is ambiguous. > > What I meant for it to say is that, in your example, there would > be a page number for apple, but not for AAPL. > > I was trying to contrast it to an index-see where there would be > no page number for apple. I was not trying to say that the contents > of the index-see-also element would magically be made an additional > entry in the index if it isn't otherwise made an entry via another > index-term of its own. > > paul > >> -----Original Message----- >> From: Eliot Kimber [mailto:ekimber@reallysi.com] >> Sent: Tuesday, 2011 April 12 8:44 >> To: dita >> Subject: [dita] Clarification of implications of index-see-also >> >> The language reference entry for index-see-also says: >> >> "In addition to its "see also" redirection, an index-see-also >> >> functions as a pointwise indexterm, thereby typically generating a >> >> page reference as well as the "see also" indication." >> >> Given this index markup: >> >> <index-term> >> apple >> <index-see-also>AAPL</index-see-also> >> </index-term> >> >> Is the intent that there will be a page number reference to this >> index-term's location for both "apple" and "AAPL" or only for "apple"? >> >> There must be a page number reference for "apple" at this term's >> location, >> that is clear (because the see-also doesn't change the basic >> functioning of >> the index term as a point reference). >> >> The question is whether or not the spec is requiring an additional >> entry for >> "AAPL" at this location or if the intent is that the see-also just >> points to >> the named term? >> >> Cheers, >> >> E. >> >> -- >> Eliot Kimber >> Senior Solutions Architect >> "Bringing Strategy, Content, and Technology Together" >> Main: 512.554.9368 >> www.reallysi.com >> www.rsuitecms.com >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]