<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thanks for the answers.</p>
<p>Some advise to duplicate the commentary for every verse (Ps.23.1,
Ps.23.2, Ps.23.3, etc.) and some said it is a frontend issue. I am
still a bit lose and disappointed for the end users.<br>
</p>
<p>I don't understand why for commentaries, the OSIS reference
"Ps.23-1.5" is not the same as "Ps.23.1 Ps.23.2 Ps.23.3 Ps.23.4
Ps.23.5" for instance. In my opinion it should be considered
exactly the same. Or else, why not? Moreover, if I declare that
this commentary covers "Ps.23.1-5", the engine should show the
commentary if I asked for commentary for verse 3 for instance. Why
only for the first vese? Or maybe I misunderstood the concept of
Crosswire commentary…<br>
</p>
<p>If I change all the OSIS references to match every verses, I hope
the module size will not grow 20 times. And if I do so, for
frontends like Xiphos which have a "commentary by chapter" view,
the frontend will duplicate the commentary or use a hack to avoid
duplication of the same text…</p>
<p>Currently I do not know what is the best, I see all these
proposals like rather hacks (in the OSIS source or in frontends).</p>
<p>--yvand<br>
</p>
<div class="moz-cite-prefix">Le 30/05/2020 à 18:18, Karl Kleinpaste
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:f0be8b71-918b-88f4-b448-11fdc5455e15@kleinpaste.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">On 5/30/20 11:45 AM, yvand wrote:<br>
</div>
<blockquote type="cite"
cite="mid:6234e25a-b61b-6cd9-fca5-53530caecf88@gmail.com">I
think Karl already talked about this feature in the past. But
maybe I am wrong, I did not find the conversation. </blockquote>
<br>
<font face="FreeSerif">Xiphos has a feature, "commentary by
chapter," so that whole commentary chapters are displayed along
with whole Bible chapters, and then the verse is tracked
visually in the commentary pane, but in a different manner from
the Bible pane (i.e. current verse always aligned to top, plus a
preceding horizontal rule). It's a UI issue IMO, not an engine
issue. If you explicitly list the verse range covered in your
markup, then I imagine you might get the effect you want in
other UIs.<br>
<br>
Up to this time, Xiphos' commentary by chapter has not been
default, and I wonder if I should make it so in the future.<br>
</font> <br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
</body>
</html>