* Read the questions and answers.
* Search the mailing list archives to see if your problem has been discussed before.
* Subscribe to the bibledit-general mailing list, and ask the question there.
As there are some drastic changes between versions, it would be helpful to have two different versions running of Bibledit.
This is possible, but not recommended for production work, as they will be overwriting each other's configuration.
Do it this way.
Install the newer version according to the instructions.
When installing the older version, do this:
./configure --prefix=/home/joe/older make sudo make install
Then to run the older version, type this:
/home/joe/older/bin/bibledit
Joe stands for the user's name.
You can fully configure in which order Bibledit displays and prints the books. This can be done in menu, Preferences, Books. Drag the books in the order you desire, and then click OK to save the settings.
Normally Bibledit stores its data in subdirectory ".bibledit" of the user's home directory, e.g. in
/home/joe/.bibledit
If it is desirable to have Bibledit store its data elsewhere, the solution is simple:
1. Move the current .bibledit directory to the new directory.
2. Create a symbolic link from .bibledit to that new directory.
There is a different way of pointing Bibledit to another data directory.
Changing is not done from within bibledit, but involves some manual work. This is done for the protection of your valuable data. To change the data directory to a new location, do the following:
Quit bibledit.
Open a terminal.
Type command
cd
to go to your home directory. Let's say you prefer to store the data on /mnt/server/.bibledit
Type command
mv .bibledit /mnt/server/.bibledit
to preserve and move existing data. (When there is no existing data, this step is not needed.)
Type command
touch .bibledit-datafolder-pointer
to make a new file in the home directory, that will point to the new data directory.
Open this hidden file in a text editor and put only this one line in it:
/mnt/server/.bibledit
That's it.
Removing file .bibledit-datafolder-pointer will cause bibledit to use the standard datafolder again.
See also backup.
Note: It is not recommended to store the data on a Windows partition. In such cases problems have been observed when special characters are used in the project name.
You can fully configure in which order Bibledit displays and prints the books. This can be done in menu, Preferences, Books. Drag the books in the order you desire, and then click OK to save the settings.
Bibledit has several windows to work in.
There are keyboard accelerators for moving between the windows.
What works fine, is the
* Tab key: moves between all windows counter-clockwise.
* Shift+Tab: moves cursor between windows clockwise.
In the example below we're going to learn how to write a table of contents for a project consisting of several books.
The table of contents comes in the book called Front Matter. Therefore, add this book to the project.
Each book that should go into the table of contents should have a USFM indicating this. Therefore, go to chapter 0 of each book and add the \toc2 marker to it. For example, in the book of Genesis, chapter 0 might look like
\id GEN \h Genesis \toc2 Genesis
Do this for all the books.
Then print the project, and be sure to include all the books, including Front Matter. The table of contents will be there.
If the versification system or language you need does not come with Bibledit, then you can create your own language or versification system and add it to Bibledit yourself. To do that, take an existing versification textfile or language textfile from /usr/share/bibledit, edit it, and save it in the data directory, subdirectory templates.
Notes.
The versification files start with versification_, the mapping files with mapping_, and the language files with language_. It is important to keep that first bit, else Bibledit won't recognize the files.
If the name of a template you added is the same as the name one of the templates that come with Bibledit, your template will be taken.
It would be greatly appreciated if you were willing to share the files you have created with others. In that way others will benefit from the work that you have already done. A good way of sharing it with the community is to submit it for inclusion into Bibledit. That way it becomes available to others in the next release.
This can be done through menu Tools, then Bible notes mass update. Tick "Crossreferences", and leave the action to take as "Make no changes but give statistics only". After clicking OK it will give the number of crossreferences in the project.