Re: [sword-devel] Error reading ulCompOffset

2018-02-22 Thread ref...@gmx.net
<<< text/html; charset=utf-8: Unrecognized >>> ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Error reading ulCompOffset

2018-02-22 Thread Timothy Shen-McCullough
..@gmx.net> <mailto:ref...@gmx.net >><mailto:ref...@gmx.net>>> wrote: >> So the module you are working on, is, despite the same >>name as >> the last one not a copyrighted translation of the Dead Sea >> scrolls? T

Re: [sword-devel] Error reading ulCompOffset

2018-02-21 Thread ref...@gmx.net
t a few times, it has always been a fault in the OSIS. The >>>    error message cod be more helpful, granted. >>>    It is too long ago to remember what it was the last time, and with >>>    the nature of your modules I have little desire to think further. >>> >>>    Sent from my

Re: [sword-devel] Error reading ulCompOffset

2018-02-20 Thread DM Smith
19, 2018, at 9:43 AM, Andrew T. > >> <mailto:thules...@gmail.com>> wrote: >> >>> Thank you for your insight. It is appreciated. I'll scrutinize the XML >> >>> more closely (again). I find general many of the XML validation tools

Re: [sword-devel] Error reading ulCompOffset

2018-02-20 Thread Tom Sullivan
as then. >>> >>>    Wrt the technical side, it is the result of a faulty OSIS. I have >>>    seen it a few times, it has always been a fault in the OSIS. The >>>    error message cod be more helpful, granted. >>>    I

Re: [sword-devel] Error reading ulCompOffset

2018-02-20 Thread Andrew T.
ailto:ref...@gmx.net> > mailto:ref...@gmx.net>> wrote: > >>> > >>>Thanks for confirming that you are of the same spirit as then. > >>> > >>>Wrt the technical side, it is the result of a faulty OSIS. I have > >>>seen i

Re: [sword-devel] Error reading ulCompOffset

2018-02-19 Thread DM Smith
of the same spirit as then. >>> >>>Wrt the technical side, it is the result of a faulty OSIS. I have >>>seen it a few times, it has always been a fault in the OSIS. The >>>error message cod be more helpful, granted. >>>It is too long ago

Re: [sword-devel] Error reading ulCompOffset

2018-02-19 Thread Tom Sullivan
it was the last time, and with the nature of your modules I have little desire to think further. Sent from my mobile. Please forgive shortness, typos and weird autocorrects. Original Message ---- Subject: Re: [sword-devel] Error reading ulCompOffset Fro

Re: [sword-devel] Error reading ulCompOffset

2018-02-19 Thread DM Smith
e >> more helpful, granted. >> It is too long ago to remember what it was the last time, and with the >> nature of your modules I have little desire to think further. >> >> Sent from my mobile. Please forgive shortness, typos and weird autocorrects. >> >>

Re: [sword-devel] Error reading ulCompOffset

2018-02-19 Thread Tom Sullivan
my mobile. Please forgive shortness, typos and weird autocorrects. ---- Original Message ---- Subject: Re: [sword-devel] Error reading ulCompOffset From: "Andrew T." To: SWORD Developers' Collaboration Forum CC:    

Re: [sword-devel] Error reading ulCompOffset

2018-02-19 Thread Andrew T.
ttle desire to think further. >> >> Sent from my mobile. Please forgive shortness, typos and weird >> autocorrects. >> >> >> Original Message >> Subject: Re: [sword-devel] Error reading ulCompOffset >> From: "Andrew T." >> To: S

Re: [sword-devel] Error reading ulCompOffset

2018-02-19 Thread Andrew T.
last time, and with the > nature of your modules I have little desire to think further. > > Sent from my mobile. Please forgive shortness, typos and weird > autocorrects. > > > -------- Original Message ---- > Subject: Re: [sword-devel] Error reading ulCompOf

Re: [sword-devel] Error reading ulCompOffset

2018-02-19 Thread Tom Sullivan
doubt you showed yourself as someone who chooses to ignore copyright rules. Peter Sent from my mobile. Please forgive shortness, typos and weird autocorrects. ---- Original Message Subject: Re: [sword-devel] Error reading ulCompOffset Fr

