Details
-
Type:
Improvement
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
When doing new module for the Bible21 (which in its second edition has apocrypha) we hit the problem that there was no v11n which would at least from afar support its text. After the discussion on sword-devel list which kind of lead nowhere, Libor Stefek
created the attached patch for libsword and the experimental CzeB21 module with it.
I know that you hoped for some more detailed research into all possible versions of the Protestant Bibles with Apocrypha, but currently I don’t think I am able to provide much more than this, and I guess this is the situation when the best cold be the enemy of good. This versioning works for this Bible, and we can build on it and to improve it eventually when the need arises.
Attachments
Activity
Err, how many modules using this (or any particular) v11n are there outisde of the https://www.crosswire.org/sword repository? How many modules we won’t have at least information about? I don’t think it is that many. Meanwhile we can add some dire information into wiki.crosswire.org or somewhere that this v11n should be considered experimental and could be changed in future versions.
Otherwise, what exactly do you expect from me to do? Analyse other so far non-existent Bibles? That doesn’t make much sense.
Versification tables unlike pretty much anything else can not be improved upon gradually and as problems become obvious. Once modules are in the wild we have no way of ensuring that there are no clashes.
At the same time each new versification has a load up penalty particularly on slow devices. So we do want new versification schemes to be as much as possible generic, covering a larger number of texts.
Therefore, I can not recommend inclusion of the patch until it is certain there is adequate testing etc done.
Peter