@Izzy In case there is a programming solution rather than a software one, would there be any problem to also post this question on another site? Any recommendation (SuperUser or another one)?
– user3169Nov 19 '18 at 19:00

If by programming you mean scripting, SU might fit. Programming normaly is located on SO. If you make sure the question is focused differently (so it's indeed a different question – e.g. here asking for existing software, there asking for scripting solutions), there shouldn't be a problem.
– Izzy♦Nov 20 '18 at 0:05

I see, but how to handle the extension change? Output files needs to have the .txt extension. FILES will be a list of file names.
– user3169Nov 23 '18 at 0:31

@user3169 Tesseract adds the extension ".txt" automatically, the last time I checked. If you say tesseract img.jpg foo.txt, then you actually get foo.txt.txt. Usually it's annoying, but here it's convenient.
– KodiologistNov 23 '18 at 3:19

I tried this and it did the tesseract processing OK, but the results were still all in one text file (FILES.txt). Your example doesn't seem to change the fact that Tesseract only supports a single file output, unless I'm missing something.
– user3169Nov 23 '18 at 19:17

@user3169 I think you may have misunderstood my example. The literal characters FILES shouldn't appear in your command. What command did you use, exactly?
– KodiologistNov 23 '18 at 20:42

No, I just named my list "FILES" to follow you example. My command: for file in FILES ; do tesseract "$file" "$file" ; done. I presume "$file" is the image file name pulled from FILE, since the ocr function was performed. But then where is the individual output text file? All I got was one FILE.txt with all the results.
– user3169Nov 23 '18 at 22:50