Re: [sword-devel] osis2mod default versification

2015-09-06 Thread Michael H 
I've been unable to verify what I was looking at when I came to the
conclusion that NRSV was used when osis2mod is run without a -v parameter.

My apologies to DM Smith and David H for creating any misunderstanding.

I now suspect I've misread a New Testament introduction that claims to be
following the King James Version to apply to the versification, when it was
only intended to apply to the source text used. (which means an error
'appending 3 John 15 to 14' was probably misunderstood as a default in the
program, not a vague statement in that intro.)


( https://www.biblegateway.com/versions/Worldwide-English-New-Testament-WE/
)
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification/MIDVERSE SECTION TITLES

2015-09-06 Thread DM Smith 
Yay!

— DM

> On Sep 5, 2015, at 9:40 PM, Kahunapule Michael Johnson  > wrote:
> 
> I just tried a build with midverse section titles turned on with Xiphos, and 
> lo and behold, it worked! Someone fixed something or my memory was faulty or 
> both.
> Verified with kkl2015eb, Acts 9:19. (This is the newest Bible in the 
> collection.)
> If you don't want to see the noncanonical section headings, you can always 
> turn them off. The GlobalOptionFilter=OSISHeadings conf option is set where 
> applicable (which will be for most of the Bibles in the collection).
> The eBible.org/swordbeta  repository is being 
> incrementally updated again, turning section titles on globally.
> 
> On 09/05/2015 01:56 PM, Peter von Kaehne wrote:
>> Yes
>> 
>> Sent from my phone. Apologies for brevity and typos.On 5 Sep 2015 11:44 pm, 
>> Kahunapule Michael Johnson  
>>  wrote:
>>> >
>>> > Should I re-enable section titles (including mid-verse section titles) in 
>>> > the OSIS I feed to osis2mod? I recall discussions about things not 
>>> > working right, but don't recall the details of what failed how in which 
>>> > front ends.
>>> >
> 
> 
> -- 
> 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 ___
> sword-devel mailing list: sword-devel@crosswire.org 
> 
> http://www.crosswire.org/mailman/listinfo/sword-devel 
> 
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread David Haslam 
The utility imp2vs also provides for a -v flag. The default is KJV.

The copy of imp2vs.exe installed along with Xiphos 4.0.3 is still Rev 2234.

Defaults in SWORD utilities should remain consistent.

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/osis2mod-default-versification-tp4655253p4655257.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread DM Smith 
There are a few more changes that can be documented, such as the change of the 
flags regarding compression and the addition of other compression 
methodologies. Both SWORD and JSword properly support these.

— DM

> On Sep 5, 2015, at 3:22 PM, David Haslam  wrote:
> 
> All significant changes for osis2mod should be documented!
> 
> Here's where past changes are listed.
> 
> http://www.crosswire.org/wiki/Osis2mod#History_of_Changes
> 
> Changing a default setting is one of the worst things a programmer can
> do!
> 
> It would be better to have removed the default and made the -v flag a
> mandatory requirement.
> Then at least every user would soon find out that his old script or
> remembered command line now gave an error message. 
> 
> David
> 
> 
> 
> --
> View this message in context: 
> http://sword-dev.350566.n4.nabble.com/osis2mod-default-versification-tp4655253p4655259.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread DM Smith 
Looking at the code, it has not changed.

— DM

> On Sep 5, 2015, at 5:08 PM, DM Smith  wrote:
> 
> It shouldn’t have changed!!!
> — DM
> 
>> On Sep 5, 2015, at 2:37 PM, 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@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread David Haslam 
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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread David Haslam 
There have been changes to the osis2md syntax help in other respects. 

I just compared the help out put for versions 3177 and 3314.

Below is the diff file.

diff  C:/Users/David/AppData/Roaming/Sword/Help/osis2mod.xiphos.help.txt
C:/Users/David/AppData/Roaming/Sword/Help/osis2mod.xiphos4.help.txt

1,3c1
< You are running osis2mod: $Rev: 3177 $
< 
< xiphos\osis2mod: 
---
> You are running osis2mod: $Rev: 3314 $
18,20d15
<(default is to convert to UTF-8, if needed,
< and then normalize to NFC)

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread Kahunapule Michael Johnson 

  
  
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@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
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread Michael H 
In modern Bible Translation (Wycliffe/SIL) circles, "default" versification
in the translation programs  (ParaTExt, SIL Translation Editor, and Teus'
BiblEdit)  is 'English' which is (as far as I know) the same versification
as what Sword calls NRSV, so this change should be considered. It will
cause less confusion for folks who've spent years working translations with
Wycliffe get their texts into sword format. There won't be that many 'new'
translations which are using KJV as their versification.

However:

1. The documentation should reflect what the code does. If the manpages
have been abandoned, they should disappear.

2. Existing modules which use KJV versification typically leave the
Versification= line out of the .conf file (SpaRVG for example).  Without an
effort to fix these legacy .conf files (forcing all .conf files to be
explicit about versification) I suspect eventually there will be front end
problems misinterpreting what 'default' means.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread David Haslam 
All significant changes for osis2mod should be documented!

Here's where past changes are listed.

http://www.crosswire.org/wiki/Osis2mod#History_of_Changes

Changing a default setting is one of the worst things a programmer can
do!

It would be better to have removed the default and made the -v flag a
mandatory requirement.
Then at least every user would soon find out that his old script or
remembered command line now gave an error message. 

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/osis2mod-default-versification-tp4655253p4655259.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread DM Smith 
It shouldn’t have changed!!!
— DM

> On Sep 5, 2015, at 2:37 PM, 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@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread DM Smith 
It is documented. It is the KJV.

