Re: [NVDA] #4233: Provision of indication options for reporting spelling errors.

[NVDA T. <nor...@nv...>]

#4233: Provision of indication options for reporting spelling errors.
--------------------------------+------------------
        Reporter:  dhankuta     |       Owner:
            Type:  enhancement  |      Status:  new
        Priority:  trivial      |   Milestone:
       Component:  Core         |     Version:
      Resolution:               |    Keywords:
Operating system:  Windows XP   |  Blocked by:
        Blocking:               |
--------------------------------+------------------
Changes document entry (for developers):


--------------------------------+------------------

Comment (by dhankuta):

 Hi,
 Thanks for the quick reply.
 Perhaps my writing may have some slightly  confusing statements.
 I understand the limitation and unusual beep while a normal reading. An
 insertion of a beep inside a text composed by joining  many
 conditional parameters of a field is not possible.
 What I mean was not while reading a line. On reading a line it will be
 either on or off mode. But the just a beep is while navigating  a word
 or character which I think is possible now.
 I think it is useful if the getFormatFieldSpeech function be redefined
 as many unconditional get functions like get style, get pagenumber, get
 color, get
 font, get spellingerrors etc. Based on the config values, we can join
 the returns of these functions as per need of a joint text.  With
 these changes; we can have many features like just knowing a single
 parameters like only the color or style, or a single line etc...
  I have done it in some parameter and using it. My suggestion is to extend
 it.

 Him Prasad Gautam.

--
Ticket URL: <http://community.nvda-project.org/ticket/4233#comment:2>
NVDA Community <http://community.nvda-project.org/>
A free and open-source screen reader for Windows