* 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.
Normally bibledit stores its data in subdirectory .bibledit of the user's home directory.
Changing that 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.
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.
Paratext remains as it is, and Bibledit accesses Paratext's data files.
Below is an example that shows how to get this working. More information is in the topic about collaboration.
- We have a Paratext project in our Windows partition. It is at /home/joe/windows/My Paratext Projects/NDB. When Windows runs, we can work on those files using Paratext. But we wish to work on the same files using Bibledit too, from Linux.
- We start Bibledit and create a new project called Ndebele.
- We import all the files at /home/joe/windows/My Paratext Projects/NDB into our project, and choose "Link to them" in the import dialog.
You can now edit some text, exit Bibledit, go to Windows, and to Paratext, and see that the changes made in Bibledit are also visible in Paratext. You can make some changes in Paratext, save them, exit Paratext and Windows and go to Bibledit, and see that the changes appear here too.
Bibledit has several areas to work in.
In Menu / GoTo there are hotkeys mentioned to move between areas.
On some distributions F5 (Text Area) and Shift+F5 (Tools Area) work fine, but Ctrl+F5 (Project Notes Area) will not work. It leaves the cursor in the area it is.
What works fine, is the
* Tab key: moves between all areas counter-clockwise,
* Shift+Tab: moves cursor between areas clockwise,
with the exception text area to references area. In this case Shift+Tab has to used twice, as using it once goes to the verse box of the toolbar.