Jump to content





- - - - -

Interlinear Issues

By APsit190, 05 September 2014 · 2,306 views

The Way An Interlinear Currently Looks Like
Attached Image

As seen in the image above, as with all interlinear  Bibles for e-Sword, the issue is the ability to have a proper flow of Greek and/or Hebrew text with its corresponding transliterated and translated text in where it one can actually read it. The way it is seen at the moment (as in the image above) makes it difficult to read. Moreover, as seen in the above example, a large part "true" interlinear is missing or left out, and therefore it really doesn't do the proper job for what it is intended to do. So we need to find a resolution to this problem in where we can have a decent interlinear Bible for e-Sword.

There are two major problems which I see that needs to be addressed in order for this to be able to happen, which are:

1. The of screen size, in particular to mobile device types, in particular to tablets and smart phones

2. Desktop PCs and Notepads (Laptops)

3. The view type used in the software.


Looking at both of these problems, I can see that the third problem can solve the issue of the first and second problems as they are really all connected.

Currently e-Sword, for its Bible, Dictionary, and Commentary Veiws, use a Rich Text Box in "Read Only" modes. This means that the views, these component windows, use the same kind of Rich Text Box as seen in any word processing program, and its for this very reason that makes it difficult to have a paper book layout, or a book type layout for the interlinear text.

In a review of Raymond Baron's Interlinear OT, I suggested placing a new line for each of the parts of the inlinear text e.g.,

First Line: Hebrew Text

Second Line" Transliterated Text

Third Line: Word for Word Translated Text

Forth Line: A Bible Translation


And only have something like about 6 - 8 words per line, and that way one, in theory, could have a reasonable kind of paper book type of layout. But the problem isn't really resolved for mobile devices, such as the Apple iPhone, and/or perhaps the tablet.

So, what is the best solution that will resolve this problem?

I think that there needs to be a complete revamp to e-Sword for Desktop, iPad, and iPhone in the kind of Text views that are currenlty used. I think there is a need to ditch the Ritch Text Boxes and replace them with an "electronic" book (page) type viewer. This means that irrespective of the size of the monitor/screen, the data/text within the view will adjust to the current size. This is theory only, and as to how that would work out in practice is another question.

Your thoughts and comments are welcome.

Blessings,
Autograph.png




 

Your observations are very good ones.  It is always a problem to show clearly the different information in an interlinear.  As you have observed, a number of interlinears are incomplete.  I do not know from what source they are derived, but in a number of cases it appears that the person who created the e-Sword module was not the creator of the interlinear text, or that the creator of the text is not trying to do a true word-for-word interlinear.

 

When creating an interlinear e-Sword module, it is possible through color and text size make it more readable, even on a phone.  I am showing a sample of how such a text can be rendered to make it more readable.  This module was created with BeST, but TT4 can also do the same.

 

To ensure a true word-for-word correspondence, the interlinear creator must enforce that. It may be that he would need to create a script to enforce creating a corresponding word for each Greek (or Hebrew) word.  It is a non-trivial task, unfortunately.

 

Creating an interlinear as described above, of course, does not give the appearance of a book, but at least it can be easily read.  I hope this is of some help.


The question, of course is who should "bell the cat"?  This would call for a major rewrite of e-Sword in all of its formats (or so it seems to me), and Rick is over worked and inundated with suggestions as it is.

Perhaps it might be done by splitting the bblx format into bblx and lbblx (linear Bible), thus limiting the rewrite to how one specific module type (the lbblx) is to be read and displayed.

That way bible, commentary, dictionary and topic/reference modules can still use the Rich Text Box (read only).  Or is it an all or nothing deal, either all of the modules are Rich Text Box or non

How are graphics handled in RTB?  Since graphics can now be inserted into most if not all of the modules, could each chapter be one large image (sort of like PDF). Or maybe it could be arranged somewhat like the Compare tab reading from four "modules" to get the layout you suggested.  (Navigation between verses might be a bit tricky, but F5, F8, F9 and F12 work for compare so why  not linear?)

First Line: Hebrew (Greek) Text

Second Line" Transliterated Text

Third Line: Word for Word Translated Text

Forth Line: A Bible Translation

I'm just not familiar with how e-sword modules are put together, but I really like the idea of having true interlinear Bibles.

Would something like this arrangement be an improvement? It flows to any size device, though of course it's html and not e-Sword.

http://bible.fether....ex.php?pager=gr

Would something like this arrangement be an improvement? It flows to any size device, though of course it's html and not e-Sword.
http://bible.fether....ex.php?pager=gr

 
I had a look at what you had done, and what you show is very similar to what you I am talking about.
 
Really appreciate your imput. Thank you. You got a "like" out of me on this one. :)
 
Blessings,
Autograph.png

Would something like this arrangement be an improvement? It flows to any size device, though of course it's html and not e-Sword.

http://bible.fether....ex.php?pager=gr

Perfect, and something I'd use a lot of.

And thanks for the site, it sure will be used by me a lot.

My Picture

August 2019

S M T W T F S
    123
45678910
11121314151617
18 192021222324
25262728293031

My Other Blog Pages

Feel free to visit my other Blog Pages here, and comment on any of the entries you read.

Recent Comments