Skip to content

Fix superscripts and subscripts reporting for MS Word (legacy).#10979

Merged
feerrenrut merged 3 commits into
nvaccess:masterfrom
CyrilleB79:fixWordLegacySuperscriptSubscript
Apr 14, 2020
Merged

Fix superscripts and subscripts reporting for MS Word (legacy).#10979
feerrenrut merged 3 commits into
nvaccess:masterfrom
CyrilleB79:fixWordLegacySuperscriptSubscript

Conversation

@CyrilleB79

@CyrilleB79 CyrilleB79 commented Apr 10, 2020

Copy link
Copy Markdown
Contributor

Link to issue number:

None

Summary of the issue:

With #10919, superscript and subscript are now reported separately from other attributes. However in MS Word legacy (no UIA), this works only if "Font attributes" is also checked in "Document formatting" setting panel. Checking only "Subscript and superscript" does not work in MS Word legacy support (no UIA).

Description of how this pull request fixes the issue:

This PR separates completely subscript and superscript handling with respect to attributes handling in winword.cpp

Testing performed:

Not yet. I have issue with my build environment on my machine. I will try an another machine when I have access to it or test with the build from appVeyor.
I leave this PR as draft in the meantime.

Planned Now Completed tests on Word (legacy mode) (as per comment ):

  • Type a text such as a1^2 + a2^2 = a^2 containing subscripts and superscripts.
  • Format the "+" and "=" in bold
  • Try the 4 possible following configurations and read the text character by character:
    • attributes off, subscripts/supberscripts off (normal)
    • attributes off, subscripts/supberscripts on
    • attributes on, subscripts/supberscripts off
    • attributes on, subscripts/supberscripts on
      Check that bold and subscripts/superscripts announcements are honored when requested.

Known issues with pull request:

None

Change log entry:

None since #10919 is not yet in a stable release.

@AppVeyorBot

Copy link
Copy Markdown

@AppVeyorBot

Copy link
Copy Markdown

See test results for failed build of commit 11e2f7e966

@CyrilleB79 CyrilleB79 marked this pull request as ready for review April 10, 2020 20:47
@CyrilleB79

Copy link
Copy Markdown
Contributor Author

Compiled and tested successfully commit 045fff0 as described in the Test section of the initial description of this PR.

@CyrilleB79

Copy link
Copy Markdown
Contributor Author

Cc @codeofdusk, @LeonarddeR and @feerrenrut since you have participated or review #10919.

@LeonarddeR LeonarddeR left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, though there are some long lines in this that could possibly be split.

@CyrilleB79

Copy link
Copy Markdown
Contributor Author

@LeonarddeR are you talking about the .cpp file? I agree the code is not well readable in this file with long lines and missing spaces. There is no linting check for .cpp files.
However, my approach was to keep the same formatting as the code around to have something coherent.

@feerrenrut feerrenrut left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @CyrilleB79

@feerrenrut feerrenrut merged commit 72ee0b9 into nvaccess:master Apr 14, 2020
@nvaccessAuto nvaccessAuto added this to the 2020.1 milestone Apr 14, 2020
@feerrenrut feerrenrut modified the milestones: 2020.1, 2020.2 Apr 14, 2020
@CyrilleB79 CyrilleB79 deleted the fixWordLegacySuperscriptSubscript branch July 6, 2020 08:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants