[sword-devel] osis2mod default versification
Peter von Kaehne
refdoc at gmx.net
Sat Sep 5 17:23:44 MST 2015
Re versifications, the need for any v11n needs to be established and well documented. Once in use we can not easily withdraw any v11n, so introduction happens careful, but nothing should stop you making a good case for specific new v11n(s). Domcox has just now produced two new v11ns which hopefully will make it into svn soon. You should check them esp with French Pacific island languages.
Yours
Peter
Sent from my phone. Apologies for brevity and typos.On 5 Sep 2015 21:33, Kahunapule Michael Johnson <Kahunapule at eBible.org> wrote:
>
> The lack of documentation agreement on what the default versification is doesn't surprise me, but it should be fixed.
> It also doesn't affect me, because I never call osis2mod without specifying the versification to use, so I never use the default.
> This is a pretty minor point compared to the architectural issue of not really being able to optimally represent the world's Bibles with the current set of hard-coded versifications.
> An even bigger point is not being able to handle mid-verse section titles. Those are VERY common. (I just have all section titles disabled temporarily on the eBible.org repository because of this.)
>
> Priorities.
>
> On 09/05/2015 08:37 AM, David Haslam wrote:
>>
>> The de facto observation that recent builds of osis2mod make NRSV the default
>>
>> v11n raises several questions:
>>
>>
>>
>> When was this change sneaked in?
>>
>>
>>
>> Was there a formal agreement among developers?
>>
>>
>>
>> Was there any announcement?
>>
>>
>>
>> Why was this not mentioned on the Developers' wiki?
>>
>>
>>
>> Which other SWORD utilities have been changed (if any)?
>>
>>
>>
>> How come the change was not reflected in the SYNTAX HELP ? (as Michael H
>>
>> reports)
>>
>>
>>
>> IMHO, this change was unwarranted.
>>
>>
>>
>> It's very galling that such a significant change could be made without
>>
>> adequate considerations of the implications.
>>
>>
>>
>> Those who have scripts for module builds may well have omitted the -v KJV
>>
>> switch for osis2mod.
>>
>> It was wrong to assume that for such module developers it would be left to
>>
>> chance to discover that their scripts were no longer working correctly.
>>
>>
>>
>> Best regards,
>>
>>
>>
>> David
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> View this message in context: http://sword-dev.350566.n4.nabble.com/osis2mod-default-versification-tp4655253p4655255.html
>>
>> Sent from the SWORD Dev mailing list archive at Nabble.com.
>>
>>
>>
>> _______________________________________________
>>
>> sword-devel mailing list: sword-devel at crosswire.org
>>
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>
>> Instructions to unsubscribe/change your settings at above page
>>
>
>
> --
>
> Aloha,
> Kahunapule Michael Johnson
>
> MICHAEL JOHNSON
> PO BOX 881143
> PUKALANI HI 96788-1143
> USA
> eBible.org
> MLJohnson.org
> Mobile: +1 808-333-6921
> Skype: kahunapule
More information about the sword-devel
mailing list