Robert Sachunsky

The only workaround ATM is to process smaller page ranges. But unless you use numerical page IDs, this will be quite difficult with the OCRD CLI. (The problem being `find_files...

> (The problem being `find_files does not support regex search for pageId` …) see https://github.com/OCR-D/core/issues/855

> Also, now there's a broken link in the setup guide: https://ocr-d.de/en/setup#translating-native-commands-to-docker-calls Still true today BTW. > This issue was lost when migrating from `docs` here: > > https://github.com/OCR-D/docs/issues/11#issue-548017304 >...

Already true for the setup guide, but not the user guide. (I wonder if this is necessary though: one can always invoke `docker run --help` or `man docker-run` if unsure.)

> * opening up the repository for comments and ammendments by users/practitioners (perhaps in the same way that the workflow guide was mirrored to the wiki and gets synchronized back...

You are right, this should work as you expect. (At least as long as we keep describing it as _default wiring_.) But this has not been implemented yet in `ocrd`...

> are there any use cases for `pc-segmentation` ? As far as I remember this was the worst of all options a year ago during my tests. Yes, and the...

Is this really a documentation issue? IIRC exporting that variable to the shell is helpful to make the Tesseract standalone CLI use the OCR-D data directories. IINM this could simply...

Looks good, except for steps 9 and 10, which should be exchanged (clipping before deskewing).

@stefanCCS that ftp server seems to be down. And it would be way easier if you just pasted the images here. Github then takes care of hosting them and you...