Thanks Peter for the answer !
About half of the conf file entries are derived from the module and we have
> tools to automatise this , but conversely the other half is not. FWIW, the
> derived part is mostly that which is needed to function , while the not
> automatic one is needed to inform the
Hi all,
Has anyone given any thought to simplifying the import of OSIS documents in
sword ?
With my bible-scraper, I'm giving users a way to easily generate OSIS
documents.
The next step is to allow them to easily import the resulting document in
sword... But the current process is quite painful
sswire-bible-society/bible-scraper
>
> Le 02/06/2024 à 11:46, Arnaud Vié a écrit :
>
> Thank you both for your interest !
>
> > What about commentary?
> > https://www.awmi.net/reading/online-bible-commentary/
>
> Not yet, I'm really focusing on bibles for th
.)
Feel free to test it : after checking out and building the repository, you
should just need to run for example:
> ./run.sh scrape -s GenericHtml -i KralickaWikisource -b Ps -c 1 -w USFM
Cheers,
Arnaud
Le dim. 2 juin 2024 à 08:50, Matěj Cepl a écrit :
> On Sun Jun 2, 2024 at 1:09 AM CEST
Hello all,
Cyrille already teased it in some of his previous mails on this list, but
I've been working for several months on a tool to scrape bibles from any
web page into a standard format (OSIS and USFM outputs are supported) : the
Bible Scraper.
It mostly serves two purposes :
- *Help
stem? Did we do a bad job with the first two? Can we not
> follow our principles and create a superset between 2 or more of these?
> And of course, these are not proper responses.
>
> So, if anyone is prayfully willing to take up this pumpkin-- to put in the
> time necessary to researc
it's very easy for these bibles to just reuse KJVA with one small mapping
for the only difference.
And that's all for today, I think that description is long enough already !
Let me know your thoughts !
If we have a consensus on these principles, we can then start working on
defining an actua
east an OSIS 2.2 spec
> that is owned by a successor organization instead of organizations that
> effectively abandoned it. That's the missing link which would provide a
> mechanism to actually make changes to the standard. People (including me)
> keep doing this search and l
Thanks Michael for all this information !
I was not aware of this Copenhagen Alliance's work - I just had a quick
look at the repository you linked, and it seems to cover a significant part
of the requirements I wanted to cover with my proposal, but not all.
I like the format, and the fact that it
velopment.
>>
>> The GitLab site was created by some of us who create modules for texts
>> which are in the public domain but have little other exposure
>>
>> OSIS - crosswire is the principal user, but as it stands it is an
>> international standard, and not und
t; GitHub project, and see if they would be willing to let me take
over jsword to refresh it :-)
Le sam. 17 févr. 2024 à 21:12, Matěj Cepl a écrit :
> On Sat Feb 17, 2024 at 4:46 PM CET, Arnaud Vié wrote:
> > I think a lot of that could be improved by making better use of the
> >
!
And whoever is currently admin of the github project, would you be willing
to grant me some permissions on the jsword repo and a new "osis-spec" repo
to start setting up all of this ?
Regards,
Arnaud Vié
___
sword-devel mailing list: sword-devel@c
Hello everyone,
I'm the person Cyrille mentioned, and I just joined the mailing list as I
thought I could maybe explain a bit more what I'm trying to do with this
new versification.
*1. Problem statement*
Simply put, my objective is to be able to align verse-by-verse the contents
of two bibles
13 matches
Mail list logo
