<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Apr 12, 2013 at 6:57 AM, John Austin <span dir="ltr"><<a href="mailto:gpl.programs.info@gmail.com" target="_blank">gpl.programs.info@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You didn't address my main point: Content providers should be given a way to have final control over how their formatted texts appear, and one which is simple and reliable. I'll comment below, but a Bible translation is not a web-page or an app which might need a new look someday, or a new skin. CSS and content abstraction etc. are great ideas, but they should not be artificially forced onto Bible publishers. Yes, they should be offered, and even encouraged- fine. But publishers should be able to say: "This is exactly how I want the formatting, everywhere, any time. Period." I don't understand why this expectation is so abhorrent. Offering a handful of content abstractions and extensions, all of whose definitions are arguable (see below) and likely in flux, is neither simple, nor satisfying to content providers who desire control over the presentation of their texts.</blockquote>
<div><br></div><div style>You'll find that many people in this list are strongly opposed to giving content providers any sort of presentational control over their text. This is unfortunate, but it is the direction Sword is lead in.</div>
<div style><br></div><div style>If you really want to have presentational control over your text, you can always encode into ThML. This gives you most of the full range of HTML tags and allows you to place CSS into a 'style' attribute on elements inherited from HTML. This style will work great in any Sword applications that use HTML rendering (Xiphos, BibleTime, BPBible, PocketSword, etc). It will be stripped and ignored on those few applications which leverage Sword and are not doing so with HTML-enabled display widgets (The SWORD Project for Windows, diatheke, etc). I have used this to fine effect to prepare documents with styles vastly different from what Sword condones.</div>
<div style><br></div><div style>Getting ThML shoe-horned into a Bible or Commentary module requires you to use the imp format and place ThML fragments into them. So you can do something like</div><div style><br></div><div style>
$$$Genesis 1:1</div><div style><span style="font-variant: small-caps">In</span> the beginning <span style="font-weight: bold; font-variant: small-caps">God</span> created the heavens and the earth.</div>
<div style>$$$Genesis 1:2</div><div style>And the earth was formless and void</div><div style><br></div><div style>It's obviously not recommended, but it's the only viable workaround I've encountered to circumvent the proscription against module creators being allowed to style their modules.</div>
<div style><br></div><div style>--Greg</div></div></div></div>