No description
Find a file
Robert Sachunsky b41278f99b
improve description of behaviour in README
clarify:
- what levels are re-ordered (`ReadingOrder` unaffected/unrelated)
- textual consistency is only the trigger, not the driver
- coordinate-based order respects annotation
2019-11-26 12:43:52 +00:00
examples 📝 Update fix script 2019-11-25 18:06:05 +01:00
ocrd_repair_inconsistencies Report missing reading direction/textline order 2019-11-25 18:05:10 +01:00
.gitignore 🎉 Initial commit 2019-11-22 16:18:05 +01:00
README.md improve description of behaviour in README 2019-11-26 12:43:52 +00:00
requirements.txt 🎉 Initial commit 2019-11-22 16:18:05 +01:00
setup.py 🎉 Initial commit 2019-11-22 16:18:05 +01:00

ocrd_repair_inconsistencies

Automatically re-order lines, words and glyphs to become textually consistent with their parents.

PAGE-XML elements with textual annotation are re-ordered by their centroid coordinates in top-to-bottom/left-to-right fashion iff such re-ordering fixes the inconsistency between their appropriately concatenated TextEquiv texts with their parent's TextEquiv text.

This processor does not affect ReadingOrder between regions, just the order of the XML elements below the region level, and only if not contradicting the annotated textLineOrder/readingDirection.

We wrote this as a one-shot script to fix some files. Use with caution.

Example usage

For example, use this fix script:

#!/bin/bash
set -e

tmp_fg=FIXED_$RANDOM

ocrd_repair_inconsistencies -I OCR-D-GT-PAGE -O $tmp_fg

for f in "$tmp_fg"/*; do
  g="OCR-D-GT-PAGE/OCR-D-GT-PAGE_${f#${tmp_fg}/${tmp_fg}_}"
  cp "$f" "$g"
done

ocrd workspace remove-group -rf $tmp_fg
rmdir $tmp_fg