[ https://issues.apache.org/jira/browse/TIKA-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652940#comment-14652940 ]
ASF GitHub Bot commented on TIKA-1703: -------------------------------------- GitHub user taidan19 opened a pull request: https://github.com/apache/tika/pull/56 TIKA-1703 Add ability to specify Tesseract config path. Link to Jira ticket - https://issues.apache.org/jira/browse/TIKA-1703 You can merge this pull request into a Git repository by running: $ git pull https://github.com/taidan19/tika TIKA-1703 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/tika/pull/56.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #56 ---- commit 86e8fdf187af5051812e1164c4cc3fef737a0644 Author: Christian Wolfe <taida...@gmail.com> Date: 2015-08-04T00:54:23Z TIKA-1703 Add ability to specify Tesseract config path. ---- > Can't Specify Tesseract Data Folder Distinct from Tesseract Executable Path > --------------------------------------------------------------------------- > > Key: TIKA-1703 > URL: https://issues.apache.org/jira/browse/TIKA-1703 > Project: Tika > Issue Type: Bug > Components: parser > Affects Versions: 1.9 > Reporter: Christian Wolfe > Priority: Minor > Fix For: 1.9 > > > If a user specifies the path to the Tesseract executable using > {{TesseractOCRConfig.setTesseractPath}}, then Tika will assume that the > Tesseract config folder (usually referred to as the 'tessdata' folder) is in > the same location. This is usually true in a Windows environment, where > everything is installed into a central location. > However, this is not necessarily the case in a Linux environment. If one were > to build Tesseract from source, for example, the config folder will be > installed in a different location than the Tesseract executable. > One way to fix this would be to add a way to specify the location of the > Tesseract config folder separate from the path to the executable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)