I ran the command line instructions, but got errors - can you help me understand what I did wrong?
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\User> cd "C:\Documents and Settings\User\My Documents\My Downloads\scricheck-0.2.9" C:\Documents and Settings\User\My Documents\My Downloads\bibledit-1.6> ./configure '.' is not recognized as an internal or external command, operable program or batch file.
Reply: When installing it on Windows, install Cygwin first. See Bibledit's Windows installation instructions. Then execute all commands from within the Cygwin terminal.
This happens when you did not install a C compiler.Installing Bibledit from source requires a C compiler. This compiler is part of development tools. The installation instructions for Linux, or for Macintosh, or Windows, give instructions on how to install such development tools. If you follow these instructions, the problem will be gone. For example, on Windows, you need to install package "gcc" in Cygwin.
Yes, it does.
Let's say to run the Outpost, normally you would type
wine "c:\Program Files\Bibledit Windows Outpost\bwoutpost.exe"
If the Outpost is already installed on your Windows partition in a dual-boot system, you could type, for example
wine "/windows/c/Program Files/Bibledit Windows Outpost/bwoutpost.exe"
The "windows/c" part depends on your configuration.
Q. When setting up the Outpost to run on another host, in the settings dialog, when I type in the name of the host, I get this error message: Host <name> cannot be contacted through the network.
A. Points to check:
1. Is the hostname you are entering the one set in Windows on the other host?
2. Try finding out Windows' IP address, and then pinging it from Linux. If that works, enter that IP number in the Outpost Setup dialog.
3. If the IP number changes continually, enter a static IP number in Windows.
4. Is the Outpost installed and running in Windows? It has to be started manually, because Bibledit can't start it over the network.
5. Be sure that the Windows firewall does not block port 51515 for incoming connections.
6. Be sure that you have typed the right IP number. It can be checked by opening a Command Prompt in Windows, and typing "ipconfig". The IP number assigned to the network should correspond with the one you entered.
This message can be either from the text or the notes database. It has been seen in cases of malfunctioning hardware, such as unreliable memory. The solution is to solve the hardware problem first, and restore the text or the notes from a backup.
This is caused by downgrading from a newer version of sqlite3 to an older version. This may occur when the data is moved from a newer version of Linux to an older version. A possible solution is to install the newest version of sqlite3 in your current system. It will then be able to read your data again.
Try starting it from a terminal, and see what happens. In the terminal type:
bibledit
If it gives a segmentation fault, then there is a problem in your configuration. A simple way to get Bibledit running again is to delete the file ./bibledit/settings and ./bibledit/configuration/configuration.xml. You will loose all your settings, but not your data, and Bibledit should start again after that.
If you wish to have this problem solved, before deleting your configuration files, make a bug report, pack all your data in a gzipped tarball, and attach this file to the bug report.
To go to the home directory, type
cd
To pack everything in a tarball, type
tar -cvf bibledit.tar .bibledit
Then compress the tarball:
gzip bibledit.tar
The resulting file is named bibledit.tar.gz and can be attached to the bug report.
If the problem is not a segmentation fault, but it shows nothing at all, then the bibledit.log file might give a clue. It is in the temporary directory. View the logfile to see what went wrong.
If you try to start bibledit, and a warning comes up that says that Bibledit is already running, then it means that Bibledit already runs somehow. Try switching to that instance of Bibledit that already runs. Or reboot. Or else open a terminal and type "killalll bibledit-bin".
Question: I am completely stopped in my work. I opened a project, but the book of Philemon freezes Bibledit completely. When restarting it, the screen comes up, but none of the menus or buttons work. I cannot scroll. The only button that works is the one to exit the program (which brings up a box giving me the option to force-quit).
Answer: You can change the project from the commandline. In a terminal, type this:
bibledit --general-configuration --write --key project --value testproject
Next time you start Bibledit, it will open project "testproject" - any name will do here.
To change the whole configuration to default values type:
bibledit --general-configuration --reset
Bibledit's online help depends on Bibledit's internal webserver. The helpfiles only work while Bibledit is running. If you quit Bibledit, online help is not available.
When Bibledit is running on Windows, FLEx won't start. While FLEx runs, Bibledit will only start after a long delay due to a timeout. It won't have clipboard functionality. The problem is being looked into. The current workaround is to start FLEx first, and after that Bibledit. Alternatively you can start Cygwin's terminal through the Cygwin icon in the Bibledit menu, and in that terminal type "startx", and then "bibledit".
Bibledit uses iconv, the standard utility on Linux to convert between various encodings.
Iconv supports a huge amount of standard encodings. Iconv does the same functions as TECkit does.
Bibledit does not at present support a TECkit map, but that is going to change in the future.
At conversion time the user sees how the text is going to look, and can change encodings until the result looks right. If there are a couple of characters not right, the search/replace functionality quickly fixes that.
There are a couple of converters on the market, that convert .pdf files to .html. Use a search engine and look for "PDF to HTML", including the quotation marks. This will give you a number of programs to try out.
Question
Printing a Bibledit project to pdf format, using ArialUnicode and SIL Doulos for it, I had the following problem:
* Feature Bold does not show up,
* Feature Italics shows up.
Trying the same with Open Office Writer and those two fonts, I found out, that both do not show up neither in bold nor in italics.
Answer
SIL Doulos does not have bold.
Try Charis SIL, that does have bold, and works fine with me.
If the USFM code is properly written, the footnote or crossreference caller is always connected to the word it belongs to.
This is an example of proper code:
Joseph was a good man\f + \ft Or “kind man”.\f*
The following two examples of code will cause the footnote caller to detach from the word it belongs to:
Example one:
Joseph was a good man \f + \ft Or “kind man”.\f*
Note the space between "man" and the "\f".
Example two:
Joseph was a good man \f + \ft Or “kind man”.\f*
In USFM a new line is equal to a space, hence there is a space between "man" and the "\f" here also.
Many older projects started a new line for each marker, also for the footnotes. This needs correction in the current system. All note markers (footnotes and cross-references) should not start on a new line, but follow immediately the word it belongs to (without even a space).
Note that in newer versions of Bibledit the \f ... code for footnotes is no longer visible - only the note itself is visible.
If the caller at the bottom of the page touches the footnote text, then you can increase the left margin of the footnote text. In the stylesheet editor, edit the left margin of the Text, marker \ft, and if necessary also for the Paragraph Mark, marker \fp.
Same applies to the Crossreferences. Make the setting under marker \xt.
This may occur in case Adobe Reader has a document loaded already. A subsequent document, printed by Bibledit, may not load in the Reader. Newer versions of the Reader do not have this problem.
There can be various causes for this.
Cause 1. Has Bibledit Windows Outpost been installed?
Cause 2: Does it say "Windows Outpost: Connected" in the logfile?
Cause 3. When BART runs under Wine, did you install Bibledit Windows Outpost in Wine too? Or when you installed BART in CrossOver Office, e.g. bottle "win98", did you install the Outpost in the same bottle too? The wine installation constitutes a separate Windows machine, and each bottle in CrossOver Office also constitute each their own Windows machines. The system BART uses for scrolling requires that it be accessed from the same Windows machine. This means that if you installed BART in a certain bottle in CrossOver Office, e.g. bottle "win98", then for scrolling to work, the Outpost needs to be installed in that same bottle too.
Cause 4: Did you set BART to receive references?
Cause 5: If you used CrossOver Office instead of Wine, then you need to start the Outpost manually through the CrossOver menu. It needs to be started each time before you start Bibledit.
Read some more info on BibleTime.
View the Logfile in the Help menu to ensure that there is a line that says "BibleTime: Connected", and that there are no "BibleTime: " lines saying anything wrong. If everything is right, then scrolling should occur.
Bibledit uses "dcop" to send scrolling commands to BibleTime. This can be seen working by ticking menu Preferences / Debug. Then go to another verse, view the logfile, and see a "BibleTime: dcop ..." command there. If this command is there, then Bibledit's job has been done, and if there is still no scrolling, the problem lies with either dcop or BibleTime. You can verify this by executing the dcop command from a terminal and see whether BibleTime scrolls, e.g. by typing
dcop bibletime BibleTimeInterface syncAllVerseBasedModules 3John.1.8
Some points to check:
1. Ensure in the Windows Outpost preferences that Bibledit can contact the other host.
2. Did you start the Outpost manually on the other host? Bibledit won't be able to start it over the network, hence Outpost needs to be started manually.
3. Bibledit uses port 51515 to contact the Outpost. Ensure that this port is opened in your firewall on Windows. If this port is closed, Bibledit can't communicate with the Outpost.
The SWORD compiler is part of the SWORD API. Bibledit uses this compiler to export a project to SWORD format.
The most likely problem is that you did not install SWORD from source, but from a binary package. Binary packages do not always install the compiler. If you install SWORD from source, the compiler will be installed too.
The compiler used is a program called osis2mod. If the compiler has been installed, but Bibledit still cannot find it, the problem might be that the compiler has not been installed in the program search path. Type
echo $PATH
in a terminal to see the program search path.
All text between the speech markers disappears when exporting to SWORD. E.g.
And Jesus said: <<I am he>>.
Everything between << and >> disappears.
This is a bug in the current SWORD compiler. The bug has been reported.
A workaround is to use the Unicode speech markers, e.g.
And Jesus said: «I am he».
SWORD currently does not support segmented verses, like verse 1a. To prevent problems Bibledit just takes any "a" or "b" out from the verse. SWORD needs to be updated to support this.
Question: I have used the \mi formatting in the list of names in Acts 13:1. The output to BibleTime lists the \mi paragraphs on separate lines, but the font is changed from my default font for that language, and there is no indenting. Under the form for editing the style for \mi, I don't see a place to select the font. And the default indenting of each line at 6 mm from the left seems right. So is this a problem of what Bibletime can display? (That might explain the lack of indenting, but it seems that the font should not change.)
Answer: For any marker, not only the \mi one, the output Bibledit generates for the Sword compiler can be seen in the temporary directory/sword_osis_input.txt. In this case, that of the \mi marker, it can be seen that no indenting information is passed to BibleTime, nor any font information.
This implies that the font problem is a problem of BibleTime, and that the indenting is not done because it does not get the information needed. If somebody knows how to pass indenting information to BibleTime, pls. let the programmer of Bibledit know and he can put that information in.
Question: When opening Bibledit and project NIV, the logfile says "(bibledit:7567): Pango-WARNING **: Error loading GSUB table 4097". I'm not sure what the warning means. The project goes ahead and opens.
Reply: This is not an issue with Bibledit, but with the Pango library Bibledit is using. Most likely you are using a font that Pango has a problem with. Problems with Pango can be reported at www.pango.org.
Remark: On starting Bibledit sometimes the logfile says "Webserver: Address already in use".
Reply: This happens after Bibledit crashed and is restarted after that. The internal webserver cannot function properly because the previous one is still running. To solve the problem, quit and start Bibledit once more.