Hi,<div><br></div><div>I must confess that to make JSword perform a little better and due to lack of xslt support on early versions of Android I tweaked jsword OSIS processing so as to use OSIS XML -> SAX processor -> HTML. I thus removed jdom and xslt. I realise there are various arguments for using jdom and xslt but performance was my main driver on such small, low powered mobile phones.</div>
<div><br></div><div>I may switch back to using xslt in the future because there is a lot of logic in the xslt stylesheet that was difficult to reproduce in SAX. Also, now, I think I may have been able to get xslt going on old Android s/w but am putting my effort into other areas.</div>
<div><br></div><div>Jdom may add too much overhead for such intense processing on small devices although it works great on pcs.</div><div><br></div><div>Best regards</div><div>Martin</div><div><br><div class="gmail_quote">
On 30 September 2010 15:07, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org">dmsmith@crosswire.org</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"> On 09/30/2010 05:24 AM, David Hollands wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My two pence.. feel free to ignore.<br>
<br>
* OSIS -> XSLT -> XHTML is unnecessarily complicated.<br>
</blockquote></div>
I'm interested in other ways that OSIS (xml in general) can be rendered. Some browsers (maybe all modern ones by now) are able to apply CSS directly to xml to produce output. Flying Saucer (<a href="https://xhtmlrenderer.dev.java.net/" target="_blank">https://xhtmlrenderer.dev.java.net/</a>) looks promising to me as something that can be used by a Java program.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* Indeed, it is easy enough to get the raw text. If you still prefer<br>
to convert raw text to OSIS first, given an XML parser/sequencer and a<br>
DOM, the programming language (Java) is all you need to produce the<br>
output (HTML). Personally, I've found using XSLT/XPath a bit<br>
cumbersome.<br>
</blockquote>
<br></div>
The biggest gain I see in using xslt is to have parameter driven output. E.g. the style of verse references, whether to show notes or not, ....<br>
<br>
The second gain is that it is simple, though it takes a bit of learning.<br>
<br>
The problem with raw text from an OSIS document is things like quotes, Words of Christ and Divine Name, i.e. Lord are marked up in such a way that they don't appear right in raw text.<div><div></div><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Love in Christ,<br>
<br>
David<br>
<br>
<br>
<br>
On 1 September 2010 18:23, DM Smith<<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 09/01/2010 12:48 PM, Manfred Bergmann wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Can the html rendering in JSword be simplified?<br>
</blockquote>
I'm not sure what you mean by simplified? Do you mean the process or the<br>
output?<br>
<br>
The process is basically this:<br>
Get the verses from the module.<br>
Convert them to OSIS. (For modules already in OSIS this is almost a<br>
pass-through)<br>
Use xslt to convert the OSIS into xhtml.<br>
<br>
The output is the final step. Another stylesheet can be used to simplify the<br>
output.<br>
<br>
Alternatively, one can create another mechanism to convert the raw text into<br>
html. It is easy enough to get the raw text.<br>
<br>
<br>
In Him,<br>
DM<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">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>
<br>
</blockquote>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">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>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">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>
</div></div></blockquote></div><br></div>