Resources

Introduction

Bibledit allows you to view resources that scroll in sync with Bibledit.

If Bibledit shows a certain verse, the Bibledit Resource Viewer will show the same verse.

Settings

There are a few settings that affect the resource viewer.

In the Bibledit Resources Viewer dialog, you can set which resources will be displayed.

To enable scrolling tick the appropriate box in menu Preferences / Reference exchange.

Operation

How does it work?

The resource viewer is a modern webbrowser. Bibledit loads some JavaScript in that browser. If this browser views any web page, either on the internet or a local one, and this web page contains certain anchors at each verse, then the JavaScript loaded will cause the browser to scroll with Bibledit. The browser reloads Bibledit's current reference every second. This reload action is visible.

Preparing contents

Introduction

The browser will display any sort of web page. Scrolling depends on certain anchors that need to be present for every verse.

These are the anchors:

Genesis_1_1

Genesis_1_2

etc...

Revelation_22_20

Revelation_22_21

Anchors example

Here is an example of some raw html code displaying part of the Gospel of Matthew. It has the anchors needed for scrolling.

<html>
<head>
</head>
<body>
<a name="Matthew_1_1"></a><p>1. The book of the generation of Jesus Christ ...</p>
<a name="Matthew_1_2"></a><p>2. Abraham begat Isaac; and Isaac begat Jacob ... </p>
<p>Main body of the text.</p>
<a name="Matthew_28_19"></a><p>19. Go ye therefore, and teach all nations ...</p>
<a name="Matthew_28_20"></a><p>20. Teaching them to observe all things ...</p>
</body>
</html>

Manually preparing content

As appears from the example given above, manually preparing content is not difficult.

At the start of each verse, just insert the appropriate anchor:

<a name="Matthew_1_1"></a>

Only that it is a bit of work seeing there are so many verses to be done...

Automatically preparing content

Bibledit has a tool that aids the preparation of contents.

This tool is in the menu, Tools, Resource converter. See there for how to do it.

Example preparations

Some example preparations follow below. They show how to prepare various resources for use in the Bibledit Resource Viewer.

Commentary from the Online Bible

The Online Bible was started. Menu File / Print was chosen. In the first tab, the option to print the text of the Bible was unticked, and the option to print the text of the commentary was ticked. The range was set from Genesis 1:1 to Genesis 50:26. In the second tab, the print options, it was set to print to file, and the filename was set to c:\poole_genesis.rtf. In the fourth tab, the commentary selection, Matthew Poole's Commentary of the Bible was ticked, and everything else was unticked. Then the OK button was clicked. Thus far for the export of the book of Genesis from Poole's commentary from the Online Bible.

The file poole_genesis.rtf was transferred to the machine running Bibledit.

Using OpenOffice the .rtf file was opened and saved as HTML Document. This gave us the desired web page.

Bibledit was started, and the Resource converter dialog was opened. The file was opened, and the option "Bookname, space, chapter, colon or dot, verse at the beginning of a line" was selected. Then the file was examined. The anchors were reviewed, and any spurious anchors were removed. Next the file was written.

This finished the conversion, and the web page was ready for viewing.

Bibles from the Online Bible

The Online Bible was used to generate c:\bible.rtf file the same way it was done for the commentary, see above, except that this time it printed the text of a Bible, and not of a commentary. You can tick one or more Bibles. More Bibles will give some kind of parallel Bible, in which the various versions are printed together per verse. The file was transferred to the machine running Bibledit, and converted to a HTML Document by OpenOffice, as described earlier.

Bibledit was started, and the Resource converter dialog was opened. The file was opened, and the option "Bookname and chapter on one line, followed by the verse numbers each starting a line" was selected. Then the file was examined. The anchors were reviewed, and any spurious anchors were removed. Next the file was written.

This finished the conversion, and the web page was ready for viewing.

Bibledit project

Projects from Bibledit can be made fit for the Resource Viewer without going through the Resource converter. A couple of books of the project were exported to OpenDocument. The resulting file was opened in OpenOffice, and saved as HTML Document. This finished the job and the web page was fit for viewing.

USFM files

The USFM files were imported into a Bibledit project. The project was exported to OpenDocument. The resulting file was opened in OpenOffice, and saved as HTML Document. This finished the job and the web page was fit for viewing.

Certain books from Translator's Workplace

Certain files in Translator's Workplace have a clearly distinguisable reference signature. This means that Bibledit's Resource Converter can find the place where a certain book/chapter/verse starts.

If a book is exported from Translator's Workplace, it may export the whole infobase and that would give a huge file. Some measures have to be taken to reduce the range to the desired book only.

The Translator's Handbook on Genesis was opened. All text on Genesis was selected. It was then exported to a .rtf file, through menu File / Export, and then saving it as Rich Text Format. The Export range was set to "Selected Records". The Export range had to be set correctly, else it would export everything.

This file was transferred to the machine running Bibledit, then opened in OpenOffice, and saved as HTML Document.

Bibledit was started, and the Resource converter dialog was opened. The file was opened, and the option "Bookname, space, chapter, colon or dot, verse at the beginning of a line" was selected. Then the file was examined. The anchors were reviewed, and any spurious anchors were removed. Next the file was written.This finished the conversion, and the web page was ready for viewing.