Hi all,
BPBible 0.5.2 has been released. This is largely a bug-fix release.
To see a list of the changes that have been included, look at
http://bpbible.com/news/bpbible-0.5.2-changes.
Jon
___
sword-devel mailing list: sword-devel@crosswire.org
http:/
Module developers,
Please forget about x-preverse. It was never intended for module
developers. It is an internal attribute we add to help the SWORD engine
process OSIS. Brief overview without details: SWORD must keep all data
in 'verse' chunks. Hence, the title for a verse goes WITHIN the
David,
You've brought up 3 issues here. Two should be on separate threads.
Regarding rendering of titles, an OSIS should be transformed into a
, , ... element by the SWORD api when rendered to (x)html. If it
is, then it will be rendered as a block element and not on the same line. If it
does
As a module author, I totally agree with David, it was very hard to start and
find a complete example to follow (Commentary) , Also had to test the module on
many frontends to be sure that my work will be the same on all devices and OSs
Making Complete tested examples, that covers all features a
Hi Nic,
No - I have not yet reached the stage of pushing the module I'm currently
working on to either PocketSword or And Bible.
Only tested it so far on Xiphos 3.1.5, xulsword 3.5 and Bible Desktop 1.6;
all on Windows 7 x64.
Yet all three front-end caused titles within chapters to be appended t
Have you tested those modules in PocketSword? Do they render their titles
correctly?
Sent from my phone, hence this email may be short...
On 17/05/2013, at 21:41, David Haslam wrote:
> But surely a related issue is that the titles in OSIS files generated by
> usfm2osis.py don't even end up wi
Vertical whitespace is one thing - I've certainly seen several modules in
which the display has too much of it.
But surely a related issue is that the titles in OSIS files generated by
usfm2osis.py don't even end up with new line when the OSIS is converted to a
module using osis2mod
As Chris
