60 Setup Options

 

 

The Options Window

The Options Window Sections

Option Flags

Startup Options

Shutdown Options

Command Line Search Options

Command Line Configuration Options

Search Window Configuration Options

Browse Window Configuration Options

Main Window Status Bar Configuration

Export Options

Notes Options
General Greek Options
General Hebrew Options
Hebrew Accent Options

Transliterated Hebrew Display Options

Internet Updater Options

Option Strings

Font Options

Output Format Options

Setting Search Limits

Wildcards

Setting Favorite Version Options

Book Names

Editing Verse Maps

Changing the Version Display Order

Changing the Book Order

Updating, Adding, and Removing Databases

The Configuration Manager

Configuring BibleWorks for Use on a Network

 


The Options Window

 

Clicking on this button will open the BibleWorks Options Window. This Window is the centralized place where you can go to change many of the configuration options in BibleWorks. Each section or tab in the window has a different set of options. To move to a different section in the options, click on the appropriate tab at the top of the window. The Options Window can also be opened from the Main Menu by selecting Tools | Options.

 


The Options Window Sections

 

The Options Window contains the following sections:

 

General

 

§      Flags  - This option enables you to set a large selection of option flags that cover a wide range of BibleWorks features.

§      Option Strings  - This option enables you to change several miscellaneous options that all require some kind of text input, and hence could not be put in the Option Flags section.

§      Fonts  - This option is used to set fonts and font size options for text that is displayed in the Browse Window and Search Window. It is also used to configure the fonts used for printing and exporting text.

Output Format Options

 

§      Verse List (no text)  - This option enables you to change the formatting of the verse lists (no text) copied from the Search Window verse list. This window also enables you to set the destination to where the verse list will be copied.

§      Verse List or Range  - This option enables you to change the formatting of verses copied from the Search Window or by means of the Popup Verse Copy Window. This window also enables you to set the destination to where the verse list will be copied.

§      Selected Browse Text  - This option enables you to change the formatting of text copied from the Browse Window. This window also enables you to set the destination to where the text will be copied.

Searching

 

§      Search Limits  - This option is used to set search limits for searches. You can set search limits by selecting from lists of check boxes, or you can enter limits manually in a text box. You can also define your own favorite limit selections and save them by name for later recall.

§      Wildcards  - This option enables you to change the definition of several "wildcards" that have been custom-designed for use with Hebrew searches.

Bible Versions

 

§      Favorites  - This option is used to set search and display versions, as well as define favorite named combinations that can be recalled later.

§      Book Names  - This option permits you to determine the way book names are displayed in the Browse Window and in exported text. You can also define book name aliases that can be used when specifying Command Line searches.

§      Verse Maps  - This option permits you to change the way verses are mapped between versions in BibleWorks. This determines how BibleWorks interprets a verse reference in one version when it is looked up in another version.

§      Version Order  - This option is used to set the display order for versions in the BibleWorks Browse Window and the Browse Tab when it is in Multiple-Version mode.

Updates  - This option can be used to update the BibleWorks program and databases via the Web, or to reconfigure BibleWorks using your BibleWorks installation disk..


Option Flags

The Option Flags selection in the Options Window  contains a large number of BibleWorks options flags, categorized by type. To open a category and see the options it contains, click the + symbol next to the category.


Startup Options

 

§     Show splash screen at startup
Checking this option displays the BibleWorks startup graphic whenever the program starts.  Pressing any key or clicking the graphic with the mouse will close it immediately.

§      Enable Configuration Manager
Checking this option shows the Configuration Manager when BibleWorks starts, permitting you to save named BibleWorks configurations and select from among them when you start the program.

§      Use separate directory for each configuration
Checking this box causes the Configuration Manager to create, for each new configuration, a new user directory set in a "Config" subdirectory of the BibleWorks Directory. Only directories containing user-configurable files are duplicated. This feature permits, for example, having a different set of notes for each configuration.

§      Hide Configuration Manager Details
Enabling this option simplifies the Configuration Manager startup window to include only the list of available configurations. If you turn this off in the Configuration Manager window, you must turn it back on here in the Startup Options section.

§      Enable Dynamic Data Exchange (DDE) services
If this option is activated, BibleWorks will be set up as a DDE client and you can use other applications to control BibleWorks. There is no reason to disable this feature unless you are experiencing problems.

§      Enable Mouse Hooks (disable for debugging)
BibleWorks installs mouse hooks for a wide variety of purposes. This option should not be disabled except as a part of trouble-shooting procedures used to isolate particular problems under the guidance of BibleWorks support staff.

§      Check for Locked Databases on Startup
If this option is enabled BibleWorks will check on startup for installed databases that require an unlock code, but which have not been unlocked. If it finds any such databases it will prompt the user for an unlock code.

§      Allow Windows XP Display Themes (on restart)
If this option is selected BibleWorks will display many items (like scrollbars) using the current XP display theme. Otherwise it will use the classic styles.

§      Enable Scripture Popups in External CHM Files
If this option is set when the mouse cursor moves over a tagged Scripture reference in a CHM (HTML Help) file, a popup will open showing the text of the Scripture reference.

§      Enable Frameless Main Window Buttons
If this option is enabled the Main Window button bar buttons will have the XP frameless style. This affects only Windows XP systems using the classic desktop style.

§      Show Getting Started Window on Startup
If this option is enabled the Getting Started Window will be shown when you start BibleWorks. This Window gives you access to introductory videos and Study Guides.

§      Reset Window sizes and locations if screen res changes
If this option is enabled window sizes and locations will all be reset to their default values on startup if you have changed the Windows screen resolution since your last BibleWorks session. This option is included because some people like to run BibleWorks on two systems with different screen resolutions and don't want the reset to occur. You should be aware though that some saved windows sizes and positions will not work well in some situations between systems with different resolutions. This is because Windows changes button and tool sizes in dialog boxes based on screen resolution. So you should leave this button checked unless you are willing to live with some  unexpected window displays.

§      Use Intel Graphics Optimizations
If this option is enabled an Intel Graphics library will be used to display images in some parts of BibleWorks. The default is "on". Turn off only for debugging purposes.

§      Use Arial Unicode MS instead of Arial
If this option is enabled when BibleWorks would normally use the system Arial font, it will use the Arial Unicode MS font instead. If Arial Unicode MS is not installed this flag has no effect. Default is off. This feature may be useful for configurations where the Windows "Language for Non-Unicode Applications" option has been set to a non-English locale. If English text is garbled in BibleWorks and you have the system set to use a different locale for non-Unicode applications, try turning on this option. You will need to restart BibleWorks after making the change.


Shutdown Options

 

§      Prompt user before exit
If you select this option, BibleWorks always requests confirmation of your choice to leave BibleWorks. If you deselect this option, confirmation is requested only if there are unsaved files.

§      Save setup options on exit
If this box is checked, the BibleWorks configuration will be saved on exit. The size and relative orientation of the various windows in BibleWorks will be saved as well. This information is saved in two files in the BibleWorks root directory. The two files are bw900.ini and bwdir.ini.

§      Initialize INI on Exit
If you check this option, when you exit BibleWorks the BibleWorks initialization file (bw900.ini) will be deleted from the BibleWorks root directory. The next time you start BibleWorks, all options will be reset to their default values. If you are having problems that cannot be resolved, this can sometimes help you to restore functionality and isolate the option setting that is causing the problem. This process does not affect the bwdir.ini file which stores BibleWorks directory information.

§      Save full network paths in .ini file (XP only)
If you check this option, when BibleWorks saves directory names in the bw900.ini file, it will include full path information, including the network computer name. Do not enable this option unless your .ini files are destined for use on a network. Use of this option will slow disk access somewhat.

§      Save checkpoint on exit
If you check this option, when BibleWorks closes it will save the current executable, initialization file and context file so that they can be loaded later if you have problems or want to revert to a prior program version or configuration. See the section on Using Checkpoints for details.

§      Enable executable checkpoints for limited users
This option enables executable checkpoints for users who are not running as an Administrator but who are running on the machine on which BibleWorks is installed. See the section on Using Checkpoints for details.


Command Line Search Options

 

§      Include NOTs in Search Window hits
If this option is not checked, and your Command Line search included NOT-ed words, the hits corresponding to those words will not be stored in the highlighting data for the hit. Some NOT-ed searches can result in almost every word being highlighted. Unchecking this flag prevents that.

§      Always compute hits for Command Line searches
Always calculate the exact number of logical hits in a Command Line query (otherwise only word and verse counts will be reported). This increases the time that a search will take, but gives you the exact number of times that a particular construction occurs. If this option is turned off, there will be no hit highlighting. It can be useful to turn this off for debugging purposes.

§      Compute Search Window hits by permutation
If this option is set, Command Line search hits will be computed by permutation. Statistics for hits will include the various combinations of words possible with the search criteria. If this is turned off, the number of hits will be the same as the number of words highlighted.

§      Add multiple hits parameter to Search Window Verse List
If this option is set, the Search Window Results Verse List will show beside each verse the number of hits occurring in the verse if it is more than one.

§      Notify user if OR search has unmatched elements
If this option is set and a Command Line OR search has unmatched elements, the user will be notified. An OR search can have hits even if some of the words did not occur anywhere in the version. It is useful to know if this is the case so we recommend leaving this flag on.

§      Extend Strong's Tags to all words
If this option is enabled and you are doing a mixed Strong's Number and word search, all words preceding a Strong's Number will be treated as if they were tagged with the number. Otherwise the tag is assumed to apply only to the immediately preceding word.

§      Search on West Euro versions is accent sensitive
If this option is turned on, searches on Western-European Bible versions will be accent sensitive. This is the default setting. Note that the word list for the version will display both accented and unaccented forms of words if they occur, regardless of this setting. However, if you turn this flag off, searches will find matching forms regardless of accents.

§      Enable Smart Apostrophes (English text only)
If this is turned on, apostrophes will not be treated as significant in English searches. For example <.brother's>, <.brothers> and <brothers'> will all yield the same results (in the NAU for example), namely the hits from all three cases. This will insure that you aren't missing any verses. This is just a fail-safe feature and is not necessary for most people. Activate it if you want and it will not slow down searches appreciably. Searches initiated by clicking on a word list are not affected (this permits you to look up the individual variants easily without turning off the feature).

§      Include all verses with highlights
When you do a Search Window string search that crosses verse boundaries, a match can span more than one verse. If this flag is turned on, both verses will be tagged as hits and will show up in the final verse list.

§      Remember Command Line Ranges
If this option is enabled, when you enter a range on the Command Line, the range will be remembered when the Browse Window is refreshed. The range is remembered only for the last verse entered on the Command Line. This allows you to scroll backwards and forwards and return to the original verse and have the original range of verses restored. It also retains the Browse Window verse range in multiple-version mode when the window is repainted by BibleWorks (for example, when you highlight and color a portion of text). This option is necessary for some people because by design the Browse Window was not intended originally to display multiple verses in multiple version mode.

§      Buffer Word List to Memory
By default BibleWorks keeps the word lists for the 5 most recent search versions in computer memory for fast switching between versions. Unchecking this option should only be done for debugging at the request of technical support staff. If a computer system has little available memory, unchecking this option may be helpful.


Command Line Configuration Options

 

§      Enable Command Line Morphology Code Help
Enabling this option pops up morphology help automatically as you type morphology codes on the Command Line.

§      Beep on Command Line error
If you type in a reference or word that doesn't exist, BibleWorks will beep. You may, for the sake of sanity, want to disable the beeper. This check box will allow you to do that.

§      Enable Popup Command Line (disable for debugging)
If this option is enabled, the BibleWorks Popup Copy Window will be accessible from any application by pressing the Shift-Ctrl-B key combination.

§      Track word list as you type on Command Line
You can specify whether or not the command line word list popup will try to keep up with your typing as you type in words. On some slower systems you may need to disable this option.

§      Auto-Select CL Keyboard when version changes
If you have this flag enabled, BibleWorks will automatically switch to various foreign keyboards depending on which search version is selected.

§      Enable BibleWorks Keyboard Hook (disable for debugging)
Disabling this option will prevent BibleWorks from installing keyboard hooks when BibleWorks is started. This can be useful for debugging purposes. Change only if instructed by Tech Support to do so.

§      Always Use English Font Maps for Hebrew/Greek
This flag will force the program to always use the default English Keyboard Maps for Hebrew and Greek. This is the default. Disable only for debugging purposes.

