This appears to be broken again as OSMHB is not recognised as having Strongs Numbers. This means that Strong numbers are probably not part of the OSMHB Lucene index. Also And Bible uses the same check to work out whether to show the Strongs toggle.
Books are checked for Strongs in various places in JSword e.g.
But these return false for OSMHB which contains:
There was a long email chain the led to this bug being created originally:
There was a hack that I briefly used at one time involving GlobalOptionFilter but I thought that was unnecessary now.
I have a junit:
Book osmhb = Books.installed().getBook("OSMHB");
assertTrue("OSMHB GlobalOptionFilter hack does not find Strongs", osmhb.getBookMetaData().getProperty("GlobalOptionFilter").toString().contains("Strongs"));
assertTrue("OSMHB not recognised as containing Strongs numbers", osmhb.hasFeature(FeatureType.STRONGS_NUMBERS) || osmhb.getBookMetaData().hasFeature(FeatureType.STRONGS_NUMBERS));