Text Format of Various Modules

[Brother Mike]

Bro. Tim

What would you suggest if making an encyclopedia type of modue. There will be a name and then a multi-line article following. Would a dictionary format be best or would there be something more specific you would use?

Thanks

[Tim]

The dictionary format would be best. That is what the International Standard Bible Encyclopedia is in and it works pretty well.

[2mc]

Regarding the text format for a Bible Module, I have three questions:

1. How do you format the verse notes--i.e., alternate readings / translations provided by the version translators?
2. Am I able to export an existing module--such as Webster's Revised Version--in order to make changes and then re-import into Bible Analyzer? If so, how do I do this?
3. Are the modules databases such that they could be opened directly by Microsoft Access or some other SQL server? If so, what format is used?

Thanks.

Matt

[Tim]

The files are SQLite databases and can be opened with any SQLite viewer.

Bibles with footnotes cannot be compiled with the built in Module Creator. They require additional tables and formatting that I do myself.

[darrel_jw]

Tim, can I include audio files as hyperlinks in modules? I was not seeing this i the user manual, although I could have missed it.

Darrel

[Tim]

Audio files would probably work but they would play in the system default audio player. I haven't tried it.

[stthomaschurch]

Is there a software or script that has been created to help in creating modules? I have alot of open source sermon content that would be great to add.

[Tim]

Bible Analyzer has a built in Module Creator for simple documents. There are basic instructions in the User Manual.

[epement]

Bible Analyzer has a built in Module Creator for simple documents. There are basic instructions in the User Manual.

The User Manual instructions say "The formatted text [for import into the Module Creator] must be saved as a plain ASCII text file."

Suppose I want to include curly quotes, curly apostrophe, em dash, en dash, copyright symbol, paragraph symbol, etc? Does the importer allow them to be entered in as either Windows-1252 or UTF-8 characters (both of which require the 8th bit or high bit to be set), or as named character entities (like "—"), or as numeric character references (like "“")?

Suppose I want to import Greek or Hebrew letters exactly? My guess is to use UTF-8, but I thought I'd ask first before trying. I am getting started at creating modules.

You warned us that the import module is not perfectly capable of handling UTF-8, but I'm hoping you can explain what things it allows and where it fails. Thanks in advance.

[Tim]

UTF-8 should work now. Give it a try. Also, named html entities should mostly work.