Re: Too many milestones can cook your buffer?
David Haslam <dfhdfh-g/[email protected]> Mon, 05 May 2025 16:45:19 +0000
| Newsgroups | gmane.comp.literature.sword.devel |
|---|---|
| Message-ID | <uLNI4M3uK9XE1_UxjD4XTM2BItRmiV1x4NmJzXJ_DcqZebisYOzFGNARLScoVmEdh92LcXdFx5lqrsuu3SK4eJef6ziNkvdMwnMFuf7wXi4=@protonmail.com> |
So if an OSIS file were so unusual as to cause the module to give decompression buffer issues, as things stand at present, you would not have a route to fix things? Not even if the submitted .conf file has BlockType=CHAPTER specified as the way to prevent this issue ? David On Mon, May 5, 2025 at 17:39, domcox <[[email protected]](mailto:On Mon, May 5, 2025 at 17:39, domcox <<a href=)> wrote: > David Haslam <[email protected]> writes: > >> How does Dom’s module release script determine the right >> BlockType for a module? > > BlockType is set with only one value: BlockType=book. > > see: > https://www.crosswire.org/svn/sword-tools/trunk/modules/conf/confmaker.py > (line=431) > > -- > Dom _______________________________________________ sword-devel mailing list: [email protected] http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page