> If there's just a div with a CSS class, frontends can handle that as they
> require, and the indenting support shouldn't cause an issue.
depending on how nicely the different front-ends play with the HTML that the
filters provide? I didn't play nicely enough in PS & so had to clean up some of
I have an update for the KJV here:
http://www.crosswire.org/~dmsmith/kjv2006/sword/2011/kjv.zip
Basic details:
Splits: (Indicate Greek translated into an English phrase that is interrupted
by the translation of another Greek word or added text.)
In the Greek, the mechanism for denoting splits hav
Some of it is going to require CSS support anyway to do the layout.
If there's just a div with a CSS class, frontends can handle that as they
require, and the indenting support shouldn't cause an issue.
BTW, with the Proverbs 28 issue, my guess is the opening is a few
chapters earlier.
In the h
Thanks heaps for this, Ben :)
Appears I had a little bug in the previous patch I emailed around. When closing
the div on line 379 of osishtmlhref.cpp I had added a "" which shouldn't
be there!
I like how you have BPBible displaying this stuff, and so it's inspired me to
fix up some of the for
Reading the OSIS stuff at
http://crosswire.org/wiki/OSIS_Bibles#Marking_poetic_material it says:
• While OSIS defines a milestoned version of the element, its use
(rather than the container version) will not produce a valid XML document. The
element can only occur within an containe
