<div class="gmail_quote">On Sat, Nov 7, 2009 at 2:05 PM, Chris Little <span dir="ltr"><<a href="mailto:chrislit@crosswire.org">chrislit@crosswire.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
We have many many Bibles that lack any kind of paragraphing markup. These will tend to be rendered as a single big block of text per chapter, which is rather ugly.<br>
<br>
Some front ends offer a verse-per-line option where every verse gets its own newline, regardless of whether the Bible has paragraphing. I think this is a good option for the case of non-paragraphed Bibles but undesirable for those that do have paragraph indication.<br>
<br>
I would like to propose that we add a new Feature to .confs (e.g. Feature=Paragraphs). If the feature is absent, a front end can know that it should output newlines at the end of each verse.<br>
<br>
Alternately, we could tag unparagraphed Bibles with Feature=NoParagraphs. There will be many more Bibles that need to be checked, updated, and re-downloaded by users. But if a user fails to update his content, in this case there wouldn't be the incorrect behavior of rendering paragraphed Bibles as verse-per-line.<br>
<br>
A third alternative (probably less attractive now that we're releasing quite a few non-KJV v11n Bibles) is to do one of the above and then offer static paragraphing like OLB does. OLB starts new paragraphs at set verses, regardless of the Bible. We could grab the paragraph data from the KJV, for example, and then insert paragraph marks in the render filters.<br>
<br>
<br>
I think my preference is to add Feature=Paragraphs and just do verse-per-line in the absence of that feature. Thoughts?<br>
</blockquote><div><br>I have no problems with this, so long as the decision of whether to use VPL or not is left to the frontend and ultimately the user to control rather than being done automatically by the library. As you say, I think VPL tends to be a frontend thing rather than a library thing anyway.<br>
<br>It would be preferable not to bump all version numbers and make all modules be re-downloaded (in frontends that support module updating) just for changes which will not make any difference to current frontends anyway.<br>
</div></div><br>Just out of curiosity, do you have any guesses as to what percentage of Bibles do have paragraphs?<br><br>Jon<br>