You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using this library to generate a list of verses therefore misses out these - which can cause errors if we iterate over two data sources (one generated based on verses from this library, and other based on verses actually present in a translation).
We should fix outstanding versification issues (such as #1) - then I think the default versification should be a "superset" which would generate all verses in all reasonable translations. This prevents this source of bugs where we miss out data.
We should export specifiic versification schemes for KJV / ESV / CEV as well.
This would (probably?) be a breaking change, so would require a major version bump.
The text was updated successfully, but these errors were encountered:
WEB also moves last 2 verses of romans 16 to last 2 verses of romans 14 - therefore increasing number of verses in romains 14. wikipedia
A "superset" versification scheme wouldn't help generic APIs which would need to remap the results for these moved veres (and actually for those listed in above post) - which potentially limits the usefulness of that idea (at least, for use as the default versification scheme).
This library uses the KJV versification scheme, compared to this:
ESV (and others?) split 3 John 1:14 of KJV in two, adding a new verse 3 John 1:15 (see
CEV (and others?) split Rev 12:17 into two, adding a new verse Rev 12:18
Using this library to generate a list of verses therefore misses out these - which can cause errors if we iterate over two data sources (one generated based on verses from this library, and other based on verses actually present in a translation).
We should fix outstanding versification issues (such as #1) - then I think the default versification should be a "superset" which would generate all verses in all reasonable translations. This prevents this source of bugs where we miss out data.
We should export specifiic versification schemes for KJV / ESV / CEV as well.
This would (probably?) be a breaking change, so would require a major version bump.
The text was updated successfully, but these errors were encountered: