BaptizedBeliever

SteveD,

You go crazy screaming about words being added.  Are you serious?  There are words in parenthesis (alternate translations) and brackets (explanitory) are the added words.  It is obvious from the format that they are not to be considered as part of the inspired text.  Then you freak out because the word "signs" appears in Revelation 1:1.  And you put the Greek and KJV up to "prove" that it was added (and say it in a very hateful way).  Did you look at what you pasted in before posting your "outrage"?  The word "signified" (literally, told in signs or symbols) was in what you pasted as proof that "signs" didn't belong there. 

I gotta ask, can you ready Greek, or did you just copy/paste that stuff?

Speaking the truth in love... regardless of whether your assertions are valid or not, it was definitely not spoken in love.

-Brad

In some older writings (especially pre-1800), the hard "s" sound was represented by an "f" in the text.  I have many of these on my computer, and am wanting to find a way to fix the spelling (convert those "f"s with an "s") without having to do it manually.  On a short document, it might not be that bad, but I've got 300+ page books that are waiting for conversion.

Is there a macro that can do this?  Or am I just pretty much stuck?

-Brad

I have some thoughts (believe it or not) on this matter. 

#1.  There are costs to producing things.  Printing Bibles costs money.  Translating the Bible costs money, because someone (many someones) are spending a lot of their time working on it.   The same thing is true with Bible commentaries--having written commentaries on a couple NT books, I can tell you that they are extremely time-consuming. 

#2.  Regarding commentaries, they are not God's word.  They are basically preaching on paper (or teaching on paper).  It takes more work to write a commentary than it does to write a sermon (I do both, so I know).  Yet, I'd be willing to guess that most of the people who cry out that these commentaries should all be free would at least hesitate to say the preacher shouldn't be paid for his preaching.  Didn't God inspire the phrase "the workman is worthy of his hire"?

#3.  I think the extent of the copyright laws in the US are ignorant, but that doesn't mean I can disregard them.  I also think the 25 mph speed limit in front of the church building here is ignorant, but that doesn't mean I can violate because I think it's ridiculous.  We obey the laws of the land because God says to.

#4.  There are VERY VERY VERY few Bible translations that you can't get a free, legal copy of somewhere.  All the big ones are free online (KJV, NKJV, ASV, NASB, NIV, NLT, ESV, etc...).  Most of the lesser-known ones are also free online--AND in e-Sword format (MLV, SENT, etc...).  Most Translations (especially the big ones) can be had for free in print if you contact Bible societies or call some of your local churches.

People complain frequently about "they're charging money for this Bible.  God's word should be free!"  That sounds good to those who don't bother to think. 

So what you're saying is that people should starve and not be able to pay any bills while translating the Bible, and that companies should actually be in business to lose money by publishing books and then not be able to recoup the costs.  And you're also saying that you're not happy enough with the fact that it is free to read online (BibleGateway.com has most of them), and that a print copy of almost all translations can be had for free if you ask the right people.  You demand that it has to also be free in e-Sword.  Demand that people put in the work and then demand that they don't get paid for it.  If your employer came to you offering that deal, would YOU take it?

-Brad

My wish list for the next e-Sword update:

1. Make it where i can open the "search" window (after having used it once this session) and be able to type in my next search without having to manually click on the box and delete the previous search.  As it is now, I open the search window and start typing, and as soon as I hit the spacebar, the whole thing closes...and it didn't record what I typed.  This is my biggest complaint.

1a. In the search window, put the binoculars button (the search button) next to the search box where you type the stuff in.

1b. Put an "x" at the top of the search window so we can close it out normally instead of having to click "okay" or "cancel."

2. The ability to create Bible modules with the option for tooltipped cross-references after each verse.  As it is, you can't tooltip a Bible module.

3. The ability to create Bible modules with the footnotes built in as a tooltip-like feature (like the NASB module). 

I think that's it for now...

-Brad

In ToolTip NT, click "modules HD", "Define Module Variables" and then fill in the info.  After finishing the translation, click "Modules HD" and then "Save BBLI module."  Then use iFunBox (an iPhone app) to move the new module to the proper folder.  Should work just fine.

-Brad

It is never illegal to cite a source, whether you own a copy or not.

Looking forward to it.  I ran it through the OCR software, but don't have the time to double-check the whole thing to make sure it matches up with the standards we try to set here.

I hope the rtf is useful in your converting the file, James.

Here's the file in rtf format, with the ÷ marks in place and the document tooltipped.  There are (especially in the "notes" section) some things that could be cleaned up, but perhaps this will give someone a good head start on it.

-Brad

My personal preference when doing a Bible file is this:

÷

Genesis 1:1 text

Genesis 1:2 text

Exodus 1:1 text

Leviticus 1:1 text

etc...

notice that the ÷ only shows up once in the entire document.  Each new verse must begin with a paragraph break (aka, hit enter at the end of the previous verse).  Tooltip reads every paragraph break as a new verse.  So, if you are making a Bible translation where you want  to show poetic verse (as in, 3 or 4 separate lines in one verse), each new line in the verse must be made with a line break (shift-enter) and not a paragraph break.

Then, in Tooltip, just save it in bblx format, using the book chapter:verse setting.

If you have other questions, just ask.  I've done enough of these that I have most of the problems figured out.

-Brad

I'll work on this.  Give me about two weeks, and I should have it ready.  Lots of projects, but I don't think this should be too difficult.

Open your file in a web browser (since it's in html format), highlight all the text, and hit ctrl-c (copy).  Then paste the whole thing in MS Word.  If there are any links, they are easily removed by hitting ctrl-a, and then after everything is highlighted, hit ctrl-shift-f9.  Save it as an rtf file and open it in T3 or T4 and go from there.

Those are all under copyright, unfortunately.

I, for one, wouldn't mind not having to have my NET, HCSB, NKJV, etc... commentary tabs taking up space if I could get a version that had them all in the bblx file.

Of course, that'd almost double the size of some bblx files, I'd wager.

Rob,

There IS a way to do it.  Unfortunately, I don't know how.  The latest NASB for e-Sword that I have has the footnotes tooltipped in the Bible file itself.  I asked Josh about doing this once before, but at least at that point, he wasn't sure how it was done.

Sorry.

-Brad

I understand that e-Sword does, but does the iPad version of e-Sword support it?  If so, I'd be happy to try to help.