As the name already implies, the Outpost allows Bibledit to interact with Windows.
All the Windows programs need this Outpost to allow Bibledit to interact with them.
The Outpost does not have any functionality of its own, but it aids Bibledit on the Windows platform.
Be aware that, for communication to take place, Windows Outpost needs to use the same emulator as the other Windows programs you use on Linux. This means that if you install BibleWorks using Wine, then Windows Outpost must also be installed on Wine. And if you use CrossOver Office, then you need to use CrossOver Office for both, and both need to be installed in the same bottle.
Bibledit connects to the interface on the Outpost, and communicates through that channel. This TCP/IP interface listens on port 51515.
For diagnostics or control you can connect to it. In a terminal type
telnet localhost 51515
The following commands are recognized.
BibleWorksConnect. This connects Outpost to BibleWorks. BibleWorksReferenceGet. This returns the reference that BibleWorks now displays. BibleWorksReferenceSet Mat 1:1. This causes BibleWorks to scroll to Matthew 1:1. BibleWorksDisconnect. This disconnects Outpost from BibleWorks. SantaFeFocusReferenceGet. This returns the reference that is displayed by programs that work with the SantaFeFocus system, such as Paratext. SantaFeFocusReferenceSet MAT 1:1. This lets programs, that work with the SantaFeFocus system, display Matthew 1:1. SantaFeFocusWordSet Saviour. This lets programs like Toolbox, that work with the SantaFeFocus system, jump to the word "Saviour". Version. This gives the version number. Hide. This hides Bibledit Windows Outpost. Show. This shows Bibledit Windows Outpost. Quit. This disconnects from Bibledit Windows Outpost. Exit. This exist Bibledit Windows Outpost. Open http://bibledit.sourceforge.net. This opens a html or pdf file. Works on Windows only.
But all this information is not really needed in normal cases, because Bibledit takes care of all that.