<div dir="ltr"><div class="gmail_extra">Thank you Simon, the --batch-script feature looks very flexible. </div><div class="gmail_extra">It almost does the trick:</div><div class="gmail_extra"><br></div><div class="gmail_extra">
   scanimage --batch --batch-script <(echo) | tesseract - -</div><div class="gmail_extra"><br></div><div class="gmail_extra">Unfortunately, it runs just a little too early. The script executes</div><div class="gmail_extra">
just before the temporary image file is renamed. Tesseract </div><div class="gmail_extra">wants to know about the final filename after it exists.</div><div class="gmail_extra"><br></div><div class="gmail_extra">My very first implementation attempt didn't work; the emitted </div>
<div class="gmail_extra">filename somehow ended up in the image data. Is there a problem</div><div class="gmail_extra">with scanimage writing to standard output?</div><div class="gmail_extra"><br></div><div class="gmail_extra">
  if (new_interoperability_feature) fprintf(stdout, "%s\n", path);</div><div class="gmail_extra"><br></div><div class="gmail_extra">I ultimately hope to make scanimage and tesseract work </div><div class="gmail_extra">
together nicely for everyone. So any suggestions or advice</div><div class="gmail_extra">are appreciated.    </div><div class="gmail_extra"><br></div><div class="gmail_extra">Cheers,</div><div class="gmail_extra">Jeff</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div>