<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 11/05/2010 03:21 PM, Chris Burrell wrote:
<blockquote
cite="mid:AANLkTinCFJnadFLXY+r0StzXHvegmphnfszZT8eyhJpb@mail.gmail.com"
type="cite">What's GNT? Greek New Testament?</blockquote>
Yes.<br>
<br>
<blockquote
cite="mid:AANLkTinCFJnadFLXY+r0StzXHvegmphnfszZT8eyhJpb@mail.gmail.com"
type="cite"> 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. <br>
</div>
</blockquote>
I used <font class="xxx">...</font> because Java's
built-in render did not know <span
class="xxx">...</span>. I'd suggest changing all font tags
to span and see if that works for you. The CSS would need to change
the font.xxx to span.xxx.<br>
<br>
<blockquote
cite="mid:AANLkTinCFJnadFLXY+r0StzXHvegmphnfszZT8eyhJpb@mail.gmail.com"
type="cite">
<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>
</blockquote>
<br>
Sounds good.<br>
<br>
<blockquote
cite="mid:AANLkTinCFJnadFLXY+r0StzXHvegmphnfszZT8eyhJpb@mail.gmail.com"
type="cite">
<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. <br>
</div>
</blockquote>
You don't need the transformations to be on the next lines. You can
have them side by side and display in a stacked fashion. This was
the sample interlinear code I was talking about.<br>
<br>
<blockquote
cite="mid:AANLkTinCFJnadFLXY+r0StzXHvegmphnfszZT8eyhJpb@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>DM, I had a look at <span class="Apple-style-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>
</blockquote>
<br>
Currently we transform OSIS into HTML. And then hand that to a
renderer. Some "browsers" are able to take xml and render it
directly using CSS. This is what flying saucer claims to do. I guess
I don't know what your target is. I was assuming a desktop
application. But if it is the web, then never mind. However, if it
is the web maybe some collaboration with FireBible on the xslt would
help you.<br>
<br>
-- DM<br>
<br>
<blockquote
cite="mid:AANLkTinCFJnadFLXY+r0StzXHvegmphnfszZT8eyhJpb@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>Chris</div>
<div><br>
<br>
<div class="gmail_quote">On 5 November 2010 03:51, Tonny Kohar <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:tonny.kohar@gmail.com">tonny.kohar@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Hi,<br>
<div class="im"><br>
On Thu, Nov 4, 2010 at 11:30 PM, DM Smith <<a
moz-do-not-send="true"
href="mailto:dmsmith@crosswire.org">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 moz-do-not-send="true"
href="http://www.kiyut.com/products/alkitab/index.html"
target="_blank">http://www.kiyut.com/products/alkitab/index.html</a><br>
</font>
<div>
<div class="h5"><br>
_______________________________________________<br>
jsword-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a moz-do-not-send="true"
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>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
jsword-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>