[Libreoffice-bugs] [Bug 108582] using nvda screen reader activating screen review in libreoffice 5.3 nvda reads dialog boxes and messages of libreoffice like one combine word!

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=108582

V Stuart Foote <vstuart.foote at utsa.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |quentin at nvaccess.org

--- Comment #17 from V Stuart Foote <vstuart.foote at utsa.edu> ---
(In reply to zahra from comment #16)
> 
> but i am sure that i asked this problem in nvda user maling list and someone
> confirms this problem in libreoffice 6.0!
> why invalid?
> its a new bug which introducing harfbuzz made for nvda users!
> it does not depend on my windows, i am sure that i used remote control
> program and tested in the system of one person who has windows ten and
> observed this issue!
> i tested with libreoffice 5.3.0.3 remotely, but on that time, i did not know
> about harfbuzz and how to disable it!
> so, my report is not specific for one windows version and specific version
> of nvda!
> its one of the bugs that introducing harfbuzz made and i did not find any
> solution for resolving this issue except disabling harfbuzz as i mentioned
> that today i learned from your comment!
> why khaled removed the option for disabling harfbuzz in 5.4?
> even if libreoffice 6.0, did not support xp, i never used it, because of not
> possible to read dialogs and messages in screen review!

No, I follow NVDA user and dev ML and of course LibreOffice, and this was not
reproduced that I recall. And as you never provided a WinDbg stack trace or
link to Libreoffice crashreporter dumps for LibreOffice, nor NVDA verbose
logging catching the "crash" it is undocumented and not confirmed.

Invalid because even if it were confirmed--it has not been--it could not be
fixed as *both* software projects have moved on.  NVDA 2017.3 and 2018.1.1 or
next 2018.2 on Windows systems with GPU driver support do not have this issue--
and conflating in the HarfBuzz source is not reasonable.

It is equally likely the issue is with NVDA and the Symphony/IAccessible2
module which has some annoying locale detection language change behavior--that
HarfBuzz handling could have complicated, but with out logging its mute.

Otherwise please be aware that at the 5.4 release with a complete transition to
HarfBuzz based rendering cross platform--the legacy GDI/DirectWrite rendering
on Windows (the so called "Old" layout engine) was completely removed from the
code base. It is gone, and will not be brought back.

Making use of HarfBuzz, Windows builds of 5.4, 6.0 and current master have two
rendering modes--legacy GDI for the "Default" rendering (by CPU or Hardware)
and Direct3D DirectWrite with OpenGL rendering. Moving forward we will be
further reducing the use of legacy GDI handling again moving Direct3D
DirectWrite forward (or possibly implementing FreeType) for text rendering.

Sorry not to be cruel, but that is reality--up to you to move on.

@Quintin, do you have any perspective from the NVAccess side?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20180421/b1ca558b/attachment.html>