Extended Strong's numbers and the SWORD engine!

I have just observed a significant technical problem that may well turn out to be a software issue in the SWORD API.

OSHB is the initialism for Open Scriptures Hebrew Bible.

The diatheke output from the OSHB module using the output option -o n for Strong's numbers does not include any of the codes with a letter suffix that are part of the extended Strong's dictionary and markup devised for the OSHB project and maybe more widely used by some other modules since (e.g. those from Tyndale House).

Aside: This puts a whole new slant on the comparisons that I've done so far for the Strong's numbers in the CrossWire KJV project.
It will no doubt mean that some of my earlier reported observations will need to be revised once the dust settles.

This may also be where the JSword fork that is part of the STEPBible project is now ahead of the SWORD engine!

It's not just diatheke which shows the symptoms; it must also be that all SWORD-based front-ends do not include the letter suffixed codes when Strong's are displayed.
Whether they truncate the letter suffices or omit these entire codes is something I've yet to determine.  More likely the former, but it needs checking.

Of course, it may simply be that when the extended Strong's codes were first proposed,
nobody thought to check whether they might not yet be supported in the SWORD API,
as all the attention would have been within front-end[s] based on JSword.

Problem reported after using diatheke command-line SWORD frontend Version 4.7  distributed with xiphos.exe 4.2.1 (gtk2 webkit1)

I assume that this was built with SWORD v1.9 - so correct me if I'm mistaken.

I have attached a counted list of the eXtended only Strong's numbers extracted from the exported IMP file generated (using mod2imp) from the OSHB module.

David Haslam
CrossWire volunteer since 2008 
Mostly focused on text and module development and module testing/analysis.