The thing I notice about font sizes is that some fonts in appearance are larger and/or smaller than others.

This phenomena is more noticable for non-Latin writing systems. Thai is usually typeset at 18pt. Most CTL writing systems need a font size of 14pt, or more, simply to be read.

jonathon

That would mean virtually every official e-Sword resource does not comply with your standard.

One of the reasons I came to that conclusion was becuase the official e-Sword resource tooltips didn't display on the monitors I had available.

jonathon

Model year 1998 Super VGA 13 inch monitor at 640x480 resolution?

Actually, it was a 1200x800 monitor that convinced me that three verses was the most that should be displayed.
Not everything in the tooltip was displayable. Not everything in the official resource could be displayed on the screen.

jonathon

Jonathan what is the benefit of doing a concordance   ???.dctx of a bible when search accomplishes the same task

For the Latin writing system, search usually works correctly.   Operative word is usually.
For other writing systems, search is a hit or miss affair, with failure being the most common result.

jonathon

I think, depending on the size of the monitor,

Size of monitor doesn't matter.  What matters is the screen resolution of the monitor.

For various reasons that I won't go into here, a tooltip should contain no more than three verses.

jonathon

I don't use either ToolTip Tool, nor ToolTip Tool NT, so perhaps these RFEs are already implemented.

* Red Letter the Bible with Words of Jesus;
* Red Letter the Bible with Words of God;
* Create a Dictionary resource that is a concordance of the selected work;

jonathon

I'm not there was a 1600 oxford dictionary?

Work on the OED was started in 1857. I think the first volume was published in 1884.
The complete set was first available in 1928.

Middle English Dictionary might be more appropriate, but it covers the language from roughly 1100 AD to 1500 AD. I'm not sure what the licensing policy is.

An Anglo-Saxon Dictionary might also be appropriate. The 1838 and 1898 editions are in the public domain. The 1921 edition is probably in the public domain. This covers roughly 450 AD to 1100 AD.

A Table Alphabeticall, published in 1604 might be usefull, if its limited vocabulary is acceptable.

A Dictionary of the English Language, published in 1755 by Samuel Johnson is probably the most suitable dictionary for understanding either the 1760 or 1769 KJV.

Webster's 1828 Dictionary of the English Language probably has too many Americanism to be useful for studying Bibles translated into British English.

jonathon

\
What I would like to see in an e-Sword Hebrew and Greek Interlinear Bible is the text for it displayed in their own line, i.e., Top line - Hebrew (Greek), Second line the Transliterated Text, Third line English word for word Translation, Forth Line (optional) an English Translation/Version (for argument sake, the NIV) of the Bible.

There is a way to do that, but the result look good only when a specific screen size, screen resolution, and e-Sword configuration are used.  Change any of those three factors, and the result are "ugly".

I've used an alternative form, which is almost as readable.Thanks to the intellectual midgets that work for the USPTO, it has been patented. Unlike Google, I don't have US$10,000,000 to waste on defending the use of a non-patent that was issued in violation of US Constitutional law, US Statuate Law, US Case Law, and USPTO rules and regulations.

Due to that patent threat, won't be publicly releasing those resources. (Nor will you be seeing them in screenshots I put up.)

jonathon

One thing that "worked" for me before (total accident) was creating a module that had T4 read as having multiple instances of Matthew 1:1.  Try it sometime.  Matthew 1:1 Hebrew.  Matthew 1:1 English.  Matthew 1:1 version.  Then convert it to a Bible file and see what happens.

I knew commentary resources could contain multiple records for the same verse.  I didn't know that Bible resources could.

Nonetheless, I don't see how one could have the words line up neatly underneath/next to each other using different record fields. I can see it producing something like that following, which isn't really what an Interlinear Bible should display/generate.

This is the proof of love, that he laid down his life for us, and we too ought to lay down our lives for our brothers.
Per ĉi tio ni konas amon:ĉar li demetis sian vivon pro ni; kaj ni devus demeti nian vivon pro la fratoj.
εν τουτω εγνωκαμεν την αγαπην οτι εκεινος υπερ ημων την ψυχην αυτου εθηκεν και ημεις οφειλομεν υπερ των αδελφων τας ψυχας θειναι
in hoc cognovimus caritatem quoniam ille pro nobis animam suam posuit et nos debemus pro fratribus animas ponere
Na konei tatou i matau ai ki te aroha, i tuku atu hoki ia i a ia kia mate mo tatou: he tika ano kia tukua tatou e tatou ano ki te mate mo nga teina.

jonathon

What else is important to a preaching calendar/plotter?

Integration with the Daily Office or Lectionary that one uses.

What ideas using current functionality would work?

A couple of years ago I proposed that sermons, and sermon outline resources are best constructed as two resource: Dictionary and Comemntary, with cross-references to each other.
The sermon, or sermon outline goes in the commentary under the scripture it is about.
The dictionary lists sermon topics, liturgical days, etc, and the Scripture the that sermon references.

Obviously, some sermons may not have an appropriate scripture reference. They can be included in the dictionary resource. Or maybe in an external Reference Library resource.

jonathon

I do not believe a copy of this file is on the internet.

TWOT, TWNT, and HALOT have been converted into e-Sword format. Said conversion was done without the knowledge, authorization, or approval of the respective copyright holders.

jonathon

I would like to see a calendar integrated into e-sword that would allow me to monitor the subject, Scripture references, dates and contexts of my messages.

The journal function is about the best that can be done for tracking time related information.
A topical file can be constructed to cover topic coverage: who, where, when.
A study note file can be constructed to cover pericope coverage: who, where, when.
Then periodically convert that data into commentary and dictionary format.

###

Maybe a calendar RFE is appropriate:

• Add scheduling functionality into the calendar;
• Import/export ICS formatted files into the calendar;

jonathon

how would one go about figuring out where it floated?

You'd use a specialized search engine.

Google is not being nice to me in this search...

Google is a general search engine that is unable to index roughly 70% of the Internet.

jonathon

I would also like a bible format for all the pseudiogrpha and apocrapha from the dead sea scrolls.

The Dead Sea Scrolls are under copyright. AFAIK, permission to distribute the English translation has not been granted.

Some of the pseudopigraphia are available as topical files, or Reference Library format.

There are around half a dozen Bibles that include the Anagignoskomena.

jonathon

There's not enough ancient languages in any free Bible software.

The major reasons for that situation:

• The writing system that is used is not supported by the software;
• The data is not available in electronic format under a license that allows for format shifting and third party re-distribution;
• There are no critical editions of the Bible in the language in question;
• Few laity know those langauges;
• Seminaries focus on Greek, Hebrew, Latin, and, maybe, Aramaic;

You could think of it this way. Would you learn Japanese in order to read the extant tenth century translation of the Bible into Japanese?

As far as the rest of your post goes, BibleSupport.com does not tolerate discussions about theology and doctrine.

jonathon