50 replies to this topic

[Atheist Rob]

Gerhard, where did you get the bible from? It it the one that you downloaded from e-sword.net (or from within the e-sword program)? As far as I know, Rick encrypts ALL bibles that he makes available on his site, including public domain bibles. If that's the case converting will not work. You might try to look if TheWord has one available as well and convert that with MySword's conversion tools (described in step 7 of Peter Pellerin's instructions).

Regards,
Rob

[Gerhard van Dyk]

Firstly, thank you for the replies guys, much appreciated. Using e-Sword for the last 6-years and got a tablet now. Managed to download and install mySword and several modules but needed the Afrikaans (mother-tongue) version as I was using it in e-Sword. Rob, thanx for the advice, will try it out now and will let you guys know.

Kind regards.......(",)
Gerhard

[forsblom]

How to convert .bblx into .myword with Hex editing.

 

Basicly finding bibles in .txt format isn't so hard, a simple search on google gives you lot of hits.

 

I used e-Sword ToolTip 3.50 for a bible I wanted to create. It requires the bibletext to have one verse / line in order to create the bible, and ofcource the right names for the different books (as displayed in e-Sword).

 

Anway, I fired it up, conversion went smooth no errors. I renamed the file to .mybible, copied it over and opened it up, aaand...

 

Bibles verses looked like this:

\uc1\lang1053\f0\fs22 "bibleverse" \cf0\i0

 

There was unwanted text infront and behind the bibleverses, plus special characters such as å,ä,ö was displayed wrong.

 

I digged around for a solution and found NONE. Then I came up with what could be a possible solution: Hex Editing.

And, It worked! It's a bit tricky, but I wrote step to step instructions of how to do it.

 

You can download the Word document: -> here <-

Edited by forsblom, 02 February 2013 - 07:04 PM.

[forsblom]

Hi, it didnt work for the AOV.bblx (Afrikaans 1953 Bible). Gives me an error Unable to convert BLOB to string........
Does anybody have a suggestion for me?

I'm working on it now. It will take some Hex editing, beacause Africaans has so many special characters, but I should have the Afrikaans 1953 mybible version ready for you next week.

Edited by forsblom, 03 February 2013 - 01:28 AM.

[Katoog]

It is easier to copy the whole Bible manually and save it in RTF format (I did the same with the encrypted Webster Bible)

Then edit with Tooltip NT:

 

#define description=Afrikaans Ou Vertaling

#define abbreviation=AOV

#define comments=1953 Afrikaans Ou Vertaling (Old Translation)

Copyright © 1953 Bible Society of South Africa
 

#define version=1

#define strong=0

#define right2left=0

#define ot=1

#define nt=1

#define font=DEFAULT

#define apocrypha=0

 

÷

Gen 1:1  In die begin het God die hemel en die aarde geskape.
 

Edited by Katoog, 03 February 2013 - 05:45 AM.

[pfpeller]

The option I usually use is to backward migrate the bblx to theWord.  The theWord file is just a text file.  

 

In order to migrate the bblx to theWord, you have to use a program called BeST. http://www.biblesupp...ile/2524-best2/

 

This program only works in Windows XP or 32 bit windows 7 machines.  If you do not have one of these machines, you will need someone to complete this step for you.

 

You can open up the theWord bible file in Notepad++ and use search/replace to remove unwanted charachters (if there are any).

 

You then use the MySword migration tools to migrate the Bible to MySword.

[forsblom]

The option I usually use is to backward migrate the bblx to theWord.  The theWord file is just a text file.  

 

In order to migrate the bblx to theWord, you have to use a program called BeST. http://www.biblesupp...ile/2524-best2/

 

This program only works in Windows XP or 32 bit windows 7 machines.  If you do not have one of these machines, you will need someone to complete this step for you.

 

You can open up the theWord bible file in Notepad++ and use search/replace to remove unwanted charachters (if there are any).

 

You then use the MySword migration tools to migrate the Bible to MySword.

 

The problem when trying to convert the .bblx file is:

 

"The file you chose cannot be opened by BeST 2. Either you do not have Read and Write access to the file, or it is protected by a password and cannot be accessed by BeST."

 

So I have no choice other than to Hex Edit it.

[MJ_]

Can someone tell me how different is the format of the txt or rtf files that you one would use to create a mysword bible module as opposed to an esword bible module.

I've found that some modules that I have will convert to mysword just by changing the extension name.  However, those that I have complied with the tooltip editor, although it will open, contains a significant amount of rtf coding for each verse.

[Katoog]

The RTF or txt file is the source for the  BBLX file without encryption.

After copying the Bible and the edit for the BBLX parameters need you only to convert RTF to BBLX.

ToolTip NT / modules /Bible/save Bible file book chap:verse

 

Don't forget that every verse or book must end with a "hard Return"

And use ComparaBiblias with the KJV as the first Bible to check if you forgot or duplicate Bible-verses

[forsblom]

Gerhald:

I've completed the conversion of the Afrikaans 1953 .bblx to .mybible.

Send me an PM with your E-mail, and I'll send it to you. Also if anyone else is interested they can have it as well.

 

I noticed you have not been online on the forum since 30th Oct last year, so I post here so you can get the news.