On Sun Feb 18, 2024 at 8:51 PM CET, Matěj Cepl wrote:
> It seems there was something on Sourceforge
> (https://sourceforge.net/p/sword/cvs/), but it is most likely
> gone.
Just for the record, the Sourceforge repo is more recent than SVN
(https://git.cepl.eu/cgit/sword/sword-sf-cvs/).
Best,
That's a debate that goes far beyond the scope of the current discussion,
but to be honest I don't understand why USX even exists ^^'
USFM favours easy editing of the files with its simple text tags.
It makes perfect sense for editing bibles, in particular in translation
software.
OSIS favours
Just to add a little to Michael Johnson's comments below, OSIS can
include significantly more metadata than USX specifies (which is little
more than the book code -- not even whether it's an original text
(Heb/Greek) or what language translation it is). OSIS can specify many
other things like
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
Thank you, Michael, for the pointer to Jonathan Robie's paper on
Scriptural markup in the Bible translation community. I think it
diplomatically states why USX won out over OSIS as the primary and
best-supported XML standard for representing Scripture.
I really don't expect USFM or USX to go
Robert's point about also standardizing Scripture metadata with the
ScriptureBurrito standard is a good one.
USX's limitations relative to OSIS are both an advantage and a
disadvantage. Because USX is more focused on primarily Scriptures, it
has the advantage that the markup is less ambiguous
Dear Arnaud and others,
Peter has done a good job summarizing.
Yes, last year we had a discussion on the CrossWire and git topic and you can
see the discussion in the mail archives here.
https://crosswire.org/pipermail/sword-devel/2023-March/subject.html
Some progress has been made.
Hi Peter and Troy, and thanks for the welcome !
Thanks Peter for the historical context, it does explain where things come
from.
I do have a lot of things to answer though :-)
The SVN site for libsword is the current, not old. It is just that very
> little changes over long stretches.
Indeed,
Another active project based on a different fork of JSword is STEP Bible.
https://stepbible.org/
I’m not directly involved in it, but I thought this to be significant enough to
draw to your attention.
Best regards,
David
On Sun, Feb 18, 2024 at 17:56, Arnaud Vié
Re: Lack of momentum for OSIS.
OSIS as described on wikipedia is owned by a committee including United
Bible Societies, SIL International, and the Society of Biblical
Literature.
However, this team got together and created the version that is available,
then almost completely ignored it, and
Le 18/02/2024 à 20:42, Michael H a écrit :
Re: Lack of momentum for OSIS.
OSIS as described on wikipedia is owned by a committee including
United Bible Societies, SIL International, and the Society of Biblical
Literature.
However, this team got together and created the version that is
On Sun Feb 18, 2024 at 8:57 AM CET, Peter von Kaehne wrote:
> The SVN site for libsword is the current, not old. It is just
> that very little changes over long stretches. Libsword is 30
Is it? The oldest revision in SVN I can find
(https://git.cepl.eu/cgit/sword/commit/?id=44ffa2f5aa5f)) is from
And one more point for the primary, original mission that Arnaud Vié
mentioned. I wrote earlier about an "unspecified versification system" in
Paratext, but did not link to anything.
https://drive.google.com/drive/folders/1aR3BOGKnTJREB0bTeYEukzdcBncACwWb?usp=sharing
Here are my collection of
And, It appears "unspecified" is no longer true for the .vrs files.
https://github.com/Copenhagen-Alliance/versification-specification
I don't think it's pulled back into Paratext yet, but this is an actual
"spec" to look at to understand the USFM ... not USFM, but
Paratext/UBS/SIL/Bible
And it's important to note that the Copenhagen-Alliance Versification
Specification working group committee includes David Instone-Brewer of
Tyndale House, producers of STEP Bible, which is build on Jsword, and
mentioned elsewhere in this thread.
On Sun, Feb 18, 2024 at 2:41 PM Michael H
15 matches
Mail list logo