— DM

> On Sep 5, 2015, at 4:33 PM, Kahunapule Michael Johnson 
>  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@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 ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread DM Smith 
Osis2mod handles mid-verse section titles properly. The problem is elsewhere. 
They work just fine in Bible Desktop and other JSword applications.

Regarding more v11n, this has nothing to do with osis2mod. osis2mod merely 
knows what SWORD makes available and allows that.

— DM

> On Sep 5, 2015, at 4:33 PM, Kahunapule Michael Johnson 
>  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@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 ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification/MIDVERSE SECTION TITLES

2015-09-05 Thread Kahunapule Michael Johnson 

  
  
I just tried a build with midverse
  section titles turned on with Xiphos, and lo and behold, it
  worked! Someone fixed something or my memory was faulty or both.
  Verified with kkl2015eb, Acts 9:19. (This is the newest Bible in
  the collection.)
  If you don't want to see the noncanonical section headings, you
  can always turn them off. The GlobalOptionFilter=OSISHeadings conf
  option is set where applicable (which will be for most of the
  Bibles in the collection).
  The eBible.org/swordbeta repository is being incrementally updated
  again, turning section titles on globally.
  
  On 09/05/2015 01:56 PM, Peter von Kaehne wrote:


  Yes

Sent from my phone. Apologies for brevity and typos.On 5 Sep 2015 11:44 pm, Kahunapule Michael Johnson  wrote:

  
>
> Should I re-enable section titles (including mid-verse section titles) in the OSIS I feed to osis2mod? I recall discussions about things not working right, but don't recall the details of what failed how in which front ends.
>
  



-- 
  
  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
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread Peter von Kaehne 
I think there is a misunderstanding.

When i said NRSV is the default, thrn i meant simply that the bulk of all 
translations i load up are NRSV and i tend not to even consider KJV, unless 
forced to. 

It is quite clear that none of the tools havr changed, also the engine has not 
changed, nor is any change necessary for having NRSV as first choicr whenever 
it fits. 

Sent from my phone. Apologies for brevity and typos.On 5 Sep 2015 6:26 pm, 
Michael H  wrote:
>
> Hi, 
>
> Recently, Peter mentioned to David that the utility osis2mod has changed it's 
> default versification from KJV to NRSV. Further testing shows this to be true 
> for osis2mod 3314 . However: 
>
> $osis2mod -h 
>
> still shows 
>
>   -v  specify a versification scheme to use (default is KJV)
>
> and $man osis2mod shows nothing about versification.  (On my ubuntu 14.04 
> system the manpage claims to support "sword 1.7.4+dfsg".)
>
> It would be nice if the built-in help or the manpage covered this as well as 
> the wiki. This is very likely tripping everyone who's trying to get a KJV 
> style text into sword module. 
>
>
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification/MIDVERSE SECTION TITLES

2015-09-05 Thread Kahunapule Michael Johnson 

  
  
Should I re-enable section titles
  (including mid-verse section titles) in the OSIS I feed to
  osis2mod? I recall discussions about things not working right, but
  don't recall the details of what failed how in which front ends.
  
  
  On 09/05/2015 11:22 AM, DM Smith wrote:


  
  Osis2mod handles mid-verse section titles properly. The problem is
  elsewhere. They work just fine in Bible Desktop and other JSword
  applications.
  
  
  Regarding more v11n, this has nothing to do with
osis2mod. osis2mod merely knows what SWORD makes available and
allows that.
  
— DM

  

  On Sep 5, 2015, at 4:33 PM, Kahunapule
Michael Johnson 
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@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

  

  

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at
above page

  
  

  
  
  
  
  ___
sword-devel mailing list: sword-devel@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

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread Peter von Kaehne 
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  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@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
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification

2015-09-05 Thread Kahunapule Michael Johnson 

  
  
On 09/05/2015 02:23 PM, Peter von
  Kaehne wrote:


  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).


I understand the way things are and have been for years. It is hard
to change, but not impossible. If someone wanted to implement
per-module versifications such that code changes weren't necessary
to deal with the way someone else split up the Bible into chapters
and verses, I would be all for it. But not enough to code the
changes, at least not now.


   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. 



I intend to add those v11ns to my versification checks when support
for them in Sword is real in the stable Sword utilities and they are
supported by the distribution versions of all actively-supported
front ends. Someone please let me know when that happens.

Seriously, there is no point making modules with a versification
nobody can read, yet. Once support is real, it is not hard for me to
check every single module again to see if the "least bad"
versification has changed with the addition of any new ones.
-- 
  
  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
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] osis2mod default versification/MIDVERSE SECTION TITLES

2015-09-05 Thread Peter von Kaehne 
Yes

Sent from my phone. Apologies for brevity and typos.On 5 Sep 2015 11:44 pm, 
Kahunapule Michael Johnson  wrote:
>
> Should I re-enable section titles (including mid-verse section titles) in the 
> OSIS I feed to osis2mod? I recall discussions about things not working right, 
> but don't recall the details of what failed how in which front ends.
>
>
> On 09/05/2015 11:22 AM, DM Smith wrote:
>
> Osis2mod handles mid-verse section titles properly. The problem is elsewhere. 
> They work just fine in Bible Desktop and other JSword applications.
>
> Regarding more v11n, this has nothing to do with osis2mod. osis2mod merely 
> knows what SWORD makes available and allows that.
>
> — DM
>
>> On Sep 5, 2015, at 4:33 PM, Kahunapule Michael Johnson 
>>  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@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
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page 
>
>
> ___
>
> sword-devel mailing list: sword-devel@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
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page