I would guess the main differences in output are all accounted for by checking
which combination of rendering engine and filter set is employed. BT e.g. wraps
and reimplements the sword engine's filters. BD and And Bible use jsword, but
use different exit points afaik, former chases all module content through a
XSLT conversion to create HTML, latter does something else.
----- Reply message -----
From: "Nic Carter" <niccar...@mac.com>
To: "SWORD Developers' Collaboration Forum" <sword-devel@crosswire.org>
Subject: [sword-devel] OSIS markup for gen books and devotionals
Date: Mon, Sep 22, 2014 03:20
As a general FYI, when I would test for conformity to how text should display,
I used to test PocketSword vs Xiphos vs Eloquent/MacSword vs BPBible. My
testing showed that they were a reasonable source of test cases. If something
looked right in them but not in PS, I knew I had a bug. :)(Karl, I would also
be interested in hearing why other front-ends don’t seem to conform. Has a lot
of work gone into other front-ends to change how some modules are presented
because the back-end code isn’t feature complete yet?)(PS: I’m on holidays and
half-hoping to have a new beta of PS out in the next 2 weeks. Perhaps even have
a new release of PS out by Christmas? iPhone 6/6+ compatibility would be good!)
On 22 Sep 2014, at 1:03 am, Karl Kleinpaste <k...@kleinpaste.org> wrote:
I find it odd that this discussion died out
without any further consideration from other app or engine developers
as to why the apps' delivery varies.
_______________________________________________sword-devel mailing list:
sword-devel@crosswire.orghttp://www.crosswire.org/mailman/listinfo/sword-develInstructions
to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