§      Command line and verse histories track version change
This flag will force command line and verse history entries to track the search version. When you access an item from the history the search version will change automatically to the version in effect when the history item was stored. You might want to disable this option, for example, if you want to look up the same phrase un multiple versions and want to fetch the phrase from the command line history (by pressing the up arrow key).

§      Word history tracks version change
This flag will force the word history list to track the search version. When you access an item from the history the search version will change automatically to the version in effect when the history item was stored.

§      Use Israeli keyboard on command line
This flag will tell BibleWorks to use the Israeli Keyboard for Hebrew input. This will be in effect only when vowel point sensitive searching is turned OFF. For vowel point sensitive searching you must use the normal BibleWorks keyboard layout. Because the Israeli keyboard does not distinguish Shin and Sin, the "a" key has Shin and the "q" key has Sin. Thus

a

shin

 j

chet (heth)

 s

dalet

 b

nun

 k

lamed

 t

alef (aleph)

 c

bet

 l

kaph

 u

vav (waw)

 d

gimmel

 m

tsade

 v

he

 e

kuf (qoph)

 n

mem

 x

samek

 f

kof (kaph)

 o

mem

 y

tet

 g

ayin

 p

pe

 z

zayin

 h

yod

 q

sin

 ,

tov (taw)

 i

nun

 r

resh

 

 

 

§      Enable command line word list popup
Checking this flag enables the command line word list popup. Unchecking this flag disables the word list popup.


Search Window Configuration Options

 

§      Put Analysis Window under Browse Window
This option controls the Main Window layout. If this option is selected the Analysis Window will be placed under the Browse Window instead of beside it. This option can only be used with the three column mode (i.e. a single column Analysis Window).

§      Show Hidden Listbox Items
This is intended for certain list boxes with morphological text that is too wide to display in the listbox. The non-visible content will be shown in a wider overlay.

§      Sort Search Window Stats by Frequency
If this option is set, search window stats in the Analysis Window "Word" Tab will be sorted by frequency rather than alphabetically.

         Enable context menus in Search Window
This option enables Context Menus in the Search Window. It is set on by default.

§      Use 4.0 Style Limits Window from Button bar
BibleWorks in versions 5 and later uses a new, scrolling window for selecting verse limits. Previous versions of BibleWorks let you select verse limits using a single, non-scrolling window. This option restores the "old-style" limits window.

§      Save Search Window State when switching Results Windows
Normally the state of the Search Window is saved when it loses focus. This permits the state to be restored after opening other windows which share resources with the Search Window. This feature should only be deactivated when debugging problems at the direction of BibleWorks support staff.

§      Include Hits when saving context
This option controls how Search Window context is saved when the verse changes. Normally all Search Window information is saved when you leave the window or change to another verse. It is restored when you return to the window or click a context button. Even search hits are saved. Especially on slower systems, switching contexts may be uncomfortably long if you have recently done a very large search (like searching on "and"). This option allows you to turn off hit highlight saving.

§      Convert JPEG Graphic Files to BMP on first use
With this option activated, BibleWorks converts to BMP NET Bible JPEG map files.  There is no reason to select this unless you have problems with the JPEG files.

§      Automatically save and load Search Window Tab Contexts
If this option is on the Search Window Tab Contexts will be saved and loaded automatically between sessions.

§      Show morphology translation in Words Tab word lists
If this option is enabled, Words Tab Word Lists that contain morphology codes will be translated in place to show the English meaning of the codes.

§      Use long version identifiers where possible
This obsolete option will be retained until we make sure eliminating it has no effect. The Bible Versions menu (activated by the Bible Versions button left of the Command Line or by the Browse Window Status Bar button) contains lists of searchable Bible versions, shown in abbreviated form unless this option is chosen, in which case a longer form containing the full version name is displayed.

§      In Verse + Text Mode display FORM for morphology versions
If this flag is on and you are searching on a Morphological Version, the text in the Verse List will show the corresponding text (i.e. brother or companion) version instead of the version being searched. Otherwise just the lemma for each word will be displayed. The default setting is ON.

§      Show Mouse Hints
Enabling this option causes BibleWorks to open hint messages in several places where users typically need help. These hints are only shown once per session and can be turned off individually via a check box on the message window.

§      Enable verse list check boxes
Selecting this option displays the check boxes in the Search Window Results List.

§      Cross Version Search Mode

o     Search Only Current Search Version
If this option is active only the current search version will be searched.

o     Search All Display Versions
If this option is active all versions currently being displayed in the Browse Window will be searched, if they are of the same language as the current search version.

o     Search and Display All Same Language Versions
If this option is selected all installed versions will be searched and displayed if they have the same language as the current search version.

o     Search and Prune All Same Language Versions
This is the same as the previous option except that versions with no hits will be removed from the Browse Window display list.

 


Browse Window Configuration Options

 

§      Enable Browse Window colors for text
If this option is enabled, the Browse Window will display colors when you mark text with the colorizer option. This just provides a quick way to disable the color without having to delete the color files that you have created.  It is on by default.

§      Enable Browse Window colors for morphology text
If this option is enabled, the Browse Window will display colors when you mark morphology text with the colorizer option. This just provides a quick way to disable the color without having to delete the color files that you have created.  It is on by default.

§      Display Browse Window References in Bold
This option turns bolded Browse Window References on and off.

§      Remove CRLF characters from Browse Window export
This option removes line breaks from text eported from the Browse Window by cut and paste.

§      Display Full book names in browse window
If this option is selected full book names will be displayed in the Browse Window. Otherwise book names will use abbreviated names.

§      Show Outline List Box on Browse Window status bar
If this option is enabled, the Browse Window Status Bar will contain the appropriate entry from the Bible Outline in the header of the Browse Window. A List Box with the entire outline available will be used for the display. If this option is off only the current entry will be shown (i.e. not the List Box).

§      Automatically make morphology versions display versions
If this flag is set and you activate a Greek or Hebrew morphology as a search version, it will automatically be activated as a display version. This permits you to do morphology searches while having only the text version displayed. For example, you can do GNM searches but have only the GNT displayed in the Browse Window. For non-Hebrew/Greek versions, activating a version as a search version always adds it to the display list as well. If this flag is not set and you activate a Greek or Hebrew morphology as a search version, it will not be activated as a display version. This permits you to do morphology searches while having only the text version displayed.

§      Enable automatic secondary Browse Windows
The typical way of opening up an additional Browse Window is to click on the New Browse Window icon in the Search Window. The typical reason for doing this is to keep the text of a particular verse in front of you while you search for related verses in another Browse Window. Turning on the Secondary Browse Window option automates this process. If this box is checked, when you do a search in a Browse Window by double-clicking or by means of the context menus, a new Browse Window will open up automatically to display the results of the search. The next time you do a search from the original window, BibleWorks will remember that there is already a secondary window open to receive the results. If you do a search from an already existing secondary window, then a new one will be opened to receive its results. BibleWorks will also remember which window was used to open up each secondary window.

§      Show Geneva Bible Notes for KJV Version
If this option is activated and the Geneva Bible Notes are installed, the notes will be displayed in the Analysis Window when a KJV verse is being examined.

§      Keep Lexicon Focus when looking up Lexicon verses
If this option is activated the Lexicon Window will retain focus when you look up hypertext verse references. Otherwise the Browse Window that displays the verse will be activated.

§      Show Word Tips
If this option is on, when you move the mouse cursor over a word in the Browse Window, a popup window will open giving information about the word. For Greek and Hebrew this will be a brief gloss and morphology information. For versions tagged with Strong's Numbers, the Strong's Lexicon entry will be shown.

§      Keep Word Tips Open
If this option is checked the Word Tips window (see previous item) will remain open. You can move the Word Tips window just by clicking and dragging with the left mouse button.

§      Automatically update last active Resource Window
If this option is checked the last active Resource Summary Window will update automatically as you move the mouse. This includes floating Resource Summary Windows as well as the copy on the Analysis Window Resource Summary tab.

§      Maintain search version after lemma search
If this option is checked the search version will not change when you right click on a Greek or Hebrew word and do a morphology lemma lookup. Otherwise the version would switch to the morphology version used for the lemma search.

§      Enable verse popups in Analysis Window and lexicons
If this option is checked verse popups will be enabled in the Lexicon Browser and in lexicons displayed in the Analysis Window.

§      Update Resource Window on Verse Change
If this option is checked, the Resource Summary Window will refresh whenever the Browse Window verse changes.

§      Show paragraph markers
If this option is checked, paragraph markers will be displayed in the Browse Window. By default the paragraph markers are the same as used in the RSV version so the paragraph divisions will be the same for all versions. If you want to have different paragraph breaks for each version create a text file containing the verse references which begin a paragraph. Name the file as the version ID with the .pat extension and place it in the BibleWorks databases folder. For samples of how to do this see the kjv.pat or rsv.pat file. When you run BibleWorks these .pat files will be compiled into .pac files if the pat files are newer than their corresponding pac files. You cannot place paragraph markers in the middle of a verse with this method. However, if a version already has paragraph markers embedded you can create an empty .pat file. This will tell the program to use the internal paragraph markers.

§      Show Matthew Henry Bible Notes for KJV Version
If this option is checked Matthew Henry Bible Notes will be displayed in the Analysis Window for the King James Version.

§      Enable Custom Double Click Popups 
If this option is checked the behavior of the program when you double-click on Greek and Hebrew words and Strong's Numbers can be reconfigured. To change the behavior right click on a word and with the SHIFT key depressed, select one of the menu options. Thereafter double clicking on a word will cause that menu selection to be used. Options for Greek, Hebrew and morphology versions are maintained separately. Deselecting this option will reset all double click custom options to the defaults.

§      Maintain main window width when toggling 4th column
If this option is selected, when you toggle the second Analysis Window column on an off, the width of the main window will remain the same. If it is not selected, the main window will be widened to make room for the new column.


Main Window Status Bar Configuration

 

§      Enable Status Bar at Bottom of Main Window
If this option is enabled the Main Window Status Bar at the bottom of the BibleWorks Window will be visible.

The following options determine which status indicators are displayed in the Main Window Status Bar. Unless you have a high-resolution display they will not all fit. You can select the ones you find most useful. See the Main Status Bar topic for details.

§      Current Search Version
If this option is set the Status Bar will display the current search version.

§      Verse Limits Active
If this option is grayed out, there are currently no search limits set for Command Line searches. If it is not grayed there are limits set. Double-click on the status area to open the Search Limits Window.

§      Strong's Numbers Active
If this option is grayed, versions with Strong's Numbers will NOT show the numbers when verses are displayed in the Browse Window. Otherwise they will be displayed.

§      Browse Mode Active
If this option is grayed, the Browse Window is in Multiple-Version mode. If it is not grayed the Browse Window is in Browse mode. To change the state double-click on the status indicator.

§      The Analysis Window On
If this option is not grayed, the Analysis Window is activated for the current Browse Window. To change the state of the Analysis Window, double-click on the status indicator.

§      Verse-Based User Notes On
If this option is not grayed, verse-based user notes are turned on. A note window will be loaded automatically into the BibleWorks Editor when the current verse changes.

§      Notify User When Verse-Based Note Available
The "V" to the left of "Verse-based User Notes" indicator will be ungrayed if user notes exist for the currently displayed verse.

§      Chapter-Based User Notes On
If this option is not grayed, chapter-based user notes are turned on. A note window will be loaded automatically into the BibleWorks Editor when the current verse changes.

§      Notify User When Chapter-Based Note Available
The "C" to the left of "Chapter-based User Notes" indicator will be ungrayed if user notes exist for the currently displayed chapter.

§      Translator Notes On
If this option is set, versions which have embedded translator notes will have those notes displayed in the Browse Window with the text. This flag also toggles the superscript indicators in versions like the NAS, which have Analysis Window notes with superscript markers in the text. You can toggle this flag by double-clicking on the status area.

§      Accent-Sensitive Searching
If this option is active, Command Line searches will be accent-sensitive. This flag reflects the state of searches for Greek, Hebrew and European Versions even though the underlying mechanisms are quite different. A separate internal flag is kept for each language type so you will see this indicator change as you change search versions. You can toggle this flag by double-clicking on the status area.

§      Vowel-Point-Sensitive Searching
If this option is active, Hebrew Command Line searches will be vowel-point sensitive. Search text must include the full pointed text. This flag does not affect Hebrew accents. You can toggle this flag by double-clicking on the status area.

