[sword-devel] SFM to OSIS handling of the \sr marker?

[Peter von Kaehne]

The more i think through this the more my conclusion is, conversion should be as little lossy as possible, presentation is the place where lossiness becomes useful. So ranges should be lists of all concerning verses, but frontends +/- filter writers might want to put more effort into transforming this into something useful. 

Sent from my phone. Apologies for brevity and typos.On 7 Jan 2016 7:27 am, Isaac Dunham <ibid.ag at gmail.com> wrote:
>
> On Wed, Jan 06, 2016 at 09:07:48AM -0800, David Haslam wrote:
> > As I continue to evaluate the efficacy of Aydeth's u2o.py script, this
> > subject surfaced in my thinking.
> > 
> > The \sr marker is described in the USFM Reference:
> > 
> > Section reference range. 
> > · The text reference range listed under a section heading. 
> > · \sr is not equivalent to \r which is used for marking parallel references. 
> > 
> > What real value is there in making these kind of references into OSIS links?
> > 
> > After all, when you see one of these headings, you're already at the
> > location.
> <snip> 
> > Of course, some front-ends (e.g. Xiphos) convert ranges to a verse list in
> > the side panel.
> > But how much value does this add for the typical user?
> > 
> > And consider how many verses could easily end up in such a verse list. e.g. 
> > <title type="scope">(<reference>Salmau 1—41</reference>)</title>
> > Does anyone really think a verse list for 41 psalms is going to be useful?
>
> All your other arguments are persuasive, so I'm not arguing against the
> conclusion.
>
> But on the general topic of converting ranges to verse lists, I would like
> to say that creating a list of all verses may not make sense for most uses,
> but it is useful to have a list of starting verses, including, "if
> reasonable", all chapter-starting verses within the range (since navigation
> is generally on the chapter level, allow one to read all the range without
> switching to "next chapter" navigation".)
> Eg, Phil. 1:12-2:4 would become a list of 
> Philippians 1:12
> Philippians 2:1
>
> Psalms 1-41 could become (depending on one's understanding of 'reasonable')
> Psalm 1:1
> Psalm 2:1
> ...
> Psalm 40:1
> Psalm 41:1
>
> or simply
> Psalm 1:1
>
> However, I'll point out that a full verse list might be very helpful when
> one is using the 'parallel' mode, as it currently is a display of a single
> verse in multiple modules.
>
> > I'm beginning to think that we should leave these as plain text headings
> > rather than active links.
> > 
> > Does anyone agree?
>
> Well...
> I suppose one might argue that these would come in handy if you're using
> a commentary viewed in chapter mode, along with parallel translations
> (possible example: I use KJV/RWP regularly, but may switch to parallel
> view with the EMTV, Darby, and Byzantine modules in addition to the KJV.)
>
> I have not used the verse list on such an occasion, however.
>
> In general, I'd agree.
>
> God bless,
> Isaac Dunham
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page