"Peter von Kaehne" <[email protected]> writes: > Basically every addressable section/subsection of a book would get its > own OsisID along the scheme described for Bibles.
Although we can devise schemes by which to extricate section separators in genbooks and dictionaries, verse-keyed commentary content is different. The identification scheme is strictly book/chapter/verse. It is exactly the need to reach into a sub-verse region that I want to accomplish. In any event, even for genbooks and dictionaries, the engine would require some modification so that, when asked for "/This/Key/That/Ends/Here/subsection" it correctly returns content for "/This/Key/That/Ends/Here" and allows the application to devise its own means by which to reach "subsection." At the moment, I am dealing quite well with verse-keyed content of the previously-mentioned form, that is, Book Ch:Vs#subsection, except that I must strip off "#subsection" manually when navigating, because currently "Gen 1:2#n13" is bogusly interpreted by VerseKey::ParseVerseList() as "Gen 1:13". /oops/ _______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
