DM, you said you might have an intearlinear model that worked? I had another look to see how I did mine previously, and found that in fact I used tables. I think I struggled for quite a while to get a model working across browsers using DIVs, but none of them seemed to wrap properly at the end of the line. But unfortunately table layouts are slow and therefore it would be better to have divs. <div>
<br></div><div>Would you be able to let me have your samples?</div><div>Chris<br><br><div class="gmail_quote">On 5 November 2010 19:21, Chris Burrell <span dir="ltr"><<a href="mailto:chris@burrell.me.uk">chris@burrell.me.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">What's GNT? Greek New Testament? I think we can do more than that too. If other Bible versions have strong numbers and/or morphology tags, then we can put those in parallel, and end up having French with English "subtitles", or English with English, as well as English with Greek, etc.<div>
<br></div><div>So I've had a look at the framework so far and it seems fairly easy not to use Bible Desktop components and have a good XSLT transformation. So all we would need to add is some helpers that users can easily integrate into their XSLTs. It would nice to have some sample XSLs for people to use. So for example, I've had to strip out all the CSS and font tags from the Bible Desktop one so as to produce a good XHTML compliant one. </div>
<div><br></div><div>Say we give the XSLT a InterlinearProvider initialised with its version and passage, as it parses the strong/morph option we can then call get($provider, @strong, @morph), which would in turn optionally return the correct words (or best word since sometimes you may have multiple options in modules tagged with strong numbers only. In fact it would be better to have something like get($provider, osis_verse_id, @strong, @morph). Since then, if we don't have the morphology of the word, at least we can limit the lookups to those words that are tagged in a particular verse (that assumes that versification is comparable between versions).</div>
<div><br></div><div>We'll want to add options to have tagged information displayed on the side of a word/phrase or below a word/phrase. At the moment the XSLT displays morph and strong tags next to the text. I'll add some transformations to have it on separate lines. Then we can reuse the same transformations to line up text beneath it. </div>
<div><br></div><div>DM, I had a look at <span style="font-family:arial, sans-serif;border-collapse:collapse">"flying saucer" , but didn't quite understand where it comes in? Would the idea be instead of the XSLT? And have it transform to different UIs?</span></div>
<div><br></div><font color="#888888"><div>Chris</div></font><div><div></div><div class="h5"><div><br><br><div class="gmail_quote">On 5 November 2010 03:51, Tonny Kohar <span dir="ltr"><<a href="mailto:tonny.kohar@gmail.com" target="_blank">tonny.kohar@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<div><br>
On Thu, Nov 4, 2010 at 11:30 PM, DM Smith <<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>> wrote:<br>
> Much of the transformations is done in BibleDesktop. Refactoring these and<br>
> putting it into JSword and/or common would be good.<br>
><br>
<br>
</div>+1<br>
Yes it would be nice to have this under JSword instead of BIbleDesktop<br>
<br>
Sincerely<br>
Tonny Kohar<br>
<font color="#888888">--<br>
Alkitab Bible Study<br>
<a href="http://www.kiyut.com/products/alkitab/index.html" target="_blank">http://www.kiyut.com/products/alkitab/index.html</a><br>
</font><div><div></div><div><br>
_______________________________________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org" target="_blank">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>