You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Richard Jones (JIRA)" <ji...@apache.org> on 2017/11/27 15:42:00 UTC

[jira] [Created] (TIKA-2509) TesseractOCRParser ignores configured ImageMagickPath in processImage method

Richard Jones created TIKA-2509:
-----------------------------------

             Summary: TesseractOCRParser ignores configured ImageMagickPath in processImage method
                 Key: TIKA-2509
                 URL: https://issues.apache.org/jira/browse/TIKA-2509
             Project: Tika
          Issue Type: Bug
          Components: ocr
    Affects Versions: 1.16
            Reporter: Richard Jones


The TesseractOCRParser class uses the configured ImageMagickPath in method hasImageMagick to determine whether ImageMagick is present.  Ref:
String ImageMagick = config.getImageMagickPath() + getImageMagickProg();

BUT then completely ignores the configured path in the processImage method meaning ImageMagick has to be present on system path (so what's the point of the ImageMagickPath config setting).

The doOCR method on the other hand DOES use the configured tesseractPath.

Incidentally I notice there is no equivalent PythonPath config setting even though Python is attempted to be found/used.

Some consistency would be appreciated so that ImageMagick and Python don't have to be present on the system path.  i.e. follow the model already in place for finding/using Tesseract.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)