Date: prev next · Thread: first prev next last
May 2015 Archives by date, by thread · List index


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

            Bug ID: 91739
           Summary: nvda can not read documents from top to bottom.
           Product: LibreOffice
           Version: unspecified
          Hardware: Other
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: medium
         Component: ux-advise
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: nasrinkhaksar3@gmail.com
                CC: libreoffice-ux-advise@lists.freedesktop.org

nvda cant read documents from top to bottom by incert down. 
when we use microsoft office nvda can read entire document when we press incert
down. 
but in libreoffice and open office when we press incert down it reads only many
lines and when we want to continue to read we should press incert down again
and nvda reads only many lines and again and again. its very difficult
specially in large documents and reading bookks. 
and also when we navigate in document word by word using control left and right
to read previous and next word after ending sentences after . when we press
control left and right it reads blank. in this case we should read charactor by
charactor to understand if its realy a blank line or not.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.