Difference between revisions of "Alternate Versification"
From CrossWire Bible Society
(→Overview) |
(→Overview) |
||
| Line 12: | Line 12: | ||
==Overview== | ==Overview== | ||
| − | # | + | Up until 1.5.11 the canon and the versification was hard coded into the engine in form of the file canon.h which offered book names and chapter + verse offsets to the engine. The new approach is that |
| + | |||
| + | # Each Bible module will carry a conf entry about its versification (unless KJV) from an approved list of versifications | ||
| + | # the engine will have for each major canon and versification variety a new header file similar to the previous canon.h | ||
| + | # On system start the engine will load for each open KJV-divergent module the relevant data presented in the relevant canon_{Versification].h. Subsequently the relevant module will be accessible via the usual methods - which have not changed from 1.5.11 | ||
| + | # What does not work anymore is to assume that a book or chapter has a set (fixed) number of verses. Instead 1.5.12 introduces a new method maxverse and maxchapter method providing you for a given module with the relevant information. | ||
| + | # At a later stage (1.5.13) the engine will allow for genBook bibles to automagically create arbitrary versification tables on the fly. | ||
| + | |||
=== How to create Modules with alternative versifications === | === How to create Modules with alternative versifications === | ||
# Set the relevant entries in the configuration file [[DevTools:confFiles| Configuration file]] | # Set the relevant entries in the configuration file [[DevTools:confFiles| Configuration file]] | ||
| − | # if your module uses a versification or canon not yet present in SWORD you will need to create a canon header file. | + | # if your module uses a versification or canon not yet present in SWORD you will need to create a canon header file. |
Revision as of 22:26, 16 March 2009
Contents
Introduction
Alternative versifications mean ultimately to allow Bible texts with arbitrary canon or versification schemes to coexist peacefully on the same SWORD installation and (ultimately) to map cleanly between each other via cross references or parallel display.
There are technically 2 routes to support this under development:
- ripping out the hardcoded KJV canon.h offsets and replacing them with VerseMgr, which allows registration of canon.h-like v11n systems.
- genbook Bibles
Both have been under development and 2 requires 1.
Overview
Up until 1.5.11 the canon and the versification was hard coded into the engine in form of the file canon.h which offered book names and chapter + verse offsets to the engine. The new approach is that
- Each Bible module will carry a conf entry about its versification (unless KJV) from an approved list of versifications
- the engine will have for each major canon and versification variety a new header file similar to the previous canon.h
- On system start the engine will load for each open KJV-divergent module the relevant data presented in the relevant canon_{Versification].h. Subsequently the relevant module will be accessible via the usual methods - which have not changed from 1.5.11
- What does not work anymore is to assume that a book or chapter has a set (fixed) number of verses. Instead 1.5.12 introduces a new method maxverse and maxchapter method providing you for a given module with the relevant information.
- At a later stage (1.5.13) the engine will allow for genBook bibles to automagically create arbitrary versification tables on the fly.
How to create Modules with alternative versifications
- Set the relevant entries in the configuration file Configuration file
- if your module uses a versification or canon not yet present in SWORD you will need to create a canon header file.
Modules requiring alternate versification
- Ohienko Ukrainian translation.
The existing module had discarded the original Ukrainian verse numbers. ua4ever has recently made an OSIS file in the KJV order, but with the original Ukrainian verse references in parentheses. Download RAR file from [1]. For related discussions, see [2]. Registration and login is required.
