<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">It is not a problem of double spaces but that one or more spaces are used to separate multiple references.</div><div class=""><br class=""></div><div class="">Here is what the ThML documentation (<a href="http://www.ccel.org/ThML/ThML1.02.pdf" class="">http://www.ccel.org/ThML/ThML1.02.pdf</a>) says:</div><div class=""><blockquote type="cite" class="">
<div class="page" title="Page 5">
<div class="layoutArea">
<div class="column"><p class=""><span style="font-size: 11.000000pt; font-family: 'TimesNewRoman'" class="">The passage attribute is a list of scripture references separated by commas or semicolons. Each
reference may consist of a book name (or abbreviation), a chapter, and a verse. The chapter and verse are
separated by a semicolon or period. If two references are separated by a dash, all of the intermediary
verses are included as well. In the case of books with only one chapter, a reference consists of a book
name or abbreviation and a verse. Book names should be as they appear in the version in use or a unique
prefix of at least two letters of the name. Abbreviations that are not prefixes may also be accepted by
programs that process ThML documents.</span><span style="font-size: 7.000000pt; font-family: 'BookAntiqua'; vertical-align: 2.000000pt" class="">7 </span></p></div></div></div></blockquote></div><div class="">It requires semi-colon or commas between multiple references.</div><div class=""><br class=""></div><div class="">As you noted the place where it is encountering the problem is in JSword in o.c.j.book.filter.thml.ScripRefTag.</div><div class=""><br class=""></div><div class="">I don’t think it would be easy to change JSword to handle it.</div><div class=""><br class=""></div><div class="">JSword assumes that multiple references are able to be split into a list on designated separators. Then each reference is split on that which can be expected to separate parts of a reference. If the reference has too many parts then it doesn’t work.</div><div class=""><br class=""></div><div class="">If a tokenizer were used to return the tokens as a stream, a parser would be able to stop processing one reference when it saw enough and start the next reference.</div><div class=""><div class=""><br class=""></div><div class="">— DM</div><div class=""><br class=""></div><div class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Jan 8, 2015, at 4:45 PM, Martin Denham <<a href="mailto:mjdenham@gmail.com" class="">mjdenham@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Clarke commentary has many occurrences of ScripRef tags like the following from Gen 1:3 which Xiphos/Sword handles well but JSword fails:<div class=""><br class=""><div class=""><scripRef passage="2Sa 22:35 Job 20:24 Ps 18:34">2Sa 22:35 Job 20:24 Ps 18:34</scripRef><br class=""></div></div><div class=""><br class=""></div><div class="">JSword fails because the references are separated by 2 spaces rather than semi-colons or commas.</div><div class=""><br class=""></div><div class="">JSword ScripRefTag converts it into: <reference osisRef="2Sam Job-Ps">... .</div><div class=""><br class=""></div><div class="">If a semi-colon is added between each reference then JSword interprets the whole reference correctly.</div><div class=""><br class=""></div><div class="">Is this a problem that needs to be fixed in the module or in JSword? I thought initially it was a module problem but Xiphos/Sword handles the double-space-separator without problems.</div><div class=""><br class=""></div><div class="">I don't know if this same problem occurs in other thml commentaries.</div><div class=""><br class=""></div><div class="">Thanks</div><div class="">Martin</div></div>
_______________________________________________<br class="">jsword-devel mailing list<br class=""><a href="mailto:jsword-devel@crosswire.org" class="">jsword-devel@crosswire.org</a><br class="">http://www.crosswire.org/mailman/listinfo/jsword-devel<br class=""></div></blockquote></div><br class=""></div></div></div></body></html>