[sword-devel] OSIS feature support and questions

[DM Smith]

On 10/02/2009 01:54 PM, Matthew Talbert wrote:
>> 3) A reference with a workID that matches the [NAME] of a module will refer
>> to that module. It is not required that the module exist at all. The use of
>> future names will probably merit some discussion to codify them. There is no
>> support for this in the SWORD engine at this time.
>>      
> Is this still accurate?
I think my statement is still accurate. I may have missed it but I don't 
see direct support in the SWORD engine for it.

>   I thought there was a long discussion about
> this previously and we discovered that there was indeed support for
> this, just the OSISHTMLHREF filters needed updated to output something
> for it. As of 1.6.0, the filters have been modified to output sword://
> style links for these references, which works in Xiphos and BPBible
> (which are the only ones using these filters as far as I know).
Is the code to handle it part of Xiphos and BPBible? or is it part of 
the SWORD engine? (If so, please point me to the file and line.)

I guess my expectation is that the SWORD engine should support the 
retrieval of indexed text for an osisID or a list for an osisRef.

Short of that I'd expect routines to give back the parts (work, v11n, 
category, grain, reference, ...) of an osisID.

> My understanding was that BibleTime already was handling these properly
> in their own filters.
>
> I've used them already quite a bit in a module I'm working on, and
> they seem to work fine. For instance, this
>
>   <reference osisRef="ISBE:MIZRAIM">Mizraim</reference>
>
> does exactly what you would expect.

That's good. Is this true of all front-ends (other than those based on 
JSword, which does not handle it.)

>   I also have this
>
> 	<work osisWork="ISBE">
> 	<refSystem>Dict.Strongs</refSystem>
> 	</work>
>
> at the beginning of my file, but I'm unsure whether this is necessary or not.
>    
 From an OSIS perspective, it is right to have it. From a SWORD 
perspective, it is unnecessary as it is thrown away in the building of 
the module.

> Anyway, this works fine for me in Xiphos, so I guess I'm unclear where
> the lack of support is.
>
> Matthew
>
> PS It looks like these links cause a segfault in BibleTime, so
> apparently they don't have support for this in their filters after
> all. Still, it's a filter issue, not an engine issue.
>    

The filters are part of the SWORD engine. I'm aware that at least one 
frontend has their own render filters. But they are or were based on the 
filters in the SWORD engine.

I think that common handling of lookup should be pushed into the SWORD 
engine.

In Him,
     DM