Documentation: Should the OCR-D processor run on RGB or binarized images?

Should the OCR-D processor run on a RGB or a binarized image input group?

I think it would be best if the README listed an example, e.g.:

ocrd-eynollah-segment -I <WHICH ONE?> -O SEG-LINE -P xyz abc

[cneud]

Ok, how about this then?

Use as OCR-D processor Eynollah ships with a CLI interface to be used as OCR-D processor. In this case, the source image file group with (preferably) RGB images should be used as input like this: ocrd-eynollah-segment -I OCR-D-IMG -O SEG-LINE -P models In fact, the image provided by @imageFilename in PAGE-XML is passed on directly to Eynollah as a processor, so that e.g. ocrd-eynollah-segment -I OCR-D-IMG-BIN -O SEG-LINE -P models will still use the original (RGB) image despite any binarization that may have occured in previous OCR-D processing steps

[cneud]

OK I’ve amended this accordingly in https://github.com/qurator-spk/eynollah/commit/441c8566dda5cc2b37fd92a39236dc595a547298 and will close here once the PR for the README update has been merged.