Hey team
I'm wondering what was the reasoning behind the move of setTesseractPath(String) method from TesseractOCRConfig to TesseractOCRParser. Why setting the Tesseract binary path is not considered as a configuration anymore? Sorry if this has been discussed previously. FWIW, the javadoc of TesseractOCRParser class [1] is not relevant anymore: TesseractOCRConfig config = new TesseractOCRConfig(); //Needed if tesseract is not on system path config.setTesseractPath(tesseractFolder); parseContext.set(TesseractOCRConfig.class, config); What's the process to modify the javadoc? Does it have to go through a bug report first? Or can I send a PR directly for this? [1] https://github.com/apache/tika/blob/5e2a3c081b3867086e417cb5cb032cb12be3c19d/tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-ocr-module/src/main/java/org/apache/tika/parser/ocr/TesseractOCRParser.java#L76-L87 David -- David Pilato, elastic.co Developer | Evangelist,
