[ 
https://issues.apache.org/jira/browse/TIKA-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15536891#comment-15536891
 ] 

ASF GitHub Bot commented on TIKA-2106:
--------------------------------------

GitHub user epugh opened a pull request:

    https://github.com/apache/tika/pull/136

    TIKA-2106.  Need to lowercase the output file to match the format passed to 
tesse…

    …ract cmd line.  

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/epugh/tika master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tika/pull/136.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 #136
    
----
commit bfc7efb1004c8cbd8678408fa37ba638a58b6f42
Author: Eric Pugh <[email protected]>
Date:   2016-09-30T17:40:09Z

    need to lowercase the output file to match the format passed to tesseract 
cmd line

----


> "hocr" case on Linux fails, but works on OSX.  Related to TIKA-2093
> -------------------------------------------------------------------
>
>                 Key: TIKA-2106
>                 URL: https://issues.apache.org/jira/browse/TIKA-2106
>             Project: Tika
>          Issue Type: Bug
>          Components: ocr
>         Environment: Bug in Linux, but fine in OSX.
>            Reporter: Eric Pugh
>
> We pass a output type, either TXT or HOCR to the Tesseract command line.   
> When we call the command line we lowercase it to "txt" or "hocr".  However, 
> when we read back in the output, we don't lower case it.  on OSX the 
> constructed file path "output.HOCR" is actually found, but in Linux it 
> doesn't.  This patch lower cases the HOCR to hocr and TXT to txt in the 
> constructed file path.
> I didn't write a unit test as I don't have a good linux env to test it in, 
> but I was able to put a patched version of the Tika Parser Jar into my Docker 
> Build to test it works.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to