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 2
Thanks Greg,
The issue in question is this (which lists an example with the USFM & the OSIS)
https://github.com/adyeths/u2o/issues/119
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 reasonabl
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 wrote:
> I think irrespective of the different context the error lies in the U
This is simply not the case, as you can have valid USFM files that convert OK
to OSIS using u2o.py but which osis2mod reports nesting errors.
Having a list item and the list end part way through a verse is not uncommon,
albeit less so than having poetry lines end part way through a verse.
David
I think irrespective of the different context the error lies in the USFM. Sent from my phone. Please forgive misspellings and weird “corrections”On 13 Jun 2023, at 12:26, David Haslam wrote: All very well, but my question arose from nesting errors arising in the context of the XML list element.
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
Nesting errors I have seen look like (pseudo code)
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
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
