| It is the placing of the endID here inside the list item which is the concern.
Usfm2osis.pl of old solved that, if I remember correctly, by doing some elaborate switching of tags towards the end of the process.
Peter Sent from my phone. Please forgive misspellings and weird “corrections” On 13 Jun 2023, at 18:11, David Haslam <dfh...@protonmail.com> wrote:
Thanks Greg,
The issue in question is this (which lists an example with the USFM & the OSIS)
Adyeths gave up trying to make u2o.py provide a consistent solution.
He wrote, "I'm also open to the resolution that u2o is already producing the most reasonable OSIS representation of the USFM sources, and it's osis2mod that's being picky. It's not clear to me how serious these warnings are."
And then, "It's unlikely that I will ever be able to produce output that completely eliminates nesting warnings reported by the osis2mod tool. I will reexamine the code, but I'm not confident that I will be able to fix this particular issue."
------- Original Message -------
On Tuesday, June 13th, 2023 at 5:52 PM, Greg Hellings <greg.helli...@gmail.com> wrote:
It might help to see the bit of OSIS it is referencing, rather than poking in the dark at possible answers to the implied question of what is wrong with the OSIS file.
On Tue, Jun 13, 2023 at 11:13 AM Peter von Kaehne < ref...@gmx.net> wrote: I think irrespective of the different context the error lies in the USFM. Sent from my phone. Please forgive misspellings and weird “corrections” All very well, but my question arose from nesting errors arising in the context of the XML list element.
It wasn’t a case like Peter just described, that touches on the underlying chapter and verse structure.
David
Sent from Proton Mail for iOS
On Tue, Jun 13, 2023 at 12:06, Peter von Kaehne < ref...@gmx.net> wrote: Nesting errors I have seen look like (pseudo code)
<chapter startID/>
<verse endID/>
Where the endID of the last verse of last chapter comes after the start is of the new chapter. It is a USFM error. It is too long that I did this but fixing the USFM makes this go away. I am not sure that u2o should fix it though recognising it would be nice of course.
Peter
Sent from my phone. Please forgive misspellings and weird “corrections”
> On 11 Jun 2023, at 07:07, David Haslam <dfh...@protonmail.com> wrote:
>
>
> If osis2mod produces modules in which chapter and verse elements use the milestone forms, how is it possible that it can report NESTING errors when (eg) a verse eID milestone and the next verse sID milestone are generated somewhere within an XML list element?
>
> How can a milestone even do such a thing?
>
> Question prompted by recent issues in the GitHub repo for Adyeths script u2o.py that converts USFM to OSIS.
> cf. It’s not something that he can comprehensively fix.
>
> Best regards,
>
> David
>
> Sent from Proton Mail for iOS
> _______________________________________________
> 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
_______________________________________________sword-devel mailing list: sword-devel@crosswire.orghttp://crosswire.org/mailman/listinfo/sword-develInstructions 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
|
