-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Display whitespace characters" view mode in output pane #11
Comments
I agree this would be useful, but I'll need to see what is the best way to implement this. For the Gtk interface, GtkSourceView provides the functionality (which is what gedit uses), however, I'd need to get GtkSpell working with GtkSourceView first. For Qt, a quick internet search did not reveal much... |
This is implemented in gimagereader-3.1, thanks for the suggestion! |
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The output pane's intelligent newline removal and whitespace cleanup functions are incredibly handy for reflowing paragraphs of text from the OCR'd document. However, especially since the output pane comes up rather narrow by default (so that nearly all recognized text is displayed wrapped, in the pane), it can sometimes be difficult to determine the line length of the text or where the existing hard newlines are.
I wonder if it wouldn't be helpful to have a display mode (either optional, or just the standard view) which displays "hidden" whitespace characters — something similar to GEdit's "Draw Spaces" plugin, perhaps.
I have my GEdit configured so that:
If the output pane had a display mode similar to the GEdit screenshot below (I'm not sure that line numbers are necessary), it would make it much easier to locate areas in the text where there are hard line breaks and other whitespace issues present that need to be cleaned up with the "Strip line breaks..." tool, as well as visibly see the effects of using it on the text. Manual cleanup and editing would also be easier with visible formatting characters.
The text was updated successfully, but these errors were encountered: