-
Notifications
You must be signed in to change notification settings - Fork 6
Menu Items
Access this dialog through menu View / Project notes.
In this dialog settngs can be made that influence which project notes are displayed, and how they are displayed.
The top part of the dialog deals with the notes selection, that is, which notes will be selected for display.
The bottom part of the dialog deals with the notes display, that is, how the notes will be displayed.
A note must satisfy four conditions to be selected for displaying.
The first condition to be satisfied is which reference or references the note belongs to.
The second condition is the date on which the note has been edited.
The third condition is the category to which the note belongs.
The fourth condition is the project to which the note belongs.
For example if you wish to select all the notes in the current chapter that have been edited today, then tick these conditions: "Notes that have the current chapter", and "Notes edited today", and "Notes of category All categories", and "Notes of project any".
Another example. If you wish to select all the notes that fall in category "For church", then tick these conditions: "Notes that have any verse", and "Notes edited at any time", and "Notes of category For church", and "Notes of project any".
"Order center around current reference". When this is ticked, Bibledit makes an attempt to display notes ordered by how close they are to the current reference. That is, for example, if the user display Matthew 10:2, then the notes that are nearest this reference are displayed visibly, and notes further away are moved away a bit.
"Include in title - project". If this has been ticked, then also the name of the project the note belongs to will be shown in the blue link, in the Notes Area.
"Text - summary". Only the first few words of the note are displayed. This allows many notes to be displayed in a small space. This is supposed to give a better overview of which notes are available.
"Text - add text of the references". If this is ticked, Bibledit displays not only the references of the notes, such as Matthew 1:1-2, but it displays the actual text of those references too. This has been found useful in cases that worksheets had to be produced for a team discussing some notes.
Build a concordance of the current version, all books. Display a new window with all the words, one tab sorted by frequency and the other sorted alphabetically. Clickable links to the verses where the words occur.
Greek, English versions of the Bible keyed to the current editor verse. Cross references with clickable links.
Bibledit shows the outline of the book that is being edited.
The outline can be seen in the Outline window, accessible through the View menu.
All the headers and titles that are in the book are visible there, with the chapters and verses they start with and end with.
The header or title that has the cursor will be focused.
If you double-click on any header, or press Enter, the chapter belonging to that will be loaded in the editor.
Notes.
-
Headers and titles that are in chapter 0, that means, before chapter 1, do not show up as such, but as chapter 0 without any verse-references.
-
There are no heading endmarkers if the heading is followed by another one.
Rearrange all the windows in a nice way, with Bibles on the left 2/3 of the screen, and resources in the right 1/3.
Links to web tools (and on Windows, Bibleworks) that open those tools to the verse that is currently focused in the editor.
This dialog comes up when choosing menu Insert / Footnote or Endnote or Crossreference.
The dialog aids you while inserting bible notes.
The numbering can be set to automatic, or no numbering at all, or a certain character.
You can set whether to automatically insert the current reference in the Bible note. If you do insert it, then you can set whether to include the chapter number, and the verse number, and what the separator between them will be. A suffix can be entered too. It will show how this is going to look in the text.
Note content can be added in the dialog too. Press the "Add content" button. A new area will be added that allows to insert a marker with its content.
The marker to be used can be selected in the combobox.
The content to be inserted can be typed in the text entry.
If "Remember content" is ticked, this content will be remembered for the next time you insert a Bible note.
To get rid of this content area, press the "Remove" button.
Tick this function to tidy the references you insert. You can influence the process in the settings.
It is possible to save a certain configuration in a template. The "New" button will make a new template, and the "Delete" button will delete the current one. If no template name is given, the default one will be used. Data is saved in a template only on pressing the "Ok" button.
The dialogs for inserting Bible notes have been designed to improve efficiency and speed.
When the dialog opens, the first entry gets focused, and you can type text there. On pressing Enter the next entry focuses, and so on, until the Ok button gets focused. Pressing Enter again inserts the note.
The tool can be accessed through menu / Tools / Transfer project notes to text.
This tool does only one thing. It copies the project notes into the currently opened project.
It does that by going through each verse of the project that is now opened in the editor. At each verse it looks at which project notes would display if that verse were visible in the editor. It then copies the text of those notes into the text of the project. It the text of a note is copied into the project, it does not overwrite the data that is already in the project, but it just appends it.
This tool can be useful in cases that somebody wishes to have some way of printing a subset of project notes along with the text, so that checking questions could be printed on the same page as the verses they refer to. To do this, the notes can be imported in some temporal project, and then a "Parallel Bible" could be created that includes that temporal project that now contains the notes.
Opinions vary on whether origin references in footnotes and crossreferences are useful. Some say that they are useful because they indicate the verse to which the note belongs. Others say that these references are just clutter and that the information is clearer without them.
A tool is available that can add or remove the origin references of all the Bible Notes in one go.
See the USFM documentation for footnotes, endnotes and crossreferences for a description of what the origin references are.
In the dialog, tick what type of notes to affect: footnotes, endnotes, crossreferences, or a combination of them. If you tick "Footnotes", for example, and leave the others unticked, then only the footnotes in your project will be affected.
Then choose the action you wish to take, whether to give statistics only, or whether to add the origin references or to remove them.
If you add them, you can set how the origin references will look.
Once all settings are made, press OK to process all verses in your project.
Changes that Bibledit will now make cannot be made undone.
Statistics of what has been found and what has been done will be given once through.
Sometimes Bible notes don't have any markers in them at all, they are just plain text. To add the default markers to the note, choose option "Add missing text labels".
The dialog to generate the word lists is available through the menu, Tools, Generate word lists.
It generates a general word list, a list of Hebrew words, and one of Greek words.
It goes through all the data in the project, collects the entries which have been marked, and then inserts the lists at a location defined by the user. Thus it can generate a glossary or topical index.
There are three possible lists: a general word list, a Hebrew word lists, and a Greek word list.
For each of these lists there are some options that the user can set:
-
Process word list: whether to process this particular word list.
-
Add an asterisk to each entry, see below.
-
Add the asterisk only to the first time this particular entry occurs in the section, see below.
Generating word lists is simple assuming that the right markers are already in the data: Just set the options, click button OK, and wait till it is through.
The word list generator uses the entries that are in the data to collect the words to insert in the list.
An entry for the general word list is inserted between the \w and the \w* markers. The Hebrew and Greek word lists use similar markers. See the USFM documentation for full details
When the word list generator runs, it will remove any asterisks () that were appended to the word. When the option "Add an asterisk to each word entry" has been selected, it will then add an asterisk after the word. If the option "the first time it occurs in a section" has been selected also, it will only add the asterisk where this particular entry occurs for the first time in the section. In this case, if for example the word "talent" occurs several times in a section, it will be given as "talent" the first time, with the asterisk, and as "talent" the other times, without an asterisk. The section headings define the size of a section.
The lists of words can be inserted once or more than once in the data. The general word list will be inserted between the markers \zopenwordlist and \zclosewordlist. These markers ought to be on a separate line. If this couple of markers occurs in several places, the word lists will be inserted in several places too. If it occurs once, only one list will be generated, and if it does not occur at all, no list will be generated.
Any entries that are already between those markers will be preserved. If there are entries between those markers, and there is no corresponding entry in the text, this entry will be commented out.
List of usfm markers that indicate the position of a word list:
\zopenwordlist
\zclosewordlist
\zopengreekwordlist
\zclosegreekwordlist
\zopenhebrewwordlist
\zclosehebrewwordlist
The markers that open and close a word list will need to be manually typed in the text at the right location. They are not part of the stylesheet.
Consider the following situation:
The text contains the following general word list entries: Hallelujah, Rabi, Pentecost.
At some place of the data, the list should be inserted, but it already contains some entries:
\zopenwordlist
\p Hallelujah: Praise the Lord
\p Rabi: Teacher
\p Mamon
\zclosewordlist
After running the word list generator, it will look so:
\zopenwordlist
\p Hallelujah: Praise the Lord
\rem Mamon
\p Pentecost
\p Rabi: Teacher
\zclosewordlist
Note the following: (1) the existing entries have been preserved, (2) a new one has been added, (3) one has been commented out, and (4) the entries have been sorted alphabetically.
Note also that any text before the first colon (:) is considered to be the actual entry. If there is no colon, then the whole text will be considered the entry.
Debugging information.
Creating a new resource can be done through menu File / Resources / New.
Editing an existing resource goes through menu File / Resources / Edit. Creating a resource
When creating a new resource, several settings will have to be made about how this new resource operates. These are described below.
The user can enter the title of the resource. This title is used for easy reference to the resource.
A resource may live on the network, or it may be local. If it is local, it should have files that belong to this resource. These files make up the body of the text of the resources, that is, these files are the actual pages to be displayed. Files can be added to this resource by pressing the button to add files. You can add complete folders too. The whole folder will be added and everything that it contains.
There is a "Home" button visible when a resource is displayed. If this button is clicked, then the home page as given will be displayed. Sample home pages:
-
index.html. This shows the file "index.html" within the local files that belong to this resource.
Special text like "" can be used as well so as to make a home page that depends on the book now opened. See heading "URL constructor" below for more information about that.
Book abbreviations are used when retrieving a resource.
Let's have a look at an example. We will retrieve the book of Matthew. The Resource will retrieve the information through a URL (Uniform Resource Locator). Take note of the following URL:
http://net.bible.org/bible.php?book=Mat
If this URL is loaded, then the book of Matthew will display. As you can see, the book of Matthew is abbreviated using "Mat". If the Resource wishes to get to Matthew, instead of writing the full "Matthew", it uses only "Mat".
There is a button "Abbreviations" on the page. Pressing this button allows you to enter the abbreviations for all the books. The "Books" dialog shows, and you can enter the abbreviations.
An example will show how to enter an abbreviation. We are going to enter abbreviation "83" for book "1 John". To enter this, follow these steps:
-
Make 1 John blue by clicking on it or scrolling to it.
-
Press the right arrow key, or click at the right side of the blue line, as if you were clicking in the second column, the column called "Book in URL".
-
Type “83� (without the quotes).
-
Press Enter.
Press OK when through.
In order to save work, you can also import the abbreviations from another, existing, resource. See button "Import".
The second set of book abbreviations work similar to the first set, as described above. How to differentiate between these will be described below.
This button allows the user to go to the Resource Converter dialog where the required anchors can be written to the files. This is only needed when the anchors are not yet in the file.
In resources types where a URL must be retrieved, this URL constructor is used to assemble the URL to be retrieved. How it works is going to be explained using an example. Let's imagine that we're going to retrieve the Resource for Matthew 5 verse 8. The Resource would like to retrieve the following URL:
http://net.bible.org/verse.php?book=Mat&chapter=5&verse=8
You see that the book is "Mat", the chapter is "5", and the verse is "8".
The URL constructor for this will be:
http://net.bible.org/verse.php?book=&chapter=&verse=
You see that part of the constructor is "". First a left pointing angle bracket, then "book", and then a right pointing angle bracket. The Resource will consult the book abbreviations, and then find that for Matthew the abbreviations is "Mat", and then it will put "Mat" where it has "". It does the same for and .
The new URL will look like this:
http://net.bible.org/verse.php?book=Mat&chapter=5&verse=8
And this is exactly the URL that we'd like to retrieve in the Resource.
The second set of book abbreviations is consulted when the Resource finds "" in the URL constructor.
When you enter a URL constructor, it will be loaded immediately, so that you can see right away what the effect will be of any change that you make. You can also choose the book, chapter and verse that will be tested. There are controls for that too.
If the Resource is not on the network but local, you can just enter the local filename. For example:
.htm#v.
This results in:
mat5.htm#v8
At the end of all, when all settings are fine, press button Apply to save the resource. It will now be ready for use, that is, this resource can be opened.
Some examples are given below to help you quickly on the way.
Manually preparing content is not difficult. At the start of each verse, just insert the appropriate anchor, for example:
Then make the appropriate settings in the dialog for this resource to work. It's not difficult, only that it is a bit of work seeing there are so many verses.
To create the NET Bible as a local resource, download the HTML frames version from www.bible.org and unpack the files in some directory. Create a new resource. As the type choose "Based upon NetBible". Add all the files of the NET Bible that were unpacked above. Tick the books and the anchors as okay. Press OK to save this resource.
The Cambridge Paragraph Bible, written by F.H.A. Scrivener, including all the footnotes and cross references, can be found in the Libronix Digital Library System. In this example we are going to create Genesis from that book as a resource. To do that, do the following. In the Libronix Digital Library System, open the Cambridge Paragraph Bible written by Scrivener, and copy the book of Genesis to a word processor. This may have to be done in stages because when tried the last time, Libronix did not allow the whole book to be copied at once. Save it as a .htm page, for example gen.htm. Move that file to Linux. In Bibledit create a new resourse of type "Retrieve a different URL for each verse". Call this resource "Cambridge Paragraph Bible". Add the file "gen.htm" to the resource. For the home page, enter whatever you wish that would make a nice home page. This could be, for example, a title page, or a page made by yourself that has links to all the books. Let's enter here "home.htm", provided that this file is made available. As the URL constructor enter ".htm#be_anc__" (without the quotes). Then enter some book names for the constructor. After pressing the Books button, enter "gen" for the book of Genesis (without the quotes). In the URL constructor above, this means that "" is replaced by "gen", so that file "gen.htm" is loaded when we go to Genesis. After this is done anchors for each verse need to be inserted in the file gen.htm. Press button "Write anchors" to do that. In that dialog set the type to "Chapter starts at a pattern, verse 1 starts at chapter, verse starts at a pattern". Open the file gen.htm for conversion. As chapter prefix enter ">", as the chapter number choose "I, II, III", and as the suffix enter ". <" (all without the quotes). As the verse prefix enter ">" and as the suffix enter "<" (without the quotes again). The verse number can be left at "1, 2, 3". Then press the "Write" button. After done, press OK. Back in the Resource Editor, tick "Books are okay" and "Anchors are there", and press OK. The resource is now ready for use.
Projects from Bibledit can be made into a resource with little effort. Export a couple of books to OpenDocument. Then open these in OpenOffice, and save them as HTML Document. Then create a new resource, view at the anchors that Bibledit placed for you, make the appropriate settings, and ready it is.
The USFM can be imported into a Bibledit project. From the Bibledit project resources can be made, as described above.
There is a transcript of a conversation between two people how they managed to create a resource out of data exported from TW/folio. This transcript is given in full and might help you gain understanding in how to create the same or a similar resource.
Visit the web page for Bibledit-Desktop at bibleditdesktop.org