WRT to JSword, we only have one OSIS/TEI filter which transforms to HTML
(actually, this is an XSLT script). Our other filters (PlainText, GBF, ThML)
transforms to OSIS and then runs through the OSIS -> HTML filter. The same
filter is used by all JSword frontends with small variations.
The current release of JSword and the next release of JSword differ. Some
frontends (STEP, AndBible) are at the next release level. Notably BibleDesktop
is not, but should have been. Don't know about Alkitab. This would account for
some variation in JSword.
We currently don't handle intra-document linking except for images as relative
urls where the base is the root of the module.
On another note: osis2mod does not require OSIS (except that which is needed to
split the module into verses) or verify OSIS. It assumes that input has been
validated externally. It is quite possible for HTML (e.g. <br/>, <span
font="red">...</span>) to be in the input and it would be stored in the module
as such. How different engines and frontends deal with that is highly variable.
I think JSword will emit a warning and strip the elements and their attributes,
not their content, in the XSL.
Another place of difference is the handling of vertical whitespace. In HTML
nesting of block elements doesn't produce extra whitespace when adjacent
opening or closing tags are present. This is not handled properly by the
filters, which needs to simulate it. OSIS has the notion of milestone starts
and ends of these elements. This does not directly translate into HTML. Also,
the preverse div (opening and closing elements) needs to never produce vertical
whitespace. There already have been lots of threads on this.
In Him,
DM Smith
On Sep 22, 2014, at 1:40 AM, ref...@gmx.net wrote:
> 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.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions 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
_______________________________________________
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
