<html><head></head><body>Quick note before I get on a long flight back to the Good Ol' U.S. of A.<br>
<br>
There are 2 distinct uses cases to consider here:<br>
<br>
1. Lookups of linked entries, e.g., Bible with word lemma, user hovers or clicks on a word.<br>
<br>
SWORD handles this use case well. The latest code in trunk allows a .conf entry which allows case sensitivity in keys to handle lexica which have entries where case matters for uniqueness.<br>
<br>
This key is not necessarily useful to display to the user, as Chris has suggested, so the entry title is there for display.<br>
<br>
2. Scrolling through entries. This use case, which I hadn't thought highly desirable until people started complaining about sort order, we do not handle well. This is where we have discussed adding a second, human understandable sort order index and have the traversable interface methods use this index.<br>
<br>
<br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.<br><br><div class="gmail_quote">David Troidl <DavidTroidl@aol.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif"><br /><br />On 4/30/2012 7:54 AM, Chris Little wrote:<br />> On 4/30/2012 4:39 AM, David Troidl wrote:<br />>> Hi Chris,<br />>><br />>> I'm certainly no expert on your TEI dictionaries, but wouldn't it make<br />>> sense to have the first key be one that would sort properly, and present<br />>> the dictionary in true alphabetical order? I'm thinking of Middle<br />>> Liddell, as well as the Hebrew. This key wouldn't even necessarily have<br />>> to be shown to the user. The second key, the title, could then maintain<br />>> the proper accents for display, without hindering sorting, searching or<br />>> navigation.<br />><br />> I confess, I don't understand what you're proposing this as an <br />> alternative to.<br />><br />> In the example Karl cites, there's just one actual key per entry. It <br />> is an uppercased version
of the entryFree's n attribute. This is the <br />> key that is sorted.<br />><br />> The un-uppercased version from the n attribute is being rendered as <br />> part of the entry text via the TEI filters. This is the part I'm <br />> proposing we retain, but render somewhere else, e.g. right-justified <br />> at the bottom of the entry.<br />><br />> We also render all the text of the entry, which in these cases <br />> includes the text from a title element.<br />><br />> I don't know what 'true alphabetical order' means, but if you mean <br />> localized sort order, it's not possible with the current <br />> implementation of this module type.<br />My main point was not to remove the key, but to use it effectively.<br /><br />The point about alphabetical order relates to Middle Liddell. Here is a <br />little chunk from the lexicon keys, as they are in BibleTime:<br />ἄωτον<br />ἀ̆́λη<br />ἆ<br />ἆγμα<br />This may be
sorting by Unicode codepoints, but could hardly be called <br />alphabetical. This arrangement of the lexicon makes it virtually <br />unusable, at least by me. If the key were something like:<br />αωτον ἄωτον<br />it would sort by Greek alphabetical order, then distinguish the accents.<br /><br />David<br />><br />> --Chris<br />><br />><br />><hr /><br />> sword-devel mailing list: sword-devel@crosswire.org<br />> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br />> Instructions to unsubscribe/change your settings at above page<br /><br /><hr /><br />sword-devel mailing list: sword-devel@crosswire.org<br /><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br />Instructions to unsubscribe/change your settings at above page</pre></blockquote></div></body></html>