Sandro Mani

Discussions in the other issues at times diverged from the original title, this is just to summarize the open issues at a glance, without having to re-read all the issues...

@zohozer The idea is to have an extra area below the canvas where the current line, the one before and the one after are displayed, you can edit lines word-wise...

For the first iteration, I'll keep the workflow word-wise, following the hOCR document structure. Having it character-wise would mean automatically adjusting word boxes or creating/dropping word items depending on mutations...

I've landed a new widget for convenient proof reading (currently Qt interface only), just click on a line or a word in the output tree to activate it. 

@zohozer > 1. An ability to continuously move the cursor between different fields using only the Left/Right cursor keys instead of using the TAB key to move between fields. [...]...

It's because the font size detection logic fails miserably with the `I`, which is not terribly surprising... I'll need to improve that.

@raindropsfromsky https://github.com/manisandro/gImageReader/commit/dce0871d0de6202246e323b6e95199c27db7849e should address this

> If the **comparacope** feature is implemented, all this hard work is not necessary, as the superimposed text can be directly compared with the original. Much faster and more accurate!...

> BTW there is the problem I described [here](https://github.com/manisandro/gImageReader/issues/438#issuecomment-612840417) also... See above: > What does the hOCR tree structure show? In case, here also please share image + hOCR file.

@raindropsfromsky Those are automated builds, not stable releases. You should pick most of the news by looking at the git commit log, usually the messages should be indicative enough.