<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Apr 12, 2013 at 4:37 PM, Matěj Cepl <span dir="ltr"><<a href="mailto:mcepl@redhat.com" target="_blank">mcepl@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><span style="color:rgb(34,34,34)">My point was that documents are more valuable and more difficult to change than programs. So we should orient on perfecting documents and change programs if necessary. And yes, possibility of using stylesheets would be awesome, but that isn't necessarily the point.</span></div>
</blockquote><div><br></div><div style>The point is</div><div style>1) His publishers want to control indents</div><div style>2) Sword doesn't want to give this control through XML</div><div style>3) Sword does not support stylesheet mechanisms for giving module creators this control.</div>
<div style><br></div><div style>Presently, there are some half-way workarounds that are only effective in some places.</div><div style><br></div><div style>1) Not use OSIS XML but instead use ThML. But this only functions in HTML-based applications</div>
<div style>2) Use the forms of OSIS XML that are mentioned earlier, which are non-ideal. But this only works in xulsword</div><div style>3) Change the applications, which is an unfeasible level of effort, as the number of applications could increase without bound.</div>
<div style><br></div><div style>This problem has been hashed out many times. There seems to be no satisfactory method to give publishers the type of control they want. We can't specify CSS styles, since only some of our applications can parse and utilize CSS. We can't specify RTF for the same reason. We can't allow XSL because only JSword uses XSLT on the OSIS whereas Sword uses a stream text processor that roughly resembles SAX which allows it to work marvelously on low-memory devices with great success.</div>
<div style><br></div><div style>In theory the ideal way for us to handle XML sources would be to allow each application or device to specify an XSLT which is combined with one from the module to prevent certain output that the target device cannot handle. But, in practice, this doesn't work very well as not every programming environment has access to XSLT libraries and some devices can't handle the large memory overhead needed to load in an XML file that is several MB (like the one for the KJV), transform it, and write it back out in an efficient manner.</div>
<div style><br></div><div style>So we're stuck in an unenviable position of being forced to either suggest a user select one of these partial hacks or tell people that we can't honor their request for control over the formatting.</div>
<div style><br></div><div style>--Greg</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br></div>
<br>
Blessings,<br>
<br>
Matěj<div class="HOEnZb"><div class="h5"><br>
<br>
-- <br>
<a href="http://www.ceplovi.cz/matej/" target="_blank">http://www.ceplovi.cz/matej/</a>, Jabber: <a href="mailto:mcepl@ceplovi.cz" target="_blank">mcepl@ceplovi.cz</a><br>
GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC<br>
<br>
<br>
</div></div><br>_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br></blockquote></div><br></div></div>