<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 19, 2013, at 8:55 AM, Ben Morgan <<a href="mailto:benpmorgan@gmail.com">benpmorgan@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi DM,<div><br></div><div>I'm looking at it for how it displays in BPBible. Mostly it seems to show up fine. </div><div>At the moment the code I had in place actually shows the tr greek text links, though it doesn't know what to look them up in (there's no dictionary matching the tr: scheme, right?). </div></blockquote><div><br></div>There are a few other modules that have lemmas other than "strong:". If you want Strong's numbers look only for strong:.</div><div><br><blockquote type="cite">
<div>I think I'll make it ignore them for now. It would be nice to have a common way with non-strongs type lemmas to</div></blockquote><blockquote type="cite"><div>1) have them togglable with options (on a class by class basis? what would you label this for tr: - TR? Greek?)</div></blockquote><div><br></div>The tr: lemma is the original greek from the TR Bible module. The src attribute gives the position of that word in the same verse. </div><div><br></div><div>You can use the tr: value for an interlinear. You could also show the tr value and use the strong for the link.</div><div><br></div><div><br><blockquote type="cite">
<div>2) have some way to look them up in dictionaries</div><div><br></div><div>However, one change I did notice was that you've swapped the order in at least one place of a q and a paragraph marker so that in the new KJV module, the <q> contains the paragraph marker:</div>
<div><q marker="" who="Jesus"><milestone marker="¶" type="x-p"/></div></blockquote><div><br></div>I think this is across the board. </div><div><br><blockquote type="cite"><div><br></div><div>Was this a deliberate change?</div></blockquote><div><br></div>Actually, it is osis2mod that is doing that. The latest osis2mod allows for the WoC to be marked up naturally, even spanning chapters, such as with the beatitudes. So that would have a start in chapter 5 and an end in chapter 7. osis2mod then marks up the words individually with the WoC markup. It always puts the marker at the beginning of the verse as it has not seen any content from the verse.</div><div><br></div><div>So yes it was deliberate. The old source file used to have per verse markup. The new file has natural markup.</div><div><br></div><div><br><blockquote type="cite"><div> This doesn't work with BPBibles code as-is </div></blockquote><div><br></div>It doesn't work with Bible Desktop either.</div><div><br><blockquote type="cite"><div>(though I could probably get it to work with a little more hacking). In general, BPBible:</div>
<div>1) turns pilcrows into paragraphs</div></blockquote><div><br></div>Bible Desktop would do both: add a paragraph break and show the pilcrow.</div><div>I plan to check to see if the verse has a pilcrow, instead of seeing if the verse has it at the beginning. Haven't made the change, but it will be small.<br><br><blockquote type="cite"><div>2) floats whitespace before verse numbers</div></blockquote><blockquote type="cite"><div><br></div><div>At the moment, the paragraph tag doesn't float out before the verse number due to the <q> tag. This ends up with the awkward situation where the previous line ends with the verse number and then the verse actually starts on a new line.</div></blockquote><div><br></div>Yes, that doesn't sound good. Bible Desktop doesn't have this problem as it has not identified the pilcrow as a paragraph separator.</div><div><br><blockquote type="cite">
<div><br></div><div>Also, in BPBible at least words of Christ are done with span tags, and having the <p> inside a span doesn't really work and the highlighting goes missing. </div><div><br></div><div>Quite possibly other frontends don't try and tweak the text like this and so aren't affected.</div>
<div><br></div><div>This isn't causing any problems, but I'm interested in the <chapter> tag which now shows up in v0. e.g.</div><div><pre class="raw"><chapter chapterTitle="CHAPTER 1." osisID="Rom.1" sID="gen1730"/> <title type="chapter">CHAPTER 1.</title></pre>
</div><div><div>Is there any expectation this will be used? Does it need to be retained here (seeing as <title> is there too)?</div></div></blockquote><div><br></div>osis2mod retains all tags and content from the module except the OSIS preamble.</div><div><br></div><div>If you dump the module w/ mod2imp, it is a simple matter of adding in verse tags to have a valid OSIS file.</div><div><br></div><div>You'll find lots of other tags that a renderer won't care about.</div><div><br><blockquote type="cite"><div><div><br></div><div>God Bless,<br>Ben<br>-------------------------------------------------------------<br>
<div>
<div>For I have no pleasure in the death of anyone, <br>declares the Lord <span style="font-variant:small-caps">God</span>; so turn, and live.”<br>Ezekiel 18:32 (ESV)</div>
</div>
<br></div>
<br><br><div class="gmail_quote">On Tue, Feb 19, 2013 at 9:19 AM, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think I have a ready-to-release update to the KJV. Please do one last check.<br>
You can get the modules here:<br>
<a href="http://www.crosswire.org/~dmsmith/kjv2006/sword/2011/kjv.zip" target="_blank">http://www.crosswire.org/~dmsmith/kjv2006/sword/2011/kjv.zip</a><br>
or if you want one with a different name and in raw format:<br>
<a href="http://www.crosswire.org/~dmsmith/kjv2006/sword/2011/av.zip" target="_blank">http://www.crosswire.org/~dmsmith/kjv2006/sword/2011/av.zip</a><br>
<br>
Many thanks to David H for finding lots of bugs.<br>
<br>
Hope to release very soon.<br>
<br>
In Him,<br>
DM<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote></div><br></div>
_______________________________________________<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page</blockquote></div><br></body></html>