From 441c8566dda5cc2b37fd92a39236dc595a547298 Mon Sep 17 00:00:00 2001
From: Clemens Neudecker <952378+cneud@users.noreply.github.com>
Date: Wed, 30 Mar 2022 17:05:04 +0200
Subject: [PATCH] additional details on OCR-D usage

---
 README.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index deedcf7..b20289d 100644
--- a/README.md
+++ b/README.md
@@ -163,9 +163,15 @@ Here are the difference in elements detected depending on the `--full-layout`/`-
 
 #### Use as OCR-D processor
 
-Eynollah ships with a CLI interface to be used as [OCR-D](https://ocr-d.de) processor. In this case, the source image file group with (preferably) RGB images should be used as input (the image provided by `@imageFilename` is passed on directly):
+Eynollah ships with a CLI interface to be used as [OCR-D](https://ocr-d.de) 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 referenced by `@imageFilename` in PAGE-XML is passed on directly to Eynollah as a processor, so that e.g. calling
+
+`ocrd-eynollah-segment -I OCR-D-IMG-BIN -O SEG-LINE -P models`
+    
+would still use the original (RGB) image despite any binarization that may have occured in previous OCR-D processing steps
 
  #### Eynollah "light"