On Wed, Nov 26, 2008 at 5:11 AM, Eeli Kaikkonen <[EMAIL PROTECTED]> wrote: > Quoting Greg Hellings <[EMAIL PROTECTED]>: > > >> >> Likewise. People (I think Chris is one of the leading people, but I >> might be mistaken on that) ought to stop advocating usage of OSIS >> references for the time being. They accomplish nothing, since they >> produce nonsense out the other end, being that they're not supported. >> Why BibleDesktop or BibleTime or BPBible don't support sword:// is >> probably because they're all working on other issues right now. DM >> already mentioned some things BibleDesktop is trying to figure out >> first, the BibleTime guys are actively working on achieving >> independence of the KDE libraries, Ben just explained why he can't get >> support into the current version of BPBible. > > Actually BibleTime uses sword:// internally but the rest of the link > specification may be a bit different from other implementations. I > have thought about changing it if necessary. This whole issue is > important enough to be resolved as soon as possible. Linking inside > and between modules should be self-evident feature in Bible software.
Greg Helling is working on the filters. His proposal is to use sword://module/OSISref links for internal links because that appears to be the easiest way to implement. There would be an option when you create the renderer to get links in either passagestudy.jsp style or sword:// style. So a reference would like like sword://ESV/Gen.1.1 for instance. Comments? _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
