- `do_order_of_regions`: simplify aggregating per-box orders
for paragraphs and headings to overall order passed to
`xml_reading_order`; no need for `order_and_id_of_texts`,
no need to return `id_of_texts_tot`
- `do_order_of_regions_with_model`: no need to return `region_ids`
- writer: no need to pass `id_of_texts_tot` in `build_pagexml`
(because the latter does not preserve coordinates;
it scales, even when resizing the image;
this caused coordinate problems when matching deskewed contours)
- reduce `sigma` for smoothing of input to `find_peaks`
(so we get deeper gaps between columns)
- allow column boundaries closer to the margins
(50 instead of 100 or 200 px, 170 instead of 370 px)
- allow column boundaries closer to each other
(300 instead of 400 px)
- add a secondary `grenze` criterion for depth of gap
(relative to lowest minimum, if that is smaller than
the old criterion relative to lowest maximum)
- for calls to `find_num_col` within parts of a page,
do allow unbalanced column boundaries
- rename `return_x_start_end_mothers_childs_and_type_of_reading_order`
→ `return_multicol_separators_x_start_end`, and drop all the analysis
pertaining to mother/child relationships and full-span separators,
also drop the separator unification rules;
instead of the latter, try to combine neighbouring separators more
generally: join column spans iff there is nothing in between
(which also necessitates passing the region mask), and keep only
one of every such redundant pair;
add the top (of each page part) as full-span separator up front,
and return separators already ordered by y
- `return_boxes_of_images_by_order_of_reading_new`:
- also pass regions with separators, so they do not have to be
reconstructed from the separator coordinates, and also contain
images and other non-text region types, when trying to elongate
separators to maximize their span (without introducing overlaps)
- determine connected components of the region mask, i.e. labels
and their respective bboxes, in order to
1. gain additional multi-column separators, if possible
2. avoid cutting through regions which do cross column boundaries
later on
- whenever adding a new bbox, first look up the label map to see if
there are any multi-column regions extending to the right of the
current column; if there are, then advance not just one column
to the right, but as many as necessary to avoid cutting through
these regions
- new core algorithm: iterate separators sorted by y and then column
by column, but whenever the next separator ends in the same column
as the current one or even further left, recurse (i.e. finish that
span first before continuing with the top iteration)
- `lines` → `seps` (to distinguish from textlines)
- `text_regions_p_1_n` → `text_regions_p_d` (because all other
deskewed variables are called like this)
- `pixel` → `label`
