[sword-devel] first non-KJV v11n

[DM Smith]

Manfred Bergmann wrote:
>
> Am 18.03.2009 um 12:15 schrieb DM Smith:
>
>>
>> On Mar 18, 2009, at 5:42 AM, Chris Little wrote:
>>
>>> I've committed the first non-KJV versification system to SVN HEAD, 
>>> as well as an expanded builtin_abbrevs[] array with all of the books 
>>> we are likely to support in 1.5.12 (or quite probably more books 
>>> than that).
>>>
>>> The v11n system I've committed is "Leningrad"--the v11n of the 
>>> Leningrad Codex. *There is no guarantee that we will ship this v11n 
>>> system in the next release. It should be considered a test v11n.*
>>>
>>> The reasons for selecting Leningrad first are that it is well 
>>> defined, different from KJV (verses & chapters are different, book 
>>> order is different, & NT is absent entirely), and there is only one 
>>> text (plus its derivatives) that uses this v11n, so people are 
>>> unlikely to go too wild with it. I've tested it only to the extent 
>>> that I've compiled Sword with it included.
>>>
>>> There are no books in this system, ATM, but I'll work on posting a 
>>> demo WLC in its native v11n tomorrow after I get home from work (in 
>>> about 10 hours).
>>
>> Chris,
>>
>> I'm excited about this!
>>
>> I'm working on osis2mod at the moment to add -v flag to it. There is 
>> a bug I mentioned in another thread, but it seems to work  as long as 
>> all the verses are in the versification. You can grab it on the 
>> CrossWire server at ~dmsmith/swordsrc/sword/utilities/osis2mod.cpp. I 
>> think the other route is to use imp2vs, but it doesn't handle out of 
>> v11n verses at all.
>>
>> When were were beta testing the German modules, many of them had the 
>> same KJV versification problems. I'd like to see a versification for 
>> that, if you don't already have one in the wings. If so, which is it? 
>> The input files are fairly easy to create, in so far as they are used 
>> by v11nsys.pl (i.e. the mapping part is not currently used). Peter or 
>> Manfred probably could pretty easily create one if it does not 
>> already exist.
>
> Create a mapping file?
> Yeah, how?
I didn't mean the mapping part, but the verse list part.
 
The program v11nsys.pl will take various inputs and output a canon_*.h 
file. The inputs are essentially a file of ordered verses. The program 
then figures out how many chapters in each book and how many verses in 
each chapter and builds some fast lookup tables where given a book, 
chapter and verse, one can determine the position of that verse in the 
canon.
>
> I've got another question in that regard.
> Do none canonical books have or get a standardized OSIS book name?
Yes, the OSIS spec has a list of OSIS standardized book names for the 
apocrypha.
See the OSIS manual page 124. You can get it here: 
http://www.bibletechnologies.net

To get a good idea of how v11n is going to work, poke around in the 
directory:
    http://www.crosswire.org/svn/sword-tools/trunk/versification
In the Bible.*.xml files the name field is the osisID.

> Or are the apocryphical books not going to be part of a Bible module?
They will be. And they will either be part of the OT or the NT, 
depending on the tradition of the v11n. Also, books will be ordered 
according to that tradition, too.

In Him,
    DM