Chris Little писал(а) в своём письме Mon, 13 Aug
2012 21:48:38 +0400:
The other type attempts to formalize a versification system
representative of numerous Bibles within a tradition. Examples of this
include the KJV(A), NRSV(A), Synodal, Catholic, & Catholic2. KJV(A) &
NRSV(A) happen to
The ulbufnum error/warning has appeared for years. As you pointed out, it is
deep in SWORD lib. Always looked benign w/in osis2mod. Probably should be
looked into and fixed.
In Him,
DM
On Aug 16, 2012, at 9:24 AM, Andrew Thule wrote:
> Yes. Using debug produces little of value but I
Yes. Using debug produces little of value but I will run further test in
verbose mode later today and produce output. That said, I've sen the same
errors produced by working modules, that keep working, so I'm less sure now
than earlier those errors are related.
~ A
On Thursday, August 16, 2012,
Andrew,
Some sanity checks before further work by others on the list
Are you using *osis2mod* to make a compressed module (ztext) or a raw text
module?
Do you get the same error message for both?
Have you tried any of the debug options?
David
--
View this message in context:
http://sw
Chris.
I threw the canon_lxxe.h file in ./src/sword/include/
Edited ./src/sword/src/mgr/versemgr.cpp
Added:
#include // LXXE v11n system
and;
systemVerseMgr->registerVersificationSystem("LXXE", otbooks_lxxe,
ntbooks, vm_lxxe);
recompiled and voila!
-v specify a versifi
On 08/13/2012 07:48 AM, Chris Little wrote:
> Because we don't do dynamic loading of versification systems, whenever we add
> a versification system to Sword, it takes up space in memory just to hold the
> versification tables. Accordingly, we try to be as conservative as possible
> in adding ne
On 08/13/2012 12:10 PM, Andrew Thule wrote:
Actually this whole business raises another issue. In the collection
of modules I've been building up, I've added Dead Sea Scrolls texts as
OSIS (but have not yet created modules for them, pending working
though versification issues).
For biblical scr
On 08/13/2012 11:43 AM, Andrew Thule wrote:
Greg wrote: "If the one you need isn't supported (I don't see LXX or
GNT at present) then you're welcome to create such a file and submit
it along with your module."
I must have mistook your earlier comments as well.. I implicitly took
them to mean yo
Actually this whole business raises another issue. In the collection
of modules I've been building up, I've added Dead Sea Scrolls texts as
OSIS (but have not yet created modules for them, pending working
though versification issues).
For biblical scrolls, versification isn't so much an issue, si
On Mon, Aug 13, 2012 at 1:48 PM, Chris Little wrote:
> Because we don't do dynamic loading of versification systems, whenever we
> add a versification system to Sword, it takes up space in memory just to
> hold the versification tables. Accordingly, we try to be as conservative as
> possible in ad
That certainly explains the apparent disorder - thanks for that.
On Mon, Aug 13, 2012 at 12:11 PM, Chris Little wrote:
> On 08/12/2012 11:23 PM, Andrew Thule wrote:
>>
>> I was making changes to the LXX2012 version - but then quit. I
>> decided to instead work on getting out a version with origi
Because we don't do dynamic loading of versification systems, whenever
we add a versification system to Sword, it takes up space in memory just
to hold the versification tables. Accordingly, we try to be as
conservative as possible in adding new versification systems. And once
we have released
On 08/12/2012 11:23 PM, Andrew Thule wrote:
I was making changes to the LXX2012 version - but then quit. I
decided to instead work on getting out a version with original text.
I've created a versification system based upon an 1857 edition of
Brenton's book (and consulted 2 other versions, includ
Thanks Chris.
Here's an English Septuagint versification system, based upon the text
I got from Michael and compared to a number of printed version. The
Chapter order doesn't quite follow the KJV or NSRV convention, but it
does follow the Septuagints order.
I appreciate it if you could add this
I was making changes to the LXX2012 version - but then quit. I
decided to instead work on getting out a version with original text.
I've created a versification system based upon an 1857 edition of
Brenton's book (and consulted 2 other versions, including a 1900
edition). The versification doesn'
I just implemented a lot of spelling
corrections for the LXX2012 (thanks to David Haslam), so you might
want to grab a fresh copy tomorrow.
On 08/10/2012 03:40 AM, Andrew Thule wrote:
Hmm, 'basons' was in my text too, so perhaps it was an
antiquate
On 08/09/2012 05:38 PM, Andrew Thule
wrote:
Michael, thanks very much. I've spell corrected the
following words:
kindreds to kindred
basons to basin
dulness to dullness.
I'm not sure which text you are using, the original Brenton or t
Too few people involved in legacy scripture preservation are aware of
Tesseract.
They struggle on using the OCR software that came bundled with their
scanner.
The results are far more error laden than they might be had they known
otherwise.
An army of touch typists would do better.
One of my TextP
It's a word, Andrew, as you can readily learn from
http://en.wikipedia.org/wiki/Lictor
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Alternate-Versification-question-tp4650784p4650803.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
_
Indeed, and I thought Eton was exclusive!
Does the next verse contain one too "and the lictors told..." or was
lictors a word?
~A
On Friday, August 10, 2012, David Haslam wrote:
> For the most amusing howler caused by an OCR error, install the Anderson
> (NT)
> module and read Acts 16:37
>
> btw
Hmm, 'basons' was in my text too, so perhaps it was an antiquated word
chosen by Brenton. Regardless, I'm working with your LXX2012 text, which
has already had some of the more archaic language improved, so will stick
with the change.
~A
On Thursday, August 9, 2012, Andrew Thule wrote:
> Michae
Yes from the CLI (initial training is painful - though skillful Internet
searches can often get you training files for particular fonts that are
close). I tried using Qtesseract, but the compilation was somewhat
problematic, and felt the time investment (to get the thing to work) was
little worth
Andrew,
Are you using Tesseract from the command line, or did you also install a
http://en.wikipedia.org/wiki/Tesseract_%28software%29#User_interfaces GUI
for Tesseract ?
If so, which? and any comments worth sharing?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.co
For the most amusing howler caused by an OCR error, install the Anderson (NT)
module and read Acts 16:37
btw. If you're British, you'll find this even more amusing than the rest of
you.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Alternate-Versification-quest
Michael, thanks very much. I've spell corrected the following words:
kindreds to kindred
basons to basin
dulness to dullness.
Otherwise the text looks very good.
I've turned it into a sword module, and will keep working on improvements,
including comparing it to the text I had. Let me know and I
Yes, please do feel free to use the
text I have posted on eBible.org, if you like. If you find errors
in it, please let me know so that I can correct them. I have found
some by comparing a couple of different sources, but there may
still be a few typos/OCR errors.
Now that I've seen Michael has place his text in the public domain, really
appreciate you pointing out these links.
This is going to make things go much quicker. Though I have already spent
some effort building source text, haven't pride enough to stop me from
using Michaels text instead, which
Thanks for the links. Yes LXXE is Brenton which I'm in the process of
throwing at Tesseract, albeit with some effort.
No I wasn't aware of Michael Johnson's efforts so should make some effort
to contact him. I appreciate your comments.
~A
On Thursday, August 9, 2012, David Haslam wrote:
> I
Yes I found that to be true (CCELs versification was, by the authors own
admission, error ridden). Regardless, with a bit of work was able to
create one that wasn't, which the CCEL one helped validate.
~A
On Thursday, August 9, 2012, Chris Little wrote:
> On 08/08/2012 07:05 PM, Andrew Thule wr
In addition to what others have said:
The list that osis2mod -h produces is not hard copy, but rather it asks the
SWORD library for the list. If osis2mod is statically compiled then the list is
fixed at compile time. Otherwise it is fixed with the build of the SWORD
library.
Either way, when y
I expect that LXXE does indeed mean the English Brenton.
If so, then Andrew should be made aware that Michael Johnson is working on a
modernized English LXX.
See these two links:
http://ebible.org/eng-Brenton/
http://ebible.org/eng-lxx2012/
David
--
View this message in context:
http://sw
On 08/08/2012 06:25 PM, Andrew Thule wrote:
However, this following page list others (such as LXX and GNT):
http://svn.crosswire.org/wiki/Alternate_Versification/System_Identification
Observe that this page is intended as an aid for figuring out which
versification is employed in a particular
On 08/08/2012 07:05 PM, Andrew Thule wrote:
Thanks Greg .. I've done that, and compared what comes with Sword to
what's listed here:
https://crosswire.org/svn/sword-tools/trunk/versification/basicv11ns/
The only difference, as far as I was able to tell was canon_gnt.h does
not appear to ship wit
I guess you're saying that's what essentially defines a versification
.. (I wasn't sure if there was more to it ..).
Thanks.
~A
On Wed, Aug 8, 2012 at 10:09 PM, Greg Hellings wrote:
> On Wed, Aug 8, 2012 at 9:05 PM, Andrew Thule wrote:
>> Thanks Greg .. I've done that, and compared what comes w
On Wed, Aug 8, 2012 at 9:05 PM, Andrew Thule wrote:
> Thanks Greg .. I've done that, and compared what comes with Sword to
> what's listed here:
> https://crosswire.org/svn/sword-tools/trunk/versification/basicv11ns/
>
> The only difference, as far as I was able to tell was canon_gnt.h does
> not
Thanks Greg .. I've done that, and compared what comes with Sword to
what's listed here:
https://crosswire.org/svn/sword-tools/trunk/versification/basicv11ns/
The only difference, as far as I was able to tell was canon_gnt.h does
not appear to ship with sword. I assume it was pruned or included
w
Some have been pruned in the past because they were either duplicates
or similar. It is also possible that some of the documentation is out
of date. The best way to know for sure is to look at the installed
header files, if you're on Linux, to see which ones are included. Each
versification is list
osis2mod -h lists the following versifications supported:
-v specify a versification scheme to use (default is KJV)
Note: The following are valid values for v11n:
Catholic
38 matches
Mail list logo
