[sword-devel] Bibles without paragraphing

johnduffy at cgcf.net johnduffy at cgcf.net
Sat Nov 7 02:37:50 MST 2009

Why not offer all the options below for the user to choose either per module
or globally.  For modules where there is a .conf entry Feature=Paragraphs
then module specific paragraph and poetry display could be enabled/offered.
Where this is not present, users could have the choice of either vpl or
static paragraphing.  It may even be possible to offer these options in the
frontends without having to change the .conf files, by simply ignoring or
replacing the module paragraphing where vpl or static options are selected -
I'm not sure.  If the user isn't to be offered the choice, then I would
agree with your final suggestion below, as I'm not sure that by default KJV
paragraphing would suit other translations/languages well.  
John Duffy

-----Original Message-----
From: Chris Little [mailto:chrislit at crosswire.org] 
Sent: 07 November 2009 03:06
To: SWORD Developers' Collaboration Forum
Subject: [sword-devel] Bibles without paragraphing

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.

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.

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.

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.

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 

I think my preference is to add Feature=Paragraphs and just do 
verse-per-line in the absence of that feature. Thoughts?


sword-devel mailing list: sword-devel at crosswire.org
Instructions to unsubscribe/change your settings at above page

More information about the sword-devel mailing list