<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Sorry for the empty post. Was going to muse whether Chapter n:1 should implicitly include all verse 0 before it.<div><br></div><div><br><div><div>On Jul 2, 2012, at 7:39 PM, DM Smith wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 2, 2012, at 12:54 PM, DM Smith wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">The work is done by
VerseRange.getName() which calls VerseRange.getName(Verse base)
which ultimately calls VerseRange doGetName(Verse base).<br>
<br>
The purpose of this routine is to get a user friendly
representation of the VerseRange. It is used in more places than
just x-gen titles. Here are a few more scenarios:<br>
<br>
First scenario:<br>
It is used in a bi-directional context. That is the user can input
Gen 1:1-31, which is not the same as Gen 1, since Gen 1 can
include intros if present.<br>
<br>
So in BibleDesktop, we allow a user to input verses freeform and
we try to figure out the best we can what they mean.<br>
<br>
In preferences they can either preserve original values in which
case we only show them what they type, but behind the scenes we
store it as we see fit.<br>
<br>
Or they can choose to have their input normalized into their
preferred form. This will result in calls to
VerseRange.getName(Verse base).<br>
<br>
This normalized form is then used to do whatever work is needed.
So the normalized form needs to be equivalent to what the user
originally specified.<br>
<br>
Second scenario:<br>
The user performs a search and the answer is included in verse 0.
Should 0 be shown to the user?<br>
<br>
Third scenario:<br>
Blurring: The user has Gen 1:4 in their list and blurs it by 10
verses, which results in Gen 1:0-14. Should it show 0? Should it
show the intro?<br>
<br>
In each of these scenarios, the output is the textual
representation of a bit map. They need to match.<br>
<br>
There may be others, but I know of these off the top of my head.<br>
<br>
So how do we change it for your scenario? What should we do for
the other scenarios?<br>
<br>
In Him,<br>
DM<br>
<br>
<br>
On 07/02/2012 12:18 PM, Chris Burrell wrote:<br>
</div>
<blockquote cite="mid:CACQnaRW0griFAzCWhtE4rKsjR2acridDKC+Gxr3ioUndRL2eGg@mail.gmail.com" type="cite">Hi DM
<div><br>
</div>
<div>The problem is that a user may type in Exodus 3-4:17 and
somehow from his point of view gets verse 0 for chapter 4 (and
no 0 for chapter 3 (note the slight difference from before -
same symptoms/results with Ex 3-... and Ex 3:1-... Verse 0 is
omitted for this chapter).</div>
<div><br>
</div>
<div>From a user's point of view, he doesn't know about a verse 0
and so verse 0 should never be in a title. Or at least, that's
my take...</div>
<div>Chris</div>
<div><br>
<div><br>
<div class="gmail_quote">
On 2 July 2012 17:11, DM Smith <span dir="ltr"><<a moz-do-not-send="true" 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">
<div text="#000000" bgcolor="#FFFFFF">
<div>
<div class="h5">
<div>On 07/02/2012 11:53 AM, Chris Burrell wrote:<br>
</div>
<blockquote type="cite">Hi
<div><br>
</div>
<div>With the introduction of verse 0, the xgen
titles sometimes now contain this. I used to use
this to display the demarcations between
passages if multiple passages are being entered.
However, this now gives the following xgen
titles: </div>
<div><br>
</div>
<div><title type="x-gen">Exodus
3:1-22</title></div>
<div><title type="x-gen">Exodus
4:0-17</title></div>
<div><br>
</div>
<div>The above example is for "Exodus 3:1-4:17". </div>
<div><br>
</div>
<div>I was just wondering if this <b><i>expected
</i></b>behaviour. If so, I'll code something
to work around this. It doesn't however happen
for "Exodus 3-4"<br>
</div>
</blockquote>
</div>
</div>
I'm not sure how it should work. It is certainly the way
it is coded. Chapter 0 and Verse 0 are full fledged
references.<br>
<br>
That is for Genesis<br>
Gen.0.0 is the Book intro/title<br>
Gen.1.0 is the Chapter intro/title<br>
<br>
In your example, Exodus 3:1-4:17 explicitly excludes the
Chapter 3 intro, if present, but explicitly includes it
for chapter 4, if present.<br>
<br>
So if you want all of Genesis, chapter 1, do you want
the title as well? Then Gen.1 will work. But if you
don't and headings are turned on, what then?
Gen.1.1-Gen.1.21?<br>
<br>
If you want part of the chapter, say the first 10
verses, what do you want? Gen.1.0-Gen.1.10 or
Gen.1.1-Gen.1.10?<br>
<br>
Right now, the code makes no distinction between one
chapter number and another or one verse number and
another. Should it?<br>
<br>
If not, what should it do?<br>
<br>
In Him,<br>
DM<br>
<br>
</div>
<br>
_______________________________________________<br>
jsword-devel mailing list<br>
<a moz-do-not-send="true" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a moz-do-not-send="true" href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jsword-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a>
</pre>
</blockquote>
<br>
<br>
</div>
_______________________________________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br></blockquote></div><br></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></div></body></html>