osis2mod already has a flag -a that will allow content to be appended to a
module. I think if a copy of the KJV is made that the -a flag with the
Apocrypha.xml (or whatever it is called) could be added in.
> On Jan 30, 2025, at 11:16 AM, David Haslam wrote:
>
> What would it take to enable osi
Thanks DM,
Indeed it has, and I’ve used it myself to create updated test versions of the
KJVA module, by appending the DC books to a module created first from the PC
books.
However that concept is not foreseen as a potential method to be used by Dom
Corbex in his module creation script.
David
Troy,
Wonderful.
In the file’s mapping section, does “to” refer to LXXNU or to the v11n being
defined?
I suppose that osis2mod will need to be changed to accept the file, that the
conf will need to implictly or explicitly point to the file, that it’ll need to
be packaged with the module and t
On Thu, Jan 30, 2025 at 10:17 AM David Haslam wrote:
> It seems a shame if we could not take advantage of this standard feature
> of XML with the main tool we use for making Bible modules.
>
This is because, in order to keep the library small, we use no standard XML
tools. Thus, no standard XML
What would it take to enable osis2mod to process a top level OSIS file that
called subsidiary XML files using the Xinclude feature?
See https://www.w3.org/TR/xinclude/
and https://en.wikipedia.org/wiki/XInclude
Potential use:
Instead of having to script the merging of two OSIS files (e.g. for t
