diff options
| author | Luke Granger-Brown <git@lukegb.com> | 2021-04-23 15:02:36 +0000 |
|---|---|---|
| committer | Luke Granger-Brown <git@lukegb.com> | 2021-04-23 18:42:35 +0000 |
| commit | 4de343cccfd6591ab798e03600d8b3626db8efbd (patch) | |
| tree | e50e66fdbac073c8a0953fe2270498b4b9456e74 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 3ac9de55b08fa8b20f8e56dfe0016d51834eb079 (diff) | |
nixos/test-driver: use a variety of different Tesseract settings for OCR
When performing OCR, some of the Tesseract settings perform better than
others on a variety of different workloads, but they mostly take
~negligible incremental time to run compared to the overhead of running
the ImageMagick filters.
After this commit, we try using all three of the current Tesseract
models (classic, LSTM, and classic+LSTM) to generate output text. This
fixes chromium-90's tests at release-20.09, and should make cases where
you're looking for *specific* text better, with the tradeoff of running
Tesseract multiple times.
To make it sensible to cherrypick this into release-20.09, this doesn't
change the existing API surface for the test driver. In particular,
get_screen_text continues to have the existing behaviour.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions