Tom - thank you for your suggestion. I had been using linux command line tools and in windows notepad++. I had forgotten about jedit, but Ill look at that again. Many validator tools will tell you there's an error but not point out where it is. Is osisCore.2.1.1-cw-latest.xsd different from osisCore.2.1.1.xsd? I suppose Ill have to find it and compare.
As for being helpful - it is. At some point its easy to run out of ideas and every new idea is useful as it provides another place to look. ~A On Mon, Feb 19, 2018 at 4:18 AM, Tom Sullivan <i...@beforgiven.info> wrote: > Y'all: > > For future reference: I have found that JEdit, with the XML addon, using > the Sword xsd, osisCore.2.1.1-cw-latest.xsd, is able to pick up OSIS errors > and report on their exact location. This process does show some > discrepancies between OSIS.pdf documentation and what the schema will > actually accept. JEdit is s-l-o-w. Other software may be better. > > Whether that will help avoid the unhelpful message is another matter. > > Tom > > Tom Sullivan > i...@beforgiven.info > FAX: 815-301-2835 > --------------------- > Great News! > God created you, owns you and gave you commands to obey. > You have disobeyed God - as your conscience very well attests to you. > God's holiness and justice compel Him to punish you in Hell. > Jesus Christ became Man, was crucified, buried and rose from the dead > as a substitute for all who trust in Him, redeeming them from Hell. > If you repent (turn from your sin) and believe (trust) in Jesus Christ, > you will go to Heaven. Otherwise you will go to Hell. > Warning! Good works are a result, not cause, of saving trust. > More info is at www.esig.beforgiven.info > Do you believe this? Copy this signature into your email program > and use the Internet to spread the Great News every time you email. > > On 02/19/2018 02:16 AM, 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 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 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 >> From: "Andrew T." >> To: SWORD Developers' Collaboration Forum >> CC: >> >> >> You showed yourself to be ignorant of the 'Fair Use' clauses of >> European, American and Canadian copyright law; dogmatic; and a >> hypocrite trying to assert copyright privilege you don't possess. >> Further you've never bothered to look at the module I've worked on >> for 9 years, examine the credits it contains, or check with >> translators to see if you're fight was a fight they wanted to be >> fought on their behalf. >> >> You should learn to let sleeping dogs lay as you're pride is >> impairing your judgement. >> I assume you're trying to find fault because you have no technical >> insights into the error I'm asking about? >> >> ~A >> >> >> >> On Sun, Feb 18, 2018 at 5:32 PM, ref...@gmx.net >> <mailto:ref...@gmx.net> <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? 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 rules. >> >> Peter >> >> Sent from 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: >> >> >> Peter - thanks for the opportunity but I'm not going to >> re-open old controversies. >> >> ~A >> >> On Sun, Feb 18, 2018 at 3:23 PM, ref...@gmx.net >> <mailto:ref...@gmx.net> <ref...@gmx.net >> <mailto:ref...@gmx.net>> wrote: >> >> 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? >> >> Thanks >> >> Peter >> >> Sent from 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: >> >> >> 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 >> <mailto:ref...@gmx.net> <ref...@gmx.net >> <mailto:ref...@gmx.net>> wrote: >> >> Has anything changed in your attitude since we >> saw you last time here? >> >> Peter >> >> Sent from my mobile. Please forgive shortness, >> typos and weird autocorrects. >> >> >> -------- Original Message -------- >> Subject: [sword-devel] Error reading ulCompOffset >> From: "Andrew T." __ >> To: SWORD Developers' Collaboration Forum __ >> CC: >> >> >> I'm currently using the command: >> /usr/bin/osis2mod . /sword/dss/DSS.osis.xml >> -z -b 4 -v KJVA >> >> Yet all I'm getting are the following errors: >> Error reading ulCompOffset >> Error reading ulCompOffset >> Error reading ulCompOffset >> ... >> >> I've created sword modules before, yet I >> don't recognize this error. >> >> I created the osis.xml file, and I'm fairly >> confident it is structured correctly - yet >> there are fragments missing (as the source >> of the text I used to create this document >> is fragmentary and incomplete). For example >> there is no New Testament, no Esther, no >> Nehemiah ...) >> >> Can anyone provide insight as to what this >> error means? >> >> ~A >> >> >> _______________________________________________ >> sword-devel mailing list: >> sword-devel@crosswire.org >> <mailto:sword-devel@crosswire.org> >> http://www.crosswire.org/mailm >> an/listinfo/sword-devel >> <http://www.crosswire.org/mail >> man/listinfo/sword-devel> >> Instructions to unsubscribe/change your settings >> at above page >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel@crosswire.org >> <mailto:sword-devel@crosswire.org> >> http://www.crosswire.org/mailman/listinfo/sword-devel >> <http://www.crosswire.org/mailman/listinfo/sword-devel> >> Instructions to unsubscribe/change your settings at >> above page >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel@crosswire.org >> <mailto:sword-devel@crosswire.org> >> http://www.crosswire.org/mailman/listinfo/sword-devel >> <http://www.crosswire.org/mailman/listinfo/sword-devel> >> Instructions to unsubscribe/change your settings at above page >> >> >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> >> >> _______________________________________________ >> 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 >> >> > _______________________________________________ > 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 >
_______________________________________________ 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
