[sword-devel] TEI formatting, duplicated key (BDB Glosses)

[David Troidl]

Hi Troy,

On 5/1/2012 2:35 AM, Troy A. Griffitts wrote:
> Quick note before I get on a long flight back to the Good Ol' U.S. of A.
>
> There are 2 distinct uses cases to consider here:
>
> 1. Lookups of linked entries, e.g., Bible with word lemma, user hovers 
> or clicks on a word.
>
> 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.
>
> This key is not necessarily useful to display to the user, as Chris 
> has suggested, so the entry title is there for display.
>
> 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.
Thank you for understanding.  I don't normally make a habit of scrolling 
through a dictionary for fun.  But if I look up hagios, then want to see 
what hagiazo says, in Strongs this isn't a problem.  When it comes to 
Middle Liddell, if I happen to know the exact accentuation of hagios, I 
can probably find it in the first place, but then hagiazo may still be a 
mile away, rather than a few entries.

David
>
>
> -- 
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
>
> David Troidl <DavidTroidl at aol.com> wrote:
>
>
>     On 4/30/2012 7:54 AM, Chris Little wrote:
>     >  On 4/30/2012 4:39 AM, David Troidl wrote:
>     >>  Hi Chris,
>     >>
>     >>  I'm certainly no expert on your TEI dictionaries, but wouldn't it make
>     >>  sense to have the first key be one that would sort properly, and present
>     >>  the dictionary in true alphabetical order? I'm thinking of Middle
>     >>  Liddell, as well as the Hebrew. This key wouldn't even necessarily have
>     >>  to be shown to the user. The second key, the title, could then maintain
>     >>  the proper accents for display, without hindering sorting, searching or
>     >>  navigation.
>     >
>     >  I confess, I don't understand what you're proposing this as an
>     >  alternative to.
>     >
>     >  In the example Karl cites, there's just one actual key per entry. It
>     >  is an uppercased v
>       ersion
>     of the entryFree's n attribute. This is the
>     >  key that is sorted.
>     >
>     >  The un-uppercased version from the n attribute is being rendered as
>     >  part of the entry text via the TEI filters. This is the part I'm
>     >  proposing we retain, but render somewhere else, e.g. right-justified
>     >  at the bottom of the entry.
>     >
>     >  We also render all the text of the entry, which in these cases
>     >  includes the text from a title element.
>     >
>     >  I don't know what 'true alphabetical order' means, but if you mean
>     >  localized sort order, it's not possible with the current
>     >  implementation of this module type.
>     My main point was not to remove the key, but to use it effectively.
>
>     The point about alphabetical order relates to Middle Liddell. Here is a
>     little chunk from the lexicon keys, as they are in BibleTime:
>     ?????
>     ?????
>     ?
>     ????
>     This may
>       be
>     sorting by Unicode codepoints, but could hardly be called
>     alphabetical. This arrangement of the lexicon makes it virtually
>     unusable, at least by me. If the key were something like:
>     ????? ?????
>     it would sort by Greek alphabetical order, then distinguish the accents.
>
>     David
>     >
>     >  --Chris
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>
>     >  sword-devel mailing list: sword-devel at crosswire.org
>     >  http://www.crosswire.org/mailman/listinfo/sword-devel
>     >  Instructions to unsubscribe/change your settings at above page
>
>     ------------------------------------------------------------------------
>
>     sword-devel mailing list: sword-devel at crosswire.org
>     http://www.crosswire.org/mailman/listinfo/sword-devel
>     Instructions to unsubscribe/change your settings at above page
>
>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20120501/2c34b6f9/attachment-0001.html>