Questions and Answers


I get the message "There was a problem in FOP".
This means that there was a problem in FOP, the Formatting Objects Processor. As a result of this, FOP could not succesfully format pages during one of the printing commands in bibledit.
To solve this problem, have a look in the System log. This is accessible through the menu, Diagnostics, View system log.
If the first error is a java.lang.OutOfMemoryError, look in one of the following questions for the solution.
If there is another error, ask for more help on the discussion list.


FOP gives a java.lang.OutOfMemoryError
This means that the Java interpreter did not have enough memory to complete the formatting process.
The solution will be to increase the amount of memory available to Java.
The default amount of memory assigned to Java is 64 Mbyte, but for printing a whole project, it needs 256 Mbyte of memory.
To increase the amount of memory assigned to Jave, carry out the following steps.
1. Look in bibledit, the menu, Preferences, FOP, and find the directory where FOP was installed.
2. In that directory, open the file called fop.sh in a text editor.
3. The last line of that file looks something like:
$JAVACMD -classpath "$LOCALCLASSPATH" $FOP_OPTS org.apache.fop.apps.Fop "$@"
4. Change that line to look like this:
$JAVACMD -Xmx256M -classpath "$LOCALCLASSPATH" $FOP_OPTS org.apache.fop.apps.Fop "$@"
(You will note the -Xmx256M. This assigns a maximum of 256 Mbyte of memory to Java.)
5. Save the file.