[sword-devel] Limitation of Sword implementation of multiple osisRefs' linkage
Karl Kleinpaste
karl at kleinpaste.org
Thu Apr 10 09:06:22 MST 2014
On 04/10/2014 11:32 AM, Matěj Cepl wrote:
> it has been https://luther.ceplovi.cz/bugzilla/show_bug.cgi?id=180 for some time
In that bug report:
/While OSIS allows for more than one reference in an osisRef, SWORD
does not handle the linking for it, but only the first listed./
I've noticed this before, and been annoyed by it. When there is a long
xref list, I consider it vastly preferable that the entire set be one
refList, as returned by getEntryAttributes. I have a module containing
this as a single xref:
Exod 15:2; 17:16; Pss 68:5, 19; 77:12; 89:9; 94:7, 12; 102:19; 104:35;
105:45; 106:1, 48; 111:1; 112:1; 113:1, 9; 115:17, 18; 116:19; 117:2;
118:5, 14, 17-19; 122:4; 130:3; 135:1, 3, 4, 21; 146:1, 10; 147:1, 20;
148:1, 14; 149:1, 9; 150:1, 6; Isa 12:2; 26:4; 38:11
(NETnote, Song 8:6#24.)
I really don't want every single item in that nightmare individually
clickable; I want the whole thing as one unit, shipped off to a verse
list UI element of some kind (Xiphos does it in the sidebar), where I
can peruse the individual items as I wish.
Why doesn't Sword allow this in the OSIS case?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20140410/ae5b01a0/attachment.html>
More information about the sword-devel
mailing list