Stefan Weil

> Why should I touch not installed file/dir? There are two different issues with similar results: 1. There is an exception if there is neither a directory nor a file...

Current results on macOS: ``` % touch /tmp/file % tesseract --tessdata-dir /tmp/file --list-langs exception: filesystem error: in recursive_directory_iterator: Not a directory ["/tmp/file/"] % ~/src/github/tesseract-ocr/tesseract/bin/debug/clang,sanitize/tesseract --tessdata-dir /tmp/missed --list-langs exception: filesystem error:...

> Old tprintfs should be removed slowly in favor of std::format. Isn't the tesserr stream even better?

> I've slightly updated `tprintf()` to C++ style. Now I get numerous compiler warnings: ``` ../../../src/ccutil/tprintf.h:37:33: warning: format string is not a string literal (potentially insecure) [-Wformat-security] ``` And the...

> Can you try changing it to [...] The suggested change still produces the compiler warnings, but I think it improves the code because like that calling `tprintf()` without any...

At least for the installation I had no problem with coremltools 8.3.0: ``` aiohappyeyeballs==2.6.1 aiohttp==3.12.15 aiosignal==1.4.0 atpublic==6.0.1 attrs==25.3.0 cattrs==25.1.1 certifi==2025.8.3 charset-normalizer==3.4.3 click==8.2.1 coremltools==8.3.0 filelock==3.18.0 flufl.lock==8.2.0 frozenlist==1.7.0 fsspec==2025.7.0 future==1.0.0 hocr-spec==0.2.0 htrmopo==0.3.0...

A full protocol with Python 3.13 is now created in my GitHub action here: ~https://github.com/stweil/kraken/actions/runs/16884630003/job/47829030222~ ~https://github.com/stweil/kraken/actions/runs/16884835512/job/47829759508~ https://github.com/mittagessen/kraken/actions/runs/16390476086/job/46315774399. It looks like the CI tests also fail with older Python releases, maybe...

Meanwhile there is a coremltools-9.0b1 which looks promissing. `pytest -k 'not test_train'` passes on my MacBook with Python 3.12: ``` 204 passed, 1 skipped, 14 deselected, 2 xfailed, 1275919 warnings...

Is this an issue? There is also no eng.xheights ~and eng.unicharset~ in the repository, and the same is true for all other languages, too. @AinazRafiei, why do you think that...

Ah, yes, sorry. So what remains to be fixed? Or can this issue be closed?