<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">From memory:<br><div><div>On Jun 10, 2013, at 5:02 PM, Chris Burrell <<a href="mailto:chris@burrell.me.uk">chris@burrell.me.uk</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi<div><br></div><div style="">I'm getting the following two types of reports in the logs, but I'm unsure what it means. </div><div style="">This happens a lot, and not just this module/verse combination.</div>
<div style=""><br></div><div style=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><ul style=""><li style="">INFO - FreLSG:Act 25:1: No content to attach word to: <WG3767>.</li></ul></blockquote></div></div></blockquote><div><br></div>This is a GBF module. The <WGxxxx> marker is used to attach the Greek Strong's Number to what immediately preceded it. In OSIS, <w lemma="G3767">word</w> surrounds the word it tags. This warning means that the Strong's number won't be attached to anything. It may be an error in the module or a bug in JSword.</div><div><br></div><div><br><blockquote type="cite"><div dir="ltr"><div style=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><ul style="">
</ul><ul style=""><li style="">ERROR - Attempt to read beyond end. offset=0 size=12 but raf.length=0</li></ul></blockquote></div></div></blockquote><div><br></div>I haven't seen these for a while. This indicates that there is a logic problem in JSword when it gets a reference from an indx file to do a read in the dat file. If the size is 12 the length should be >= that.</div><div><br></div><div><br><blockquote type="cite"><div dir="ltr"><div style=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><ul style=""><li style="">INFO - FarsiOPV:Psa 34:0: Parse FarsiOPV(Psa 34:0) failed: Error on line 1: XML document structures must start and end within the same entity.</li></ul></blockquote></div></div></blockquote><div><br></div>Not sure. I'd have to look. Basically, JSword requires that a verse (even verse 0) be a complete valid XML fragment. We surround each verse with <div>...</div> before parsing it so that it is a single element.</div><div><br><blockquote type="cite"><div dir="ltr"><div style=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><ul style="">
</ul><ul style=""><li style="">INFO - TSK:Rev 3:4: scripRef has no passage attribute, unable to guess: (11:13; *Gr:) due to Cannot understand Gr as a chapter or verse.</li></ul></blockquote></div></div></blockquote>This is from a THML module. In ThML a scripRef element does not have to have a passage attribute. It should but it does not have to. (The value of such is that the reference can be clear) So JSword takes the text content of the element and tries to parse it. When it cannot parse it, this is the message that is given. It really is an indication that the module needs to be updated.</div><div><br><blockquote type="cite"><div dir="ltr"><div style=""><div style=""><br>
</div><div style="">(Unfortunately, I don't have a module for this - as I'm looking at the logs retrospectively).</div><div><br></div></div><div style="">What is a our log level policy? I usually have INFO for my own stuff and libraries close-to-home, and WARN for third party. JSword at the moment falls into INFO. What do others have it set to?</div></div></blockquote><div><br></div>It has been rather haphazard. During development and testing it is good to see more information provided it is not overwhelming. On occasion, I get all modules and use ReadEverything to find what JSword complains about. I recently did this to find repeated common problems that can easily be fixed.</div><div><br></div><div><br><blockquote type="cite"><div dir="ltr">
<div style=""><br></div><div style="">I'm thinking some of those "INFO" should really be WARN or ERROR. </div></div></blockquote><div><br></div>Probably. Feel free to change them. Just realize that making something more severe means that it is more likely to show.</div><div><br></div><div><br><blockquote type="cite"><div dir="ltr"><div style=""><br></div><div style="">Chris</div><div style=""><br></div></div>
_______________________________________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>http://www.crosswire.org/mailman/listinfo/jsword-devel<br></blockquote></div><br></body></html>