§      Search on Qere (Hebrew)
If this option is not set, words in Hebrew text that have a Qere marker are ignored. You can toggle this flag by double-clicking on the status area.

§      Search on Kethib (Hebrew)
If this option is not set, words in Hebrew text that have a Kethib marker are ignored. You can toggle this flag by double-clicking on the status area.

§      Show Current Keyboard Language
This status area shows the currently loaded Command Line Keyboard Layout.


Export Options

§      Send RTF to clipboard when exporting
Text copied to the clipboard is normally sent in both an ASCII format without formatting/font information and a rich-text format (RTF) with full format/font information. The target word processor chooses which it uses. If your word processor has trouble with RTF formatting, you may want to uncheck this box.

§      Send CR/LFs to clipboard when exporting
To have text pasted from the clipboard into a single target word processor paragraph, you do not want Carriage Returns/Line Feeds copied to the clipboard with the text: thus you should uncheck this option. Since word processor Hebrew text wrapping is unpredictable, this option's setting is ignored if Hebrew text is copied.

§      Export colors to Clipboard and Editor
This option affects only text copied from the Analysis Window and from utilities like the Lexicon Browser. It has no effect on Bible text copied from the Popup Copy Window, the Browse Window or the Results Verse List. The format of these items is determined by settings in the Output Format Options section. This option determines whether text color attributes are copied. It also affects the copying of hypertext links.

§      Export formatting to Clipboard and Editor
This option affects only text copied from the Analysis Window and from utilities like the Lexicon Browser. It has no effect on Bible text copied from the Popup Copy Window, the Browse Window or the Results Verse List. The format of these items is determined by settings in the Output Format Options section. This option determines whether attributes like bolding, italics and underlining are copied.

§      Export Reference String when Exporting Browse text
This option copies verse references with Browse Window text in Browse Mode.

§      Remove CR/LFs when exporting Browse Text
Checking this option replaces Carriage Returns/Line Feeds with blanks in text exported from the Browse Window in Browse Mode.

§      Remove Hebrew Accents when exporting
This option strips off Hebrew Accents when Browse Window text is exported.

§      Keep Hebrew justification when exporting Hebrew text
Checking this option retains BibleWorks wrap formatting for exported Hebrew text; i.e., exported text will have carriage return/line feed characters spaced according to the Hebrew line width set in the Output Format Options Window.

§      Export Hebrew superscripts (Unicode)
If this option is checked, when you export Hebrew Bible text, superscripted verse numbers will be exported using the default Unicode Hebrew font, instead of English. This will render the entire reference except for the initial book, chapter and verse, as Hebrew text. This may work better for some cut and paste operations. If you do not do this the verses will be treated as Hebrew verses interspersed with non-Hebrew verse numbers. The default is off.

§      Use Windows 98 Print Window
Setting this option forces the Windows 98 Print Window to be used, even on later systems, permitting a workaround on Windows versions with a Print Window bug.

§      Enable Lexicon Browser drag and drop.
You can drag selected text in the Lexicon Browser from BibleWorks to an external application like a Word processor. On some systems this process is unstable. In such cases this option can be used to turn the feature off.

§      Enable Browse Window drag and drop.
You can drag selected text in the Browse Window from BibleWorks to an external application like a Word processor. On some systems this process is unstable. In such cases this option can be used to turn the feature off.

§      Filter RTF Export for maximum compatibility.
If this option is enabled, when you export RTF text, it will be filtered to enable maximum compatibility with other applications. You may lose some formatting so you should use this option only if you are having problems getting another application to accept RTF text exported from BibleWorks.

§      Close Copy Dialog/Popup on copy.
If this option is enabled, when you copy text using the BibleWorks Popup Copy Window, the Popup Copy Window will be close automatically after the text is copied.

§      Remove Hebrew space-dots
The WTM Hebrew morphology version contains a few "lemmas" consisting of two or more words. In places like this the Hebrew display text has a raised dot instead of a space between the words in order to indicate that these words are treated as a single entity. Checking this option removes the Hebrew space-dots when exporting the Hebrew text.

§      Enable HTML output to clipboard.
If this option is enabled, when you copy text using the clipboard, an HTML formatted copy will be placed in the clipboard as well. This only works for BibleWorks copy processes that place RTF text on the clipboard. The HTML is created by converting the RTF text. The option is on by default but can be turned off if problems related to the conversion occur.

§      Enable HTML file editing
This option enable HTML file editing in the BibleWorks editor. Editing is actually done in RTF but converted to HTML when a file is saved.


Notes Options

 

§      Maintain user notes for each chapter (not verse)
User notes will be saved per chapter, rather than per verse, if this option is selected.  Notes file names are constructed from the three-letter book abbreviation plus a chapter number and the normal extension for BibleWorks text files (.bww).  For example, with BWORKS the main BibleWorks directory, the notes for Genesis Chapter 30 will appear in BWORKS\NOTES\GEN30.BWW.  These files are kept in a subdirectory called NOTES under your main BibleWorks directory.

If this option is not selected, a note file will be maintained for each verse for which user notes have been entered.  File names will then be constructed from current chapter and verse numbers and stored in a subdirectory (different for each book) called NOTES\XXX (where XXX represents the three letter book name abbreviation for the current book), located in the main BibleWorks directory.  An example file name for Gen 30:22 would be BWORKS\NOTES\GEN\30_22.BWW.

§      Show availability on status bar when verse changes
This option checks for available user notes once a verse is changed in the Browse Window.  The “Verse Notes” or “Chap Notes” indicators (if enabled) on the Main Status Bar will be ungrayed if there is a note.

§      Make User Notes Read-Only
If this option is checked User Notes will not be editable.

§      Load User Notes Automatically
With this option enabled, user notes will automatically load into the Analysis Window User Notes Tab when a verse changes in the Browse Window.  If you are in single version Browse Mode, notes will also change when you move the mouse cursor over a new verse.

§      Filter editor output for RTF (debug only).
If this option is enabled, when you export RTF text, it will be filtered to enable maximum compatibility with other applications. You may lose some formatting so you should use this option only if you are having problems getting another application to accept RTF text exported from BibleWorks.


General Greek Options

 

§      Show entries from all Greek Lexicons in Analysis Window
If this option is active, the Analysis Window will show the Lexicon entries from all available Greek lexicons when the user places the mouse cursor over a Greek word. This setting overrides the default Greek lexicon setting in the Analysis Window. The order in which the lexicon entries is displayed is not confiurable. This option is not available for Hebrew lexicons.

§      Search on Greek versions is accent sensitive
If this option is set, Command Line searches on Greek Versions will be accent sensitive.

§      Show all LXX variants in Browse Window
If this option is set, BibleWorks will automatically display LXX variant readings when verses from the LXX are displayed.


General Hebrew Options

 

§      Display vowel points for Hebrew text
If this option is turned off, vowel points will be stripped from Hebrew text displayed in the Browse Window.

§      Ignore Dagesh in Hebrew Searches
If this option is active, Hebrew Command Line searches will be Dagesh-insensitive. This flag is meaningful only if you have vowel-point sensitivity turned on as well.

§      Include qere readings (Hebrew) in searches
If this option is not set, words in Hebrew text that have a Qere marker are ignored.  

§      Include kethib readings (Hebrew) in searches
If this option is not set, words in Hebrew text that have a Kethib marker are ignored.

§      Reverse Order of Hebrew Analysis Window Definitions
Many Hebrew words can be decomposed into several lemmas. When you move the mouse over a word, definitions for each of these will be displayed in the Analysis Window. The order will be the normal right-to-left reading order. However, in the majority of cases the most significant part of a form is at the end (just think of how many words begin with a waw). This option reverses that order so that in most cases the most significant entry will be shown first. This minimizes scrolling.

§      Search on Hebrew versions is vowel point sensitive
If you have this flag turned on, searches on Hebrew versions will be vowel point sensitive.

§      Show full Analysis Window data for Hebrew words with Maqqef
If this flag is set and the mouse cursor is over a Hebrew word with a Maqqef, lexical information will be show for both parts. Otherwise information will just be shown for the part immediately under the mouse cursor.

§      Display a plus between morphemes in WTT
If this option is checked a plus sign will be displayed between morphemes in the WTT display in the Browse Window.

§      Display all homonyms in Analysis Window
If this option is checked all homonyms will be displayed in the Analysis Window (not available for all Hebrew Lexicons). Off by default.


Hebrew Accent Options

§      Permit accent code searching in Hebrew morph. version(s)
If this option is enabled, extra parsing codes will be added to the WTM database so that you can search for accent information.

§      Show the following Hebrew word accents in Browse Window
If this option is turned on, all of the Hebrew accents that are checked in the following list will be displayed in the Browse Window when the WTT text is displayed. Each of these accents can be turned on and off individually.

Segolta (a)

Sinnorit (s)

Zarqa, Sinnor (b)

Pazer (t)

Pashta, Azla Legarmeh (c)

Pazer Mag or Qarne Parv (u)

Pashta (with previous left) (d)

Zaqep Magnum (v)

Telisha Parvum (e)

Mahpak or Mehuppak (w)

Paseq [separator] (f)

Mereka (y)

Yetib (g)

Mereka Kepulah (z)

Dehi or Tipha (h)

Tipha, Majela, or Tarha (0)

Mugrash (i)

Munah (1)

Telisha Magnum (j)

Silluq [meteg (left)] (9,2)

Ole or Mahpakatum (k)

Meteg (right) (3)

Geresh or Teres (l)

Tebir (4)

Gershajim (m)

Atnah (5)

Azla or Qadma (n)

Galgal or Jerah (6)

Illuj (o)

Darga (7)

Shalshelet (mag,parv) (p)

Telisha Qetannah (med) (A)

Zaqep Parvum (q)

Telish Magnum (med) (B)

Transliterated Hebrew Display Options

The following tags are used with the BHT transliterated Hebrew text in BibleWorks. They toggle the display on and off for the indicated character(s).

§         Show accents.

§         Show Metheg.

§         Show Silent Shewa


Internet Updater Options

§      Backup files that are updated by the patch
If this option is selected files that are updated by the patch will be first copied to a backup directory as a safety precaution. It is normally off to save disk space.

§      Save patch file after applying the patch
If this option is selected patches will be saved to disk after being applied. Otherwise they will be deleted. If you think you may need to reapply patches later, or transfer them to another machine, you should select this option. It is normally off.

§      Display all patch files (including applied patches)
Normally after a patch is applied it will no longer appear in the list of available patches. If this option is selected all patch files will be displayed, even those that have already been applied. This permits you to reapply old patches to revert to an earlier version.

§      Automatically check for updates
When this option is checked, BibleWorks will automatically check for updates at program start. Automatic checking for updates only works if the computer is connected to the Internet at the time of program start. If updates are available, the updater window will list the available updates for your selection. BibleWorks will not update files without your approval.

§      Check for updates only once every 48 hours.
If this option is not checked, a check will be made every time BibleWorks is started.


Option Strings
 

The Option Strings Tab in the Options Window  permits you to change several miscellaneous options that all require some kind of text input, and hence could not be put in the Option Flags section. The options are as follows:

 

§      Popup Copy Key

It often happens that you are in your favorite word processor and want to insert a few verses. You could run BibleWorks and use the Clipboard over and over to do this, but that could get a little tedious. Fortunately BibleWorks provides an easier means to do this. What you must do is first run BibleWorks, and then your word processor. Then while in the word processor, if you hold down the <Ctrl> key and the <Shift> key and then press the <B> key, the Popup Copy Window will open. For details see the Popup Copy Window topic.

The setup parameter labeled "Popup Copy Window Key" allows you to choose which key combination calls up the Popup Copy Window. If there is a conflict with your word processor, you can change it. The default is the "Control-Shift-B" combination, which is entered in the Options window as "+^B". To change the setting, all you do is enter a letter from A to Z preceded by one or more characters selected from the list "^+%". These three characters stand for the shift key ("+"), the control key ("^") and the alt key ("%"). The text in the box labeled "word processor Insertion String" represents the key sequences that are sent to your word processor after the verse you enter is looked up, to cause the text to be copied from the Windows Clipboard to your word processor. The standard Windows default is the "Control-V" combination and you probably will not have to change it. If you do need to change it, you enter the proper sequence by using the "+", "^" and "%" characters, as before, to indicate the shift, control and alt keys respectively. Alphabetic characters are represented by themselves and other special keys are entered by special key words enclosed by curly braces. Thus "+{insert}" stands for the <Shift-Insert> key sequence. Other key words that you might need to use are as follows:

 

