Hi Pierre,
This is a very good idea but it would require considerable effort to
incorporate into the release process script by the modules team.
First though, can osis2mod handle a file that uses this method? If not, what
would it take to implement it in the ModTools & SWORD ?
Discuss details.
Aside: I’ve seen at least one example of an XML file set that uses this method.
Une version TEI XML de la traduction française de la Vulgate (Bible latine) par
l'Abbé Glaire (†1879)
https://github.com/MarjorieBurghart/VulgateGlaire
I once converted her TEI files to a single OSIS file and built a module. Never
got round to a formal submission to CrossWire.
Best regards
David
Sent from ProtonMail Mobile
On Sun, Jan 17, 2021 at 10:14, pierre amadio <amadio.pie...@gmail.com> wrote:
> Hi there !
>
> I am having a look at the Osis format and find it inconvenient to deal
> with the whole scripture in a single large xml document.
>
> I would like to be able to have all books in a separate xml file and a
> single container xml file referring to each book to be included in the
> final bible.
>
> I am not sure what is the best way to do that so that it is easy to
> deal with osis2mod: XML entities, XInclude, something else ?
>
> Any tips or suggestions welcome.
> _______________________________________________
> sword-devel mailing list: sword-devel@crosswire.org
> http://crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
