Revision 3177 works as required.
In the snippet pasted below, I removed the INFO(WRITE) lines, just to avoid
clutter.
INFO(V11N): 3John.1.15 is not in the KJV versification. Appending content to
3John.1.14
INFO(V11N): Rev.12.18 is not in the KJV versification. Appending content to
Rev.12.17
Davi
Thanks - good that it's fixed already in Revision 3016.
Please would one of the developers recompile & upload the Sword utilities
for Windows,
so that I can begin to used the latest fixed version.
In the past, Greg has been kind enough to do this.
Revision 2908 were compiled 16 months ago, so th
Has anyone already reported this?
If so, has the source code for osis2mod been corrected?
I reported a similar bug, see
http://www.crosswire.org/tracker/browse/MODTOOLS-56 but it has been fixed.
___
sword-devel mailing list: sword-devel@crosswire.org
Further evidence that it's a more general software bug... (i.e. not
particular to Synodal)
>From another module build.
INFO(V11N): Jude is not in the KJV versification. Appending content to
3John.1.14
INFO(V11N): Rev.13 is not in the KJV versification. Appending content to
Rev.12.17
It should ha
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
When I rebuilt the Bela module today using osis2mod: $Rev: 2893 $,
there were three info warnings in the log file.
INFO(V11N): Job.21 is not in the Synodal versification. Appending content to
Job.20.29
INFO(V11N): Ps.130 is not in the Synodal versification. Appending content to
Ps.129.8
INFO(V11N