Key

Code

Key

Code

Backspace

{BS}

End

{end}

Break

{break}

Enter

{enter}

Caps Lock

{capslock}

Insert

{insert}

Delete

{del}

Left

{left}

Down

{down}

Num Lock

{numlock}

Page Down

{pgdn}

F6

{F6}

Page Up

{pgup}

F7

{F7}

Scroll Lock

{scrolllock}

F8

{F8}

Tab

{tab}

Escape

{esc}

F5

{F5}

Home

{home}

 

§      WP Insertion String
This specifies the hotkey to use to paste from the clipboard into your word processor. For most word processors, Ctrl-V will paste the current clipboard contents into the word processor.

§      Meter Threshold
When you do a word search, the text box in the status bar just below the Search Window will keep you informed of the progress of the search. Normally this just amounts to an indication in words of the various stages in the search process. For long searches a graphical progress "meter" bar will show you the current status. There is however a lot of overhead involved in displaying the graphical "meter" and you may want to turn it off except for very long searches where you need to have some idea of how much further you have to go (so you can abort the search if need be). This parameter allows you to set the threshold at which BibleWorks will begin to display the bar. The number is roughly equivalent to the number of distinct words resulting from the wildcard expansion of your search expression. Since simple searches are almost instantaneous anyway, you do not want the status bar displayed for them, as it will slow the search significantly. A value of 2000 is reasonable for most computers. A value of zero turns the graphical status bar off entirely.

§      Verse List Context
The Results Verse List Box in the Search Window can display results in three different modes. The results of a search can be displayed (1) as a list of references, (2) as a list of references along with a phrase from each verse , or (3) as a list of references along with the full text of each verse. When you are displaying a phrase from each verse in the Verse List Box, this field specifies how many words from the verse should be displayed in front of the first highlighted word.

§      Search Context
This parameter allows you to define the default verse context setting for BibleWorks AND type word searches and Linear String Searches. When you do an AND type word search on more than one word or a Linear String Search, the search will find all verses that contain all the specified words within the specified number of verses.

§      Misc Font Size
This option specifies the font size used in a number of List Boxes and textboxes in BibleWorks. Users should have no need to change the default setting.

§      Analysis Window Frequency Cutoff
The Analysis Window Frequency Cutoff settings govern what definitions and parsings appear in the Analysis Window. This section contains two settings, one for Greek and one for Hebrew. The vocabulary frequencies come from the Vocabulary Flashcard glosses files. The versions used for these files are GNM and WTM lemmas. If you use a version other than the GNM/GNT (and probably the BNM/BNT) and the WTM/WTT, the frequency numbers may not be correct for your version.

§      Default Text Editor
When you are creating a user-defined Bible version, you can edit the text of the Bible version just by clicking on the Edit button in the Version Database Compiler Window. This entry specifies the editor to use for editing the Bible text. By default, this is set to use write. In Windows 98 and following, this command will actually load WordPad, the RTF editor that ships with Windows.

§      Word Tip Settings
If you have Word Tips enabled (the default) a brief definition and morphology summary will appear in a popup window when you pass the mouse cursor over a Greek NT or Hebrew OT word. The window will not open until you have "dwelt" for a certain period over the word and it will remain open for a set period after the mouse stops moving. The Word Tips section allows you to set these time delays and also enable or disable Word Tips.

§      Found Text
This section lists formatting options for the display of search results found text in the Browse Window. The options are bold, italics, underlining, text color, and background color.

§      Exported Text Tag
This option lets you set the style name that is applied to RTF text exported to the clipboard. If you uncheck the "Tag Exported Text" check box no style name will be exported. This permits you to control how text is integrated into the target paragraph. It is also useful if you want to tag exported text for search and replace purposes.


Font Options


The Fonts Tab in the Options Window contains a number of controls which allow you to set the default typefaces, styles and sizes for the English, Greek, Hebrew, Cyrillic, Vietnamese, and Central European fonts used in the Search Window and Browse Windows. You can also change the default printer and clipboard fonts. For each language group, three different sets of fonts and fonts sizes can be selected. One set of fonts and font sizes is used for the Search Window, one set is used for the Browse Windows, and one is used for the printer and clipboard. To see a list of fonts that ship with BibleWorks and a discussion of BibleWorks Font and Keyboard Options see BibleWorks Keyboard Layouts .

 

Choosing a Font Set

To make any changes you must first select the Font Set that you want to work with. This is done by choosing one of the radio button options in the "Font Set to Edit" group box. You can choose one of three possible font sets:

 

§      Search Window Fonts - When you select this button, fonts and sizes in the "Font Sets" group box will show font settings used for the Search Window windows.

§      Browse Window Fonts - When you select this button, the fonts and sizes in the "Font Sets" group box will show font settings used for the Browse Window. The AW section to the right side of the window sets the size of the Analysis Window Analysis Tab fonts. The AW setting only changes the Analysis Tab setting. It does not change the size of fonts in other Analysis Window tabs.

§      Export Fonts - When you select this button, fonts and sizes in the "Font Sets" group box will show font settings used for text exported to the Clipboard or sent to the printer. When you select this font set, you can also set font-remapping options by clicking the "Edit Export Maps" button (see below).

 

After selecting the font set you want to edit, just click on the controls in the "Font Sets" area and choose the typefaces, sizes and styles that you want for each language group. You may want to experiment with different point sizes and styles. If you have a high-resolution monitor, for example, you may want larger point sizes. You may have to exit BibleWorks and reenter for all changes to become effective. You will be notified if this is necessary. Notice that the Command Line and list boxes will adjust automatically to new point sizes and fonts. The fonts defined as defaults for the Browse Window will be used also when you copy text to the BibleWorks editor.

 

Export Fonts

 

When you export text to the Clipboard or send it to the printer, the same fonts and point sizes as are used in the Browse Window will be used. They will not be changed for the exported text. This is not always desirable. Fonts which look good on the screen do not always look as good in print. This is the reason an option was implemented to force font conversions to the fonts used in the target medium.

 

By default the Export Fonts are the same as the Browse Window fonts unless this behavior is overridden by the settings in this section. Unless you change the font selections with the "Export Fonts" option selected, exported text will use the same fonts as are used for display purposes. Changing the fonts allows you to print with different fonts than the ones you use for the screen. However, if you choose to export Greek and/or Hebrew in Unicode, the Unicode settings at the bottom of the Fonts window will take precedence.

 

Unicode Fonts (Export Only)

 

The Unicode Fonts (Export Only) section enables you to change the Unicode export font and size for Greek and Hebrew. BibleWorks ships with two Unicode Hebrew fonts called "Ezra SIL SR" and "SBL Hebrew". Point sizes of 12 or 14 look good for each. BibleWorks also ships with the SIL Galatia Unicode Greek font and the SBL Unicode Greek font. The Microsoft Arial Unicode MS fonts also contain Unicode Greek and Hebrew.

 

The check boxes for exporting Greek and Hebrew resources as Unicode normally govern parts of the BibleWorks program except the Editor and exporting text using the verse copy settings. These settings govern, for example, the exporting of Greek and Hebrew text from the Lexicon Browser or the Analysis Window.

 

However, if the bottom check box is checked ( "Use these Unicode settings also for Verse text") these settings will override the settings in the Output Format Options panes (see below) which determine how Bible verse text is exported. So if all three of these check boxes are checked, Greek and Hebrew text exported from the Lexicon Browser, Analysis Window, Browse Window and Results Verse List box, will all be in Unicode. If you have the bottom check box checked, the Unicode setting options in the Output Format Options section will be grayed out and will reflect the override settings selected here.

 

CHM Module Settings

 

This section contains settings that affect how external CHM modules are displayed. It contains a list box which allows you to specify the default fonts size for external CHM modules.  The options are these:

 

X-large
Large
Medium
Small
X-small

 

The actual size displayed depends on how your Internet Browser is configured. Note that in order to implement this feature all modules had to be modified and rebuilt to use this setting. This feature will be implemented in new modules and old modules will be modified and reposted as time permits.

 

Font Remapping

 

The previous section describes how to change the fonts and font sizes used when you export text to the clipboard or printer. Some fonts, however, use entirely different keyboard mapping tables. If you want to export text using these fonts, the actual characters must be remapped to a different Keyboard Layout. For example, the final sigma may be on one keyboard character in one font and on another keyboard character in another font. Text designed for one font will not display properly using the other font unless the text is remapped.

 

BibleWorks provides a utility to do precisely this. It lets you define and customize font mapping files. For instance, if you wanted to convert Greek text using Bwgrkl, the BibleWorks Greek font, into text using the SIL Greek font, you would need to translate the text when the font is changed. BibleWorks ships with mapping files for commonly used Greek and Hebrew fonts, like the SIL fonts and the Linguist Software Greek and Hebrew fonts.

 

To use this feature you must first install the fonts that you want to be used for exported text. Then you simply change the typeface for the Greek or Hebrew font. You must also create a font mapping table, if one does not already exist, to tell BibleWorks how to translate a character in one font to the same character in the other font. Four sample mapping files are included (they have a .FMP extension). They map the BibleWorks Bwgrkl and Bwhebb fonts to Linguist Software (Hebraica and Graeca) and SIL (SIL Ezra and SIL Galatia) fonts.

 

To enable an already-existing font map, click the Edit Export Maps button. In the Font Mapping Tables window, then select the Open button. Select the font map that you want to use. Check the Enable check box, then click Close.

 

Creating Font Maps

 

To create or edit font map files, click on the "Edit Export Maps" button. This will open an editor which you can use to create or modify font map files. The font mapping files are very simple. A font map file consists of a text file listing the character mappings in two columns. The first column contains the character number in the source font (the BibleWorks font). The second column contains the translated character number in the destination font. So, for example, if character 35 in the source font maps to character 63 in the destination font, an entry in the font map file would read "35 63".

 

For fonts like the SIL Hebrew fonts, you have to precede vowel point characters with a '<' character. This tells BibleWorks that the character is a "forward spacing" character. This is necessary because SIL vowel point characters are typed before their consonant, while in some other fonts, like Hebraica and BibleWorks fonts, they are typed after their consonant. If a target character maps to two BibleWorks characters, simply include two ASCII numbers separated by a slash. See the sample SIL Galatia font for an example.

 

Setting Analysis Window Font Sizes

 

 If you select the "Browse Window Fonts" as the Font Set to Edit, a new column will be added to the Font Sets section under the title "AW". Changing these settings allows you to specify the font sizes of text displayed in the Analysis Window. The AW setting only changes the Analysis Tab setting. It does not change the size of fonts in other Analysis Window tabs.

 

 

Selecting Fonts for Double-Byte Languages (Chinese, Korean, etc.)

 

If you click on the "Double-byte Fonts" Button a Window will open to permit you to select the fonts that will be used for Arabic, Chinese, Korean and Japanese versions. The default font is "Arial Unicode MS" but since not all systems will have this font, you may need to specify another. These font selections will be used only if the font specified in the version's DBU file is set at "default".

 


Output Format Options

 

The Output Format Options Settings Window enables you to configure the various text and verse list Copy settings. There are three sections of the Output Format Options Window: Verse List (no text), Verse List or Range, and Selected Browse Text.

 

Keep in mind that when you copy or paste text into a word processor, the input focus will usually be placed at the end of the inserted text. If you start typing at that point, text will be added using the format of the inserted text, not the format of the text at the insertion point before the copy. This is the way all word processors work. One easy way to keep the original formatting is to type a blank and move the insertion point left before inserting the copied text.

 

Verse List (no text)

 

The Verse List (no text) window contains settings for configuring the export of verse reference lists. This window contains the following settings:

 

§      What to copy
This section enables you to select either the verses in the Search Window that are checked, or all verses.

§      Where to copy the verse list
This section enables you to select copying the verse reference list to the clipboard, the last BibleWorks editor window, a new BibleWorks editor window, Microsoft Word, or to another program file.  If you have another program (such as a word processor or e-mail program) that is already open, you can select a destination program for the information that you are copying. You can select a destination program from the dropdown list that appears next to this button. Make sure the application is open before opening the menu. Then select the application from the list of window titles. The information will be copied to the currently active window in that program. The target application must be able to handle RTF text properly for formatting information to be preserved in the transfer.

