[sword-devel] Synodal versification as compiled into osis2mod

David Haslam dfhmch at googlemail.com
Sat Nov 29 06:00:03 MST 2014


I now think that it's that osis2mod was giving misleading info warnings,
in that osisID "not in the specified v11n" is stated wrongly as the next
chapter.

It should really be stated for the next verse in each instance.

The error output should therefore have been:

INFO(V11N): Job.20.30 is not in the Synodal versification. Appending content
to Job.20.29
INFO(V11N): Ps.129.9 is not in the Synodal versification. Appending content
to Ps.129.8
INFO(V11N): Song.1.17 is not in the Synodal versification. Appending content
to Song.1.16 

Has anyone already reported this?

If so, has the source code for osis2mod been corrected?

If not, please would someone fix this software bug.

David



--
View this message in context: http://sword-dev.350566.n4.nabble.com/Synodal-versification-as-compiled-into-osis2mod-tp4654258p4654259.html
Sent from the SWORD Dev mailing list archive at Nabble.com.



More information about the sword-devel mailing list