Bug 95681 - Spelling and Grammar dialog does not display subscript and superscript
Summary: Spelling and Grammar dialog does not display subscript and superscript
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
Depends on:
Blocks: Matters-to-Caolan Spell-Checking-Dialog
  Show dependency treegraph
Reported: 2015-11-08 22:08 UTC by jirib
Modified: 2018-02-26 14:41 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

screenshot of Spelling and Grammer dialog (35.04 KB, image/png)
2015-11-08 22:08 UTC, jirib

Note You need to log in before you can comment on or make changes to this bug.
Description jirib 2015-11-08 22:08:34 UTC
Created attachment 120391 [details]
screenshot of Spelling and Grammer dialog

Spelling and Grammer dialog does not display chemical formulas correctly, it confuses users as they could think they have chemical formulas written in the text incorrectly, even it is not so.

See attached screenshot.

- have correctly written chemical formula in the text
- put some typo error in the text so Spelling and Grammer dialog does display
  the line with chemical formula
- check how is chemical formula displayed in Spelling and Grammer dialog preview

Comment 1 Buovjaga 2015-11-12 09:30:45 UTC
I confirm this, but I don't know what kind of revamp it would take to enable this. It might also make it more difficult to view the check, if all styles would be taken into consideration.

I'll swing this by UX.
Comment 2 V Stuart Foote 2015-11-12 13:52:22 UTC
This has merit, and agree that some level of displaying formatting the paragraph text for display in the indicator window would be a reasonable enhancement--without the full on Preview window of the related RFE bug 95685, nor implementing spell check in the Math module for OLE embedded formulas.

The rolling text selection of the spell-check preview does not currently extract style or even font details from the displayed text from the document. So needs a substantial tweak in feeding the dialog.

Imagine this is doable, but would *not* want it to be on by default--adding formatting to the display for every paragraph passing through spell check would be a drag on resources. 

So, would need to be a toggle--either in Tools -> Options -> Language Settings or in Expert Configuration.
Comment 3 jirib 2015-11-12 14:10:48 UTC
I personally would prefer BZ95685 - a preview window.
Comment 4 V Stuart Foote 2015-11-12 15:10:14 UTC
(In reply to jirib from comment #3)
> I personally would prefer BZ95685 - a preview window.

Start coding ;-)

But seriously--this facet can possibly be achieved by parsing limited font and style format details (possibly even fully formatted) in display of the paragraph currently active in the spell check. We've done similar for correctly handling font and preview in the Special Character dialog.

A full page "preview" as in bug 95685 is much more ambitious and requires parsing at least the current page, and applying block highlighting against misspelling, and zooming the preview to the active area. Then reparsing and updating the preview as changes/corrections are made. Would also have decisions about how much of the "preview" to show and where--a pop-out, small window in the dialog panel lots of design and functional issues in pursuing.

Would point out that in your ABBY Finereader example attachment 129397 [details] the verification dialog is showing the OCR result and spell-checking, but the "preview" is the source raster image.  That preview image doesn't change, and the active misspelling box is just advanced through the same image.  Adobe Acrobat does similar. So it is pretty common fare, even fundamental for OCR process. Not so much for spellcheck of original material.

Comment 5 Robinson Tryon (qubit) 2016-08-25 05:39:17 UTC Comment hidden (obsolete)
Comment 6 Heiko Tietze 2018-02-26 11:12:58 UTC
Basic font properties like bold/italic/underline, highlighting, super/subscript etc are not supported yet. If we start with one we have to take all. 

The right solution is something like a callout, a window that points to the error and provides a few functions (same reason as for bug 95685). Right now you can read the formatting from the document.