§      Output Format Options
This section enables you to configure the verse reference list output format. A sample output preview window appears below the Output Format Options section. The Sample output displays the verse references currently in the Search Window. Included in this section are the following options:

Add a new line after each reference. This option places each verse reference or range of merged consecutive references on its own line.

 

Merge consecutive references. This option merges references. When checked, verses in the same chapter appear together as a merged reference. For example, a string of references such as "Gen 1:1, Gen 1:2, Gen 2:1" would be converted to "Gen 1:1-2; 2:1".

 

Remove frequency data from the list. When there is more than one search hit in a verse, the number of hits in the verse appear after the verse reference in the Search Window with an asterisk (*) followed by the number of hits in the verse. When this option is checked, the frequency data is removed from the verse list. The frequency data is automatically removed if Merge consecutive references option is checked.

 

Consecutive verses more than this number will be replaced with the "ff" abbreviation. If selected this option specifies the minimum number of verses when the "f" and "ff" abbreviations are used for merged verse references. If this setting is greater than zero and the range only covers two verses, an "f" will be used instead of an "ff".  If you wish to merge references but not use the "f" or "ff" abbreviations, enter a large number in the box.

 

Reference separators. This section enables you to specify the separators that will appear between verses, between chapter and verse, and between references. The references separator is used only if the Add new line after each reference is turned off. When multiple verse references are being copied and the "New line after each item" option is off, the references will be separated by punctuation. These text boxes let you specify the different punctuation marks to use. This is useful for European users because outside the United States different delimiters are normally used than the colon and semi-colon.

 

§      Sample output
This preview window enables you to view the output of a portion of your Search Window verses using the settings chosen in the Output Format Options section. If your Search Window verses or your Output Format Options settings change, you can use the Refresh button to refresh the preview.

 

Verse List or Range

 

The Verse List or Range window contains settings for configuring the export of verse lists or ranges of text. This window contains the following settings:

 

§      Copy settings for this Menu Option
Select from this dropdown box the type of copy or source of copy that you wish to configure. Options in this box include Copy Verse List + Text, Copy Selected Results List Verse, Copy Browse Window Verse, and Open Popup Copy Window. These four options appear on the Copy button and the Search Window context menu.

§      Favorite Settings for this Menu Option
This dropdown box contains configurable preset copy configurations. Each configuration in the dropdown list contains the settings selected in the Verse List or Range window. You can have up to 20 preset copy configurations for each of the four menu options listed above. You can change the name of the configurations by selecting the configuration or one of the undefined configurations, then type a new name for that configuration in the dropdown box. The new configuration will appear on the Copy button or Search Window context menu. After creating a name for your configuration, select the content and formatting options you prefer from the sections in the Verse List or Range window.

§      What to copy
This section enables you to select either the verses in the Search Window that are checked, or all verses.

§      Where to copy the verse list
This section enables you to select copying the verse list to the clipboard, the last BibleWorks editor window, a new BibleWorks editor window, Microsoft Word, or to another program file. If you have another program (such as a word processor or e-mail program) that is already open, you can select a destination program for the information that you are copying. You can select a destination program from the dropdown list that appears next to this button. Make sure the application is open before opening the menu. Then select the application from the list of window titles. The information will be copied to the currently active window in that program. The target application must be able to handle RTF text properly for formatting information to be preserved in the transfer.

§      What Versions to include
This section enables you to select what versions you want to include in the copy. You can copy either the current search version, the version used to create the search results list, all of the versions in the Browse Window, or you can specify what version or versions you want to copy.

§      Output Format Options
This section enables you to specify the formatting you want for your copied verses.

Export Unicode Greek - If this option is checked verse list Greek text will be exported using the Greek Unicode font specified in Tools | Options | General | Fonts | Export Fonts | Unicode Fonts. If this check box is grayed out, it means that this option has been overridden by the "Use these Unicode settings also for verse text" option in Tools | Options | General | Fonts | Export Fonts | Unicode Fonts. If you want to set the Unicode options for each verse copy favorite individually, you must turn off the above setting in the Fonts pane.

 

Export Unicode Hebrew - If this option is checked verse list Hebrew text will be exported using the Hebrew Unicode font specified in Tools | Options | General | Fonts | Export Fonts | Unicode Fonts. If this check box is grayed out, it means that this option has been overridden by the "Use these Unicode settings also for verse text" option in Tools | Options | General | Fonts | Export Fonts | Unicode Fonts. If you want to set the Unicode options for each verse copy favorite individually, you must turn off the above setting in the Fonts pane.

 

Interleave Versions - When copying multiple verses from multiple Bible versions, this option will copy verse text from all Bible versions selected before moving to the next verse in the list. If this option is off, (1) text from multiple verses will be copied from a single Bible version at a time; and (2) after all verses from a single Bible version are copied, the same verses will be copied from the next Bible version.

 

Add New line after each verse - If this option is checked, when multiple verses or references are being copied, each verse or reference will be separated by a line break. If this option is not checked, all verses or references will appear in a single large paragraph.

 

Use user Defined Book Names - If this option is checked, when Bible references appear in the copied information, the Bible Book Names defined in the Tools | Options | Bible Versions | Book Names window will be used. Otherwise the default BibleWorks names will be used. For more information on how to set user-defined book names, see Book Name Abbreviations. 

 

Include Translator Notes - This option includes embedded version notes, if available for that version.

 

Export Colors (hit highlighting) - This option includes the hit highlighting during the text output. If this option is checked, any displayed text coloring will also be exported along with the text.

 

Superscript Verse Numbers (internal) - This option includes the verse references as superscripted numbers. This option is only valid when the verse number appears alone, separate from the chapter number.

 

Export Formatting (bold, italics, etc.) - this option specifies that formatting present in the Bible text will be copied along with the text.

 

Place reference before text - This option specifies that, when Bible text is being copied, a verse reference for the text will be placed in front of the text.

 

Place reference after text - This option specifies that, when Bible text is being copied, a verse reference for the text will be placed after the text.

 

Enclose verse text in quotes - If this option is checked, the exported verse text will be enclosed in quotation marks.

 

Hebrew line wrap width (Non-Unicode) - This setting specifics the line wrap width of exported non-Unicode Hebrew text. This option only applies when Hebrew text is being copied, and when it is exported using a non-Unicode font. This setting enables proper word wrap when Hebrew text is pasted into a word processor. Most word processors do not support the left wrapped text. So when lines of Hebrew text are longer than one line, the word processor will break the line and wrap it, but the line will be broken incorrectly. With this option, you can specify a column width for the Hebrew text and have BibleWorks automatically break and wrap Hebrew lines when you are copying. A hard return will be placed at the end of each line. In the text area for this option you can specify the maximum width of the lines as they are wrapped for exporting. You should make it less than the maximum line width in the document you are creating.

 

§      Reference Format
This section enables you to specify the formatting of the verse reference. A dropdown box enables you to enter formatting tags for including as part of the reference the book name (<book>), chapter reference (<chapter>), verse reference (<verse>), version name(<version>), paragraph returns (<p>), tabs (<tab>), bold (beginning <b> and ending </b> tags), and italics ( beginning <i> and ending </i> tags). You can enter the formatting tags and any other text in the text input box in the order you want it to appear when you copy text. To enter tags using the dropdown box, first place your cursor in the text input box in the locate where you want the formatting tag to appear, then select the appropriate tag from the dropdown box.

Selected Browse Text

 

The Selected Browse Text window contains settings for configuring the export of selected Browse Window text. This window contains the following settings:

 

§      Favorite Settings for Browse Window Copy Menu
This dropdown box contains configurable preset copy configurations. Each configuration in the dropdown list contains the settings selected in the Selected Browse Text window. You can have up to 20 preset copy configurations. You can change the name of the configurations by selecting the configuration or one of the undefined configurations, then type a new name for that configuration in the dropdown box. The new configuration will appear on the Copy button, the Search Window context menu, and the Browse Window context menu. After creating a name for your configuration, select the content and formatting options you prefer from the sections in the Selected Browse Text window.

§      Where to copy the selected text
This section enables you to select copying the selected text to the clipboard, the last BibleWorks editor window, a new BibleWorks editor window, Microsoft Word, or to another program file.  If you have another program (such as a word processor or e-mail program) that is already open, you can select a destination program for the information that you are copying. You can select a destination program from the dropdown list that appears next to this button. Make sure the application is open before opening the menu. Then select the application from the list of window titles. The information will be copied to the currently active window in that program. The target application must be able to handle RTF text properly for formatting information to be preserved in the transfer.

§      Reference Format
This section enables you to specify the formatting of the verse reference. A dropdown box enables you to enter formatting tags for including as part of the reference the book name (<book>), chapter reference (<chapter>), verse reference (<verse>), version name(<version>), paragraph returns (<p>), tabs (<tab>), bold ( beginning <b> and ending </b> tags), italics (beginning <i> and ending </i> tags) and superscript (beginning <sup> and ending </sup> tags). You can enter the formatting tags and any other text in the text input box in the order you want it to appear when you copy text. To enter tags using the dropdown box, first place your cursor in the text input box in the locate where you want the formatting tag to appear, then select the appropriate tag from the dropdown box.

§      Output Format Options
This section enables you to specify the formatting you want for your copied text. 

 

Export Unicode Greek - This option exports Greek text using the Greek Unicode font specified in Tools | Options | General | Fonts | Export Fonts | Unicode Fonts.

 

Export Unicode Hebrew - This option exports Hebrew text using the Hebrew Unicode font specified in Tools | Options | General | Fonts | Export Fonts | Unicode Fonts.

 

Use user Defined Book Names - If this option is checked, when Bible references appear in the copied information, the Bible Book Names defined in the Tools | Options | Bible Versions | Book Names window will be used. Otherwise the default BibleWorks names will be used. For more information on how to set user-defined book names, see Book Name Abbreviations. 

 

Export Colors (hit highlighting) - This option includes the hit highlighting during the text output. If this option is checked, any displayed text coloring will also be exported along with the text.

 

Export Formatting (bold, italics, etc.) - this option specifies that formatting present in the Bible text will be copied along with the text.

 

Superscript Verse Numbers (internal) - This option includes the verse references as superscripted numbers. This option is only valid when the verse number appears alone, separate from the chapter number.

 

Place reference before text - This option specifies that, when Bible text is being copied, a verse reference for the text will be placed in front of the text.

 

Place reference after text - This option specifies that, when Bible text is being copied, a verse reference for the text will be placed after the text.

 

Enclose verse text in quotes - If this option is checked, the exported verse text will be enclosed in quotation marks.

 

Remove CR/LF characters (Browse mode)  - If this option is checked, breaks between verses in copied Browse Window text will be removed. It has no effect on text copied from a window in multiple version mode.

 

Hebrew line wrap width - This option determines how Hebrew text is exported when you do not have Unicode export enabled. Non-Unicode fonts do not wrap automatically as the line width is changed. This option allows you to export text in the BibleWorks Hebrew font (BWHEBB) to any word processor and still have the text display properly. To do that ensure that the line width in the target word processor is less that the value entered here.

 


Setting Search Limits

 

This Window permits you to limit searches to a particular passage of Scripture. The Search Limits tab in the Setup Window can also be activated by clicking on the Command Line Versions Button  and selecting "Choose Search Limits", or from the Main Menu by selecting Search | Set Search Limits or Tools | Options | Searching | Search Limits. You can also access the Search Limits Window by double-clicking on the "Limits" area in either the Main Status Bar or the GSE Status Bar.

 

Search Limit Options

 

In this window there are three choices for how to set search limits:

 

§      Do not apply any limits to the search
Choosing this option deactivates all search limits. All searches will search the entire Bible version. If this option is selected, the settings from other sections of this Window are ignored.

§      Limit the search using the books selected here
If this option is selected, searches will be limited using the limits specified in the tree view window. To see all of the books, you will need to scroll down in the window. With the Select buttons (NT, OT, Apoc, and Clear All), you can quickly select or unselect all books, the entire Old Testament, New Testament, or the Apocrypha.

§      Limit the search using a custom search range
If this option is selected, the search will be limited using the settings in the "Predefined Ranges" window. This allows you to create customizable preset search ranges. It also allows a finer level of granularity in the search limit range. You can specify arbitrary books, chapters, and verses in the creation of search limits.

When you click on a range in "Predefined Ranges" the selected range will be used to limit all searches. The details of the selected range will be displayed in the "Add new Predefined Range" section. To edit the existing ranges, select the predefined range you want to edit, then edit the range in the "Add new Predefined Range" section.

