DoctorDaveT.com
Bible
Study

Welcome   l   Doctrinal Statement   l   Copyright Policy   l   Contact DoctorDaveT   l   DDT Twitter

Copyright 2010-2014

Bible Reference

Newest Modules

Q&A Forum

 

Doctrinal Studies

 

Commentaries

 

Dictionaries

 

Expositor’s Bible

 

ICCNT Modules

OT Studies

NT Studies

 

 

TW Premiums

MORE Modules!

KJV Modules

Converting Resources to theWord

 

Costas (the software creator of theWord) has created a very nice tool that is used to convert some resource types to theWord’s format. While this tool is multi-functional - and can be used to create new resources, too - this blog post is simply going to be about bringing eSword resources into theWord format.

 

I would like to inform folks right up front that Costas’ converter will not convert “locked” modules. For instance: any modules purchased as a “premium” eSword resource will not convert to TW. It’s a shame, because eSword has some nice premium stuff. Oh well.

 

Almost all of the modules that I build here at DDT I release for both eSword and theWord. Not all module builders do that, however. You may occasionally find modules built for eSword that you want for theWord. With these instructions, you’ll be able to convert just about every eSword module (except for “premium” resources and .refx files) you’ll ever find.

 

Simple Instructions For Savvy Computer Users

 

For those of you who are a little more computer savvy, I’ll simply list the steps here. Everyone else (and I do mean everyone else, because it’s relatively easy to do): I’ll amplify this list with further instructions and pictures just below.

 

1. Download the TW Converter by clicking here. Install the converter.

 

2. Open the Converter and click the “e-Sword” tab.

 

3. Click the “browse” button and navigate to the eSword resources you want to convert. Batch converting is not only allowed, but encouraged!

 

4. Click the “convert” button and navigate to the folder where you want your resources to be created. (NOTE: sometimes modules don’t convert right the first time. Do it a second time, and delete the first module that was built.)

 

5. Install the module as normal - because the conversion was that easy and is done.

 

Simple Amplified Instructions For Everyone Else

 

OK - for the rest of us, here are the amplified instructions.

 

1. Download the TW Converter by clicking here. Install the converter.

 

The Installation will automatically install the converter to the main TW installation folder, which is C:\Program Files\theWord\. While you can put the converter anywhere, it’s probably simplest just to leave it right there. When the installation is finished, you have to go get it. Here’s how:

 

Open your windows explorer. Navigate to the C:\Program Files\theWord folder. Look for the file called “twimport.” That’s your file. RIGHT-Click it with your mouse, and choose “Create Shortcut.” Win7 probably won’t let you put a shortcut here - and it should ask if you want it on your desktop instead. Choose “yes” - and then your shortcut is ready to use. Navigate back to your desktop, and there it is! To open the converter, simply double-click the desktop shortcut.

 

2. Open the Converter and click the “e-Sword” tab.

 

OK - so far, so good. Take a “mouse over look” at the picture over here to the right....

 

3. Click the “browse” button and navigate to the eSword resources you want to convert. Batch converting is not only allowed, but encouraged!

 

Most/All of your eSword resources you’ll want to convert are located in the “C:\Program Files\e-Sword” folder. If you go there, you’ll find all of your files. If you only want to convert one resource, just click it. You can also “shift-click” a range of modules, or “ctrl-click” multiple resources.

 

4. Click the “convert” button and navigate to the folder where you want your resources to be created.

 

Generally speaking, if you’re doing one module at a time, I’d recommend converting the modules right to your desktop. If there are any difficulties with the converter (keep reading...), it will be easy to take care of the issues. If there are no problems, then you cut/paste them right into the proper folders. If you’re batch converting, then here’s where you’ll want to pay a little bit of attention.

 

BIBLES - the TW converter does not convert eS9x+ Bible modules (*.bblx). It only converts eS8x and below Bible modules (.bbl). Costas is of the opinion that there are already enough bibles available. If you have a Bible version you want converted, go to the main TW Bible site and look for it there. If you can’t find it there, check out wordmodules.com - a great source for third party TW modules. By the way - I agree with Costas. Not only are there enough English Bibles available, I’ll go one further: there are too many. But that’s for another blog....

 

Once your Bible module has converted, you’ll need to put it in a special folder: C:\ProgramData\theWord\Bibles. NT Bibles end with “.nt”; OT Bibles end with “.ot”; and full Bibles end with “.ont”.

 

ALL OTHER MODULES - the TW converter handles conversions for eS7-10x (except for the special .refx module type). And you can do all of the resources at one time if you wish. All modules that are not Bibles should be placed in the “C:\ProgramData\theWord\Books” folder.

 

CONVERSION DIFFICULTIES - For some reason unknown to me, sometimes I’ll have a conversion that doesn’t work the first time, and I get an error dialogue. I immediately reconvert the module, and it almost always works correctly the second time. (Rarely I’ll have to do it a third time, but by then it almost always works). Again, not sure what the problem is. Here’s is what you need to know. 1) When the error happens, don’t delete the module that was built. 2) Run the converter again. If successful, the good module will be missing the middle suffix (.gbk for book modules; .cmt for commentaries; and .dct for dictionaries). So you’ll have two files that will look like this:

 

abcdefg.gbk.twm

abcdefg.twm

 

After you’ve run a successful conversion, 1) delete the first file; and then 2) rename the second file by adding the middle suffix to it. Simply right-click the file with your mouse, and choose “rename.” Then add the “.gbk” (or “.cmt” or “.dct” as the case may be) where it belongs. Easy as pie.

 

5. Install the module as normal - because the conversion was that easy and is done.

 

Now all you need to do is put the module in the correct folder, and voila! You’re done!

 

Whether you want to migrate your entire library, or just convert a stray module, Costas’ converter is very well done. Thank you, Costas!