What is the proper markup for a Commentary in OSIS so that it can be
loaded as a Sword Module? As I looked at it, if I were to mark up a
commentary as an OSIS Bible with the content about a verse using the
and tags, and make the ModDrv=RawCom then it will work
just fine. The only trick is to
So I have a collection of files (based on vulgate and NRSV works) that will
become commentaries.
The first thing I'd like to address are the differences in the
versification, primarily (for the vulgate stuff) so that commentary about
Psalm 119 doesn't show up on 118 or 120.
The only place I see t
I'm working on a commentary in OSIS, and I have an issue. It seems to
be related to having more than one per . In this case, I have
two 's like so:
some content
some more content
Everything is fine up to and including the two . But afterwards,
there is no content in the commentary at all, and
er/archive/2005
- Original Message -
From: "DM Smith" <[EMAIL PROTECTED]>
To: "SWORD Developers' Collaboration Forum"
Sent: Tuesday, August 16, 2005 7:49 PM
Subject: [sword-devel] OSIS Commentary
> What is the proper markup for a Commentary in OSIS so tha
Given Sword's current architecture for commentaries, that would be the
best method of encoding them (for use in Sword). In reality,
commentaries are generally a bit more free-form, but to use them in
Sword you'll want to treat them as if they have the same structure as
Bibles, basically.
Ther
On Sun, Sep 22, 2019 at 2:08 PM Michael H wrote:
> So I have a collection of files (based on vulgate and NRSV works) that
> will become commentaries.
>
> The first thing I'd like to address are the differences in the
> versification, primarily (for the vulgate stuff) so that commentary about
> Ps
The text (https://git.door43.org/Door43-Catalog/en_tn) is not in currently
in a format supported by anything except unfoldingWord, (
https://door43.org/u/Door43-Catalog/en_tn/ff70a8adb2/) but it is in a
regular format. So the manual transform into a supported form is currently
planned to go direct
There is a command line argument for versification for the osis2mod module
compiler.
http://wiki.crosswire.org/Osis2mod
I don't think it looks at the OSIS file metadata to figure out what
versification to use. It gets it from the command line.
At least that is how I'm using it and it seems t
On Mon, Sep 23, 2019 at 12:27 PM Michael H wrote:
> The text (https://git.door43.org/Door43-Catalog/en_tn) is not in
> currently in a format supported by anything except unfoldingWord, (
> https://door43.org/u/Door43-Catalog/en_tn/ff70a8adb2/) but it is in a
> regular format. So the manual transf
hi all,
I'm trying to prepare an OSIS commentary module (just in the preliminary
stage really), and am having trouble with multi-verse content. In my
case, trouble means that I don't get any. I'm trying to follow the
wiki. This is my sample file:
--
Could it be that Diatheke does not understand linked verses. Can you
try another app to see if it is there?
On Jul 9, 2008, at 10:01 PM, Brian J. Dumont wrote:
hi all,
I'm trying to prepare an OSIS commentary module (just in the
preliminary stage really), and am having trouble with multi-v
Diatheke uses the API, which inherently understands linked verses. It's
not even possible for a Sword app to not return a value for a linked
verse if it exists because there's no difference from the data stored
for the primary verse.
Besides, I've seen the linking bug myself. I've got a couple
Hi Chris,
So what would you suggest that I do? I know we all have more ideas than
time, and I suspect that you also have quite a number of other things on
your plate. If you expect this fix to be in place in, say, less than 6
months, then I'd go ahead building my module. If you suspect that
I think DM is planning to do some other work on osis2mod, so we can hope
he spots this bug in the course of doing that. The bug could possibly be
in the library itself.
I would suggest building the module correctly the first time. Fixing
this bug /should/ be a priority. How soon a priority item
On Jul 11, 2008, at 11:45 AM, Chris Little wrote:
> I think DM is planning to do some other work on osis2mod, so we can
> hope
> he spots this bug in the course of doing that. The bug could
> possibly be
> in the library itself.
Chris,
I think we can use JSword to test if this is a library b
DM Smith wrote:
> I think we can use JSword to test if this is a library bug or a module
> bug. Can you point me to a module that exhibits the problem and a
> reference in that module?
>
> If it is a module bug, then it can be fixed in osis2mod.
>
> -- DM
Excellent idea. The mir_BL_1988 mo
Chris Little wrote:
> DM Smith wrote:
>
>> I think we can use JSword to test if this is a library bug or a module
>> bug. Can you point me to a module that exhibits the problem and a
>> reference in that module?
>>
>> If it is a module bug, then it can be fixed in osis2mod.
>>
>> -- DM
>>
Hi David Trotz .
(and the rest of the SwordReader team).
DM Smith wrote:
>> Linking Matthew 1:23 to Matthew 1:22
>> Linking Matthew 1:24 to Matthew 1:22
>> Linking Matthew 1:25 to Matthew 1:22
This reminds me that we need to add to the 'todo' list (if I haven't
added it already), the fact t
I am working on a personal commentary and have the following markup and
despite the paragraph tags ( ) the Sword Project frontend runs all the
text together. Am I doing something wrong or is this a bug?
http://www.bibletechnologies.net/2003/OSIS/namespace";
xmlns:xsi="http://www.w3.org/2001/XMLSc
19 matches
Mail list logo
