Robert Knight

https://github.com/robertknight/tesseract-wasm/pull/34 can help by providing a way to detect non-portrait orientation and then providing the user with a way to correct it.

Update: This only happens in Safari, so I think it is just another case of the issue where Safari does not respect EXIF orientation information when loading images via `createImageBitmap`...

Possibly related WebKit issues: https://bugs.webkit.org/show_bug.cgi?id=203482 (Orientation not preserved after image resizing) https://bugs.webkit.org/show_bug.cgi?id=207088 (EXIF metadata lost when using file upload) I should note that I have the "High efficiency" (HEIF/HEVC) option...

An option for Safari might be to handle reading and applying the EXIF orientation data from the file ourselves, eg. using https://github.com/exif-js/exif-js, this is assuming that the relevant EXIF data...

> Images taken on my iPhone X+ are 3024x4032 at their native resolution. With the current 128MB memory cap they will load into the WebAssembly memory when first dropped into...

> Convert the image to 8-bit greyscale before loading into Tesseract I tried this. For a 3024x4032 image (default from a current iPhone), allocating an 8-bit greyscale image with Leptonica...

> Since text recognition is the expensive step, a middle ground would be to do detection in one thread, then use multiple threads to perform recognition of different text lines...

Hmm ... I wonder whether it would make sense to just expose an API for receiving logging output specifically. Compared to Tesseract options, there may be more risk that custom...

Hello - There isn't currently an option to configure the page segmentation mode (psm). It would make sense to expose this configuration though. The API could look something like: ```js...

Another option that occurs to me is to use `-DCMAKE_BUILD_TYPE=MinSizeRel` but use different flags for small number of source files that are performance critical.