The conf file tells the engine where it should look for its library. These
aren't the module conf files that need documentation but the master
sword.conf file. There's only a very limited amount of data that can go
into it, but it's not at all unreasonable to have a manpage for this file.
It has no
Since the .conf files have no user configuration switches... fedora is
wrong.
Files of this type, .conf files, in unix regularly have switches. Fedora is
suggesting the Man pages describe what the end user can do by changing the
configuration files. The only thing they can do is cause the program
Fedora's automatic packaging check suggests that we ought to have a man
page for /etc/sword.conf. Knowing nothing about man pages, is there anyone
out there who feels that this is important enough to tackle?
--Greg
___
sword-devel mailing list: sword-dev
Hi John,
If you're planning to submit to crosswire for hosting, All of these
questions are handled by the module maintainer at crosswire (currently
Peter.) You don't really need to worry about them, other than to confirm
your source does compile. You need to confirm it's clean source (the OSIS,
Th
In the Wiki, on the http://wiki.crosswire.org/DevTools:Modules page it gives directions for using mod2zmod for compressing
modules.
However osis2mod.exe has command-line switches for creating compressed modules.
My question is: do these produce equivalent results? Which is preferred?
For
Greetings.
I am a little unclear about how to know when to use the 4-byte -s 4 entry option for osis2mod for commentaries and bibles. I have
some LARGE commentaries, and I don't know how I can find out if there are any entries that are over 64K. Is there a message
generated somewhere?
Or a
