Hi,
I would like to ask a question that I was planning to ask for a while
already ...
What's the recommended solution of mapping different versification systems?
And what working implementations for this are already out there?
I realize that my understanding of versifications has been a bit l
The reason I'm not just using markdown for everything is that all these
works have references. And it all comes down to how to handle those
references.
ThML scripture references include the attribute "scripRef" which describes
a specific work for the reference, but I'm not aware that ThML has anyt
On 5/5/20 1:36 PM, Michael H wrote:
> it's the only option listed for genbooks in the howto section
Obligatory "ThML for everything." :-/
I've never produced an OSIS module, but a quick check says I've produced
89 ThML modules. And there's some new ones I'm due to produce (BIBdraft
and BSBdraft
Greg,
OSIS is the best choice for genbooks. In fact, on the wiki (
wiki.crosswire.org) it's the only option listed for genbooks in the howto
section. I do understand that OSIS for scripture doesn't look like OSIS for
genbooks, and tools designed to convert scripture may not be well suited to
conv
I know Jeff Klassen of UBS ICAP.
We met in 2012 at the DB Summit.
David
Sent from ProtonMail Mobile
On Tue, May 5, 2020 at 05:33, Michael H wrote:
> The Short answer about the OSIS spec tho
>
> For now, I've been coding the PDF -> text -> USFM intending to ultimately
> convert it to either m
OSIS is no longer the only XML schema in common use for Scripture markup.
It seems to be the case that all the founder agencies connected with the DBL
more or less lost interest in OSIS with the advent of USX. I know for sure that
YouVersion uses USX for Bible import.
Apart from CrossWire, who
On Mon, May 4, 2020 at 1:07 PM Michael H wrote:
> I've got 40 works and growing that I've been meaning to look at creating
> Sword Modules. All of these are genbooks. Almost 100% currently are works
> by Andrew Murray (but the list is much bigger.)
>
> But, as I try to make sense of the OSIS spec
