14 replies to this topic

[BaptizedBeliever]

Experts,

 

I'm looking for a way to convert a .bblx to TheWord format without losing the formatting (color, superscript, soft-breaks).  Any ideas?  Or, if you can tell me how to convert the rtf to theWord, that'd be helpful.  Thanks.

 

-Brad

[patchworkid]

Hi 

 

I  would like to know that myself.

Here is a sample of Gen 1:1 of my Study bible in two formats of the Word bible software

 

version one is my first bible http://www.wordmodul...tudy-bible-set/

 

and version two is my new up to date version

 

Version one

 

<TS1>Original Earth<Ts><n><CL>In the beginning<n> God<n> <WH430> <NAVY>(prepared, formed, fashioned, and)<Navy> created<n> <WH1254> the heavens <WH8064> and the earth<n> <WH776> <NAVY>(perfect<Navy><n><NAVY>, complete and to be inhabited<Navy><n><NAVY>)<Navy>.

 

Version two

 

<font color="#800000"><b>Original Earth<FR></b>^(n)<Fr><CL>In the beginning<FR>⁽ⁿ⁾ God <font color="#808000">אֱלֹהִ֔ים</font><FR>^{(n)<Fr><font color="#008000">H<WH430></font><font color="#000080">}(prepared, formed, fashioned, and)</font> created<FR>^(n)<Fr><font color="#008000">^{H<WH1254></font>}the heavens <font color="#008000">^{H<WH8064></font>}and the earth<FR>^(n)<Fr><font color="#008000">^{H<WH776></font><font color="#000080">}(perfect<FR>^{(n)<font color="#000080">}, complete and to be inhabited<FR>^{(n)<font color="#000080">})</font>. </font></i></b><u>

 

The codes is very different (I am trying to figure this out myself. (to have it in all formats)

this will help others like http://www.biblesupp...-new-testament/

this person had problems (MySword) as well. I think he got it fixed with some help.

 

Can someone Please help us to get this corrected.

 

check this out:  http://www.theword.n...tools&l=english

 

 

thanks a lot

Patchworkid

Edited by patchworkid, 26 October 2013 - 05:13 PM.

[larryj999]

Replying to PWK ...

 

I love your work. Please keep it up.

 

"version one" is taking advange of TW tags and verse.rules. <TS1>...<Ts> applies heading format to the text. Also, the same with verse.rules. e.g., <NAVY>...<Navy> which will defined elsewhere in the module. This is perhaps the most powerful feature with TW bibles. They allow the creation of custom tags to allow more efficient use of formatting. Define once, use many times. One KJV bible was 50% smaller with appropriate rules applied.

 

"version two" also also includes some Hebrew.

 

It is hard to say much without seeing more, but I would be happy to take a look and see if I might help, if I could get a copy to review. If you can't post it here, perhaps one of the moderator's could forward my email address to you. Josh Bond or JPG might have it.

 

Regards,

ALbeSh

[patchworkid]

hi Larry999,

 

Thank you for response and liking my work.

 

Yes I would like some help in making my Bible set into the Word and MySword.

 

thanks a lot 

Patchworkid

[larryj999]

I think we worked out a procedure for converting a BBLX to a theWord OT\ONT. It's probably not for everyone, or for every bible, but Niobi's project is fairly complex, and we got most of the way there with this method. Additional software is required, but if you are working with modules, you may already have it.

 

GENERAL: 

 

1. Starting with a BBLX file read with ToolTipNT, it was saved as an RTF file. 

2. The RTF file was converted to an HTML file with defined styles. 

3. The styles are then converted onto theWord verse.rules. 

4. The HTML style tags within the bible text are then converted to correspond with the verse rules.

 

MORE SPECIFIC:

 

1-Read:

In ToolTip Tool NT, read the BBLX from "Modules" | "Bible" | "Read ...". Save it to an RTF: "File" | "Save" or "Save as".

 

2-Convert the RTF to an HTML

theWord bibles are text files that use HTML-like codes. Convert the RTF to an HTML file with defined styles. The styles can be defined internally, or as a separate file. If internal, it will be cut & pasted into another file for editing. I used the ActionTest demo, http://www.trichview.../actiontest.zip. It's free and makes a nice simple file with internal styles.  

 

Once the styles have been removed for editing, clean out everything except the bible text. Make sure that the resulting file is in a verse-per-line format. 23,145 lines for OT. 31,103 for ONT. This will become the ONT file.

 

3-Convert the styles to verse.rules.

A typical style produced by ActionTest looks like this:

span.rvts20
{
 font-size: 12pt;
 font-family: 'Arial', 'Helvetica', sans-serif;
 font-weight: bold;
 color: #800000;
}

It is converted to the verse rule:

verse.rule="<X20>(.*?)<20>" "<font size=0 name=Arial, Helvetica, sans-serif color=#800000><b>$1</b></font>"

Note that the style number was kept. The opening tag only is prefixed with an X. This will important later with the text tags. TW does not use points for text size, so: 12 pts. is size=0. Since 0 is the default it could have been left off. Add or subtract for different sizes. See the TW: "tw3-bible-module-spec.doc" for more information on this.

 

In the trial, 83 styles were produced. This is too much for hand editing, so regular expressions were applied with some fixing afterwards. The text editor Editpad Pro is an outstanding tool for this.

 

4-Converting the tags within the bible text.

This is quick, but the only way I know how to do this is with a regular expression. The regex will also work in the free Notepad++.

 

(a) The HTML text:

<span class=rvts1>In the beginning</span>

( The regex:

Search:

 <span class=rvts(\d+)>(.*?)</span>

Replace:

<X\1>\2<\1>

© Will produce something that looks like this:

<X1>In the beginning<1>

Note that the number corresponds to the verse.rule. The verse.rules will now apply to the text tags in the module.

 

5-Finish:

Skip a few spaces. Paste the edited verse.rules at the end of the file. Add some TW bible ID. Save to an OT/ONT file.

 

To Do

Strong's Numbers, Notes fixup.

 

Good luck,

 

ALbeSH

 

 

 

[patchworkid]

hi Larryj999,

 

thanks a lot for all your help.

Patchworkid

[patchworkid]

Hi BH, and others.

 

what happens if you save the file in T4 as HTML file.  will it convert over to the word better?

 

thanks

[larryj999]

TNT4 doesn't save HTML with styles. It could be worked out though. The advantage to working with styles is that the patterns are already derfined for you. With HTML style -> TW verse.rules, you get a file about one-half the size. Then by changing a verse.rule in one place, you can change all instances of that particular style in the bible text.

 

ALbeSh

[Denis Ganin]

Is there a way to convert the other way around? From TheWord bibles to bblx?

Any work in progress?

I'm a professional IT person and used to program in C years ago.

Willing to help any way I can

[Josh Bond]

Is there a way to convert the other way around? From TheWord bibles to bblx?

Any work in progress?

I'm a professional IT person and used to program in C years ago.

Willing to help any way I can

 

theWord's bible is just a text file, with one verse per line.

 

You could open that text file in ToolTip NT. Then you could generate an e-Sword module. You would have to reconfigure the module information and insert ToolTip NT's required header information.

 

The only variable not accounted for are theWord's html type of tags indicating color, text style, etc. The tags themselves would probably show in the e-Sword version. 

 

 tw3-bible-module-spec.doc   74K   37 downloads