On 03/02/2012 06:58 AM, Brian J Dumont wrote:
On 03/02/2012 09:13 AM, Greg Hellings wrote:
2012/3/2 Brian J Dumont:
Hi Matej,
The difference is that you compiled it as a compressed module. This
makes
the limit to be 64kb per section after it is zipped. If you triple the
contents of the th
On 03/02/2012 09:13 AM, Greg Hellings wrote:
2012/3/2 Brian J Dumont:
Hi Matej,
The difference is that you compiled it as a compressed module. This makes
the limit to be 64kb per section after it is zipped. If you triple the
contents of the then you'd have the same trouble.
I avoided using
2012/3/2 Brian J Dumont :
> Hi Matej,
>
> The difference is that you compiled it as a compressed module. This makes
> the limit to be 64kb per section after it is zipped. If you triple the
> contents of the then you'd have the same trouble.
>
> I avoided using a zipped module so that the issue w
Hi Matej,
The difference is that you compiled it as a compressed module. This
makes the limit to be 64kb per section after it is zipped. If you
triple the contents of the then you'd have the same trouble.
I avoided using a zipped module so that the issue wasn't confused, but
it also happe
On 2.3.2012 14:02, Brian J Dumont wrote:
I'm not compiling it into a compressed format. My command/output is:
[bjdasc@ascpc5] osis2mod mod debug.osis.xml
You are running osis2mod: $Rev: 2671 $
SUCCESS: osis2mod: has finished its work and will now rest
Interesting. Either it is in the version or
That would be super-keen DM. It would be nice if it also noted the need
for ModDrv "RawCom4" to go along with "-s 4"
Thanks,
Brian
On 03/02/2012 08:15 AM, DM Smith wrote:
I think osis2mod should detect the problem, output an error and a clear
suggestion to use -s 4.
Cent from my fone so the
On 03/02/2012 08:06 AM, Greg Hellings wrote:
On Fri, Mar 2, 2012 at 7:02 AM, Brian J Dumont wrote:
Hi all,
I've struggled with large commentaries before. It always seemed that once
commentary sections get too big, then random sections of text start
disappearing.
I'm currently almost done rep
I think osis2mod should detect the problem, output an error and a clear
suggestion to use -s 4.
Cent from my fone so theer mite be tipos. ;)
On Mar 2, 2012, at 8:06 AM, Greg Hellings wrote:
> On Fri, Mar 2, 2012 at 7:02 AM, Brian J Dumont
> wrote:
>> Hi all,
>>
>> I've struggled with large
>From memory -s 4 perhaps?
Cent from my fone so theer mite be tipos. ;)
On Mar 2, 2012, at 8:02 AM, Brian J Dumont wrote:
> Hi all,
>
> I've struggled with large commentaries before. It always seemed that once
> commentary sections get too big, then random sections of text start
> disappear
On Fri, Mar 2, 2012 at 7:02 AM, Brian J Dumont wrote:
> Hi all,
>
> I've struggled with large commentaries before. It always seemed that once
> commentary sections get too big, then random sections of text start
> disappearing.
>
> I'm currently almost done repackaging a part of the EarlyFathers
I just noticed that the last date in
http://crosswire.org/wiki/Osis2mod#History_of_Changes
was 2009-06-06.
When you've fixed all the bugs, and built a new release, someone with the
knowledge of changes since that date should update the table in the wiki
page.
David
--
View this message in contex
Today, Troy and I fixed some bugs in osis2mod that had resulted in the
program terminating early without warning when it encountered a verse
not in the selected versification.
I'm still trying to find the problem of a compressed text not being
complete. We looked at the code and it looks corre
FYI, the problem is a chapter number not in the chosen versification.
Finding a versification with the chapter or artificially changing the
chapter number to the last valid in the versification and changing the
verse numbers to larger than in the last chapter should work.
On 01/25/2010 07:18 P
On 01/25/2010 06:41 PM, Peter von Kaehne wrote:
DM Smith wrote:
This is the first that I've taken time to look at it.
Is there any update on it?
I have a module which appears to segfault at every single versification
I throw at it. While it might well require its own versififcation
e
DM Smith wrote:
> This is the first that I've taken time to look at it.
Is there any update on it?
I have a module which appears to segfault at every single versification
I throw at it. While it might well require its own versififcation
eventually I am at the moment not even able to test it.
Is
Yes, it is the same. Chris had reported even earlier that it segfaulted
on books that were not in the chosen canon.
This is the first that I've taken time to look at it.
-- DM
On 01/04/2010 11:58 AM, Manfred Bergmann wrote:
I'm having similar problems with osis2mod for quite a while which I r
I'm having similar problems with osis2mod for quite a while which I reported in
a mail to this list on 4th July 2009: "osis2mod segfault".
Is this the same issue that was discussed here lately?
Manfred
Am 04.01.2010 um 16:52 schrieb DM Smith:
> I took a quick look at the problem. Seems that
I took a quick look at the problem. Seems that osis2mod chokes on
chapter numbers that are not in the book.
(It works just fine if the chapter is valid but the verse number is not.
And I still cannot reproduce the bug where it chokes on a book not in
the versification.)
Here is the smallest va
On Tue, Dec 2, 2008 at 2:24 PM, DM Smith <[EMAIL PROTECTED]> wrote:
> I figured out a work around.
> On Dec 2, 2008, at 11:32 AM, DM Smith wrote:
>
>> I found the osis2mod bug and I need a bit of help. I guess I don't
>> understand the SWORD engine all that well:)
>>
>> In an OSIS document we might
I figured out a work around.
On Dec 2, 2008, at 11:32 AM, DM Smith wrote:
> I found the osis2mod bug and I need a bit of help. I guess I don't
> understand the SWORD engine all that well:)
>
> In an OSIS document we might have an osisID="John.2"
>
> When I do the following:
> VerseKey currentVerse
I found the osis2mod bug and I need a bit of help. I guess I don't
understand the SWORD engine all that well:)
In an OSIS document we might have an osisID="John.2"
When I do the following:
VerseKey currentVerse;
currentVerse.autoNormalize(0);
currentVerse.Headings(1);
currentVerse.Persist(1);
21 matches
Mail list logo
