Re: [sword-devel] Script to find a best fit v11n

Arnaud Vié writes: > It might be a silly question, but can't we just consider changing the > libsword license to something more permissive to allow such use cases, > without overthinking about GPL compatibility issues ? Relicensing to GPLv2+ or GPLv3+ or LGPL seems like a good idea However, reli

Re: [sword-devel] Script to find a best fit v11n

On Tue Jul 1, 2025 at 1:35 AM CEST, Greg Hellings wrote: > I think this sentiment from Peter is the crux of why people in this > community don't want to use a more permissive license. Most of us don't > want our work on scripture, scripture access, and the surrounding utilities > to be turned into

Re: [sword-devel] Script to find a best fit v11n

On Mon Jun 30, 2025 at 3:32 PM CEST, Arnaud Vié wrote: > It is quite uncommon for open source libraries to use GPL nowadays, as it's > very restrictive by nature. GPL remains mostly for "complete" applications > - libraries tend to rather use LGPL, Apache 2.0 or MIT license (depending > on the leve

Re: [sword-devel] Script to find a best fit v11n

m > *Sent:* Monday, June 30, 2025 2:57 pm > *To:* sword-devel mailing list > *Cc:* David Instone-Brewer ; Jamie Jamieson > > *Subject:* Re: [sword-devel] Script to find a best fit v11n > > Hi Peter, > > STEP Bible is formally & organisationally separate from Tyndale

Re: [sword-devel] Script to find a best fit v11n

nt:* Monday, June 30, 2025 2:40 pm > *To:* sword-devel mailing list > *Subject:* Re: [sword-devel] Script to find a best fit v11n > > Does anyone know whether STEP Bible uses JSword as is, or a modified form > of JSword ? > > Asking in view of Arnaud’s observation about LGPL. &g

Re: [sword-devel] Script to find a best fit v11n

On Mon, Jun 30, 2025, 9:32 AM Arnaud Vié wrote: > It might be a silly question, but can't we just consider changing the > libsword license to something more permissive to allow such use cases, > without overthinking about GPL compatibility issues ? > It could be done, yes. But it is not a change

Re: [sword-devel] Script to find a best fit v11n

On Mon, Jun 30, 2025, 8:43 AM Matěj Cepl wrote: > On Mon Jun 30, 2025 at 4:55 AM CEST, Aaron Rainbolt wrote: > > From what I understand as someone who isn't a lawyer but has done > > licensing audits for applications in Ubuntu and Debian, you'll only > > run into issues if you publish *built bina

Re: [sword-devel] Script to find a best fit v11n

<<< text/html; charset="utf-8": Unrecognized >>> ___ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Script to find a best fit v11n

