Searcher

This topic has been quiet for a very long time!  I may be the only person left on the planet still using BeST2!  But that is coming to an end.  I discovered that BeST2 has been messing up my files since about 2010!  It only has happened on complete Bibles and Interlinears.  What it does is skip 2 Corinthians 13:12, and move the text to verse 13.  It then takes the text from verse 13 and moves it to verse 14.  It then appends the text from 14 as an extra line.  You can see it here:

 

I stayed with e-Sword 10 because I could not reliably convert my interlinears to the BBLI format.  I didn't have an iPad or iPhone and I was happy with what I had.  But now e-Sword runs quite well on Android, and I am trying to move everything over.  I have been importing the BBLX files into ToolTip Tool NT, and then saving them as BBLI files, but each and everyone would go bonkers on 2Co 13:12, so I looked into it.

 

I already have my workaround, but I am sharing this with the Forum just in case there are any others who may have used BeST2 in the past.

Wine does work on MAC.  I have installed it on mine along with e-Sword and it works without pain.  The link below gives details of how it can work.  Wine is best known for working on Linux, but it is also for MAC.  David Baumgold's article may be of assistance.

 

http://www.davidbaum...rials/wine-mac/

 

As for installing e-Sword, I followed the instructions found on the "Pentecostal Blogger".  This following link will take you there:

 

http://www.pentecost...ord-on-the-mac/

 

There is also this thread here:

 

http://www.biblesupp...esword-for-mac/

 

Hope this helps!

Someone mentioned the following and it works on tablets nicely.

 

http://www.lovesumme...epointer/en-us/

Thanx!  It works nicely.

I just got a new Dell Venue Pro 8 that runs the full version of Windows 8.1 (not RT).  It is snappy, has a beautiful (though only 1240 x 800 resolution) screen, and easily installs the latest PC version of e-Sword.  The only problem I am running into are my clunky fingers and navigating with them on-screen.  Too bad there are not skins that could be used to "fatten" things up a bit.  Has anyone else run into a nice way to work around this problem?  Suggestions would be appreciated!

Sadly, Microsoft does not support Windows Mobile 6.5 or earlier programs on either Windows Phone 7 or 8.  I too greatly lament the fact that I cannot transfer my Pocket e-Sword files to my new Nokia Lumia 521 running Windows Phone 8.  I read that Microsoft provided tools to assist in porting programs, but since Pocket e-Sword is not under development nor supported, I imagine that is not going to happen.  Has there ever been anyone who has started an open source version?

 

I have created a number of specialized files (such as Interlinears) that run on the pocket version of e-Sword.  Does Olivetree allow you to create your own modules?  How well does it support Greek and Hebrew?  Besides creating Bible modules, can you create dictionaries and commentaries?  Any input and direction would be most appreciated!

 

Max

As noted above, these codes allow the reader to quickly understand the grammatical role of each word.  There are a number of different Greek texts that use them, including for the Septuagint (LXX).  As a help, I created a chart that lists all of the codes, including the ones used in the LXX.  It is based entirely upon Dr. Robinson's notes.

 

Dr. Robinson is an advocate of the Majority Text, but is well aware of the TR's limitations.  That is why he created the Byzantine Textform, which is also available.  My humble suggestion would be to use it if the TR tradition is your preference.

 

 Greek Parsing Notation.pdf   29.29K   12 downloads

 

Please feel free to use (with care) and share.

BH,

Many thanx for your useful updates.  I can report partial success.  I have attached section 3 of the interlinear to illustrate what is happening.

To create the file, I used the following steps within T4.  First I ran the Strong's Numbers Fixup tool.  That was followed by the Unicode Greek fixup tool.  And then by the Reset ALL Character tool.  After that I created the module.  Some of the text came out just fine (see Romans chapter 8) and some just as before (see Romans chapters 1-7).  I tried changing the font size within e-Sword, but to no effect.

After running the Reset ALL Chars, I observed that there was not uniform line spacing.  The line spacing in the areas I checked were set to 13 points, but it resulted in part of the bottom of the characters being truncated.  So I selected all, and set line spacing to single.

I might also mention that when the Strong's number tool is run, upon completion it selects (highlights) the first Strong's number of the file.  If I forget to unselect it and immediately run the Greek Unicode Char fixup it assumes that it should only do its job within the selected text.  Not really a problem, just a minor irritation (with myself for forgetting).

Max
 Interlinear1.zip   1.72MB   7 downloads

Another good and free converter is Calibre:

http://calibre-ebook.com

I do not normally use Microsoft Word for creating Bible modules.  However, I am working on one that has unusual and varied special formatting.  I have completed the Bible using the format "Book Chapter ¶ Verse Text".  I have been using BeST to import Bibles, but I am having trouble with this one.  The biggest issue is that of transferring text in small caps (lower case letters printed as small upper case ones).  I have attached one book so that you can see the problem.  I have tried exporting to XML, I have looked for a macro that would put RTF format symbols around the special text, all with no success.  Any suggestions?  Many thanx, Max