Bible Module Footnotes

GeorgeCurtis

GeorgeCurtis

Member
Messages
42
I'm adding footnotes to a Bible module using the curly braces {} and "; HAS FOOTNOTES" at the beginning of the file per the Forge manual instructions. When I import the module and toggle Show Footnotes, they show in the text exactly the way I added them, i.e. "{footnote}" instead of showing them as actual footnotes in the Bible margin area. I have done this successfully before. Any suggestions?
 
Here's a snippet from one I did a while ago. I just ran the whole Bible through forge again and it worked fine, putting a footnote at the beginning of the verse and the note in the margin area without the {}

; User Bible module
; TITLE: King James Bible 1900 Edition
; ABBREVIATION: PKJB
; HAS FOOTNOTES
$$ Ge 1:1
{Creation}IN the beginning God created the heaven and the earth.
$$ Ge 1:2
And the earth was without form, and void; and darkness was upon the face of the deep. And the Spirit of God moved upon the face of the waters.
...

I have a footnote on each 1:1 verse in this Bible.
 
GeorgeCurtis said:
I'm adding footnotes to a Bible module using the curly braces {} and "; HAS FOOTNOTES" at the beginning of the file per the Forge manual instructions. When I import the module and toggle Show Footnotes, they show in the text exactly the way I added them, i.e. "{footnote}" instead of showing them as actual footnotes in the Bible margin area. I have done this successfully before. Any suggestions?
Click to expand...
How (or can you) add footnotes when you are not using Forge?
 
Regie said:
How (or can you) add footnotes when you are not using Forge?
Click to expand...
There is no way to build a Bible module without Forge.
 
On the USER tab, just click to CREATE USER BOOK or CREATE USER COMMENTARY. You then type in NEW TITLE and NEW ABBREVIATION. Then a little window pops up for me to select which module sets should include this library module. Next you begin by clicking on "add new entry."
 
Regie said:
On the USER tab, just click to CREATE USER BOOK or CREATE USER COMMENTARY. You then type in NEW TITLE and NEW ABBREVIATION. Then a little window pops up for me to select which module sets should include this library module. Next you begin by clicking on "add new entry."
Click to expand...
I think I see now. As far as I know, I have never made a new bible module - only books or commentaries.
 
Regie said:
On the USER tab, just click to CREATE USER BOOK or CREATE USER COMMENTARY. You then type in NEW TITLE and NEW ABBREVIATION. Then a little window pops up for me to select which module sets should include this library module. Next you begin by clicking on "add new entry."
Click to expand...
Ok, but I wonder if you are losing something by not compiling it via Forge. Not a criticism, just a question of curiosity.
 
So to clarify, there is no way to create or edit Bible modules within the SwordSearcher user interface. You must use Forge for that, and there is a documented way of creating footnotes within Bible text so that they work correctly in the Bible margin.

None of that is relevant to creating books or commentaries. I highly recommend using the in-program features for making books and modules. There are scenarios where Forge is a better solution (if you have large amounts of text to compile and you know how to pre-process it for Forge).

Creating "linked footnotes" in a book/commentary module entry like some of the included modules have requires editing the HTML code by hand.
 
Brandon Staggs said:
So to clarify, there is no way to create or edit Bible modules within the SwordSearcher user interface. You must use Forge for that, and there is a documented way of creating footnotes within Bible text so that they work correctly in the Bible margin.

None of that is relevant to creating books or commentaries. I highly recommend using the in-program features for making books and modules. There are scenarios where Forge is a better solution (if you have large amounts of text to compile and you know how to pre-process it for Forge).

Creating "linked footnotes" in a book/commentary module entry like some of the included modules have requires editing the HTML code by hand.
Click to expand...
Thanks @Brandon Staggs
 
You must log in or register to reply here.
Back
Top