Robert Sachunsky

Mostly affects the User Guide, I think.

ping @lena-hinrichsen

> Also: templates for processors of various task groups (preprocessing, segmentation, recognition, postprocessing). Or at least runnable API examples. Perhaps in the form: "HowTo Wrap xyz for OCR-D"

Not quite. The original idea was to provide some middle ground between single processor description and full-blown workflows: simple reusable recipes for special tasks (e.g. how to segment handwriting, how...

The popup or help button should IMO also link to the respective tool's README, which often provides more depth/structure and background that the plaintext help strings of the processor and...

@jbarth-ubhd can we close this?

ping @lena-hinrichsen

BTW, the ALTO **download** then removes the HTML-encoded newline characters – too bad!

@sebastian-meyer notified me (via other communication) that one necessary ingredient is v4 support in the Solr indexer. So as long as this is not integrated/configured/tested, we still have to ingest...

> Also, we have to take into account the [solr_ocrhighlighting](https://dbmdz.github.io/solr-ocrhighlighting/0.8.3/) plugin we are using, because that interprets ALTO as well in order to get the word coordinates. I am not...