gt; > Peter > > Sent from [Outlook for iOS](https://aka.ms/o0ukef) > > --- > > From: sword-devel on behalf of David > Haslam > Sent: Monday, June 30, 2025 2:40 pm > To: sword-devel mailing list > Subject:

Re: [sword-devel] Script to find a best fit v11n

<<< text/html; charset="utf-8": Unrecognized >>> ___ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Script to find a best fit v11n

Does anyone know whether STEP Bible uses JSword as is, or a modified form of JSword ? Asking in view of Arnaud’s observation about LGPL. Kind regards, David Sent from [Proton Mail](https://proton.me/mail/home) for iOS On Mon, Jun 30, 2025 at 14:32, Arnaud Vié <[unas.zole+a...@gmail.com](mailt

Re: [sword-devel] Script to find a best fit v11n

It might be a silly question, but can't we just consider changing the libsword license to something more permissive to allow such use cases, without overthinking about GPL compatibility issues ? It is quite uncommon for open source libraries to use GPL nowadays, as it's very restrictive by nature.

Re: [sword-devel] Script to find a best fit v11n

On Mon Jun 30, 2025 at 4:55 AM CEST, Aaron Rainbolt wrote: > From what I understand as someone who isn't a lawyer but has done > licensing audits for applications in Ubuntu and Debian, you'll only > run into issues if you publish *built binaries* of your code. That technically may be true, but it

Re: [sword-devel] Script to find a best fit v11n

On Sun, Jun 29, 2025 at 9:55 PM Aaron Rainbolt wrote: > From what I understand as someone who isn't a lawyer but has done > licensing audits for applications in Ubuntu and Debian, you'll only > run into issues if you publish *built binaries* of your code. If you > just publish code, even if it's

Re: [sword-devel] Script to find a best fit v11n

From what I understand as someone who isn't a lawyer but has done licensing audits for applications in Ubuntu and Debian, you'll only run into issues if you publish *built binaries* of your code. If you just publish code, even if it's explicitly intended to be used with license-incompatible librari

Re: [sword-devel] Script to find a best fit v11n

On Sun, Jun 29, 2025, 8:56 PM Matěj Cepl wrote: > On Mon Jun 30, 2025 at 2:05 AM CEST, Greg Hellings wrote: > > I was about to publish it and produce binaries, but I ran into a problem: > > I used Slint to create the UI, and Slint is licensed for either > commercial > > or GPLv3 > > SWORD is lice

Re: [sword-devel] Script to find a best fit v11n

On Mon Jun 30, 2025 at 2:05 AM CEST, Greg Hellings wrote: > I was about to publish it and produce binaries, but I ran into a problem: > I used Slint to create the UI, and Slint is licensed for either commercial > or GPLv3 > SWORD is licensed as GPLv2 Isn’t GPLv3 downward compatible? I.e., you can

Re: [sword-devel] Script to find a best fit v11n

Someone left me alone for too long and I converted my original Python script for parsing versifications into a Rust GUI application. You can see the quick screencast of what I've done here: https://youtu.be/IwTQTF8PRC4 I was about to publish it and produce binaries, but I ran into a problem: I use

Re: [sword-devel] Script to find a best fit v11n

On Thu, Jun 19, 2025 at 4:13 PM DM Smith wrote: > > On Jun 19, 2025, at 3:24 PM, Greg Hellings > wrote: > > > Like most things, it's a trade-off. Working with the bindings requires > that the Sword bindings are installed on the host system. For someone > running on Windows, this is particularly

Re: [sword-devel] Script to find a best fit v11n

> On Jun 19, 2025, at 3:24 PM, Greg Hellings wrote: > > > > On Thu, Jun 19, 2025 at 9:07 AM DM Smith > wrote: >> Greg, >> There’s an extraneous %s in the output. > > Ah, not surprising. That is the old, Python 2 way of formatting variables > into a string, simi

Re: [sword-devel] Script to find a best fit v11n

On Thu, Jun 19, 2025 at 9:07 AM DM Smith wrote: > Greg, > There’s an extraneous %s in the output. > Ah, not surprising. That is the old, Python 2 way of formatting variables into a string, similar to C style printf syntax with variable arguments coming in a tuple after an overload of the modulus

Re: [sword-devel] Script to find a best fit v11n

manageable number as long as you know what to look for in final decision making. Peters PeterSent from Outlook for iOS From: sword-devel on behalf of DM Smith Sent: Thursday, June 19, 2025 5:17 pmTo: SWORD Developers' Collaboration Forum Subject: Re: [sword-devel] Script to find a best fit

Re: [sword-devel] Script to find a best fit v11n

June 19, 2025 6:41 am > To: SWORD Developers' Collaboration Forum > Subject: Re: [sword-devel] Script to find a best fit v11n > > My script eschews percentages because they seemed relatively pointless to me > for measuring a mismatch like this. Instead it gives a count of both Old a

Re: [sword-devel] Script to find a best fit v11n

Greg, There’s an extraneous %s in the output. If you put the enumeration after the line "There are 93 OT IDs and 5 NT IDs in v11n which aren’t in your file.” Then you wouldn’t need the heading "The following IDs don’t appear in your file:” It’d also be nice to format it a few per line, indented

Re: [sword-devel] Script to find a best fit v11n

Greg, I like that it's very simple to read. Having a summary is good. And the other email which lists the exact ids extra/missing per testament is very helpful. I think that enumerating the names of the extra/missing books and extra/missing chapters would be good. No sense in enumerating the id

Re: [sword-devel] Script to find a best fit v11n

Percentages are pointless. Counting both extra and missing is better. > On Jun 18, 2025, at 11:40 PM, Greg Hellings wrote: > > My script eschews percentages because they seemed relatively pointless to me > for measuring a mismatch like this. Instead it gives a count of both Old and > New Testa

Re: [sword-devel] Script to find a best fit v11n

On Thu Jun 19, 2025 at 6:02 AM CEST, Greg Hellings wrote: > Here is an example of the first lines of running my script against the > kjv.osis.xml file from the git repo: KJV is probably the best fitting Bible anywhere, because the most software was created around it. Try something more funny. I ha

Re: [sword-devel] Script to find a best fit v11n

That script is what I have used for years witg good effect. Thank you Greg. Sent from Outlook for iOS From: sword-devel on behalf of Greg Hellings Sent: Thursday, June 19, 2025 6:41 amTo: SWORD Developers' Collaboration Forum Subject: Re: [sword-devel] Script to find a best fit v11n My s

Re: [sword-devel] Script to find a best fit v11n

And here's an example now that I've fixed the output of the osisIDs when there are fewer than 100 of them: [vagrant@localhost ~]$ ./av11n.py kjv.osis.xml Checking Calvin: The following IDs don’t appear in your file: %s 1Kgs.22.54, 1Sam.20.43, 1Sam.24.23, 3John.1.15, Act

Re: [sword-devel] Script to find a best fit v11n

My script eschews percentages because they seemed relatively pointless to me for measuring a mismatch like this. Instead it gives a count of both Old and New Testament osisIDs that it finds missing and another that it finds unexpectedly for a given versification. If the total of either count is few

Re: [sword-devel] Script to find a best fit v11n

Here is an example of the first lines of running my script against the kjv.osis.xml file from the git repo: Checking Calvin: There are 93 OT IDs and 5 NT IDs in v11n which aren’t in your file. There are 0 OT IDs and 30 NT IDs in your file which don’t appear in v11

Re: [sword-devel] Script to find a best fit v11n

It’s not just the number of “missing” verses that should figure in the percentage score, but also the number of verses that get concatenated to the last one in a chapter. The differences in v11n for the Psalms will be especially significant for this, in that some v11n renumber many of them. Lik

Re: [sword-devel] Script to find a best fit v11n

David, Because it only considers the xml, scope is automatically built into it. It is only comparing what is present in the xml with what is part of the av11ns. It might be good to add the enumeration of missing verses. — DM > On Jun 18, 2025, at 4:02 PM, David Haslam wrote: > > Does it tak

Re: [sword-devel] Script to find a best fit v11n

Didn’t know about that. Sounds like a great idea. I think the modules team should include such in their module building protocol. As I said, I don’t know python and have never programmed in it. But I can read and tweak them. > On Jun 18, 2025, at 4:03 PM, Greg Hellings wrote: > > There has b

Re: [sword-devel] Script to find a best fit v11n

No. Both DM's script (and mine) operate on an OSIS file. Not on a module. --Greg On Wed, Jun 18, 2025 at 3:03 PM David Haslam wrote: > Does it take account of the Scope key in the .conf file for a less than > complete Bible ? > > David > > Sent from Proton Mail for

Re: [sword-devel] Script to find a best fit v11n

There has been this file, which I think I wrote a geological epoch ago: https://www.crosswire.org/svn/sword-tools/trunk/versification/av11n.py Like yours, it is a very rough attempt to brute force compare the osisIDs found in a file with known versification schemes. Unlike yours, it depends on ha

Re: [sword-devel] Script to find a best fit v11n

Does it take account of the Scope key in the .conf file for a less than complete Bible ? David Sent from [Proton Mail](https://proton.me/mail/home) for iOS On Wed, Jun 18, 2025 at 20:51, DM Smith <[dmsm...@crosswire.org](mailto:On Wed, Jun 18, 2025 at 20:51, DM Smith < wrote: > Hi, > > Severa