Re: [sword-devel] Error reading ulCompOffset

2018-02-18 Thread ref...@gmx.net
Thanks for confirming that you are of the same spirit as then. Wrt the technical side, it is the result of a faulty OSIS. I have seen it a few times, it has always been a fault in the OSIS. The error message cod be more helpful, granted. It is too long ago to remember what it was the last time, and

Re: [sword-devel] Error reading ulCompOffset

2018-02-18 Thread Andrew T.
terial discusses then is without doubt copyrighted and > without doubt you showed yourself as someone who chooses to ignore > copyright rules. > > Peter > > Sent from my mobile. Please forgive shortness, typos and weird > autocorrects. > > > ---- Original Message -

Re: [sword-devel] Error reading ulCompOffset

2018-02-18 Thread ref...@gmx.net
So the module you are working on, is, despite the same name as the last one not a copyrighted translation of the Dead Sea scrolls? There was no controversy, the material discusses then is without doubt copyrighted and without doubt you showed yourself as someone who chooses to ignore copyright rule

Re: [sword-devel] Error reading ulCompOffset

2018-02-18 Thread Andrew T.
on this > matter, the reference is not really applicable. > > So I am asking again, have you changed your attitudes since we saw you > last time? > > Thanks > > Peter > > Sent from my mobile. Please forgive shortness, typos and weird > autocorrects. > > >

Re: [sword-devel] Error reading ulCompOffset

2018-02-18 Thread ref...@gmx.net
Thanks for the reminder, but given that this is not a matter of forgiveness but of respect for copyright and our project's views on this matter, the reference is not really applicable. So I am asking again, have you changed your attitudes since we saw you last time? ThanksPeterSent from my mobile.

Re: [sword-devel] Error reading ulCompOffset

2018-02-18 Thread Troy A. Griffitts
Andrew, I am still not clear what problem you are experiencing. Can you let us know: What OS? Are you using svn trunk or something else? Do you have a very concise OSIS snippet which doesn't get parsed correctly into a module? What exactly command line produces the unexpected behavior? Thanks for

Re: [sword-devel] Error reading ulCompOffset

2018-02-18 Thread DM Smith
Couple of things to try: Don’t compress. The resulting data file is then readable. If the module is complete, then compression has the problem. Use -d 2 to add verse marks. Makes an uncompressed module’s data file more meaningful. DM > On Feb 18, 2018, at 1:54 PM, Andrew T. wrote: > > Yes,

Re: [sword-devel] Error reading ulCompOffset

2018-02-18 Thread Andrew T.
Yes, I'm missing content for sure, but I've been able to parse incomplete osis before which was missing content (it's never seemed to mind before). (I've also been able to parse osis where the verses|chapters|books are out of order - which is not true in this case). I saw this thread which also se

Re: [sword-devel] Error reading ulCompOffset

2018-02-18 Thread DM Smith
I’ve seen the error before. I’ve even tried to debug osis2mod to find it. To no avail. I never saw that they hindered the proper operation of osis2mod. Were you saying that the built module is missing expected content? DM > On Feb 17, 2018, at 11:14 PM, Andrew T. wrote: > > I'm currently usin

Re: [sword-devel] Error reading ulCompOffset

2018-02-18 Thread Andrew T.
Peter, I asked a question about an error message. Your response deflected to me. Is this your way of illustrating Matt 18:22? Do you know what the error message means or no? ~A On Sun, Feb 18, 2018 at 1:50 AM, ref...@gmx.net wrote: > Has anything changed in your attitude since we saw you las

Re: [sword-devel] Error reading ulCompOffset

2018-02-17 Thread ref...@gmx.net
Has anything changed in your attitude since we saw you last time here?PeterSent from my mobile. Please forgive shortness, typos and weird autocorrects. Original Message Subject: [sword-devel] Error reading ulCompOffsetFrom: "Andrew T." To: SWORD Developers' Collaboration Forum CC: I