You can tell BibleWorks to use a BibleWorks verse list file (VLS) as the search range by clicking on the "Use Verse List File" button. This will display a list of all the VLS files in the BibleWorks ASE folder (something like "c:\BibleWorks 9\ASE"). To use a VLS file as a verse range the file must be located in the ASE folder.

 

Adding New Custom Ranges

 

To add a new custom range, select one of the current predefined ranges, then in the "Add new Predefined Range" section, change the Description text to the name of your new custom range. Enter the version and the verse range you want to include in your custom search range. Click on Save to save your new custom search range.

 

You can also edit the custom ranges by clicking on the "Edit" button. This will load the entire list of custom ranges in raw form into an edit control. Make the changes that you want and click on OK. The raw file requires that the Description, Version, and Range setting be separated by a forward slash.

When adding verses to the Range field, multiple sub-ranges must be separated by semicolons. If you do not put the full verse reference, BibleWorks will make a judicious guess at what you intend. A book name by itself, for example, will be interpreted as the entire book. For example, to create a search limit for the four gospels, you would enter:

 

Mat;Mar;Luk;Joh

 

You can also create ranges that span books and chapters, such as

 

Joh 14-17; 1Co 13, 1Ti 1:1 - Heb 13:25


To delete a predefined range, select it from the "Predefined Ranges" list and click the Delete button.

 

Using a Verse List File as a Search Limit - Setting via Command Line

 

A verse list search limit can be set on the command line without having to open the Search Limits Window. For example you might have a verse list file called test.vls. To use this as custom search limit:

 

