<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 3/17/19 6:23 AM, <a class="moz-txt-link-abbreviated" href="mailto:refdoc@gmx.net">refdoc@gmx.net</a>
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:gwc710-rixo-kzjic-7xq9takz8s026amjr7-cztqmx-9ncqyedkysxtyiumt3c0zgxf-b2qiusoztbbo-cjs7zxkcjt86-nobwyr-42539be0615h9xzzsx-tiwra4-bfg95s-yts6l212scbl-zas2dt.1552818195771@email.android.com">Xiphos
then adds a few further standard (for Xiphos) CSS styles to the
mix. <br>
</blockquote>
<font face="FreeSerif">Not exactly.<br>
<br>
Xiphos uses exactly one nonstandard CSS control, .introMaterial,
specifically because OSIS tools and Sword processing do not
generate a distinct display class for introductory material. I
initially encoded a simple "<i>...</i>" wrap but then
decided to generalize it to ".introMaterial { font-style: italic;
}", because I'd have to change Xiphos for any future Sword change
anyhow.<br>
<br>
However, for this purpose, the deeper problem is that Sword
erroneously generates self-closing <div> tags, which do not
work. Search "html self-closing div" and discover all the
conflicting noise over it. My solution in Xiphos was simply to
obliterate these tags in introductory material; they have no
visual manifestation and I don't know why the XHTML filters pass
them in the 1st place. They look like<br>
<br>
<div sID="gen34165" type="introduction"/><br>
<br>
and they caused my .introMaterial change to bleed throughout the
chapter until I implemented the obliteration. See
<a class="moz-txt-link-freetext" href="https://github.com/crosswire/xiphos/issues/845">https://github.com/crosswire/xiphos/issues/845</a><br>
<br>
No other class tag is specific to Xiphos. It will process class
any tag the module creator or user puts to use.<br>
<br>
As far as the mention of front-ends' display being different, if
there is any standard display toolkit against which to compare,
WebKit is that standard, and Xiphos has used it for years now.
It's WebKit that's unhappy with self-closing <div> above,
and Xiphos' display has always consisted almost entirely of "ask
engine for content, paste content into widget for WebKit
interpretation," with a few grotesque HTML post-delivery hacks to
get around stuff like bad self-closing <div>.<br>
</font>
</body>
</html>