On Tue, Mar 10, 2020 at 6:49 PM Michael H wrote:
> I owe you lunch Greg.
>
I sure wouldn't turn down an offer like that!
--Greg
>
> On Tue, Mar 10, 2020 at 6:37 PM Philip White
> wrote:
>
>> Ahh, that C API looks like what I would want.
>>
>> I didn't mean to disparage or be uppity by stating
I owe you lunch Greg.
On Tue, Mar 10, 2020 at 6:37 PM Philip White
wrote:
> Ahh, that C API looks like what I would want.
>
> I didn't mean to disparage or be uppity by stating my preference for
> standardization; I greatly appreciate what this project (I use And
> Bible on my phone). This is by
Ahh, that C API looks like what I would want.
I didn't mean to disparage or be uppity by stating my preference for
standardization; I greatly appreciate what this project (I use And
Bible on my phone). This is by far the smaller of my two concerns. I
may also suffer from not-invented-here syndrome
On Tue, Mar 10, 2020 at 5:56 PM Michael H wrote:
> Greg,
>
> Diatheke on Ubuntu 18.04LTS is broken since Ubuntu 18 released. The bugs
> were identified and fixed by this team on around march of 2018, but the way
> the features freeze on Ubuntu, it remains broken. trying to update only the
> sword
Greg,
Diatheke on Ubuntu 18.04LTS is broken since Ubuntu 18 released. The bugs
were identified and fixed by this team on around march of 2018, but the way
the features freeze on Ubuntu, it remains broken. trying to update only the
sword package without updating the core is locked by dependencies.
On Tue, Mar 10, 2020 at 5:27 PM Philip White
wrote:
> Thanks for the responses. I will consider using the Sword library. One
> reason I am reluctant to do so is my preference for C over C++.
>
There is a C file in the bindings that allows you to access the library
through C instead of C++. You c
Beyond the specific request for OSIS version of KJV w strongs, I use
diatheke on the Linux command line, although I had to build a virtual
session with Ubuntu19.04 because ubuntu 18.04 was shipped with a sword
engine that contains bugs.. If you're seeing the doubled last verse from
diatheke, just u
Thanks for the responses. I will consider using the Sword library. One
reason I am reluctant to do so is my preference for C over C++.
Another is my preference for building software on top of standards
instead of ad-hoc knowledge.
> This is the beauty of the Sword library. It hides all the rest of
There are a lot of places to get scripture in free formats. OSIS supported
by the Sword project is very old, and not many places still provide it.
I suggest you start at ebible.org,
https://ebible.org/download.php
which provides the KJV with strongs in OSIS among other formats.
https://ebible.or
On Tue, Mar 10, 2020 at 4:08 PM Philip White
wrote:
> Hi,
>
> I'm interested in building a linux command line module viewer. From
> the wiki and the FAQ, it seems that the only way to work with the
> modules available from the website is to use the SWORD library. If the
> raw OSIS files were avai
We strongly discourage this. The import and export is not leading to the same result. The export is lossy. PeterSent from my mobile. Please forgive shortness, typos and weird autocorrects. Original Message Subject: [sword-devel] How to access raw OSIS filesFrom: Philip White To: swo
Hi,
I'd stick trying to leverage on sword libraries instead of reinventing the
wheel. Or do you have any constrains?
Have you seen pysword? It seems to be a fairly obvious choice.
Kind regards,
Kristof
On Tue, Mar 10, 2020 at 10:09 PM Philip White
wrote:
> Hi,
>
> I'm interested in building a
Hi,
I'm interested in building a linux command line module viewer. From
the wiki and the FAQ, it seems that the only way to work with the
modules available from the website is to use the SWORD library. If the
raw OSIS files were available, then I think I could write a
low-dependency piece of softw
13 matches
Mail list logo