1. Enter "cl-test.vls" as the description (don't enter the quotes)

2. Enter the three version ID used in the file

3. Enter test.vls as the range.

 

A quick way to do this would be to just enter

 

l test.vls

 

on the command line.



Wildcards

The Searching | Wildcards window in the Options Window contains an interface for defining special wildcard characters for use in Hebrew vowel-point sensitive searches. In order to use these special Hebrew wildcards in a search, you must turn on Vowel Point Sensitive Searching (Hebrew) on the Command Line context menu. This window is opened by selecting Tools | Options | Searching | Wildcards from the main menu of BibleWorks, or you can select Define Hebrew Vowel Wildcards on the Command Line context menu.

 

An example of the power of the Hebrew vowel point wildcards may be helpful.  Suppose you wanted to find all occurrences any consonant with a hireq, followed by a doubled yod.  Here is the search you would enter:To enter the box with a plus in it (standing for a consonant) press the <insert> key and release it. Then press the number 1 key and press the <insert> key again. Note that for this search you must also select Dagesh Sensitive Searching (Hebrew) on the Command Line context menu, or turn off the Ignore Dagesh in Hebrew Searches option in Tools | Options | General | Flags | General Hebrew Options. Note that vowel point sensitive searching must also be on if you have dagesh sensitive searching on.

 

This feature was introduced to address a longstanding problem with Hebrew vowel-point searches. It has been very difficult to do wildcard searches with vowel-point sensitive Hebrew. The reason is obvious to anyone who has tried it. There was no way to distinguish between consonants and vowels, and the display of the * and ? wildcard characters with Hebrew text was problematic at best. The solution that we have come up with is a set of wildcard characters specifically designed for use with Hebrew text. There are five new wildcards that can be used with pointed Hebrew text. The meaning of each one can be changed to suit your needs simply by editing the list of characters in the text boxes associated in the display with each wild card. In the text boxes, the alephs are just holders for the vowels. They are just there to make the vowels readable.

§      (Ins-2) One Vowel
The first wildcard is entered by pressing the INS key followed by the numeral 2 key. Then press the INS key again to turn off the special code insertion mode. The wildcard will appear as a small open box under its consonant. It represents any of the vowels in the list.

§      (Ins-5) Zero or One Vowel
The second wildcard is entered by pressing the INS key followed by the numeral 5 key. Then press the INS key again to turn off the special code insertion mode. The wildcard will appear as a small closed box under its consonant. It represents any of the vowels in the list or none of the vowels. It is somewhat similar to the familiar ? wildcard except that it also matches zero vowels, whereas the ? requires the presence of a single character.

§      (Ins-1) Any Consonant µ
The next wildcard is entered by pressing the INS key followed by the numeral 1 key. The wildcard will appear as an empty box with a plus sign in it. It represents any of the consonants in the list. The list initially contains all consonants with and without dagesh.

§      (Ins-4) Consonants without Dagesh ¤
The next wildcard is entered by pressing the INS key followed by the numeral 4 key. The wildcard will appear as an empty box. It represents any of the consonants in the list. The list initially contains all consonants without dagesh.

§      (Ins-3) Consonants with Dagesh £
The next wildcard is entered by pressing the INS key followed by the numeral 3 key. The wildcard will appear as a box with a dot in the middle. It represents any of the consonants in the list. The list initially contains all consonants with dagesh.

When you click the Default button next to each field, the default values for that wildcard are restored.

 


Setting Favorite Version Options

 

The Bible Versions | Favorites window provides three related options having to do with the use of Search and Display Versions in BibleWorks:

 

Setting the Current Search and Display Versions

If you click on the "Choose Search Versions" Button a window will open that enables you to select the current Search Version for Command Line Searches. If you click on the "Choose Display Versions" button, a window will open that enables you to select the current Display Versions used in the Browse Window when it is in Multiple-Version Mode. This is one of many ways in BibleWorks to change Search and Display Versions. 

 

Creating Search and Display Version Favorites

If you use BibleWorks frequently you will find that you use some combinations of Bible versions more than others.  It can become tedious to change the mix of versions displayed in the Browse Window back and forth between favorite combinations if you do it by selecting and deselecting versions. To solve this problem BibleWorks allows you to define sets of versions that you like to work with and give them names that you can use to recall them later.

 

Creating Display Favorites

To create a favorite display version setup, all you have to do is click on the "Add" button in the "Search and Display Favorites" group box. This will create a new favorite based on the current display versions set in the Browse Window. A default name will be given to the favorite composed of the current search version plus the list of display versions (e.g. "KJV+KJV GNT NIV"). You can change this name to something more descriptive like "My_Favorite" and also add and remove versions by clicking on the "Edit" Button. If you change the name of the favorites you are encouraged to use names with no blanks and to keep the names short. Instead of blanks use the underscore character "_". The reason for this is that you can load the favorites from the Command Line if they have no blanks.

 

Using Display Favorites

If you want to change the Browse Window and Command Line so that they use one of your predefined favorites, all you have to do is click on the Command Line Versions Button . When you do that you will notice that the Display Favorites that you defined have been added to the menu. All you have to do is select the one you want to use. An alternative method is just to enter "display" or just "d" on the Command Line followed by the custom name that you have defined.

Creating Parallel Version Favorites

The Parallel Versions option in BibleWorks allows you to open a single window with multiple versions that are displayed side-by-side and scroll in unison. This is done by opening the Parallel Versions Setup Window and choosing the versions you want to use. This can become tedious if you use the same versions frequently. For that reason a feature has been added that permits you to define Parallel Version favorites, in a fashion very similar to what you can do with Search and Display Versions.

Creating a Parallel Version Favorite

To create a Parallel Versions Favorite all you have to do is click on the "Add" Button in the "Parallel Versions Favorites" group box. A new "favorite" will be initialized using the display versions in the current Browse Window. You can then edit the favorite by clicking on the "Edit" button to change the name and/or the versions included. If you want to change the order of the versions, select the version you want to move and click on "Up" or "Down". To delete a version, highlight the version by clicking on it and click on "delete". To add a version, find it in the upper list boxes, select it, and then click on the "Add" button. It will be inserted after the selected version in the Favorites List Box.

Reviewing and Editing the Favorites

For both the Parallel Favorites and Display Favorites group boxes, the list of favorites on the left side shows all of your favorites. When you click on a favorite in this list, the details for that favorite are displayed in the text area on the right. If you double-click on the favorite, or if you select it and click the Edit button, a window opens in which you can modify the favorite. You can display a Parallel Versions favorite by entering "p" on the Command Line followed by the custom name of the preferred Parallel Versions favorite.

Choosing Popup Versions

There are many places in BibleWorks where moving the mouse cursor over a verse reference will pop up a temporary window to display the verse text. Clicking on the "Choose Popup Versions" button will open a dialog which permits you to determine which versions are displayed.



Book Names

The Book Names Tab in the Options Window permits you to customize the Bible book names used in BibleWorks, both for display and for searching. The Bible books names are used when text and references are displayed in Browse Windows, when text and references are exported to the clipboard, when you enter references on the Command Line, and various other places in BibleWorks. When you enter verse references to look up on the Command Line, you enter the appropriate abbreviation for the book containing the verse that you want to look up. For example, <Rom 8:28>. By default BibleWorks recognizes three-letter abbreviations which, for the most part, are made up of the first three letters of the book. You can define aliases for these abbreviations, which BibleWorks will then recognize when you do searches.  You can define up to six aliases for each book. The most prominent part of the Book Names Tab is the list of current book names and aliases. This is shown in the center of the window. Across the top of the window you will see the filename for the current book name scheme. You can define more than one book name scheme and save each one to a different file, but only one can be active at a time. The default book names file is books.bna.

The list of book name abbreviations contains the following columns:

 

§      Def
This is the internal three letter abbreviation of the book. It is always used in verse lists and file names constructed from book names (user notes). This entry cannot be edited. It usually is the first three letters of a book name.

§      Browse Window
This is the book name that is printed with references in the Browse Window. It can contain blanks if you like. This allows you to specify how book names in text that you export are spelled.

§      Export
This is the book name that is used when Search Window verse lists (just the lists, not including the text of the verses) are exported to the clipboard or BibleWorks editor. It can contain blanks if you like.

§      Alias 1, Alias 2, Alias 3, Alias 4, Alias 5, Alias 6
These are Command Line aliases for the book names. The Command Line will accept them as valid book names for searches. You can enter up to six aliases, but you must have at least one and the entries cannot contain any blanks. When you enter a reference on the Command Line, these entries are first checked for an exact match, and if no exact match is found, then all these entries are checked for a partial match.§         Editing the book names list
To edit a book name, double-click in the Def. column (the first column) on the book name that you want to edit. A window will open for that book name, allowing you to edit the fields listed above.

§      Checking consistency
When you click the Check Consistency button, BibleWorks will check your abbreviations for duplicates and inconsistencies. If any are found the list will not be implemented. It is suggested that you use the Check Consistency button to check the entries before exiting, so that you can have the opportunity to make any necessary corrections.

 

Multiple configurations

You can define many different sets of book names. This may be useful if you are working in different languages -- you might have one set of book names in French, and another set of book names in English. The way to manage different sets of book names is to use different book name files. The name of the currently loaded book name file is displayed across the top of this window. To create a new book name file, make the changes you desire in the current settings, click on the Save as button, and give the file a new name. To switch to another previously saved book name file, click on Open and select the file to load. When you press Save, the changes to the currently loaded book name file will be saved. BibleWorks supplies a number of different book name files for you to use. It might be helpful to keep in mind that the file name of the current book name alias file is stored in your configuration file. This means that you could have a different configuration file (using the Configuration Manager) and hence a different set of aliases for use with different languages.

 


Editing Verse Maps

The Verse Maps Options Tab of the Options Window  permits you to edit the tables that are used in BibleWorks to convert a verse reference in one version to a verse reference in another version. These tables are necessary because several of the versions supported by BibleWorks have different verse numbering schemes and text bases. This means there is not, for example, a one to one correspondence between the verses in the Hebrew and the LXX Greek Old Testament, or between the Hebrew text and any English version. When you look up a verse in one of these versions BibleWorks will attempt to display the right verses for each version (if they exist) even if the verse numbers do not match. In many cases, particularly where the LXX is concerned, the choice of which verses to display is quite subjective.

 

Mapping File Format

Rather than impose our own choices on the user, we have decided to implement verse mapping databases that users can customize. These user-definable databases are accessed by selecting Tools | Options | Verse Maps from the main menu of BibleWorks. When you do that, the verse maps editor will open. To create your own verse mappings, follow the patterns already there and make or edit the verse mapping entries. There is a mapping file for each version in BibleWorks. Each line in a mapping has the following entries:

 

§      Source Ref - The verse reference in the version being edited

§      Dest Ref - The corresponding reference in one of the original language versions or the NRS. The possibilities are WTT, GNT, LXT or NRS.

§      Ver - The BibleWorks name for the version used in the Dest Ref column. Each Version in BibleWorks has a short name, three or more letters long, used to reference the version in BibleWorks.

§      Comment - A user supplied comment. This is just for documentation and does not affect the mapping.

If the verse reference in Source Ref specifies a verse range, then the reference in Dest Ref must cover the same number of verses. Ranges cannot span books. The reference specified in Dest Ref (and Ver) does not specify the origin of the Bible translation being mapped. It would be better to think of the reference in Dest Ref and Ver as a reference in an imaginary universal Bible version (non-existent) to which all verses in all versions can be mapped. This provides a reliable way to map a verse reference from any one real Bible version to another. The rules for adding a verse to the mapping file are as follows:

 

§      If a verse in the version being mapped exists in the WTT or GNT and the verse numbers in the version and GNT/WTT are different, there should be an entry in the mapping file.

§      If a verse in the version being mapped exists in the WTT or GNT and the verse numbers in the version and GNT/WTT are the same there should NOT be an entry in the mapping file. The verse mapping routines will assume that all verses in the version, without an entry in the mapping file, have a corresponding verse in the GNT or WTT and that the reference is the same in both versions. This keeps the size of the mapping file small.

§      If the verse in the version being mapped is in an Apocryphal book, and has a corresponding entry in the LXX, but the reference is different in the two versions, there should be an entry in the mapping file.

§      If the verse in the version being mapped is in an Apocryphal book, and has a corresponding entry in the LXX, and the reference is the same in the two versions, there should NOT be an entry in the mapping file. The verse mapping routines will assume that all Apocryphal verses in the version without an entry in the mapping file, have a corresponding verse in the LXX and that the reference is the same in both versions. This keeps the size of the mapping file small.

§      If a verse in the version being mapped has no corresponding verse in the WTT or GNT, or LXX if it is Apocryphal, and there is a corresponding verse in the NRS, then there should be an entry in the mapping file with NRS in the last column.

§         If a verse in the version being mapped has no corresponding verse in the WTT, GNT, LXX or NRS, then there should be an entry in the mapping file with the same verse reference in column 1 and 2 and with the third column containing the BibleWorks name for the version in question. This tells the verse mapping routines that this verse is unique to the version being mapped.

The LXX-Hebrew mappings for BibleWorks were originally obtained from the University of Pennsylvania Center for Analysis of Texts (CCAT) Aligned LXX-Hebrew Database, courtesy of Dr. Robert A. Kraft. See the section on Database Source and Copyright Information  for details. These verse mappings have been corrected by BibleWorks staff, and extensively modified as a result of input from users. BibleWorks contains mapping files for almost every Bible version. These have been developed over many years by BibleWorks staff with input from many users, and especially from Mark Eddy, for whose unselfish work we are thankful. The mapping files are saved with a .vmf extension and are ASCII text files. The actual files used by BibleWorks to do the mapping are saved in binary files with the same name, but with a .vmc extension. BibleWorks will construct the binary files behind the scenes from your text files, so you do not have to worry about it. If you edit one of the text files outside of BibleWorks, you will need to delete the corresponding .vmc file, so that BibleWorks will know that it needs to construct a new one the next time you run it.

Editing verse maps 

To view the verse map for a specific version, simply select the language group for the version from the Languages control, and then select the Bible version from the Version control. To edit a particular entry in the mapping, double-click with the left mouse button on the entry in the Source Ref column. A small window will open in which you can edit the information for the four mapping columns described above. If you want to copy or delete rows, you must first select them by clicking with the left mouse button (select multiple rows by clicking and holding the shift key or control key) in the Source Ref column. Then click on the Edit button. This button opens a menu with basic clipboard features (cut, paste, etc.). In addition, the Edit button allows you to insert blank rows into the mapping table. In this way you can cut, paste and delete rows of references. After editing a mapping table, you should press the Check Consistency button to test the mapping. This will test the mapping for duplicate entries and mapping problems. When you are sure you want to keep your mapping table, press the Save button. The .vmc and .vmf files for that version will be created.

Manual Editing 

If you like, you can edit the mapping files externally. They are stored in ASCII text files with a .vmf extension (VMF stands for verse mapping file). Just follow the format that you see in any of the .vmf files. After editing you should load them into the Verse Map window so you can check them for consistency. All versions have a .vmf file. It will have the same name as the version but with the .vmf extension. After you edit a .vmf file manually you should delete the corresponding .vmc. This is a compiled version of the mapping file. If you delete the .vmc file the program will create a new one when you start the program. The compiled files are created to make loading of the maps in real time more efficient.

A Mapping Example 

As an illustrative example consider a sample from the Latin Vulgate VUL Mapping file. It has the following lines:

 

Psa 35:1

Psa 36:1

WTT

Psa 35:1

Psa 36:2

WTT

Psa 35:2

Psa 36:1

WTT


Suppose that the WTT and VUL are display versions. And suppose your search version is the VUL and you enter the reference Psa 35:1 on the Command Line. The program searches all the entries in column one from beginning to end. Everywhere it finds Psa 35:1 it will display the corresponding WTT verse. In this case Psa 36:1 and Psa 36:2 will be displayed. Now suppose you make the WTT your search version and enter Psa 36:1 on the Command Line. The Browse Window will display Psa 36:1 in the WTT and Psa 35:1 and Psa 35:2 in the VUL version. It will search the Dest Ref column from beginning to end and display a VUL verse every time it finds Psa 36:1.Note that if you want the same verse number to be displayed in two versions in addition to a collateral verse, you will need two entries. The English Version Psalm headings are good examples. The KJV mapping file, for example, has these lines:

 

Psa 3:1

 Psa 3:1

WTT

Psa 3:1-8

Psa 3:2-9

WTT


The Psalm Headings in the KJV are combined with the first verse of the Psalms. But in the WTT they are in verse one, with the Psalm text beginning in verse two. The above fragment handles this case. If you have the KJV as your search version and enter Psa 3:1, you will get both Psa 3:1 and Psa 3:2 in the WTT. But if you have the WTT as your search version and enter Psa 3:1, you will get only Psa 3:1 in the KJV. Note the duplicate Psa 3:1 entry in the first row. This is necessary here, but remember that if a single verse maps completely to another single verse with the same reference, a mapping file entry is usually not needed (this would make for very large mapping files!).When you enter a reference in a version that is not the WTT, GNT, LXX or NRS, and want to display a verse in a version that is also not the WTT, GNT, LXX or NRS, two mapping files are used. For example, if you have the KJV and TOB as your display versions and the KJV as your search version, and enter Psa 3:1 on the Command Line, this is what happens when the Browse Window decides what verses to display: the KJV mapping file is opened and the Source Ref column is searched for all entries of Psa 3:1. The corresponding Dest Ref column (WTT) entries are stored. Then the TOB mapping file is opened and its Dest Ref column is searched for the previously stored entries from the first mapping file. For every one that is found, the corresponding Dest Ref column TOB reference is displayed. The best way to learn how all this works is to open up some mapping files and experiment. Make sure you back up the mapping files (all .vmc and .vmf files) first. If you make a mistake, however, you can always re-install these files from your CD.

 


Changing the Version Display Order

This tab can also be opened by selecting View | Version Display Order from the Main Menu or from the Browse Window Options Button  menu. When you are in Multiple Version mode in the Browse Window , the text from several Bible versions can be displayed at the same time. The Version Order Window lets you change the default order in which Bible versions appear.  To change the order of a Bible version, click on the Bible version in the list, and click the Move up and Move down buttons. The selected Bible version will move up or down in the list accordingly. To move a Bible to the very top of the list or bottom of the list, select the Bible version and click on the Move to Top button or Move to Bottom button. The list of versions in this window is fairly long. If you are interested in just ordering the versions currently displayed, you can click on the Show Active Only check box. If this box is checked, only the current display versions will be shown. You can save the version sort order to a file. This option enables you to have different version sort orders for different study needs. The version order files are saved as .vdo files. You can open a version sort order file from the Command Line by typing <order filename> (without the brackets) and pressing Enter on your keyboard. For example, a version order file named "grkheb" would be opened by typing <order grkheb> and pressing Enter. You can also use the shortcut <o grkheb>. Be sure not to include any spaces in the file name, or you will not be able to open the version order file on the Command Line. A strategy for creating version sort orders is to create your version display favorite file and a companion version sort order file with the same name. In this way it is easy to remember the name of the sort order file. For example, a display favorite file containing BGT, WTT, ESV, could be called bgtwttesv. The companion version sort order file could sort the versions in the order BGT, WTT, ESV, and use the same name bgtwttesv.

 


Changing the Book Order

 

You can change the Bible book sort order used in the Search Window, Verse List Manager, and other parts of BibleWorks. Each version can have its own custom sort order. To change the book sort order, select the Bible version in the list of Bible versions. The current book sort order is listed to the right of the Bible version name. BibleWorks supplies a number of common book sort order (BSO) files. Select the desired BSO file from the Ordering dropdown box, then click the Apply this ordering to selected Bibles button. If you want to create your own sort order or modify an existing order, select a book sort order file from the Ordering dropdown list, then click the Edit sort order button. In the Edit Verse List Sort Order window, select the book name to move, then use the two arrow buttons at the right of the book names window to move the book up or down. The Reset button returns the books to their original order. Type a new name in the Description box at the top of the window, then click the Save button. Changing the book sort order is useful for replicating the book order of some key manuscripts or traditional sort order (such as the traditional Hebrew Bible sort order or the Septuagint sort order). You may also want to change the book sort order to display search results for certain books higher up in the search results for more rapid review of search results in specific Biblical books.

 

 


Updating, Adding, and Removing Databases

 

The Updates tab in the Options Window contains the controls you need to update and modify your BibleWorks installation. There are two different update options available: 

 

§      Web Updates
If you want to check the BibleWorks server for program and database updates, press the "Check for Updates" button. This will connect you to the BibleWorks Internet server and show you available updates. You may need to first connect to the Internet before pressing this button. For more information see Getting Updates.

§      Adding Bible Versions, Removing Other Databases
If you need to add or remove databases or Bible versions to your installation, insert the BibleWorks program disk and click the "Proceed" button in the "Add or Remove Databases" section. This will open InstallShield, which will walk you through the steps to add and remove databases and versions.



The Configuration Manager

BibleWorks is probably one of the most configurable programs you are likely to find. You will probably find many different configurations that suit different purposes. And you might begin to wish that there was a way to store different configurations and save them for later use. The Configuration Manager will help you to do precisely that.

 

Enabling the Configuration Manager 

To enable the configuration manager go to the Options Window and open the Startup Options section. Then check the "Enable Configuration Manager" box. Then shutdown BibleWorks.

 

The next time you start BibleWorks you will not see the familiar BibleWorks interface. Instead you will see the BibleWorks Configuration Manager Window. The window consists basically of a list of named configurations. To activate one you just click on it and then click on "Load".

 

Creating a New Named Configuration 

To create a new configuration proceed as follows:

 

§      In the list of available Named Configurations click on the one that you want to use as the basis of the new configuration. If the list is empty, the default configuration will be used as the basis for your new configuration file.

§      Click on the "New" button. You will be prompted for a name to give the configuration. Name it anything you like but you should use only alphabetic characters. The name will be used as a filename so you can only use valid file name characters. Blanks are permitted of course. Then click on OK.

That's all there is to it. To start the new configuration just click on it, and then click on "Load". Make whatever changes you want in the program and exit as you always do. Then the next time you start BibleWorks the new configuration will be in the list. If you want to delete a Named Configuration just click on it and click on the "Delete" button.

 

Reinitializing and returning to the Default Configuration 

The group box at the bottom of the Configuration Manager provides you with a variety of ways to startup without using the Named Configurations. The caption of the group box tells you where the default configuration file is located. You have two options:

 

§      If you just click on "Load" the indicated default initialization file will be loaded and BibleWorks will be started.

§      If you click on "Initialize and Load" the default initialization file will be deleted and BibleWorks will be started. This will start BibleWorks with all default settings.

In both cases if you have the "Enable Configuration Manager" check box checked, BibleWorks will start with the Configuration Manager enabled. Otherwise it will be disabled.

 

Hiding Configuration Details 

If you enable the check box labeled "Hide Configuration Details", the Configuration Manager startup window will be simplified to include only the list of available configurations. If you enable this option in the Configuration Manager Window, you must go to the Option Flags tab under the Options Window to turn it off again. This option is useful especially for network setups where the system manager wants to enable multiple users to have their own configuration files but wants to hide confusing configuration details from them. 

 

Use New Directory for Each Configuration 

If you enable the check box labeled "Use New Directory for Each Configuration", the Configuration Manager will create a new set of user directories for each new configuration. They will be placed in a new directory called "Config" under the BibleWorks Directory. Only directories containing user-configurable files will be duplicated. This is useful, for example, if you want to have a different set of notes for each configuration.

 


Configuring BibleWorks for Use on a Network

 

There are two ways to install BibleWorks on a network: 1) Standalone configuration, or 2) Server configuration.

 

