content of PageXML overwritten

I have a problem that has repeatedly led to considerable data loss (and I have the impression that I have seen some Issue/discussion on that, so I apologize in advance):

In a set of legacy PageXMLs some run through smoothly in v.0.6, other however get overwritten. Here is a diff of the first 7 resp. 8 lines. The file on the left is processed without problem, the file on the left is overwritten as soon as saved.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>	      |	<?xml version="1.0"?>
<PcGts xmlns="http://schema.primaresearch.org/PAGE/gts/pageco	<PcGts xmlns="http://schema.primaresearch.org/PAGE/gts/pageco
  <Metadata>							  <Metadata>
    <Creator/>						      |	    <Creator>User123</Creator>
    <Created>2022-01-19T20:02:07</Created>		      |	    <Created>2021-06-16T20:13:22</Created>
    <LastChange>1970-01-01T00:00:00</LastChange>	      |	    <LastChange>2021-06-16T20:13:22</LastChange>
    <Comments/>						      <
  </Metadata>							  </Metadata>

Here is a file that gets overwritten when saved with the current OCR4all docker version: https://cloud.uni-halle.de/s/cgzRExPB0xPRP3I

After saving the right file is reduced to the following:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

Do you happen to know how to avoid this behaviour?

[alexander-winkler]

Fantastic help, thank you very much!

Just for the record (and an aide-memoire for myself), I followed @bertsky 's advice:

wget "https://www.primaresearch.org/schema/PAGE/gts/pagecontent/2019-07-15/pagecontent.xsd"
xmllint --schema pagecontent.xsd --noout BOOK/processing/*.xml

Only pages with negative coordinates didn’t validate.

Then I used the xslt mentioned above to transform my pagexmls.

wget "https://raw.githubusercontent.com/bertsky/workflow-configuration/master/page-fix-coords.xsl"
mkdir tmp_output
for i in BOOK/processing/*.xml; do xsltproc -o tmp_output/$(basename $i) page-fix-coords.xsl $i; done

The PageXMLs in tmp_output work perfectly fine.

Many thanks to both of you!

[maxnth]

Is it just the negative coordinates that cause the problem?

At least for the file provided in #301 the negative coordinates are indeed the only thing which make the PAGE XML invalid. I just set all negative coordinate points to 0 and it loaded just fine afterwards.