Wolfgang, On Monday, 2016-12-12 21:09:09 +0100, Wolfgang Thämelt wrote:
> ... > > But what you'll really HAVE to do is to weed out duplicate sub-indices: > > > > Activity > > color (Assign colors to track activities), track (Assign colors to > > track activities) > > > > Data organization > > data items (Organization of QMapShack data), databases (Organization > > of QMapShack data), group in database (Organization of QMapShack > > data), lost & found (Organization of QMapShack data), projects > > (Organization of QMapShack data), qms files (Organization of > > QMapShack data), workspace (Organization of QMapShack data) > ... > Look at a computer science book with an Index. There quite often you > have the following picture: > ... > Thus in a book there is: > > Index - subindex1: 13, 27 > - subindex2: 13, 48 I think you completely missed my point. Let's use your computer science book example. In the many computer science books I've read in my life I never came accross an index saying Index - subindex1: 13, subindex2: 13, subindex3: 13, subindex4: 13 But that's exactly what the two examples "Activity" and "Data organizat- ion" actually are doing. In a book this would simply be reduced to Index: 13 without any subindices. > ... > Index - [subindex1](link13) (link13_section_header), ... (second (..) > text string outside or inside the link, playground page) In this example in particular "link13_section_header" should not occur more than once per index term because this does not provide more inform- ation. And "subindex1" should be truely informative, not just the short phrases in the "Activity" and "Data organization" examples quoted above. > ... > It is difficult for me to get precisely your idea of the index. Just pretend not to know anything about QMapShack and then try to find answers to plenty of questions by solely using the index. If this works for many different questions, the index is a good one, otherwise it is not. The question is not so much what the index is looking like but how it is able to help a QMapShack novice. My point is that neither "Activ- ity - color" nor "Activity - track" will help a novice much, and even less so when it's evident that both index entries are referring to the same location. And to return to your book example: while the main indices mostly are single words or short phrases like "Activity" and "Data organization", the subindices often are longer phrases like "assigning activities to track segments" or "assigning colors to track activities" which really convey some information. > ... > Activity, color and > Activity, track > > (meaning of course: color of activity, activity of a track - but this is > the way an index in a book is read) That's exactly the point: in my book your phrase "meaning of course" is plainly wrong. A good index in a book would read at least Activity, color of Activity, assigning to track segment Sincerely, Rainer ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
