For an uncompressed module there are 2 files per testament: an index file and a data file. There is one entry in the index file per verse in the versification. Each entry consists of a 4 byte offset and a 2 or 4 byte length. The -s flag indicates the byte size of the length. So using a -s4 will increase the size of the index file by 33%.
The data file is unchanged by the -s flag. The compressed module is similar but has an extra set of files to indicate the block start and block size. This file does not change based upon the -s flag. So using the -s 4 flag is not a big deal. When we build modules for the CrossWire repository we’ll use the smallest available. Every message that osis2mod creates is found in the wiki: http://wiki.crosswire.org/Osis2mod#Messages <http://wiki.crosswire.org/Osis2mod#Messages> There is no message for it. In His Service, DM Smith > On Jan 26, 2018, at 5:24 PM, John Dudeck <john.dud...@sim.org> wrote: > > 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 alternatively, is there any disadvantage to just always using the -s 4 > option? > > John Dudeck > Programmer at Editions Cle Lyon, France > john.dud...@sim.org j...@editionscle.com > -- > "No man is an island, entire of itself; every man is a piece of the continent, > a part of the main...." -- John Donne > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
