Clemens Neudecker

But note that **only** PAGE files produced by [OCR-D](https://github.com/OCR-D) include this information - I am not aware of any other tool producing PAGE output currently populating this section in this...

I may be missing sth, but those are actually all reasons for using IIIF ;) - Cropping images is done server-side via API request, you directly get the snippets returned...

> https://qurator-data.de/~mike.gerber/experiments/image-cropping-using-css/image-cropping-using-css.html Based on your example, here is how this can also be done serverside just with the pixel information you already have in the OCR and an [awesome API](https://github.com/IIIF/awesome-iiif)....

You could always minify the CSS+JS and include it inline for maximum portability.

This is all about https://github.com/qurator-spk/dinglehopper/issues/10#issuecomment-641491377

Duplicate of #11?

Basically this comes down to a number of pre-defined common use cases or scenarios, with the added possibility for users to create their own scenarios. This is also the approach...

> the belief that CERs are somehow comparable when produced by different tools I too strongly doubt they are! Looking at e.g. results and metrics from ICDAR papers, many resort...

@wrznr E.g. ``Aletheia`` (but only the ``Pro`` edition) also has functionality included with which it should be possible to fix this. Anyway I second @mikegerber that it would be really...

Just leaving this here for documentation - this is also sometimes referred to as "significant words" evaluation. > The number of occurrences of content words for which users might be...