Installing BibleWorks in Standalone configuration

 

In a Standalone configuration, BibleWorks is installed locally on each workstation on the network. With Standalone configuration, no data is shared between workstations and when BibleWorks needs to be updated, each workstation will need to be individually updated. Here are the installation steps for BibleWorks in Standalone configuration:

  1. Using an account with Administrator privileges, install BibleWorks onto a workstation just as you would normally install BibleWorks on a home computer. Note: When entering activation codes: If you received one BW90 and BNET activation code per node, then use a separate code for each machine.

    • If you received one BW90 and BNET activation code per node, then use a separate code for each machine.
       
    • If you received only one BW90 and BNET activation code, use that code for all machines.
       
  2. The installation program should instruct you to restart after the files are all copied. Restart your computer.
     

  3. Using an account with Administrator privileges, run the program and activate the program and all modules.
     

  4. Using an account with Administrator privileges, apply any available BibleWorks 9 updates from the Internet (Help | BibleWorks on the Internet | Check for updates).  
     

  5. Shut down BibleWorks 9.

 

Installing BibleWorks in a Server Configuration

 

In a Server configuration, the installation procedures are a little more involved, but no files, except for a shortcut link, are stored on the workstations on the network. In this configuration, only the server installation needs to be updated when applying BibleWorks updates and patches. Setting up a Server configuration of BibleWorks involves the following steps:
 

 

I. Install BibleWorks on the server.


First install BibleWorks on a node or server that is accessible by all users who need access to BibleWorks. A full installation is strongly recommended. For the illustration purposes of this guide let us assume that you will be doing a full installation on a server named \\Snoopy in the directory c:\Program Files\BibleWorks 9. On the server, please follow the steps below:

  1. Install BibleWorks and any additional BibleWorks modules you have purchased.
    When running the installer, make sure you enter the activation codes both for BibleWorks 9 and for Network Installation. The BibleWorks 9 activation code is of the form “BW90-WWWW-XXXX-YYYY-ZZZZ”. The Network Installation activation code is of the form “BNET-WWWW-XXXX-YYYY-ZZZZ”.
     

  2. Run the program and activate the program and all modules.

    NOTE: You must activate the network installation activation module before adding remote users on the workstations. If you do not activate the network support activation, the necessary files will not be copied. All modules should be installed and activated on the server before adding remote users on client machines. If not, the modules will not work. If you add modules to the server at a later date, then you must manually copy the *.ACV files from the BibleWorks 9\init folder on the server to each BibleWorks 9\users\*\init folder on the server.
     

  3. Apply any available BibleWorks 9 updates from the Internet (Help | BibleWorks on the Internet | Check for updates).  
     

  4. Shut down BibleWorks 9.
     

  5. Change the folder sharing permission settings on the server. On the server, enable the sharing of the BibleWorks 9 folder on the network (Properties | Sharing), setting "Full Control" for "Everyone" and all User Groups which will use BibleWorks over the network. Also select the Properties | Security settings, and enable "Full Control" (which includes both Change and Read) for "Everyone" as well as for all users and user groups (Users, Authenticated Users) that will be accessing the server. See the pictures below.

    [The screenshots are both from Windows Server, but depending on which mode you are running Server, you will see different properties.]
     
     

  6. Configure your workstation user accounts to connect to the BibleWorks folder when the user logs in. 

II. Install the BibleWorks fonts and Adobe Flash Player on each workstation.


BibleWorks comes with a set of TrueType fonts that must be installed on each workstation in order to view Greek and Hebrew text. After the server installation, all of these fonts will be located in \\Snoopy\BibleWorks 9 (where "Snoopy" is your server name). Install all of the fonts found in this folder with the exception of Hebrew.ttf.

To view the training videos, Adobe Flash (for IE) needs to be installed on each workstation. If Flash is not installed, you can install it by running the install_flash_player_10_active_x.exe program in the server BibleWorks folder. You may need to be running from an account on the workstation with Administrative privileges to do this.
 

III. Change the Local Intranet security settings on each workstation.

 

In order to enable BibleWorks to run over the network without seeing the Open File - Security Warning window each time the program is started, the Local Intranet security settings need to be set as described below on each workstation that will connect to the server.

 

A. Set Computer Configuration settings

 

If you know how to use the Group Policy Object Editor, edit the following settings at Computer Configuration-Administrative Templates-Windows Components-Internet Explorer-Internet Control Panel-Security Page:

 

The following settings should be set here:

  1. Turn on Automatic detection of intranet - Enabled (This option may only be visible with IE7+.)

  2. Intranet Sites: Include all local (intranet) sites not listed in other zones - Enabled

  3. Intranet Sites: Include all sites that bypass the proxy server- Enabled

  4. Intranet Sites: Include all network paths (UNCs)- Enabled

  5. Site to Zone Assignment List: Add the server name to the zone (e.g. \\SNOOPY) and give it a value of 1.

 

B. Set User Configuration settings

 

In the Group Policy Object Editor, go to

User Configuration-Windows Settings-Internet Explorer Maintenance-Security:

 

 

Right-click "Security Zones and Content Ratings" and click "Properties".

 

 

Select "Import the current security zones and privacy settings". If you are prompted, click "Continue". Then click "Modify Settings".

 

 

Select "Local Intranet" and then click "Sites".

 

 

The following settings should be set:

  1. Include all local (intranet) sites not listed in other zones - Enabled

  2. Include all sites that bypass the proxy server- Enabled

  3. Include all network paths (UNCs)- Enabled

  4. Click Advanced and add the server name to the zone as a trusted site (e.g. \\SNOOPY).

C. Link the GPU that you created and run "gpupdate"

 

These changes should prevent the Open File - Security Warning window from displaying when BibleWorks is run from the client workstations.

 

 

Manual instructions: Alternately, to set the Local Intranet settings on the workstations without using Group Policies, you can do the following.

  1. On each of the workstations, login to the user accounts (the account that users will use when they are running BibleWorks).
     
  2. Open the Windows Control Panel | Internet Options | Security.
     
  3. Then, select "Local intranet".
     
  4. Click the Sites button.
     
  5. In the Local intranet window that opens, all the check boxes should be checked. You may need to temporarily uncheck "Automatically detect intranet network" in order to check all check boxes.
          
  6. Select the Advanced button.
     
  7. In the "Add this website to the zone" field, enter two backslashes followed by the name of the server. In our example, you would enter "\\Snoopy"
         
     
  8. Click the Add button.

 

IV. Create a shortcut on each workstation.


In the network installation, user-selected settings are unique for each user, regardless of workstation. The BibleWorks fonts are stored on the workstation; all other files (including most executable and initialization files) are stored on the server.

  1. Create a shortcut file pointing to the BibleWorks executable.
     

  2. Open the Properties window for the shortcut and set the "Target" field to point to the program file on the server. After the "Target" path you must also include the string

         /remoteuser="user"

    (including the quotes and preceded by a space). The string /remoteuser="user" tells BibleWorks to create files and directories on the server in such a way as to allow each user access to their own settings and files regardless of which workstation the user logs onto.

    For our example, if your server name is "Snoopy", the "Target" parameter would look like this:

         "\\Snoopy\BibleWorks 9\bw900.exe" /remoteuser="user"

    When the /remoteuser="user" setting is used, it is necessary to have already activated the network capability through activation of a network activation code. This activation code is entered above under step 1.


    NOTE: You can also install BibleWorks so that local users on one machine have their own separate folders and settings. This installation is useful if there is only a single machine in use, rather than having a separate server plus client workstation, but you want each user to have their own settings and files. For this type of installation, use the string

          /localuser="user"

    instead of

          /remoteuser="user"

    If using the /localuser="user" string in the "Target" path, no network activation is needed. The /localuser="user" setting will not work on a network installation that has a separate server and client. In that case you must use the /remoteuser="user" string, and obtain a network activation code. The /localuser="user" setting only works on the same machine where BibleWorks is installed.

    The word "user" can be any name. If you use the word "user", the operating system will look up the name of the current user and substitute the current user name for the word "user". If you use a different name in place of "user", the name used will be the name of the file where the new user's files will be located.


  3. You must also enter the full path of the BibleWorks main directory in the "Start in" field of the shortcut properties window. "Start in" would look like this for our example:


          "\\Snoopy\BibleWorks 9"

         

  4. The shortcut can now be copied to all workstations which will be accessing BibleWorks.

V. Set up the COM Server settings.


BibleWorks needs to be registered as a COM server on each of the workstations. This, among other things, allows BibleWorks to provide popup verse text inside HTML Help files. To do this automatically, on each workstation that will be using BibleWorks, the following command needs to be run using Administrator privileges:

 

      \\Snoopy\BibleWorks 9\bw900.exe /netclsetup

 

(where "Snoopy" is the server name). Under Vista, if you create a shortcut to do this, right-click the shortcut and select "Run as administrator".

 

If the "Run As" window (see below) appears, select Current User and uncheck "Protect my computer". Click OK. 

 

If for some reason this does not work, you can follow the manual instructions below.

 

Manual Instructions:

  1. Log in to the client machine with an account having Administrator privileges.

    Under Vista, right-click on the shortcut created in the previous steps, hold down the Shift key, and select "Run as Administrator". Hold down the Shift key until the Trouble-shooting Options window opens. If an "Open file-Security Warning" window opens, keep holding the Shift key and click "Run".

    Under XP, start BibleWorks on the client machine using the shortcut created in the previous steps, holding down the Shift key when you double-click on the shortcut. If an "Open file-Security Warning" window opens, keep holding the Shift key and click "Run".

     

  2. In the Trouble-shooting Options window that opens, select "Reset Automation Server", then click "Perform these actions and exit". If the "Run As" window (see below) appears, select Current User and uncheck "Protect my computer". Click OK. 

 

VI. Change the HTML Help security settings.


To set the HTML Help security settings on the workstations automatically, run the same automatic command described for automatically registering the BibleWorks COM server. If you have already done this, the step does not need to be repeated. On each workstation that will be using BibleWorks, the following command needs to be run using Administrator privileges:

 

      \\Snoopy\BibleWorks 9\bw900.exe /netclsetup

 

(where "Snoopy" is the server name). In Vista, if you create a shortcut to do this, right-click the shortcut and select "Run as administrator".

 

If the "Run As" window (see below) appears, select Current User and uncheck "Protect my computer". Click OK. 

If for some reason that does not work, you can follow the manual instructions below:
 

Manual Instructions: On each workstation, using Administrator privileges, apply the hhctrl.reg file found in the BibleWorks main folder.

To see what security issues are involved in doing this see the following Microsoft links:
     http://support.microsoft.com/?kbid=896054
     
http://support.microsoft.com/?kbid=892675


VII. Informational Note


The first time a user double clicks this shortcut to access the program, a subdirectory will be created on the server to store that user's files. The name of the directory will be derived from the user's login name on the workstation computer. For example, if a user logs in under the name "JoeCool" a folder named “\\snoopy\BibleWorks 9\users\JoeCool” will be created on the server \\snoopy to store any files that are created or modified by JoeCool.
 

VIII. Possible networking problems: 

 

BibleWorks starts from client machines but crashes on startup

Verify that BibleWorks and the BibleWorks Network Installation module are both activated on the server.
 
Verify that the client machine can read and write to the BibleWorks folder on the server (copy a test file from the client to the server folder).

Verify that the two folder settings for the BibleWorks shortcut on the client machines are correct.

Verify that all steps above are followed, particularly noting which steps need to be run as an Administrator and which steps need to be run from the user account.

Scripture Popups in Modules or Study Guide links are not working
This usually occurs when the COM server is not registered properly. See section V.

CHM file pages do not display (“Navigation to the webpage was canceled”).

This usually occurs when Internet Security settings and HTMLHelp settings are not adjusted. See sections III and VI.