Tom wrote:
>I think that is a broad "all-seeing" and "all-knowing" thing for you to say.
It is broad. It also is based on my experience hunting for STEP modules.
> I personally know of one retired Pastor in Texas that is still composing
> modules in Texas
... and he is still offering CD's with
On Wed, 8 Mar 2006, Jonathon Blake wrote:
_CROSS_ might be in wider usage than OSIS. [At least, none of the
commercial vendors brag about using OSIS. They do brag about using
CROSS.]
Um. No, commercial vendors don't brag about using CROSS, the commercial
vendor that owns CROSS does. CROSS
They are OLB verbal morphology codes, I believe. I think the "T" stands
for tense, and may be a relic of GBF encoding of this data. We should
probably create a new morphology code system and convert these codes to
that. But for the moment, preserve them at least.
They should map into the old
On Tue, 7 Mar 2006, DM Smith wrote:
Here is a summary of the changes:
2) replace (not allowed under OSIS) with
Not sure, but these might be paragraph milestones (similar to type="x-p"/>). They shouldn't be pagebreaks. (But maybe that was a typo
and supposed to be .
3) On elements, replac
On Tue, 7 Mar 2006, DM Smith wrote:
At the end of many verses there is a . It only occurs
in the OT and in every OT book.
What is this?
It's a paragraph "milestone". To correct, the marker should be converted
to (Every KJV chapter begins a new chapter. So conversion
should be as easy
On Tue, 7 Mar 2006, Kahunapule Michael Johnson wrote:
Chris Little wrote:
GBF is a proprietary format and non-XML.
GBF is not proprietary, at least not as I understand the word. It is
non-XML. It is openly published, freely usable, and one of the first
formats supported by The Sword Project. I
Jonathon Blake wrote:
On 3/5/06, Kahunapule Michael Johnson <[EMAIL PROTECTED]> wrote:
The future is hard to predict. Currently, OSIS (or rather a subset of OSIS) is used by The Sword Project as one option for Scripture text import.
There also is a utility program that
Yep, is ThML (probably what was being copied for this tag). Mea
culpa.
--Chris
On Tue, 7 Mar 2006, DM Smith wrote:
The element is actual and the milestone has been
there for a long time.
___
sword-devel mailing list: sword-devel@crosswire.org
h
Brother Jonathan:
I think that is a broad "all-seeing" and "all-knowing" thing for you to
say. I personally know of one retired Pastor in Texas that is still
composing modules in Texas ... and he is still offering CD's with STEP
modules! And I don't claim to know that there are no more out t
On 3/5/06, Kahunapule Michael Johnson <[EMAIL PROTECTED]> wrote:
> The future is hard to predict. Currently, OSIS (or rather a subset of OSIS)
> is used by The Sword Project as one option for Scripture text import.
There also is a utility program that converts OSIS input to e-Sword,
or Pocket e-
[EMAIL PROTECTED] wrote:
> At the end of many verses there is a . It only
> occurs in the OT and in every OT book.
Various versions of the Hebrew Bible use the Hebrew letter "pe" to
indicate a blank column in the original manuscript. This would
indicate a "section break".
Thanks David,
I ne
In the KJV OT I find the following type of morphology.
Does anyone know what this indexes into?
morph="strongMorph:TH8804
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsub
I have made an alpha module for kjv2006. You can obtain it at
www.crosswire.org/~dmsmith/kjv2006/kjv2006.zip
This module will not overwrite your current kjv as it is called kjv2006.
I have tested it in "SWORD for Windows" versions 1.5.6 and 1.5.8 and
also in BibleDesktop.
It does not work prope
> At the end of many verses there is a . It
only > occurs in the OT and in every OT book.Various versions of
the Hebrew Bible use the Hebrew letter "pe" to indicate a blank column in the
original manuscript. This would indicate a "section break".
Peace,David
__
I thought I'd let everyone know where the KJV2006 project stands. So far
it has been a solo effort. Not that I don't want help, but that it has
all been prep work so far.
I have dumped the KJV2003 by books into
www.crosswire.org/svn/modules/KJV/trunk/text
and have created a tag for it at
At the end of many verses there is a . It only
occurs in the OT and in every OT book.
What is this?
I was thinking that it might be the pilcrow, ¶, that comes at the
beginning of many verses, but that can't be it because it is at the end.
The reason I ask is that OSIS now defines a larger se
Don't know who lurks on sword-support, but I found this to be interesting.
Maybe some here can respond to Helmut?
Original Message
Subject:[sword-support] Wrong Luther-Version?
Date: Tue, 7 Mar 2006 07:29:02 +0100
From: Helmut Weidner-Kim <[EMAIL PROTECTED]>
Reply-To
Chris Little wrote:
> To make a long story short, OSIS is the best format for everything
> that Sword needs to do. It encodes Bibles richly and explicitly. It
> can contain every other type of book we handle (though none of these
> require the same level of richness in markup). And it's open and it
L.Allan-pbio wrote:
Please, any of you that have the time, read the manual and provide
revisions and comments. As they are actively working on OSIS 2.5, now
is a good time.
Based on your reading, would the upgraded osis spec be usable to
prepare a module that could be used to generate a print
The element is actual and the milestone has
been there for a long time.
Chris Little wrote:
L.Allan-pbio wrote:
Please, any of you that have the time, read the manual and provide
revisions and comments. As they are actively working on OSIS 2.5,
now is a good time.
Based on your reading,
L.Allan-pbio wrote:
Please, any of you that have the time, read the manual and provide
revisions and comments. As they are actively working on OSIS 2.5, now
is a good time.
Based on your reading, would the upgraded osis spec be usable to prepare
a module that could be used to generate a prin
To make a long story short, OSIS is the best format for everything that
Sword needs to do. It encodes Bibles richly and explicitly. It can
contain every other type of book we handle (though none of these require
the same level of richness in markup). And it's open and it's XML. And
if there are
DM Smith wrote:
Chris Little wrote:
OSIS is already being used in CrossWire's KJV in ways other than what
was intended. The lemma and morph attributes indicate the lemma and
morphology of their content, but the CrossWire KJV uses them to
indicate the lemma and morphology of words in a complete
DM Smith wrote:
Chris Little wrote:
DM Smith wrote:
The following construct if fairly frequent:
and took
him by the throat
The problem is that does not allow for .
Should this be changed to subType="added">him?
(This is the form that is used within study notes.)
If the markup is correct,
24 matches
Mail list logo
