iscnetwork

Thank you very much for your insights.

In short we did the Tooltip thing with the .rtf file.
Converted module to .bbli format.
Opened in SQLite, converted to .sql

Renamed to .txt

Find/replace on some patterns to add the HTML goo needed.

MLV 2021 will be up shortly after the proofreaders look over the results.

The superscript should be smaller by rights but in the display it is not, even though the mlv.rtf file looks perfect in Word or Writer. (See 1:18)

I have some time today before service calls tomorrow, so I am going to experiment with the .bbli file.

I wish ToolTip just did HTML files.  I could go from Word Perfect with one click to HTML.

Thank.

Sorry to hear about Brent. 
Sorry but life got in the way on my end.

I did similar and exported to CSV just to see the embedded coding which I thought was supposed to be HTML now and not this proprietary coding.

Our biggest concern is 10 pt. font on all the superscript & blue content but I don't know the codes...

Mat. 1:1
40,1,1,"{\cf2 {NOTES: If your plans are to read the entire N.T., start in Mark. Please read the \u8216?Definitions\u8217? Section and other non-bible sections. In this translation Old Testament names will be in their Old Testament form.}}\line

Currently Blue but needs to be 10 pt. font size.

Then on our for* [* is our universal footnoting as you know]

for{\super *}
 

What would be the coding for making the * 10pt size and stay superscript? 

Thanks so much for your help. Butch

Brent,

I have been using Tooltip for almost a decade.  But now it will NOT keep my 10 pt font size and then recently {curly braces} disappear in the final .bblx file.

{Mar 15:6-19 & Mat 27:15-30 & Joh 18:39-19:16 Fri., April 7, 30AD.}  (blue & 10 pt)

to

Mar 15:6-19 & Mat 27:15-30 & Joh 18:39-19:16 Fri., April 7, 30AD.  (still blue but 12 pt.)

how do I fix the .rtf input file for the compiler?